driverdev-devel.linuxdriverproject.org archive mirror
 help / color / mirror / Atom feed
From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: NeilBrown <neil@brown.name>, driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH 2/4] staging: mt7621-pci: add myself as a contributor of the driver
Date: Mon, 23 Mar 2020 12:31:08 +0100	[thread overview]
Message-ID: <CAMhs-H9iO4=bQU9WRHX-J+dNKM9u48xH+27ooif6NXuHUmt38w@mail.gmail.com> (raw)
In-Reply-To: <20200323103227.GA433808@kroah.com>

Hi Greg,

On Mon, Mar 23, 2020 at 11:32 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Sat, Mar 21, 2020 at 02:36:22PM +0100, Sergio Paracuellos wrote:
> > During a long time I have been cleaning and fixing this driver
> > in order to use current kernel's apis and try to get it out of
> > the staging area. At the end the driver is mt7621 specific and
> > has been completely re-written. Hence, add myself to the header
> > as a contributor of this driver.
> >
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > ---
> >  drivers/staging/mt7621-pci/pci-mt7621.c | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c b/drivers/staging/mt7621-pci/pci-mt7621.c
> > index b8065b777ff6..5e80479ce653 100644
> > --- a/drivers/staging/mt7621-pci/pci-mt7621.c
> > +++ b/drivers/staging/mt7621-pci/pci-mt7621.c
> > @@ -13,6 +13,9 @@
> >   *
> >   * May 2011 Bruce Chang
> >   * support RT6855/MT7620 PCIe
> > + *
> > + * 2018-2020 Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > + * Re-write the driver for SoC mt7621
>
> That's what the maintainers file is for, and the changelog, we don't add
> new items to the top of files for this, otherwise that would just be all
> the kernel consists of :)
>

Pretty clear, thanks for letting me know.

> thanks,
>
> greg k-h

Best regards,
    Sergio Paracuellos
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2020-03-23 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 13:36 [PATCH 1/4] staging: mt7621-pci: use builtin_platform_driver() Sergio Paracuellos
2020-03-21 13:36 ` [PATCH 2/4] staging: mt7621-pci: add myself as a contributor of the driver Sergio Paracuellos
2020-03-23 10:32   ` Greg KH
2020-03-23 11:31     ` Sergio Paracuellos [this message]
2020-03-21 13:36 ` [PATCH 3/4] staging: mt7621-pci-phy: use builtin_platform_driver() Sergio Paracuellos
2020-03-21 13:36 ` [PATCH 4/4] staging: mt7621-pci-phy: re-do 'xtal_mode' detection Sergio Paracuellos

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='CAMhs-H9iO4=bQU9WRHX-J+dNKM9u48xH+27ooif6NXuHUmt38w@mail.gmail.com' \
    --to=sergio.paracuellos@gmail.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=neil@brown.name \
    /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).