Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752755AbbBWNzD (ORCPT ); Mon, 23 Feb 2015 08:55:03 -0500 Received: from mail-wi0-f173.google.com ([209.85.212.173]:58437 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752655AbbBWNzA (ORCPT ); Mon, 23 Feb 2015 08:55:00 -0500 From: Matt Fleming X-Google-Original-From: Matt Fleming Date: Mon, 23 Feb 2015 13:54:57 +0000 To: Ivan Khoronzhuk Cc: ard.biesheuvel@linaro.org, leif.lindholm@linaro.org, linux-kernel@vger.kernel.org Subject: Re: [Patch v2 2/3] firmware: dmi_scan: use full dmi version for SMBIOS3 Message-ID: <20150223135457.GC19367@codeblueprint.co.uk> References: <1424259201-24886-1-git-send-email-ivan.khoronzhuk@linaro.org> <1424259201-24886-3-git-send-email-ivan.khoronzhuk@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1424259201-24886-3-git-send-email-ivan.khoronzhuk@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 971 Lines: 25 On Wed, 18 Feb, at 01:33:20PM, Ivan Khoronzhuk wrote: > New SMBIOS3 spec adds additional field for versioning - docrev. > The docrev identifies the revision of a specification implemented in > the table structures, so display SMBIOSv3 versions in format, > like "3.22.1". > > In case of only 32 bit entry point for versions > 3 display > dmi version like "3.22.x" as we don't know the docrev. > > In other cases display version like it was. > > Signed-off-by: Ivan Khoronzhuk > --- > drivers/firmware/dmi_scan.c | 20 ++++++++++++-------- > 1 file changed, 12 insertions(+), 8 deletions(-) Applied to the EFI 'next' branch, thanks Ivan. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/