From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Dan Aloni <da-x@monatomic.org>,
Bernhard Walle <bwalle@suse.de>
Subject: Re: [PATCH] Add ELF note with Linux version
Date: Thu, 13 Sep 2007 14:56:59 -0700 [thread overview]
Message-ID: <46E9B22B.1000002@goop.org> (raw)
In-Reply-To: <20070913144228.2efcd5d9.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 06 Sep 2007 11:36:21 +0100
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>> Bernhard Walle wrote:
>>
>>> This patch adds version information to the ELF kernel file. Together
>>> with the bzImage version information, this allows distributions to
>>> identify the kernel version based on the file name.
>>>
>>>
>> Seems reasonable to me, but I think the macro could be just called
>> "ELFNOTE".
>>
>>
>
> You removed Bernhard from the cc list.
>
Didn't mean to... Oh, he has a "mail-followup-to" header which doesn't
include himself...
> I'd like to know a little bit more about why this is needed, how it will be
> used, etc. And given that this feature is intended to improve life for
> distributors, it would be nice to get some feedback from the appropriate
> persons.
Hm, yes. ELF notes don't appear in the bzImage, since it isn't an ELF
file, so perhaps this doesn't satisfy the requirement. It would help to
have more detail.
J
next prev parent reply other threads:[~2007-09-13 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 15:00 [PATCH] Add ELF note with Linux version Bernhard Walle
2007-09-06 10:36 ` Jeremy Fitzhardinge
2007-09-13 21:42 ` Andrew Morton
2007-09-13 21:56 ` Jeremy Fitzhardinge [this message]
2007-09-14 7:52 ` Bernhard Walle
2007-09-14 20:00 ` Jeremy Fitzhardinge
2007-09-13 22:13 ` Sam Ravnborg
2007-09-13 22:44 ` Jeremy Fitzhardinge
2007-09-14 6:08 ` Sam Ravnborg
2007-09-14 19:47 ` Jeremy Fitzhardinge
2007-09-14 21:07 ` Sam Ravnborg
2007-09-14 21:15 ` Roland McGrath
2007-09-14 21:31 ` Jeremy Fitzhardinge
2007-09-15 1:30 ` Roland McGrath
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=46E9B22B.1000002@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=da-x@monatomic.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.