public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Dan Aloni <da-x@monatomic.org>
Subject: Re: [PATCH] Add ELF note with Linux version
Date: Fri, 14 Sep 2007 13:00:16 -0700	[thread overview]
Message-ID: <46EAE850.1000503@goop.org> (raw)
In-Reply-To: <20070914075234.GI30366@suse.de>

Bernhard Walle wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> [2007-09-13 23:56]:
>   
>>> 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.
>>     
>
> the bzImage already contains the version (and much more, e.g. if the
> kernel is relocatable, the command line length it accepts). See
> Documentation/i386/boot.txt.
>   

Yes, I'm familiar with that.  I'm wondering what end result you're
trying to achieve though.  What's the specific problem?

    J

  reply	other threads:[~2007-09-14 20:00 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
2007-09-14  7:52       ` Bernhard Walle
2007-09-14 20:00         ` Jeremy Fitzhardinge [this message]
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=46EAE850.1000503@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox