From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Johnny Kim <johnny.kim@atmel•com>,
Guenter Roeck <linux@roeck-us•net>, Arnd Bergmann <arnd@arndb•de>
Subject: Re: linux-next: build warnings after merge of the staging tree
Date: Sat, 20 Jun 2015 20:48:26 +1000 [thread overview]
Message-ID: <20150620204826.010cd35a@canb.auug.org.au> (raw)
In-Reply-To: <20150601185012.093db327@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
Hi Greg,
On Mon, 1 Jun 2015 18:50:12 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> On Fri, 29 May 2015 20:40:02 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > After merging the staging tree, today's linux-next build (x86_64
> > allmodconfig) produced a large number of warnings in
> > drivers/staging/wilc1000.
>
> Since there are so many warnings, I have disabled the driver for now.
I tried building this with the driver enabled but it still produces and
inordinate number of warnings, so I have disabled it again. Please
either get them sorted out or disable this driver before asking Linus
to merge it.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-20 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 10:40 linux-next: build warnings after merge of the staging tree Stephen Rothwell
2015-06-01 8:50 ` Stephen Rothwell
2015-06-20 10:48 ` Stephen Rothwell [this message]
2015-06-20 14:50 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2019-02-05 3:22 Stephen Rothwell
2019-02-05 10:24 ` Jonathan Cameron
2018-05-14 4:34 Stephen Rothwell
2018-05-14 9:26 ` Greg KH
2017-11-02 4:38 Stephen Rothwell
2017-07-31 5:02 Stephen Rothwell
2017-08-09 1:25 ` Stephen Rothwell
2017-08-22 1:49 ` Stephen Rothwell
2017-08-17 17:57 ` Greg KH
2017-08-18 12:02 ` JB Van Puyvelde
2015-05-06 4:10 Stephen Rothwell
2015-05-06 6:56 ` Julia Lawall
2012-01-31 3:25 Stephen Rothwell
2012-01-31 5:14 ` Greg KH
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=20150620204826.010cd35a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=greg@kroah$(echo .)com \
--cc=johnny.kim@atmel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
/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