From: Vivek Goyal <vgoyal@in.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: Jon Loeliger <jdl@jdl.com>,
Fastboot mailing list <fastboot@lists.osdl.org>,
linuxppc-dev@ozlabs.org, Horms <horms@verge.net.au>
Subject: Re: [Fastboot] [PATCH] kexec: remove memory reserve patching for powerpc device tree
Date: Fri, 22 Sep 2006 10:23:25 -0400 [thread overview]
Message-ID: <20060922142325.GG18611@in.ibm.com> (raw)
In-Reply-To: <20060922011153.39DD867B79@ozlabs.org>
On Fri, Sep 22, 2006 at 10:41:51AM +0930, Michael Neuling wrote:
> In message <20060921143253.GC1542@in.ibm.com> you wrote:
> > On Thu, Sep 21, 2006 at 09:18:39AM -0500, Jon Loeliger wrote:
> > > So, like, the other day Vivek Goyal mumbled:
> > > >
> > > > Now with distros adopting kexce-tools, I am in for maintaining the backwa
> rd
> > > > compatibility as far as possible. Putting a note in the code is good that
> > > > down the line, get rid of this code.
> > >
> > > Perhaps scheduling it as an entry in
> > >
> > > Documentation/feature-removal-schedule.txt
> > >
> > > just so people (distros) can plan around it?
> >
> > Perfect. In kexec-tools it can go in doc/feature-removal-schedule.txt.
>
> It doesn't really need to go in the kernel source as the kernel has
> already changed and besides, we were adding a feature to the kernel, not
> removing one.
>
> At this stage, it's just a kexec tools feature removal.
>
Well, what I meant is that a similar file can go in kexec-tools/doc/ dir.
-Vivek
prev parent reply other threads:[~2006-09-22 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 1:10 [PATCH] kexec: remove memory reserve patching for powerpc device tree Michael Neuling
2006-09-21 1:59 ` Michael Ellerman
2006-09-21 2:51 ` [Fastboot] " Horms
2006-09-21 3:40 ` Michael Ellerman
2006-09-21 4:04 ` Michael Neuling
2006-09-21 13:55 ` Vivek Goyal
2006-09-21 14:18 ` Jon Loeliger
2006-09-21 14:32 ` Vivek Goyal
2006-09-22 1:11 ` Michael Neuling
2006-09-22 1:21 ` Horms
2006-09-22 14:23 ` Vivek Goyal [this message]
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=20060922142325.GG18611@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=fastboot@lists.osdl.org \
--cc=horms@verge.net.au \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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.