From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759383Ab3FMWIM (ORCPT ); Thu, 13 Jun 2013 18:08:12 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:42659 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757866Ab3FMWIK (ORCPT ); Thu, 13 Jun 2013 18:08:10 -0400 Message-ID: <51BA42C8.60900@wwwdotorg.org> Date: Thu, 13 Jun 2013 16:08:08 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Grant Likely CC: linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Grant Likely Subject: Re: [PATCH 1/2] dtc: Update generated files to output from Bison 2.5 References: <1371160133-10104-1-git-send-email-grant.likely@linaro.org> <1371160133-10104-2-git-send-email-grant.likely@linaro.org> In-Reply-To: <1371160133-10104-2-git-send-email-grant.likely@linaro.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.