From: Anshul <anshulusr@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: richard.henderson@linaro.org, ink@jurassic.park.msu.ru,
mattst88@gmail.com, linux-alpha@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixed formatting issues
Date: Mon, 28 Aug 2023 15:52:29 +0530 [thread overview]
Message-ID: <CAPwwkU77=FvjtEFM9gzoMRLdporY8F7y1zXNky1Rj4cL0UpXHQ@mail.gmail.com> (raw)
In-Reply-To: <2023082801-cost-radiance-95fa@gregkh>
> Why are you changing coding style issues in this portion of the kernel?
> Do you have this hardware to test with?
I was exploring the source code and noticed a few discrepancies in the
coding style and followed to run `scripts/checkpatch.pl`.
> Normally coding style cleanups like this are only allowed in the
> drivers/staging/* portion of the kernel. Unless you get approval from
> the maintainer of the subsystem you are changing, I wouldn't work on
> this as it's generally considered bad form.
I was not aware of that. I apologise in case my actions caused any
undue inconveniences, that was never my intention.
> Your name is only 1 word?
Yes, my legal name doesn't have a last name. I could change my From:
or Signed-off-by: lines to have "Anshul A" or add my informal last name
if that aligns better with kernel standards.
I appreciate your feedback and apologise for any problems caused,
Anshul
next prev parent reply other threads:[~2023-08-28 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:18 [PATCH] fixed formatting issues Anshul
2023-08-28 7:28 ` Greg KH
2023-08-28 8:24 ` Anshul
2023-08-28 9:11 ` Greg KH
2023-08-28 10:22 ` Anshul [this message]
2023-08-28 8:06 ` [PATCH] alpha/boot: fixes formatting issues in `main.c` Anshul
2023-08-28 9:12 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPwwkU77=FvjtEFM9gzoMRLdporY8F7y1zXNky1Rj4cL0UpXHQ@mail.gmail.com' \
--to=anshulusr@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).