From: David Miller <davem@davemloft.net>
To: mcarlson@broadcom.com
Cc: greg@kroah.com, netdev@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [PATCH net-2.6/stable] tg3: Restrict phy ioctl access
Date: Wed, 16 Feb 2011 15:11:03 -0800 (PST) [thread overview]
Message-ID: <20110216.151103.189711682.davem@davemloft.net> (raw)
In-Reply-To: <20110216230613.GA11053@mcarlson.broadcom.com>
From: "Matt Carlson" <mcarlson@broadcom.com>
Date: Wed, 16 Feb 2011 15:06:13 -0800
> On Wed, Feb 16, 2011 at 02:39:35PM -0800, Greg KH wrote:
>> On Tue, Feb 15, 2011 at 02:51:10PM -0800, Matt Carlson wrote:
>> > If management firmware is present and the device is down, the firmware
>> > will assume control of the phy. If a phy access were allowed from the
>> > host, it will collide with firmware phy accesses, resulting in
>> > unpredictable behavior. This patch fixes the problem by disallowing phy
>> > accesses during the problematic condition.
>> >
>> > Upstream commit ID f746a3136a61ae535c5d0b49a9418fa21edc61b5
>>
>> There is no such upstream git commit id in Linus's tree. What am I
>> doing wrong here?
>
> The commit is in Dave Miller's net-next-2.6 tree.
>
If it wasn't appropriate for net-2.6, it absolutely it not appropriate
for -stable.
next prev parent reply other threads:[~2011-02-16 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 22:51 [PATCH net-2.6/stable] tg3: Restrict phy ioctl access Matt Carlson
2011-02-16 22:39 ` [stable] " Greg KH
2011-02-16 23:06 ` Matt Carlson
2011-02-16 23:11 ` David Miller [this message]
2011-02-16 23:52 ` Matt Carlson
2011-02-17 0:00 ` Greg KH
2011-02-17 0:11 ` Matt Carlson
2011-02-17 0:10 ` David Miller
2011-02-17 0:39 ` Matt Carlson
2011-02-17 0:56 ` David Miller
2011-02-17 22:11 ` 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=20110216.151103.189711682.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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 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).