All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: Tom Rix <trix@redhat.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Ivan Bornyakov <i.bornyakov@metrotek.ru>,
	Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
	linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fpga: microchip-spi: add missing module author entry
Date: Mon, 15 Aug 2022 11:28:55 +0800	[thread overview]
Message-ID: <Yvm9dzhyj6k4+01g@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <53f6e675-1fc5-fb17-ce6f-aa952d61132f@redhat.com>

On 2022-07-28 at 05:29:48 -0700, Tom Rix wrote:
> 
> On 7/28/22 12:50 AM, Conor Dooley wrote:
> > Add the missing MODULE_AUTHOR entry for the Microchip spi-slave FPGA
> > programming driver.
> > 
> > Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> Reviewed-by: Tom Rix <trix@redhat.com>

Acked-by: Xu Yilun <yilun.xu@intel.com>

Applied to for-next

> > ---
> >   drivers/fpga/microchip-spi.c | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/fpga/microchip-spi.c b/drivers/fpga/microchip-spi.c
> > index bd284c7b8dc9..7436976ea904 100644
> > --- a/drivers/fpga/microchip-spi.c
> > +++ b/drivers/fpga/microchip-spi.c
> > @@ -395,4 +395,5 @@ static struct spi_driver mpf_driver = {
> >   module_spi_driver(mpf_driver);
> >   MODULE_DESCRIPTION("Microchip Polarfire SPI FPGA Manager");
> > +MODULE_AUTHOR("Ivan Bornyakov <i.bornyakov@metrotek.ru>");
> >   MODULE_LICENSE("GPL");
> 

  reply	other threads:[~2022-08-15  3:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  7:50 [PATCH] fpga: microchip-spi: add missing module author entry Conor Dooley
2022-07-28 12:29 ` Tom Rix
2022-08-15  3:28   ` Xu Yilun [this message]
2022-07-28 18:46 ` Ivan Bornyakov
2022-07-28 19:18   ` Conor.Dooley

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=Yvm9dzhyj6k4+01g@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@intel.com \
    --cc=conor.dooley@microchip.com \
    --cc=hao.wu@intel.com \
    --cc=i.bornyakov@metrotek.ru \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=trix@redhat.com \
    /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.