From: Purva Yeshi <purvayeshi550@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jikos@kernel.org, bentiss@kernel.org, corbet@lwn.net,
jdelvare@suse.com, linux@roeck-us.net, skhan@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] docs: Fix spelling and grammatical issues
Date: Wed, 5 Feb 2025 01:54:11 +0530 [thread overview]
Message-ID: <ec91ca3b-d348-49b4-88b2-a3ce97ce2a2d@gmail.com> (raw)
In-Reply-To: <2025020411-ravine-stand-530a@gregkh>
On 04/02/25 19:37, Greg KH wrote:
> On Tue, Feb 04, 2025 at 07:18:06PM +0530, Purva Yeshi wrote:
>> Fix several spelling and grammatical errors across multiple
>> documentation files.
>>
>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>
> Hi,
>
> This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
> a patch that has triggered this response. He used to manually respond
> to these common problems, but in order to save his sanity (he kept
> writing the same thing over and over, yet to different people), I was
> created. Hopefully you will not take offence and will fix the problem
> in your patch and resubmit it so that it can be accepted into the Linux
> kernel tree.
>
> You are receiving this message because of the following common error(s)
> as indicated below:
>
> - Your patch did many different things all at once, making it difficult
> to review. All Linux kernel patches need to only do one thing at a
> time. If you need to do multiple things (such as clean up all coding
> style issues in a file/driver), do it in a sequence of patches, each
> one doing only one thing. This will make it easier to review the
> patches to ensure that they are correct, and to help alleviate any
> merge issues that larger patches can cause.
>
>
> If you wish to discuss this problem further, or you have questions about
> how to resolve this issue, please feel free to respond to this email and
> Greg will reply once he has dug out from the pending patches received
> from other developers.
>
> thanks,
>
> greg k-h's patch email bot
I understand and will split my patch into smaller, logically grouped
changes to make the review process easier. I will resend the patches
accordingly.
next prev parent reply other threads:[~2025-02-04 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:48 [PATCH] docs: Fix spelling and grammatical issues Purva Yeshi
2025-02-04 14:07 ` Greg KH
2025-02-04 20:24 ` Purva Yeshi [this message]
2025-02-04 14:39 ` Guenter Roeck
2025-02-04 15:17 ` Jonathan Corbet
2025-02-04 20:32 ` Purva Yeshi
2025-02-04 20:27 ` Purva Yeshi
2025-02-04 18:11 ` Randy Dunlap
2025-02-04 20:40 ` Purva Yeshi
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=ec91ca3b-d348-49b4-88b2-a3ce97ce2a2d@gmail.com \
--to=purvayeshi550@gmail.com \
--cc=bentiss@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=jikos@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=skhan@linuxfoundation.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 NNTP newsgroup(s).