linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	stable <stable@vger.kernel.org>, "Michal Hocko" <mhocko@suse.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	"Dave Jiang" <dave.jiang@intel.com>, "Jan Kara" <jack@suse.cz>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Huang Ying" <ying.huang@intel.com>,
	"Matthew Wilcox" <willy@linux.intel.com>,
	"Ross Zwisler" <ross.zwisler@linux.intel.com>,
	"Hugh Dickins" <hughd@google.com>,
	"Tobin C Harding" <me@tobin.cc>, linux-mm <linux-mm@kvack.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: hide a #warning for COMPILE_TEST
Date: Fri, 16 Feb 2018 09:42:42 -0800	[thread overview]
Message-ID: <CA+55aFxRo=X3_fb5JC55JjWt8KOWAdaMaBt5k5VPZhosT25WpQ@mail.gmail.com> (raw)
In-Reply-To: <20180216152608.1626885-1-arnd@arndb.de>

On Fri, Feb 16, 2018 at 7:25 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>
> The warning is reasonable by itself, but gets in the way of
> randconfig build testing, so I'm hiding it whenever CONFIG_COMPILE_TEST
> is set.

Ack, looks sane, so I just applied it directly to my tree instead of
waiting for this to get back to me from Andrew ;)

                 Linus

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2018-02-16 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 15:25 [PATCH] mm: hide a #warning for COMPILE_TEST Arnd Bergmann
2018-02-16 17:42 ` Linus Torvalds [this message]

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='CA+55aFxRo=X3_fb5JC55JjWt8KOWAdaMaBt5k5VPZhosT25WpQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dave.jiang@intel.com \
    --cc=hughd@google.com \
    --cc=jack@suse.cz \
    --cc=jglisse@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=me@tobin.cc \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=willy@linux.intel.com \
    --cc=ying.huang@intel.com \
    /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).