public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linux GPIO <linux-gpio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [GIT PULL] intel-gpio for 6.16-1
Date: Wed, 21 May 2025 12:24:40 +0300	[thread overview]
Message-ID: <aC2b2L5h4-0U5qjT@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=McwUF-668OYqctaahRQFPOTpXqnCZKE3R5zKsoWWEyU+w@mail.gmail.com>

On Wed, May 21, 2025 at 11:18:11AM +0200, Bartosz Golaszewski wrote:
> On Wed, May 21, 2025 at 11:12 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Wed, May 21, 2025 at 12:03:47PM +0300, Andy Shevchenko wrote:
> > > On Wed, May 21, 2025 at 10:44:16AM +0200, Bartosz Golaszewski wrote:
> > > > On Tue, May 20, 2025 at 9:45 PM Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:

...

> > > > > Bartosz Golaszewski (2):
> > > > >       gpio: graniterapids: use new line value setter callbacks
> > > > >       gpio: ich: use new line value setter callbacks
> > > >
> > > > These have been in my gpio/for-next branch for a long time and the
> > > > ones in your PR have different commit hashes. Please remove them. I
> > > > don't see any notification about you having picked those up neither in
> > > > my inbox.
> > >
> > > Really? I though I commented a few weeks ago that I prefer to take them
> > > when Stephen complained on dups. After that there were no dups noticed.
> > > Since you haven't answered to that email, I (rightfully) assumed you are
> > > okay with the proposed course of actions.
> >
> > FWIW, check your mailbox:
> > https://lore.kernel.org/linux-gpio/Z_OUr5xvoXh-sFne@smile.fi.intel.com/
> > https://lore.kernel.org/linux-gpio/Z_OS4nx2E12yjL7_@smile.fi.intel.com/
> > https://lore.kernel.org/linux-gpio/Z__xUsSeYNQAvnNp@smile.fi.intel.com/
> > https://lore.kernel.org/linux-next/aAEkrx0P5LFj1r6a@smile.fi.intel.com/
> >
> > Note the last one, you didn't respond. So?
> 
> I really don't have them. Neither of the three. Probably gmail spam
> filter borked? Anyway, would you mind removing them from your PR?

Okay for this. But let's talk *again* about maintainership of
the Intel GPIO drivers.  Last time we discussed that you have
agreed that I'm in charge of that. If you think otherwise,
let me know.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-05-21  9:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 19:45 [GIT PULL] intel-gpio for 6.16-1 Andy Shevchenko
2025-05-21  8:44 ` Bartosz Golaszewski
2025-05-21  9:03   ` Andy Shevchenko
2025-05-21  9:12     ` Bartosz Golaszewski
2025-05-21  9:12     ` Andy Shevchenko
2025-05-21  9:18       ` Bartosz Golaszewski
2025-05-21  9:24         ` Andy Shevchenko [this message]
2025-05-21  9:29           ` Bartosz Golaszewski
2025-05-21  9:31             ` Andy Shevchenko
2025-05-21  9:50               ` Andy Shevchenko
2025-05-21 10:11                 ` Bartosz Golaszewski

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=aC2b2L5h4-0U5qjT@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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