From: eric ernst <eric.ernst@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Josh Boyer <jwboyer@fedoraproject.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
mark.gross@intel.com
Subject: Re: [PATCH 1/1] Add kernel parameter for kernel version
Date: Mon, 02 Jun 2014 11:41:43 -0700 [thread overview]
Message-ID: <538CC567.2060305@linux.intel.com> (raw)
In-Reply-To: <5384F034.8030303@infradead.org>
On 14-05-27 01:06 PM, Randy Dunlap wrote:
> On 05/27/2014 12:48 PM, Josh Boyer wrote:
>> On Tue, May 27, 2014 at 3:40 PM, <eric.ernst@linux.intel.com> wrote:
>>> From: Eric Ernst <eric.ernst@linux.intel.com>
>>>
>>> Create a kernel cmdline parameter, "version_addendum", which can be
>>> used to add text to the kernel version that is reported from
>>> /proc/version.
>> Why?
>>
>> What is the intended purpose of this and why would someone want to use it?
> and if the patch were to continue to live, it needs a Documentation addition
> to kernel-parameters.txt.
>
Randy - ACK.
Josh - we have a need to keep a single product binary (kernel) across
multiple android devices. A subset of these platforms are looking for
extra versioning information appended to it, accessible via
/proc/version. Rather than build multiple otherwise identical kernels
with only this extended versioning as differentiation, we are looking to
make this a command line parameter. Understandable if there isn't
enough value-add for the community in this patch, but I figured I'd give
the patch a shot, as we need this functionality locally. Thanks.
next prev parent reply other threads:[~2014-06-02 18:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 19:40 [PATCH 1/1] Add kernel parameter for kernel version eric.ernst
2014-05-27 19:48 ` Josh Boyer
2014-05-27 20:06 ` Randy Dunlap
2014-06-02 18:41 ` eric ernst [this message]
2014-06-05 22:09 ` [PATCH v1 " eric.ernst
2014-06-05 22:16 ` Andrew Morton
2014-06-05 22:15 ` eric ernst
2014-06-05 22:29 ` Randy Dunlap
2014-06-05 22:56 ` eric ernst
2014-06-05 23:06 ` Richard Weinberger
2014-06-05 22:30 ` David Rientjes
2014-06-05 22:17 ` Randy Dunlap
2014-06-05 22:16 ` eric ernst
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=538CC567.2060305@linux.intel.com \
--to=eric.ernst@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).