linux-kernel - Re: [PATCH 1/2] dtc: Update generated files to output from Bison 2.5

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACxGe6tWx_GDYfZqKB-wN14jva51=SAdogjGkv2CicSJNUgNDw@mail.gmail.com>
Date:	Thu, 13 Jun 2013 23:24:55 +0100
From:	Grant Likely <grant.likely@...aro.org>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	devicetree-discuss <devicetree-discuss@...ts.ozlabs.org>
Subject: Re: [PATCH 1/2] dtc: Update generated files to output from Bison 2.5

On Thu, Jun 13, 2013 at 11:08 PM, Stephen Warren <swarren@...dotorg.org> wrote:
> On 06/13/2013 03:48 PM, Grant Likely wrote:
>> This patch merely updates the generated dtc parser and lexer files to
>> the output generated by Bison 2.5. The previous versions were generated
>> from version 2.4.1. The only reason for this commit is to minimize the
>> diff on the next commit which fixes a bug in the DTC #line directive
>> parsing. Otherwise the Bison changes would be intermingled with the
>> functional changes.
>
> Do you actually need this patch? It should make no functional
> difference, and patch 2/2 only affects the lexer, not the parser, so
> wouldn't have these changes mingled in.
>
> But I suppose I'm not objecting.

I wasn't going to change one without the other. I rebuilt all of dtc
based on the version of dtc currently in the kernel and committed the
result. I'm not experienced enough with bison to try and hand select
the changes that do and do not go in.

g.
--
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/