lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqLgbEST-aBog1gf5MQeaH3q9xomXb+HbzPN+Jpe+_yMgg@mail.gmail.com>
Date:   Thu, 1 Mar 2018 09:38:40 -0600
From:   Rob Herring <robh@...nel.org>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Frank Rowand <frowand.list@...il.com>, devicetree@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/6] kbuild: remove remaining use of undefined YACC_PREFIX

On Thu, Mar 1, 2018 at 8:01 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
> 2018-03-01 22:39 GMT+09:00 Rob Herring <robh@...nel.org>:
>> On Thu, Mar 1, 2018 at 5:35 AM, Masahiro Yamada
>> <yamada.masahiro@...ionext.com> wrote:
>>> Hi Rob,
>>>
>>> 2018-03-01 13:20 GMT+09:00 Masahiro Yamada <yamada.masahiro@...ionext.com>:
>>>> 2018-03-01 8:32 GMT+09:00 Rob Herring <robh@...nel.org>:
>>>>> Commit eea199b445f6 ("kbuild: remove unnecessary LEX_PREFIX and
>>>>> YACC_PREFIX") removed YACC_PREFIX definition, but left one use of it. There
>>>>> was not any build error since there is no user of "cmd_bison_h" currently.
>>>>> Remove the last remaining occurrence of YACC_PREFIX.
>>>>>
>>>>> Fixes: eea199b445f6 ("kbuild: remove unnecessary LEX_PREFIX and YACC_PREFIX")
>>>>> Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>
>>>>> Signed-off-by: Rob Herring <robh@...nel.org>
>>>>
>>>> You can replace CC with my
>>>>
>>>> Acked-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
>>>
>>>
>>> I got a reason to send a fixes pull request this week.
>>>
>>> If you do not mind, may I include this one in
>>> my Kbuild fixes pull request?
>>
>> Yes, please do.
>>
>>>
>>> I do not see dependency between 1/6 and the rest of the series.
>>
>> Only that dtc won't build without it. :)
>>
>
> Sorry, I missed that.
> You are right.
>
> I see this series is already queued up in your tree.

It is not really queued up, I just pushed out a tree for 0-day
testing. And it turns out I need strrchr in several places.

> So, just keep it in your tree.

Okay.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ