From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: Ryan Wilson <hap9@epoch.ncsc.mil>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch/x86/pci/xen.c: fix a typo in comments
Date: Fri, 11 Jan 2013 12:28:44 -0500 [thread overview]
Message-ID: <20130111172844.GA26287@phenom.dumpdata.com> (raw)
In-Reply-To: <CABawtvNHe7f9n+BAFfCzha2WNuovxNvfQabTyWFH_5oyfAh5Xg@mail.gmail.com>
On Thu, Dec 20, 2012 at 09:22:11AM +0800, Ethan Zhao wrote:
> Konrad,
> This patch fix a typo in comments of arch/x86/pci/xen.c
Hm, so somehow I don't see your SOB on the patch? Can you please
include that.
>
> Thanks,
> Ethan.zhao@oracle.com
>
> ---------------------------------------
> commit 333a48b76d5311ae370d65dfac293ca0d839c455
> Author: ethan.zhao <ethan.kernel@gmail.com>
> Date: Thu Dec 20 20:23:31 2012 -0800
>
> Fix a typo in comments
>
> diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
> index 56ab749..8de6ced 100644
> --- a/arch/x86/pci/xen.c
> +++ b/arch/x86/pci/xen.c
> @@ -2,7 +2,7 @@
> * Xen PCI - handle PCI (INTx) and MSI infrastructure calls for PV, HVM and
> * initial domain support. We also handle the DSDT _PRT callbacks for GSI's
> * used in HVM and initial domain mode (PV does not parse ACPI, so it has
> no
> - * concept of GSIs). Under PV we hook under the pnbbios API for IRQs and
> + * concept of GSIs). Under PV we hook under the pnpbios API for IRQs and
> * 0xcf8 PCI configuration read/write.
> *
> * Author: Ryan Wilson <hap9@epoch.ncsc.mil>
next parent reply other threads:[~2013-01-11 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABawtvNHe7f9n+BAFfCzha2WNuovxNvfQabTyWFH_5oyfAh5Xg@mail.gmail.com>
2013-01-11 17:28 ` Konrad Rzeszutek Wilk [this message]
2012-12-20 2:13 [PATCH] arch/x86/pci/xen.c: fix a typo in comments Ethan Zhao
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=20130111172844.GA26287@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ethan.kernel@gmail.com \
--cc=hap9@epoch.ncsc.mil \
--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