linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: andy.shevchenko@gmail.com
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Linus Walleij <linus.walleij@linaro.org>,
	Prathamesh Shete <pshete@nvidia.com>,
	thierry.reding@gmail.com, bgolaszewski@baylibre.com,
	linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, smangipudi@nvidia.com,
	kyarlagadda@nvidia.com, Manish Bhardwaj <mbhardwaj@nvidia.com>
Subject: Re: [PATCH v3] gpio: tegra186: Check GPIO pin permission before access.
Date: Tue, 23 May 2023 19:32:48 +0300	[thread overview]
Message-ID: <ZGzqsGG7uTYkO7Uf@surfacebook> (raw)
In-Reply-To: <a3d7c16f-fe87-9c04-5f92-42f10597df6d@nvidia.com>

Tue, May 23, 2023 at 02:42:52PM +0100, Jon Hunter kirjoitti:
> On 23/05/2023 10:17, Bartosz Golaszewski wrote:
> > On Tue, May 23, 2023 at 8:22 AM Jon Hunter <jonathanh@nvidia.com> wrote:
> > > On 17/10/2022 10:31, Linus Walleij wrote:

...

> > > I did not see this anywhere in the mainline/next. However, I also
> > > noticed that we don't have the correct email address for Bartosz (again).
> > 
> > I have only ever changed my address in MAINTAINERS once, so "again" is
> > not really the right term. And scripts/get_maintainer.pl should be
> > used anyway every time when submitting patches.
> 
> Sorry I meant that WE did not send to the correct email AGAIN and not that
> you updated your email address :-)

FWIW, you may look into my "smart" script [1] which automatically fills the Cc
and To WRT MAINTAINERS records.

[1]: https://lore.kernel.org/linux-gpio/Yz62XmiH8YG3Dtsf@orome/T/#t

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-05-23 16:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 12:21 [PATCH] gpio: tegra186: Check GPIO pin permission before access Prathamesh Shete
2022-09-14 13:22 ` Thierry Reding
2022-10-04  7:48   ` [PATCH v2] " Prathamesh Shete
2022-10-06 11:05     ` Thierry Reding
2022-10-07  5:59       ` [PATCH v3] " Prathamesh Shete
2022-10-07 10:25         ` Thierry Reding
2022-10-17  9:31         ` Linus Walleij
2023-05-23  6:22           ` Jon Hunter
2023-05-23  9:17             ` Bartosz Golaszewski
2023-05-23 13:42               ` Jon Hunter
2023-05-23 16:32                 ` andy.shevchenko [this message]
2023-05-23 16:43                   ` andy.shevchenko
2023-05-24 10:50                     ` [PATCH v4] " Prathamesh Shete
2023-05-26 12:29                       ` Bartosz Golaszewski
2022-09-14 13:43 ` [PATCH] " Linus Walleij

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=ZGzqsGG7uTYkO7Uf@surfacebook \
    --to=andy.shevchenko@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=jonathanh@nvidia.com \
    --cc=kyarlagadda@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mbhardwaj@nvidia.com \
    --cc=pshete@nvidia.com \
    --cc=smangipudi@nvidia.com \
    --cc=thierry.reding@gmail.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 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).