From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: jdmason@us.ibm.com, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH 0 of 4] x8-64: Calgary: updates for CONFIG_IOMMU_DEBUG
Date: Thu, 3 Aug 2006 02:23:13 +0300 [thread overview]
Message-ID: <20060802232313.GF4982@rhun.ibm.com> (raw)
In-Reply-To: <200608030116.48607.ak@suse.de>
On Thu, Aug 03, 2006 at 01:16:48AM +0200, Andi Kleen wrote:
> On Thursday 03 August 2006 00:59, Muli Ben-Yehuda wrote:
> > Hi Andi,
> >
> > A few Calgary updates for CONFIG_IOMMU_DEBUG: print a message when
> > CONFIG_IOMMU_DEBUG is on, remove dangerous bringup debugging code and
> > only double check our bitmap handling if currently debugging.
> >
> > Please apply, patches are againt mainline with all previous Calgary
> > patches applied (which should apply cleanly to your tree).
>
> Added thanks.
>
> In the future please be a little bit more verbose in the changelog
> department.
The patches themselves have verbose changelog entries, I never know
quite what to write in the introductory message - I guess I'll just
hack mercurial's email extension to get rid of it (unless it's useful
to you?)
Cheers,
Muli
next prev parent reply other threads:[~2006-08-02 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <patchbomb.1154559547@rhun.haifa.ibm.com>
2006-08-02 23:16 ` [PATCH 0 of 4] x8-64: Calgary: updates for CONFIG_IOMMU_DEBUG Andi Kleen
2006-08-02 23:23 ` Muli Ben-Yehuda [this message]
[not found] ` <515131a26b151f1e4596.1154559549@rhun.haifa.ibm.com>
2006-08-03 3:57 ` [PATCH 2 of 4] [x86-64] Calgary: only verify the allocation bitmap if CONFIG_IOMMU_DEBUG is on Jon Mason
2006-08-03 3:54 ` Andi Kleen
2006-08-03 7:19 ` Muli Ben-Yehuda
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=20060802232313.GF4982@rhun.ibm.com \
--to=muli@il.ibm.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jdmason@us.ibm.com \
--cc=linux-kernel@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