From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Jeff Garzik'" <jeff@garzik.org>,
"'David Miller'" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: RE: Fixed PHY regression
Date: Tue, 9 Oct 2007 07:46:59 +0200 [thread overview]
Message-ID: <00ab01c80a37$cfb19560$04ac10ac@Jocke> (raw)
In-Reply-To: <470AC3B2.7090802@garzik.org>
> -----Original Message-----
> From: Jeff Garzik [mailto:jeff@garzik.org]
> Sent: den 9 oktober 2007 01:57
> To: David Miller
> Cc: joakim.tjernlund@transmode.se; netdev@vger.kernel.org
> Subject: Re: Fixed PHY regression
>
> David Miller wrote:
> > From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
> > Date: Mon, 8 Oct 2007 20:17:33 +0200
> >
> >> David, any chance the second item, Oops while modprobing
> phy fixed module, in
> >> http://marc.info/?l=linux-kernel&m=119178673421891&w=2
> >> will make it into 2.6.23?
> >>
> >> The fix is now in your tree,
> >>
> http://git.kernel.org/?p=linux/kernel/git/davem/bak-net-2.6.24
.git;a=commit;h=bbb4c0c35a4c2aed5e025b668c8dfc99c5b74cff
> >>
> >> It has been in Andrews tree for a while, then in Garzik
> and now it is in your tree.
> >
> > Jeff, any reason you didn't submit this one for 2.6.23?
>
> Two reasons:
> * despite the subject, after discussion it looked like a problem with
> module release, making "build it into your kernel" a valid workaround
I don't use modules and this does not work for me. Basically
Fixed PHY is broken for me.
Jocke
> * the fix was quite invasive this late in the game
>
> If people still think it should go for 2.6.23, that's cool with me.
>
> Jeff
>
>
>
>
>
prev parent reply other threads:[~2007-10-09 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 18:17 Fixed PHY regression Joakim Tjernlund
2007-10-08 21:20 ` David Miller
2007-10-08 23:56 ` Jeff Garzik
2007-10-09 5:46 ` Joakim Tjernlund [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='00ab01c80a37$cfb19560$04ac10ac@Jocke' \
--to=joakim.tjernlund@transmode.se \
--cc=davem@davemloft.net \
--cc=jeff@garzik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox