From: "Robert P. J. Day" <rpjday@mindspring.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: getting support for command-line flash partitioning
Date: Thu, 1 Jul 2004 12:48:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0407011244070.16076@localhost.localdomain> (raw)
In-Reply-To: <1088695697.14216.3060.camel@hades.cambridge.redhat.com>
On Thu, 1 Jul 2004, David Woodhouse wrote:
> On Thu, 2004-07-01 at 10:45 -0400, Robert P. J. Day wrote:
>> so how is this being added to the files? as in, who will add this
>> feature to the individual files, and get it pushed upstream, if that's
>> what's going to happen? just curious as to how this feature will
>> eventually end up in the mainstream.
>
> The owner of each board support ('map') file is expected to make sure
> that it's kept up to date in my CVS tree. Periodically I push updates to
> Linus, although individuals are welcome to send their own changes to
> Linus as soon as they're committed to CVS too.
ok, i was just trying to figure out how the different versions of the
kernel i have have such differing levels of that CMDLINE support.
the original kernel tree i have from embedded planet (approx. 2.4.22)
has a small number of map files that make any reference to that
feature. the CVS tree from denx (2.4.25) has considerably more. and
neither the latest "bk pull" of the 2.5/2.6 kernel from bkbits.net, or
the standard 2.6 kernel on my fedora core system has *any* support for
that feature in the map files (even though the kernel has the internal
support).
i was just trying to figure out the logical flow of how that feature
worked its way in. thanks.
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-01 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 14:45 getting support for command-line flash partitioning Robert P. J. Day
2004-07-01 15:28 ` David Woodhouse
2004-07-01 16:48 ` Robert P. J. Day [this message]
2004-07-01 17:53 ` Sylvain Munaut
2004-07-01 18:17 ` Robert P. J. Day
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=Pine.LNX.4.60.0407011244070.16076@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=dwmw2@infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.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).