From: Greg KH <gregkh@linuxfoundation.org>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH v2 0/2] some checkpatch fixes in the file rxtx.c
Date: Tue, 1 Nov 2022 19:21:44 +0100 [thread overview]
Message-ID: <Y2FjuHeVzY5VYG97@kroah.com> (raw)
In-Reply-To: <cover.1667305446.git.tanjubrunostar0@gmail.com>
On Tue, Nov 01, 2022 at 12:37:58PM +0000, Tanjuate Brunostar wrote:
> These fixes are focused on the function s_vFillRTSHead
>
> v2: changed confusing changelog messages
>
> Tanjuate Brunostar (2):
> change the function name s_vFillRTSHead
> Join some lines of code to avoid code lines ending in (
>
> drivers/staging/vt6655/rxtx.c | 48 ++++++++++++++++-------------------
> 1 file changed, 22 insertions(+), 26 deletions(-)
Please look at your subject lines you are using here, and look at the
mailing list for previous patch submissions, and at the git log for this
file, and fix them up to have the proper prefixes on them.
As is, I can't take these.
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-01 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 12:37 [PATCH v2 0/2] some checkpatch fixes in the file rxtx.c Tanjuate Brunostar
2022-11-01 12:37 ` [PATCH v2 1/2] change the function name s_vFillRTSHead Tanjuate Brunostar
2022-11-01 13:32 ` Joe Perches
2022-11-01 14:55 ` Tanju Brunostar
2022-11-01 12:38 ` [PATCH v2 2/2] Join some lines of code to avoid code lines ending in ( Tanjuate Brunostar
2022-11-01 18:21 ` Greg KH [this message]
2022-11-01 18:34 ` [PATCH v2 0/2] some checkpatch fixes in the file rxtx.c Tanju Brunostar
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=Y2FjuHeVzY5VYG97@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tanjubrunostar0@gmail.com \
/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