From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: ben.dooks@codethink.co.uk, linux-kernel@lists.codethink.co.uk,
netdev@vger.kernel.org, linux-sh@vger.kernel.org,
laurent.pinchart+renesas@ideasonboard.com
Subject: Re: [PATCH v5] sh_eth: ensure pm_runtime cannot suspend the device during init
Date: Sat, 29 Mar 2014 15:39:42 -0400 (EDT) [thread overview]
Message-ID: <20140329.153942.127963096052575502.davem@davemloft.net> (raw)
In-Reply-To: <5336D007.1090709@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Sat, 29 Mar 2014 17:52:07 +0400
> Hello.
>
> On 29-03-2014 1:18, David Miller wrote:
>
>>>>> I thought it was against the net next tree, given the number of
>>>>> patches that are currently being applied to the sh_eth driver.
>
>>>> Fair enough, applied to net-next, thanks!
>
>>> It probably makes sense to queue this for the stable kernels as well.
>
>> Sorry, that's not how this works.
>
>> If it's good enough for -stable, meaning that users are activly
>> hitting
>> the problem and it's a serious bug, then it's good enough for 'net'
>> and should have been submitted against 'net'.
>
> I thought that at this point only regression fixes are good for 'net'.
> Although, this can be considered a regression too -- since addition of
> runtime PM support back in 2009.
-stable has more stringent requirements for inclusion than 'net',
therefore it is never valid for something to go -stable which is
not in 'net'.
prev parent reply other threads:[~2014-03-29 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:09 [PATCH v5] sh_eth: ensure pm_runtime cannot suspend the device during init Ben Dooks
2014-03-21 12:14 ` Geert Uytterhoeven
2014-03-21 13:00 ` Laurent Pinchart
2014-03-28 18:26 ` David Miller
2014-03-28 19:25 ` Ben Dooks
2014-03-28 20:00 ` David Miller
2014-03-28 21:10 ` Sergei Shtylyov
2014-03-28 21:18 ` David Miller
2014-03-29 13:52 ` Sergei Shtylyov
2014-03-29 19:39 ` David Miller [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=20140329.153942.127963096052575502.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben.dooks@codethink.co.uk \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).