linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ooi, Joyce" <joyce.ooi@intel.com>
Cc: "Tham, Mun Yew" <mun.yew.tham@intel.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 pci 0/2] Update Mun Yew Tham as Pci Driver maintainer
Date: Wed, 29 Sep 2021 16:37:37 -0500	[thread overview]
Message-ID: <20210929213737.GA793548@bhelgaas> (raw)
In-Reply-To: <CO1PR11MB4820E3A166F8C08A85125458F2A99@CO1PR11MB4820.namprd11.prod.outlook.com>

On Wed, Sep 29, 2021 at 05:25:06AM +0000, Ooi, Joyce wrote:
> > -----Original Message-----
> > From: Tham, Mun Yew <mun.yew.tham@intel.com>
> > Sent: Wednesday, September 29, 2021 1:10 PM
> > To: Ooi, Joyce <joyce.ooi@intel.com>; Lorenzo Pieralisi
> > <lorenzo.pieralisi@arm.com>; Bjorn Helgaas <bhelgaas@google.com>; Rob
> > Herring <robh@kernel.org>
> > Cc: Krzysztof Wilczyński <kw@linux.com>; linux-pci@vger.kernel.org; linux-
> > kernel@vger.kernel.org; Tham, Mun Yew <mun.yew.tham@intel.com>
> > Subject: [PATCH V2 pci 0/2] Update Mun Yew Tham as Pci Driver maintainer
> > 
> > This is to update both Pci Driver For Altera Pcie Ip and Pci Msi Driver For
> > Altera Msi Ip maintainer.
> > 
> > Mun Yew Tham (2):
> >   Update Mun Yew Tham as Pci Driver For Altera Pcie Ip maintainer
> >   Update Mun Yew Tham as Pci Msi Driver For Altera Msi Ip maintainer
> > 
> >  MAINTAINERS | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Acked-by: Joyce Ooi <joyce.ooi@intel.com>

Seems like the original patch got lost.  All I can see is the
response, which isn't enough to apply this.  Can you (Mun Yew Tham, I
guess?) resend it?

Since you're becoming the maintainer for this, note that I
consistently capitalize "PCI", "PCIe", "MSI", "MSI-X", "IP", etc., so
they match the spec and common usage for acronyms and initialisms.

Bjorn

      reply	other threads:[~2021-09-29 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210929050955.25758-1-mun.yew.tham@intel.com>
2021-09-29  5:25 ` [PATCH V2 pci 0/2] Update Mun Yew Tham as Pci Driver maintainer Ooi, Joyce
2021-09-29 21:37   ` Bjorn Helgaas [this message]

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=20210929213737.GA793548@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=joyce.ooi@intel.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mun.yew.tham@intel.com \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).