From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
konrad.wilk@oracle.com
Subject: Re: [PATCH] x86, iommu: Fix header comments regarding standard and _FINISH macros
Date: Thu, 9 Apr 2015 10:02:16 +0200 [thread overview]
Message-ID: <20150409080216.GA4793@gmail.com> (raw)
In-Reply-To: <20150409075408.GB25453@pd.tnic>
* Borislav Petkov <bp@suse.de> wrote:
> On Thu, Apr 09, 2015 at 09:37:44AM +0200, Ingo Molnar wrote:
> > So while we are touching it, how about making it more readable:
> >
> > *
> > * The standard vs the _FINISH variants differ in that the
> > * standard variant will continue detecting other IOMMUs in the
> > * call list after the detection routine returns a positive number.
> > * The _FINISH variant will stop the execution chain. Both variants
> > * will still call the 'init' and ...
> > *
>
> I went a step further :-)
>
> ---
> From: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> Date: Wed, 8 Apr 2015 10:46:57 -0500
> Subject: [PATCH] x86/iommu: Fix header comments regarding standard and _FINISH
> macros
>
> The comment line regarding IOMMU_INIT and IOMMU_INIT_FINISH macros
> is incorrect:
>
> "The standard vs the _FINISH differs in that the _FINISH variant will
> continue detecting other IOMMUs in the call list..."
>
> It should be "..the *standard* variant will continue detecting..."
>
> Fix that. Also, make it readable while at it.
>
> Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> Fixes: 6e9636693373 ("x86, iommu: Update header comments with appropriate naming")
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: x86-ml <x86@kernel.org>
> Cc: konrad.wilk@oracle.com
> Link: http://lkml.kernel.org/r/1428508017-5316-1-git-send-email-Aravind.Gopalakrishnan@amd.com
> Signed-off-by:
> ---
> arch/x86/include/asm/iommu_table.h | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/include/asm/iommu_table.h b/arch/x86/include/asm/iommu_table.h
> index f42a04735a0a..e37d6b3ad983 100644
> --- a/arch/x86/include/asm/iommu_table.h
> +++ b/arch/x86/include/asm/iommu_table.h
> @@ -79,11 +79,12 @@ struct iommu_table_entry {
> * d). Similar to the 'init', except that this gets called from pci_iommu_init
> * where we do have a memory allocator.
> *
> - * The standard vs the _FINISH differs in that the _FINISH variant will
> - * continue detecting other IOMMUs in the call list after the
> - * the detection routine returns a positive number. The _FINISH will
> - * stop the execution chain. Both will still call the 'init' and
> - * 'late_init' functions if they are set.
> + * The standard IOMMU_INIT differs from the IOMMU_INIT_FINISH variant
> + * in that the former will continue detecting other IOMMUs in the call
> + * list after the detection routine returns a positive number, while the
> + * latter will stop the execution chain upon first successful detection.
> + * Both variants will still call the 'init' and 'late_init' functions if
> + * they are set.
> */
> #define IOMMU_INIT_FINISH(_detect, _depend, _init, _late_init) \
> __IOMMU_INIT(_detect, _depend, _init, _late_init, 1)
Sounds good to me!
Thanks,
Ingo
next prev parent reply other threads:[~2015-04-09 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:46 [PATCH] x86, iommu: Fix header comments regarding standard and _FINISH macros Aravind Gopalakrishnan
2015-04-09 7:27 ` Borislav Petkov
2015-04-09 7:37 ` Ingo Molnar
2015-04-09 7:54 ` Borislav Petkov
2015-04-09 8:02 ` Ingo Molnar [this message]
2015-04-09 10:31 ` Konrad Rzeszutek Wilk
2015-04-09 10:38 ` Borislav Petkov
2015-04-09 9:04 ` [tip:x86/cleanups] x86/iommu: " tip-bot for Aravind Gopalakrishnan
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=20150409080216.GA4793@gmail.com \
--to=mingo@kernel.org \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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.