From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>, ben.dooks@codethink.co.uk
Cc: 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: Fri, 28 Mar 2014 20:10:29 +0000 [thread overview]
Message-ID: <5335E53C.6020208@cogentembedded.com> (raw)
In-Reply-To: <20140328.160024.136488246522581222.davem@davemloft.net>
Hello.
On 03/28/2014 11:00 PM, 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.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>, ben.dooks@codethink.co.uk
Cc: 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 00:10:20 +0300 [thread overview]
Message-ID: <5335E53C.6020208@cogentembedded.com> (raw)
In-Reply-To: <20140328.160024.136488246522581222.davem@davemloft.net>
Hello.
On 03/28/2014 11:00 PM, 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.
WBR, Sergei
next prev parent reply other threads:[~2014-03-28 20:10 UTC|newest]
Thread overview: 19+ 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 11:09 ` Ben Dooks
2014-03-21 12:14 ` Geert Uytterhoeven
2014-03-21 12:14 ` Geert Uytterhoeven
2014-03-21 12:59 ` Laurent Pinchart
2014-03-21 13:00 ` Laurent Pinchart
2014-03-28 18:26 ` David Miller
2014-03-28 18:26 ` David Miller
2014-03-28 19:25 ` Ben Dooks
2014-03-28 20:00 ` David Miller
2014-03-28 20:00 ` David Miller
2014-03-28 20:10 ` Sergei Shtylyov [this message]
2014-03-28 21:10 ` Sergei Shtylyov
2014-03-28 21:18 ` David Miller
2014-03-28 21:18 ` David Miller
2014-03-29 13:52 ` Sergei Shtylyov
2014-03-29 13:52 ` Sergei Shtylyov
2014-03-29 19:39 ` David Miller
2014-03-29 19:39 ` David Miller
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=5335E53C.6020208@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.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 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.