public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: John Whitmore <arigead@gmail.com>
Cc: kstewart@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	John Whitmore <johnfwhitmore@gmail.com>,
	pombredanne@nexb.com, colin.king@canonical.com
Subject: Re: [PATCH v5 8/8] staging: rtl8192e: remove unnecessary parentheses - Coding Style
Date: Wed, 6 Jun 2018 12:49:28 +0200	[thread overview]
Message-ID: <20180606104928.GA4992@kroah.com> (raw)
In-Reply-To: <20180606102512.lvepwliyqd6pkbgj@xux707>

On Wed, Jun 06, 2018 at 11:25:14AM +0100, John Whitmore wrote:
> On Sun, Jun 03, 2018 at 02:28:35PM +0200, Greg KH wrote:
> > On Sun, Jun 03, 2018 at 01:04:13PM +0100, John Whitmore wrote:
> > > Signed-off-by: John Whitmore <johnfwhitmore@gmail.com>
> > > ---
> > >  drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c | 12 ++++++------
> > >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> > I can not take patches without any changelog text at all :(
> 
> Sorry I created a one line commit message, which became the subject of the
> patch email. I couldn't think of anything more to add for a second line. My
> mistake. I did an ammend of that, as it was the last commit, to add a second
> line.
> 
> Now I'm probably going to get this next bit wrong. Can I simply bump the
> version of patch 8/8 to v6 and resend that single patch file, or bump all 8
> patches to v6 and resend all of them? I'll bump the last patch file and attach
> it to this email, hope for the best.

I can't take attachments, sorry.

Try resending the whole series, as a new version (v6), and all should be
fine.

Note that I can't do anything with patches until the merge window
closes, in 2 weeks, so don't expect a response until then.

thanks,

greg k-h

      reply	other threads:[~2018-06-06 10:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 12:04 staging: rtl8192e: Series of coding style changes John Whitmore
2018-06-03 12:04 ` [PATCH v5 1/8] staging: rtl8192e: Add and remove blank lines - Coding style John Whitmore
2018-06-03 12:04 ` [PATCH v5 2/8] staging: rtl8192e: Addition of prefered spacing " John Whitmore
2018-06-03 12:04 ` [PATCH v5 3/8] staging: rtl8192e: Remove unnecessary return statements " John Whitmore
2018-06-03 12:04 ` [PATCH v5 4/8] staging: rtl8192e: Correct alignment of if statements - Coding Style John Whitmore
2018-06-03 12:04 ` [PATCH v5 5/8] staging: rtl8192e: Remove unrequired space at start of line " John Whitmore
2018-06-03 12:04 ` [PATCH v5 6/8] staging: rtl8192e: Correct declaration of HTResetIOTSetting " John Whitmore
2018-06-03 12:04 ` [PATCH v5 7/8] staging: rtl8192e: Optimise Comparison to NULL tests " John Whitmore
2018-06-03 12:04 ` [PATCH v5 8/8] staging: rtl8192e: remove unnecessary parentheses " John Whitmore
2018-06-03 12:28   ` Greg KH
2018-06-06 10:25     ` John Whitmore
2018-06-06 10:49       ` Greg KH [this message]

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=20180606104928.GA4992@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arigead@gmail.com \
    --cc=colin.king@canonical.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=johnfwhitmore@gmail.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pombredanne@nexb.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