From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 kexec/kdump 2.6.18-rc5 patch
Date: Wed, 30 Aug 2006 08:27:19 +0000 [thread overview]
Message-ID: <20060830082717.GA21121@verge.net.au> (raw)
In-Reply-To: <1156837594.2598.15.camel@linux-znh>
On 30 Aug 2006 06:03:23 +0800, Zou Nan hai wrote:
> On Wed, 2006-08-30 at 03:38, Bjorn Helgaas wrote:
>> On Tuesday 29 August 2006 01:46, Zou Nan hai wrote:
>> > +#ifdef CONFIG_KEXEC
>> > +void
>> > +ioc_iova_disable(void)
>> > +{
>>
>> Ugh. If you really need this functionality (which I have to say
>> looks
>> like a band-aid), it probably should be a platform vector. And
>> should
>> be split into a separate patch.
>>
> Hi Bjorn,
> The ioc_iova_disable code comes from Aziz in HP, I have almost
> no idea
> of how IOMMU works on HP platform.
> I am looking for an HP machine with IOMMU to test.
That sounds like even more reason to break it out into a separate patch.
Actually, I really think that you sould either provide a set or smaller
patches, or incremental patches. Its quite hard to follow what is
changing with the current jumbo-patch format.
Its also quite unclear what if any portions you would like merged, and
even which tree you want them merged into - you patches are against
2.6.18-rc5, but the ia64 tree seems the most likely path, and your code
doesn't apply there because some of the changes are already present.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
next prev parent reply other threads:[~2006-08-30 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 7:46 IA64 kexec/kdump 2.6.18-rc5 patch Zou Nan hai
2006-08-29 19:38 ` Bjorn Helgaas
2006-08-29 22:03 ` Zou Nan hai
2006-08-30 8:27 ` Horms
2006-08-30 8:27 ` Horms
2006-08-30 8:27 ` Horms [this message]
2006-09-01 2:24 ` Horms
2006-09-12 17:13 ` Jack Steiner
2006-09-12 19:59 ` Jack Steiner
2006-09-12 20:23 ` Luck, Tony
2006-09-12 21:25 ` Jack Steiner
2006-09-12 22:56 ` Zou Nan hai
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=20060830082717.GA21121@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@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