From: Greg KH <gregkh@linuxfoundation.org>
To: Shreeya Patel <shreeya.patel23498@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Remove checkpatch warnings
Date: Wed, 17 Jan 2018 14:58:08 +0100 [thread overview]
Message-ID: <20180117135808.GA5262@kroah.com> (raw)
In-Reply-To: <cover.1516127876.git.shreeya.patel23498@gmail.com>
On Wed, Jan 17, 2018 at 12:24:50AM +0530, Shreeya Patel wrote:
> This patchset removes some warnings generated by checkpatch
> for cleanup of the rtl8723bs driver. Also some additional
> cleanups are introduced in the *[1/4] and *[3/4] patches
> to make the code according to the kernel coding style.
>
> Changes in v2
> -Rebase and resend the patches [2/4], [3/4] and [4/4].
That's horrid, I now think I'm missing patch 1 of the series, how am I
supposed to know that?
Just renumber them when you resend if you drop a patch.
Also, why cc: linux-usb, it doesn't care about staging drivers...
Please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-17 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 18:54 [PATCH v2 0/4] Remove checkpatch warnings Shreeya Patel
2018-01-17 13:58 ` Greg KH [this message]
2018-01-17 15:36 ` Shreeya Patel
2018-01-17 16:00 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-01-16 18:57 [v2,2/4] Staging: rtl8723bs: Change names to conform to the kernel code Shreeya Patel
2018-01-16 19:01 ` [PATCH v2 2/4] " Shreeya Patel
2018-01-16 19:03 [v2,3/4] Staging: rtl8723bs: Change condition to assignment Shreeya Patel
2018-01-16 19:03 ` [PATCH v2 3/4] " Shreeya Patel
2018-01-16 19:05 [v2,4/4] Staging: rtl8723bs: Use !x instead of NULL comparison Shreeya Patel
2018-01-16 19:05 ` [PATCH v2 4/4] " Shreeya Patel
2018-01-17 9:51 [v2,3/4] Staging: rtl8723bs: Change condition to assignment Dan Carpenter
2018-01-17 9:51 ` [PATCH v2 3/4] " Dan Carpenter
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=20180117135808.GA5262@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shreeya.patel23498@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.