From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] net, thunderx: Use bool in structs where possible
Date: Thu, 18 Feb 2016 15:06:31 -0500 (EST) [thread overview]
Message-ID: <20160218.150631.574392083739567663.davem@davemloft.net> (raw)
In-Reply-To: <20160218164217.GP24726@rric.localdomain>
From: Robert Richter <robert.richter@caviumnetworks.com>
Date: Thu, 18 Feb 2016 17:42:17 +0100
> On 18.02.16 11:05:14, David Miller wrote:
>> From: Robert Richter <rrichter@caviumnetworks.com>
>> Date: Thu, 18 Feb 2016 13:39:09 +0100
>>
>> > From: Robert Richter <rrichter@cavium.com>
>> >
>> > Looks like the :1 notation was accidentally introduced (this still
>> > uses 1 byte per flag). Using bool instead, which is the common use.
>> >
>> > Signed-off-by: Robert Richter <rrichter@cavium.com>
>>
>> Such cleanups are not appropriate for 'net'. Only real bug fixes should
>> be targetted that.
>>
>> Respin these patches targetting the correct tree(s).
>
> Do you mean posting the two as "trivial" patches?
No I mean posting #1 targetted at my 'net' GIT tree as a bug fix,
and posting #2 targetted separately at my 'net-next' GIT tree as
a cleanup.
This is how we've been doing things for more than a decade.
next prev parent reply other threads:[~2016-02-18 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:39 [PATCH 0/2] net: thunderx: Small cleanups Robert Richter
2016-02-18 12:39 ` [PATCH 1/2] net: thunderx: Fix const type in nicvf_set_rxfh() Robert Richter
2016-02-18 12:39 ` [PATCH 2/2] net, thunderx: Use bool in structs where possible Robert Richter
2016-02-18 16:05 ` David Miller
2016-02-18 16:42 ` Robert Richter
2016-02-18 20:06 ` David Miller [this message]
2016-02-22 11:00 ` David Laight
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=20160218.150631.574392083739567663.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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