From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Rutland <mark.rutland@arm.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the random tree
Date: Wed, 18 Mar 2020 23:30:23 -0400 [thread overview]
Message-ID: <20200319033023.GB1067245@mit.edu> (raw)
In-Reply-To: <20200316165923.043f4454@canb.auug.org.au>
On Mon, Mar 16, 2020 at 04:59:23PM +1100, Stephen Rothwell wrote:
> > Yes, that looks fine. Reordering the functions to move them under the
> > #ifdefs will make the code less readable, and adding extra
> > #ifdef/#endif would also make things less readable.
> >
> > Thanks for the patch, will apply.
>
> How are we going with this?
I've applied and pushed out Mark's patch.
- Ted
next prev parent reply other threads:[~2020-03-19 3:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 3:44 linux-next: build warning after merge of the random tree Stephen Rothwell
2020-03-06 4:53 ` Stephen Rothwell
2020-03-10 12:17 ` Mark Rutland
2020-03-10 14:46 ` Theodore Y. Ts'o
2020-03-16 5:59 ` Stephen Rothwell
2020-03-19 3:30 ` Theodore Y. Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-16 5:52 Stephen Rothwell
2018-06-08 3:37 Stephen Rothwell
2018-06-18 3:35 ` Stephen Rothwell
2018-06-18 5:29 ` Tobin C. Harding
2018-07-10 7:26 ` Stephen Rothwell
2017-02-01 6:09 Stephen Rothwell
2014-07-21 7:49 Stephen Rothwell
2013-09-23 4:39 Stephen Rothwell
2013-09-23 4:42 ` 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=20200319033023.GB1067245@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sfr@canb.auug.org.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).