From: David Miller <davem@davemloft.net>
To: stefan@osg.samsung.com
Cc: s.schmidt@samsung.com, linux-wpan@vger.kernel.org,
alex.aring@gmail.com, netdev@vger.kernel.org
Subject: Re: pull-request: ieee802154 2018-05-08
Date: Tue, 08 May 2018 20:06:38 -0400 (EDT) [thread overview]
Message-ID: <20180508.200638.1908252284342544792.davem@davemloft.net> (raw)
In-Reply-To: <a61fa7c3-fa57-535c-7f00-b495d0a46bb0@osg.samsung.com>
From: Stefan Schmidt <stefan@osg.samsung.com>
Date: Tue, 8 May 2018 21:55:37 +0200
> On 05/08/2018 04:18 PM, David Miller wrote:
>> Please submit the -stable fix directly, you can feel free to CC: me.
>
> Will do when the patch hits Linus git tree.
>
> I have a quick question on the process here. From the netdev-faq document
> I was under the impression all stable patches under net/ and drivers/net
> should be brought up to you and would be handled by you.
>
> Does this apply to the core part of net (I fully understand that ieee802154
> is rather a niche) or is there some other reason for this exception?
>
> Both processes (the normal stable one as well as the slightly different one
> for net/) would be fine to go with for me. Just need to know which one I
> should use for future stable patches. :-)
>
> regards
> Stefan Schmidt
Generally wireless and ipsec have been submitting them directly,
sometimes the Intel ethernet guys do too.
Sometimes this makes things easier for me, and I'll ask you to submit
things directly when that is the case like right now.
Thank you.
next prev parent reply other threads:[~2018-05-09 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 8:29 pull-request: ieee802154 2018-05-08 Stefan Schmidt
2018-05-08 14:18 ` David Miller
2018-05-08 19:55 ` Stefan Schmidt
2018-05-09 0:06 ` David Miller [this message]
2018-05-09 7:31 ` Stefan Schmidt
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=20180508.200638.1908252284342544792.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.schmidt@samsung.com \
--cc=stefan@osg.samsung.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