From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: linux-next: build warnings after merge of the net tree
Date: Wed, 16 Jun 2010 16:30:48 +1000 [thread overview]
Message-ID: <20100616163048.f72345c7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100615.215212.214211994.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
Hi Dave,
On Tue, 15 Jun 2010 21:52:12 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
>
> I've commited the patch below to deal with this, thanks for the report.
Thanks.
> There's some pre-existing warnings someone will need to deal with at
> some point:
>
> drivers/usb/gadget/rndis.c: whole file: warning: coding style is bolixed
:-)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-16 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 3:38 linux-next: build warnings after merge of the net tree Stephen Rothwell
2010-06-16 4:52 ` David Miller
2010-06-16 6:30 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-31 1:55 Stephen Rothwell
2010-08-31 4:56 ` David Miller
2010-09-01 1:25 ` Stephen Rothwell
2010-09-01 3:57 ` David Miller
2011-08-12 1:53 Stephen Rothwell
2011-08-12 10:01 ` David Miller
2016-05-20 3:33 Stephen Rothwell
2016-05-20 5:57 ` David Miller
2021-11-04 3:48 Stephen Rothwell
2022-04-11 4:36 Stephen Rothwell
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=20100616163048.f72345c7.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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