| To: | Andrew Morton <akpm@xxxxxxxx> |
|---|---|
| Subject: | Re: [rft/update] r8169 changes in 2.6.x |
| From: | Francois Romieu <romieu@xxxxxxxxxxxxx> |
| Date: | Wed, 23 Feb 2005 09:59:21 +0100 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, jdmason@xxxxxxxxxx, rich@xxxxxxxxxxxxxxxxxxxx, jgarzik@xxxxxxxxx |
| In-reply-to: | <20050222172935.30e43270.akpm@xxxxxxxx> |
| References: | <20050222234810.GA17303@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20050222172935.30e43270.akpm@xxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
Andrew Morton <akpm@xxxxxxxx> :
> There are already a bunch of r8169 patches in Jeff's tree. The combination
> isn't pretty:
[removed by parental advisory]
I sent r8169-4{0/1/2/3/4}0 on netdev + Jeff the 22/02/2005. Jeff's netdev
(thus your tree) already had the r8169-3xx changes.
Jeff has acked r8169-4{0/1/2/3}0 on 23/02/2005. r8169-440 (PCI-ID) won't
be applied (there should be no functionnal change nor merge side-effect).
r8169-4{5/6}0 have been published only here (so far).
So you can:
- apply r8169-4{0/1/2/3/5/6}0 if you have not updated to Jeff -netdev beyond
what is currently available through plain old patch
- apply r8169-4{5/6}0 if you are bk-synced with Jeff -netdev (assuming that
Jeff acked after he actually pushed to its bk repo)
- do something else until I verify the above and generate a dedicated
patchsets for your tree.
--
Ueimor
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [patch 2.6.11-rc4-netdev1 5/5] r8169: literate PCI ID, Francois Romieu |
|---|---|
| Next by Date: | Re: [rft/update] r8169 changes in 2.6.x, Andrew Morton |
| Previous by Thread: | Re: [rft/update] r8169 changes in 2.6.x, Jeff Garzik |
| Next by Thread: | Re: [rft/update] r8169 changes in 2.6.x, Andrew Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |