From: David Miller <davem@davemloft.net>
To: rusty@rustcorp.com.au
Cc: joe@perches.com, linux-kernel@vger.kernel.org,
pawel.moll@arm.com, netdev@vger.kernel.org
Subject: Re: [PATCH 14/15] module_param: make bool parameters really bool (net & drivers/net)
Date: Mon, 19 Dec 2011 16:22:10 -0500 (EST) [thread overview]
Message-ID: <20111219.162210.1739976094495078504.davem@davemloft.net> (raw)
In-Reply-To: <87ehw1nm9r.fsf@rustcorp.com.au>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Mon, 19 Dec 2011 16:19:52 +1030
> On Thu, 15 Dec 2011 23:15:17 -0500 (EST), David Miller <davem@davemloft.net> wrote:
>> From: Rusty Russell <rusty@rustcorp.com.au>
>> Date: Fri, 16 Dec 2011 09:44:31 +1030
>>
>> > Dave, did you want a true/false cleanup too?
>>
>> Please, this kind of stuff rots forever and not using bool properly
>> drives me crazy.
>
> And here's the updated patch:
Neither of your two patches comes close to applying cleanly to net-next,
even when I try to apply it by hand there are rejects and references to
files that don't even exist in net-next any more.
Please respin them.
Thanks!
next prev parent reply other threads:[~2011-12-19 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 3:21 [PATCH 14/15] module_param: make bool parameters really bool (net & drivers/net) Rusty Russell
2011-12-15 3:45 ` Joe Perches
2011-12-15 23:14 ` Rusty Russell
2011-12-16 0:33 ` Joe Perches
2011-12-19 5:38 ` Rusty Russell
2011-12-16 4:15 ` David Miller
2011-12-19 5:49 ` Rusty Russell
2011-12-19 6:42 ` Joe Perches
2011-12-19 21:22 ` David Miller [this message]
2011-12-19 23:54 ` Rusty Russell
2011-12-19 23:56 ` [PATCH 1/2] net: fix assignment of 0/1 to bool variables Rusty Russell
2011-12-20 6:56 ` David Miller
2011-12-20 0:08 ` [PATCH 2/2] module_param: make bool parameters really bool (net & drivers/net) Rusty Russell
2011-12-20 6:56 ` David Miller
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=20111219.162210.1739976094495078504.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).