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: Adrian Bunk <bunk@kernel•org>,
	linux-next@vger•kernel.org, David Miller <davem@davemloft•net>,
	LKML <linux-kernel@vger•kernel.org>,
	"Luis R. Rodriguez" <lrodriguez@atheros•com>
Subject: Re: linux-next: wireless-current tree build failure
Date: Wed, 6 Aug 2008 02:35:52 +1000	[thread overview]
Message-ID: <20080806023552.604deebe.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080805160026.GA14186@tuxdriver.com>

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

Hi John,

On Tue, 5 Aug 2008 12:00:26 -0400 "John W. Linville" <linville@tuxdriver•com> wrote:
>
> I imagine that we would be happy to do that.  Anyone have a clue as to how?

I think that "not yet" is the answer :-(

If we don't get a useful answer soon, we may just have to merge the
driver with appropriately commented negative "depends on" in Kconfig for
the arches it breaks.

-- 
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:[~2008-08-05 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05  6:21 linux-next: wireless-current tree build failure Stephen Rothwell
2008-08-05 15:37 ` Adrian Bunk
2008-08-05 16:00   ` John W. Linville
2008-08-05 16:35     ` Stephen Rothwell [this message]
2008-08-05 19:06     ` [2.6 patch] ath9k: work around gcc ICEs Adrian Bunk
2008-08-05 16:02   ` linux-next: wireless-current tree build failure Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-04-22  5:19 Stephen Rothwell
2009-04-22 13:03 ` John W. Linville
2009-04-22 18:08   ` reinette chatre

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=20080806023552.604deebe.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=bunk@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linville@tuxdriver$(echo .)com \
    --cc=lrodriguez@atheros$(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