public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "John W. Linville" <linville@tuxdriver•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	"David S. Miller" <davem@davemloft•net>
Subject: Re: linux-next: manual merge of the wireless tree with the net-current tree
Date: Thu, 9 Jul 2009 09:42:33 +1000	[thread overview]
Message-ID: <20090709094233.77232ec3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090708140425.GE4253@tuxdriver.com>

[-- 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 --]

      reply	other threads:[~2009-07-08 23:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=20090709094233.77232ec3.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linville@tuxdriver$(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