From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@basil.nowhere.org>
Subject: Re: Please revert 86c0baf123e474b6eb404798926ecf62b426bf3a
Date: Tue, 8 May 2007 16:54:50 +0100 [thread overview]
Message-ID: <20070508155449.GB13212@flint.arm.linux.org.uk> (raw)
In-Reply-To: <46409512.5000502@redhat.com>
On Tue, May 08, 2007 at 11:19:46AM -0400, Prarit Bhargava wrote:
> Linus Torvalds wrote:
> >On Tue, 8 May 2007, Russell King wrote:
> >
> >>Shall I invent __CPUINIT to mark data to always be thrown away, or are
> >>the x86 folk going to withdraw this patch and do it properly?
> >>
> >
> >I can certainly revert the patch, but it would probably be better if you
> >were to just start adding the infrastructure you need and send it as a new
> >patch instead (where the revert is part of it, and the __CPUINIT is
> >additional).
>
> I've sent Russell a new patch to test off-list. He or I will submit a
> fix here after he tests.
I'm not sure it'd make much sense for me to test it - I don't have x86
based test boxes here.
Assuming your intention is to revert this commit and replace it with your
patch which doesn't change the semantics of __INIT, it shouldn't cause me
any problems.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-05-08 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 13:49 Please revert 86c0baf123e474b6eb404798926ecf62b426bf3a Russell King
2007-05-08 14:07 ` Prarit Bhargava
2007-05-08 15:17 ` Linus Torvalds
2007-05-08 15:19 ` Prarit Bhargava
2007-05-08 15:54 ` Russell King [this message]
2007-05-08 15:56 ` Prarit Bhargava
2007-05-13 10:56 ` Russell King
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=20070508155449.GB13212@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=andi@basil.nowhere.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=torvalds@linux-foundation.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