From: Johannes Berg <johannes@sipsolutions•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: wireless tree build warnings
Date: Thu, 31 Dec 2009 14:19:25 +0100 [thread overview]
Message-ID: <1262265565.3592.0.camel@johannes.local> (raw)
In-Reply-To: <20091231105709.c50f22c0.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
On Thu, 2009-12-31 at 10:57 +1100, Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next build (i386 defconfig) produced thes warnings:
Yeah I didn't notice because it was 64-bit here, Kalle already send a
fix.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-12-31 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 23:57 linux-next: wireless tree build warnings Stephen Rothwell
2009-12-31 0:56 ` René Bolldorf
2009-12-31 2:00 ` Stephen Rothwell
2009-12-31 13:19 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-10 9:41 Stephen Rothwell
2009-08-10 17:29 ` Luciano Coelho
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=1262265565.3592.0.camel@johannes.local \
--to=johannes@sipsolutions$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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