From: Milton Miller <miltonm@bga•com>
To: "Kok, Auke" <auke-jan.h.kok@intel•com>
Cc: Jeff Garzik <jeff@garzik•org>, Jeff Garzik <jgarzik@pobox•com>,
e1000-devel@lists•sourceforge.net,
David Acker <dacker@roinet•com>,
netdev@vger•kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel•com>,
Jeff Kirsher <jeffrey.t.kirsher@intel•com>,
Scott Feldman <sfeldma@pobox•com>,
John Ronciak <john.ronciak@intel•com>
Subject: Re: [PATCH] fix e100 rx path on ARM (was [PATCH] e100 rx: or s and el bits)
Date: Tue, 5 Jun 2007 12:56:27 -0500 [thread overview]
Message-ID: <4112397f218a0744ebf8656c81acf850@bga.com> (raw)
In-Reply-To: <4665A0B6.6020902@intel.com>
On Jun 5, 2007, at 12:43 PM, Kok, Auke wrote:
> Jeff Garzik wrote:
>> On Tue, Jun 05, 2007 at 10:27:19AM -0700, Kok, Auke wrote:
>>> We need to make sure that now that we're getting closer to 2.6.22 we
>>> don't end up killing e100 in it. Should we drop the current fixes in
>>> it to be on the safe side and aim for 2.6.23? I would hate to see an
>>> untested codepath breaking e100 on something like ppc or mips...
>>> that will be very painful
>> I certainly agree with this assessment...
>> I've been wondering if, based on all this recent work, we should
>> revert
>> the s-bit stuff and wait for 2.6.23.
>
> Yes, that's my point. If Milton and David agree I think we should do
> so immediately.
We definitely need something other than what is in now.
> If so, do you want me to write a revert-patch or do you have some
> magic to do that for me?
>
The simple git revert won't work because there have been other changes
(ioread for instance) that conflict.
milton
next prev parent reply other threads:[~2007-06-05 17:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 11:24 [PATCH] e100 rx: or s and el bits Milton Miller
2007-05-01 15:01 ` David Acker
2007-05-02 20:21 ` David Acker
2007-05-04 21:43 ` David Acker
2007-05-06 6:36 ` Milton Miller
2007-05-07 15:27 ` David Acker
2007-05-14 18:26 ` [PATCH] fix e100 rx path on ARM (was [PATCH] e100 rx: or s and el bits) David Acker
2007-05-18 1:54 ` Jeff Garzik
2007-05-18 3:47 ` Kok, Auke
2007-05-18 14:07 ` David Acker
2007-05-18 14:20 ` David Acker
2007-05-18 15:29 ` Kok, Auke
2007-05-18 15:47 ` David Acker
2007-05-18 15:59 ` Kok, Auke
2007-05-18 17:11 ` David Acker
2007-05-18 17:47 ` Kok, Auke
2007-05-21 17:35 ` Milton Miller
2007-05-21 17:45 ` Kok, Auke
2007-05-22 16:51 ` Milton Miller
2007-05-22 22:07 ` David Acker
2007-05-23 14:02 ` Milton Miller
2007-05-23 21:32 ` David Acker
2007-05-24 5:26 ` Milton Miller
2007-05-24 11:21 ` Milton Miller
2007-05-24 12:51 ` David Acker
2007-05-24 14:25 ` Milton Miller
2007-05-29 15:58 ` David Acker
2007-05-30 8:26 ` Milton Miller
2007-06-01 20:45 ` David Acker
2007-06-01 21:13 ` Jeff Garzik
2007-06-01 22:13 ` Kok, Auke
2007-06-04 9:03 ` Milton Miller
2007-06-05 13:34 ` David Acker
2007-06-05 16:14 ` Milton Miller
2007-08-27 17:34 ` Kok, Auke
2007-08-27 18:32 ` David Acker
2007-06-05 16:14 ` Milton Miller
2007-06-05 17:27 ` Kok, Auke
2007-06-05 17:39 ` Jeff Garzik
2007-06-05 17:42 ` David Acker
2007-06-05 17:43 ` Kok, Auke
2007-06-05 17:56 ` Milton Miller [this message]
2007-06-05 23:33 ` Kok, Auke
2007-06-05 23:44 ` Jeff Garzik
2007-06-06 2:26 ` Kok, Auke
2007-06-06 9:28 ` Milton Miller
2007-06-11 15:58 ` Milton Miller
2007-06-15 14:39 ` Jeff Garzik
2007-05-24 12:44 ` David Acker
2007-05-24 4:13 ` Milton Miller
2007-05-01 15:21 ` [PATCH] e100 rx: or s and el bits Kok, Auke
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=4112397f218a0744ebf8656c81acf850@bga.com \
--to=miltonm@bga$(echo .)com \
--cc=auke-jan.h.kok@intel$(echo .)com \
--cc=dacker@roinet$(echo .)com \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=jeff@garzik$(echo .)org \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=jgarzik@pobox$(echo .)com \
--cc=john.ronciak@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfeldma@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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