From: "Baxter, Jim" <jim_baxter@mentor.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Oliver Neukum <oliver@neukum.org>
Subject: Re: [PATCH V1 1/1] net: cdc_ncm: Fix TX zero padding
Date: Mon, 8 May 2017 13:02:39 +0100 [thread overview]
Message-ID: <e64bb76f-a302-062f-58a5-22fcec3fdb23@mentor.com> (raw)
In-Reply-To: <87shkfbo7r.fsf@miraculix.mork.no>
Bjørn Mork <bjorn@mork.no> writes:
> "Baxter, Jim" <jim_baxter@mentor.com> writes:
>
>>
>> Do I need to submit this to the stable queue myself?
>
> No, davem will handle that.
>
> That is, assuming that you had posted this to netdev in the first
> place... Sorry, I just assumed you did without verifying it when I
> replied. You will have to repost the patch to the appropriate
> recepients. Use
>
> scripts/get_maintainer.pl drivers/net/usb/cdc_ncm.c
>
> for that. Feel free to include my Reviewed-by tag. And if you mark the
> patch for "stable" somewhere outside the commit message, then davem will
> pick that up and add it to his stable queue in patchwork. I don't know
> if there is any officially documented way to do this, but a "stable" tag
> inside the [] brackets in the subject, or a comment below the --- marker,
> usually works fine.
>
> Note that the "Cc: stable..." method isn't used for netdev patches. See
> https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt
>
>
> Bjørn
>
Thank you, I will resend this to netdev.
I had used the command:
scripts/get_maintainer.pl drivers/net/usb/cdc_ncm.c --sections
so only sent it to the lists in the first section "USB CDC ETHERNET DRIVER".
I will remove the --sections in future.
Jim
prev parent reply other threads:[~2017-05-08 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 19:41 [PATCH V1 0/1] " Jim Baxter
2017-05-04 19:41 ` [PATCH V1 1/1] " Jim Baxter
2017-05-04 21:01 ` Bjørn Mork
2017-05-08 10:49 ` Baxter, Jim
2017-05-08 11:08 ` Bjørn Mork
2017-05-08 12:02 ` Baxter, Jim [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=e64bb76f-a302-062f-58a5-22fcec3fdb23@mentor.com \
--to=jim_baxter@mentor.com \
--cc=bjorn@mork.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.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
Powered by JetHome