From: Erwan Velu <e.velu@criteo.com>
To: Jean Delvare <jdelvare@suse.de>, Erwan Velu <erwanaliasr1@gmail.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"David S. Miller" <davem@davemloft.net>,
Changbin Du <changbin.du@intel.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Sumit Garg <sumit.garg@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Michal Marek <michal.lkml@markovi.net>,
Mattias Jacobsson <2pi@mok.nu>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] firmware/dmi: Report DMI Bios release
Date: Wed, 27 Nov 2019 15:05:37 +0000 [thread overview]
Message-ID: <5781c7dd-c19d-7664-4022-6e86e405f0f5@criteo.com> (raw)
In-Reply-To: <20191021165321.60be88cd@endymion>
On 21/10/2019 16:53, Jean Delvare wrote:
> This would also be in line with how it was implemented in dmidecode. Is
> there any reason to NOT go that route?
The main reason was I though it would be easier to compare releases by
splitting major & minor.
That is probably overkill, so I'll stick to the usual way to represent a
release in V2.
Thanks for the review,
Erwan,
next prev parent reply other threads:[~2019-11-27 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 9:43 [PATCH 1/3] firmware/dmi_scan: Add dmi_save_release to save releases fields Erwan Velu
2019-09-18 9:43 ` [PATCH 2/3] firmware/dmi: Report DMI Bios release Erwan Velu
2019-10-21 14:53 ` Jean Delvare
2019-11-27 15:05 ` Erwan Velu [this message]
2019-09-18 9:43 ` [PATCH 3/3] firmware/dmi: Report DMI Embedded Firmware release Erwan Velu
2019-10-21 14:55 ` Jean Delvare
2019-10-21 14:32 ` [PATCH 1/3] firmware/dmi_scan: Add dmi_save_release to save releases fields Jean Delvare
2019-11-27 15:04 ` Erwan Velu
2019-11-27 15:07 ` [PATCH 1/2] firmware/dmi: Report DMI Bios release Erwan Velu
2019-11-27 15:07 ` [PATCH 2/2] firmware/dmi: Report DMI Embedded Firmware release Erwan Velu
2020-02-06 12:24 ` Jean Delvare
2020-02-06 12:25 ` Erwan Velu
2020-02-07 8:38 ` Erwan Velu
2020-02-06 12:16 ` [PATCH 1/2] firmware/dmi: Report DMI Bios release Jean Delvare
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=5781c7dd-c19d-7664-4022-6e86e405f0f5@criteo.com \
--to=e.velu@criteo.com \
--cc=2pi@mok.nu \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bbrezillon@kernel.org \
--cc=changbin.du@intel.com \
--cc=davem@davemloft.net \
--cc=erwanaliasr1@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rpjday@crashcourse.ca \
--cc=sumit.garg@linaro.org \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®