From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>,
"Anuj Mittal" <anuj.mittal@intel.com>,
"Otavio Salvador" <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: kernel menuconfig broken?
Date: Fri, 21 Sep 2018 11:57:54 -0400 [thread overview]
Message-ID: <b8ccd853-2b25-4364-7770-7ef8df4db646@windriver.com> (raw)
In-Reply-To: <4e5235ad-b3a6-4985-43b4-ef71d6bf16a6@windriver.com>
On 2018-09-21 11:34 AM, Bruce Ashfield wrote:
> On 2018-09-21 11:33 AM, Andreas Müller wrote:
>> On Fri, Sep 21, 2018 at 4:39 PM, Andreas Müller
>> <schnitzeltony@gmail.com> wrote:
>>> On Fri, Sep 21, 2018 at 1:46 PM, Anuj Mittal <anuj.mittal@intel.com>
>>> wrote:
>>>>> Hi,
>>>>>
>>>>> seems upstream has introduced changes 4.17 -> 4.18 - the patch does
>>>>> not apply anymore. Is this patch available for 4.18 somewhere?
>>>>>
>>>>
>>>> Are you looking for this:
>>>>
>>>> https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit?h=v4.18/standard/base&id=bd6314212686ef8156a108b6f1eec67d34402878
>>>>
>>>>
>>>> https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v4.18/standard/base&id=0aa800372a846d6ed2c0fc3e0fdc22656d268968
>>>>
>>> Exactly thanks
>>>
>> Otavio pointed to it when I sent them to linux-fslc: Why the code
>> duplication?
>>
>
> What do you mean by code duplication ? There was a bug in the initial
> port that needed a 2nd commit to fix it, but there's no duplicated
> code.
Ah. I see what you mean now. That was a mistake. I've already fixed
it in future versions, but since nothing breaks with it, the extra
block has stayed in 4.18.
Bruce
>
> Bruce
>
>> Andreas
>>
>
next prev parent reply other threads:[~2018-09-21 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 21:49 kernel menuconfig broken? Andreas Müller
2018-04-02 21:57 ` Trevor Woerner
2018-04-12 20:28 ` Andreas Müller
2018-04-12 21:19 ` Cal Sullivan
2018-04-12 21:29 ` Andreas Müller
2018-04-12 21:38 ` Cal Sullivan
2018-04-12 21:46 ` Andreas Müller
2018-04-12 22:12 ` Andreas Müller
2018-04-14 9:10 ` Paul Barker
2018-04-14 12:55 ` Andreas Müller
2018-04-14 18:42 ` Trevor Woerner
2018-04-14 19:06 ` Andreas Müller
2018-09-21 10:04 ` Andreas Müller
2018-09-21 11:46 ` Anuj Mittal
2018-09-21 12:31 ` Bruce Ashfield
2018-09-21 14:39 ` Andreas Müller
2018-09-21 15:33 ` Andreas Müller
2018-09-21 15:34 ` Bruce Ashfield
2018-09-21 15:57 ` Bruce Ashfield [this message]
2018-04-13 19:54 ` Bruce Ashfield
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=b8ccd853-2b25-4364-7770-7ef8df4db646@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=schnitzeltony@gmail.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