[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLUgeyn6MobUQ=wrQRBjfBPF7OHTSxJuSsYeYKC-U2KMGA@mail.gmail.com>
Date: Mon, 4 Aug 2014 11:27:03 -0700
From: John Stultz <john.stultz@...aro.org>
To: Kees Cook <keescook@...omium.org>
Cc: Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux-Next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
David Riley <davidriley@...omium.org>
Subject: Re: linux-next: manual merge of the driver-core tree with the tip tree
On Fri, Aug 1, 2014 at 4:38 PM, Kees Cook <keescook@...omium.org> wrote:
> On Thu, Jul 31, 2014 at 8:20 PM, Greg KH <greg@...ah.com> wrote:
>> On Thu, Jul 31, 2014 at 05:07:35PM +1000, Stephen Rothwell wrote:
>>> Hi Greg,
>>>
>>> Today's linux-next merge of the driver-core tree got a conflict in
>>> lib/Kconfig.debug between commit e704f93af5a0 ("kernel: time: Add
>>> udelay_test module to validate udelay") from the tip tree and commit
>>> 0a8adf584759 ("test: add firmware_class loader test") from the
>>> driver-core tree.
>>>
>>> I fixed it up (see below) and can carry the fix as necessary (no action
>>> is required).
>>
>> Looks good, thanks.
>
> For keeping things regularized, could this module instead be named
> "test_udelay", to match the rest of most of the test modules?
> (Starting with "test_".)
Sure. I'll spin up a patch to change it and will submit here shortly.
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists