* linux-next: manual merge of the wireless tree with the net-current tree
@ 2009-07-08 2:40 Stephen Rothwell
2009-07-08 14:04 ` John W. Linville
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2009-07-08 2:40 UTC (permalink / raw)
To: John W. Linville; +Cc: linux-next, linux-kernel, David S. Miller
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Hi John,
Today's linux-next merge of the wireless tree got a conflict in
drivers/net/wireless/p54/p54common.c between commit
0ca1b08eba627b4245efd0f71b55a062bf163777 ("Revert "p54: Use SKB list
handling helpers instead of by-hand code."") from the net-current tree
and commit 373234a7c69600397aea39c1452806736df2dfc5 ("p54: Modify p54
files for new organization") from the wireless tree.
For today, I just ignored the net-current change. This will need fixing.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the wireless tree with the net-current tree
2009-07-08 2:40 linux-next: manual merge of the wireless tree with the net-current tree Stephen Rothwell
@ 2009-07-08 14:04 ` John W. Linville
2009-07-08 23:42 ` Stephen Rothwell
0 siblings, 1 reply; 3+ messages in thread
From: John W. Linville @ 2009-07-08 14:04 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, David S. Miller
On Wed, Jul 08, 2009 at 12:40:05PM +1000, Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next merge of the wireless tree got a conflict in
> drivers/net/wireless/p54/p54common.c between commit
> 0ca1b08eba627b4245efd0f71b55a062bf163777 ("Revert "p54: Use SKB list
> handling helpers instead of by-hand code."") from the net-current tree
> and commit 373234a7c69600397aea39c1452806736df2dfc5 ("p54: Modify p54
> files for new organization") from the wireless tree.
>
> For today, I just ignored the net-current change. This will need fixing.
There is some code reorganization happening in wireless-next-2.6,
resulting in a couple of files getting deleted. I'm guessing that
if/when Dave pulls net-2.6 into net-next-2.6 (which wireless-next-2.6
gets rebased upon) then this should resolve itself.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the wireless tree with the net-current tree
2009-07-08 14:04 ` John W. Linville
@ 2009-07-08 23:42 ` Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2009-07-08 23:42 UTC (permalink / raw)
To: John W. Linville; +Cc: linux-next, linux-kernel, David S. Miller
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Hi John,
On Wed, 8 Jul 2009 10:04:25 -0400 "John W. Linville" <linville@tuxdriver.com> wrote:
>
> There is some code reorganization happening in wireless-next-2.6,
> resulting in a couple of files getting deleted. I'm guessing that
> if/when Dave pulls net-2.6 into net-next-2.6 (which wireless-next-2.6
> gets rebased upon) then this should resolve itself.
Indeed, that is why I ignored the problem for now. I was just flagging
that the issue will need to be resolved at some point. (Although I am
assuming that ignoring the fix in net-current does not produce too much
bad fallout right now.)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-07-08 23:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-08 2:40 linux-next: manual merge of the wireless tree with the net-current tree Stephen Rothwell
2009-07-08 14:04 ` John W. Linville
2009-07-08 23:42 ` Stephen Rothwell
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.