From: Greg KH <gregkh@linuxfoundation.org>
To: Nishka Dasgupta <nishkadg.linux@gmail.com>
Cc: devel@driverdev.osuosl.org, benniciemanuel78@gmail.com,
linux-kernel@vger.kernel.org, hardiksingh.k@gmail.com
Subject: Re: [PATCH] staging: rtl8723bs: core: rtw_mlme_ext.c: Remove unused variables
Date: Mon, 10 Jun 2019 09:25:21 +0200 [thread overview]
Message-ID: <20190610072521.GA20470@kroah.com> (raw)
In-Reply-To: <7554e171-360f-f0a8-5742-9a60e4a1cc2d@gmail.com>
On Mon, Jun 10, 2019 at 12:44:05PM +0530, Nishka Dasgupta wrote:
> On 10/06/19 11:19 AM, Greg KH wrote:
> > On Mon, Jun 10, 2019 at 10:08:21AM +0530, Nishka Dasgupta wrote:
> > > On 09/06/19 4:32 PM, Greg KH wrote:
> > > > On Fri, Jun 07, 2019 at 12:41:23PM +0530, Nishka Dasgupta wrote:
> > > > > Remove variables that are declared and assigned values but not otherwise
> > > > > used.
> > > > > Issue found with Coccinelle.
> > > > >
> > > > > Signed-off-by: Nishka Dasgupta <nishkadg.linux@gmail.com>
> > > > > ---
> > > > > drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 9 ---------
> > > > > 1 file changed, 9 deletions(-)
> > > >
> > > > You sent me 8 patches for this driver, yet only 2 were ordered in a
> > > > series. I have no idea what order to apply these in :(
> > > >
> > > > Please resend them _all_ in a numbered patch series so I have a chance
> > > > to get this correct.
> > >
> > > Yes, I can do that. Who do I send the patch series to in that case? The
> > > maintainers list is slightly different for each file, and most of the
> > > patches in this driver are for different and unrelated files (except, I
> > > think, the two that I did send as a patch series). Do I combine the
> > > maintainers lists and send the entire patch series to everyone listed as a
> > > maintainer for any one of the patches in it?
> >
> > The maintainer and mailing list is the same for all of the files in a
> > single driver. If not, then something is wrong.
>
> I'm using get_maintainers.pl with no arguments, and for rtl8723bs, I am
> getting a lot of different mailing lists.
> E.g
> For core/rtw_ieee80211.c, I'm getting the following list:
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Michael Straube <straube.linux@gmail.com>
> Andy Shevchenko <andy.shevchenko@gmail.com>
> Hardik Singh Rathore <hardiksingh.k@gmail.com>
> Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
> Nishka Dasgupta <nishkadg.linux@gmail.com>
> devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
> linux-kernel@vger.kernel.org (open list)
>
> Which is not the same as for core/rtw_mlme_ext.c (the current patch).
>
> > And yes, you can combine the list of people if you wish but be sure you
> > are not just randomly including people who happened to touch the driver
> > "last".
>
> Okay, I'll combine then. But is there any metric I should be using to filter
> the output of get_maintainer.pl? Currently I'm running it with no arguments
> and just adding everyone.
Look at the "role" that each person has. Here is the output of
get_maintainer.pl when I run it on the first file above:
$ ./scripts/get_maintainer.pl --file drivers/staging/rtl8723bs/core/rtw_ieee80211.c
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM,commit_signer:16/16=100%)
Michael Straube <straube.linux@gmail.com> (commit_signer:14/16=88%,authored:14/16=88%,added_lines:43/59=73%,removed_lines:114/130=88%)
Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com> (commit_signer:1/16=6%,authored:1/16=6%,added_lines:3/59=5%)
Hardik Singh Rathore <hardiksingh.k@gmail.com> (commit_signer:1/16=6%,authored:1/16=6%,added_lines:13/59=22%,removed_lines:13/130=10%)
Andy Shevchenko <andy.shevchenko@gmail.com> (commit_signer:1/16=6%)
devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
That shows that "Greg Kroah-Hartman" is a reviewer for this subsystem,
Michael and Payal and Hardik and Andy have all submitted patches
"recently", and then devel@ is the mailing list for the patches to be
sent to.
So, just include the maintainer and the mailing list and you will be
fine. No need to bother lkml with staging patches, nor the people who
last sent cleanup patches.
hope this helps,
greg k-h
next prev parent reply other threads:[~2019-06-10 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 7:11 [PATCH] staging: rtl8723bs: core: rtw_mlme_ext.c: Remove unused variables Nishka Dasgupta
2019-06-09 11:02 ` Greg KH
2019-06-10 4:38 ` Nishka Dasgupta
2019-06-10 5:49 ` Greg KH
2019-06-10 7:14 ` Nishka Dasgupta
2019-06-10 7:25 ` Greg KH [this message]
2019-06-10 7:33 ` Nishka Dasgupta
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=20190610072521.GA20470@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benniciemanuel78@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=hardiksingh.k@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nishkadg.linux@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.