All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linux GPIO <linux-gpio@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Daniel Scally <djrscally@gmail.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [GIT PULL] intel-gpio for 5.14-1
Date: Mon, 5 Jul 2021 11:20:15 +0200	[thread overview]
Message-ID: <cb18b7d2-8636-feed-e9f8-212ce7aa7eff@redhat.com> (raw)
In-Reply-To: <75eae548-fd62-1be6-498d-9664d9c7deab@redhat.com>

Hi,

On 7/5/21 11:16 AM, Hans de Goede wrote:
> Hi,
> 
> On 7/5/21 11:03 AM, Bartosz Golaszewski wrote:
>> On Mon, Jun 14, 2021 at 5:09 PM Andy Shevchenko
>> <andriy.shevchenko@linux.intel.com> wrote:
>>>
>>> On Mon, Jun 07, 2021 at 06:12:10PM +0300, Andy Shevchenko wrote:
>>>> Hi Linux GPIO and TWIMC maintainers,
>>>>
>>>> This is GPIO material for v5.14 cycle. It contains some stuff that other
>>>> subsystems may take due to dependencies. Consider this tag immutable.
>>>
>>> Bart, any comments on this? Can you, please, pull?
>>>
>>> --
>>> With Best Regards,
>>> Andy Shevchenko
>>>
>>>
>>
>> Hi Andy,
>>
>> I was looking for you PR for this cycle and couldn't find it in my
>> inbox. Somehow this went into spam. I'll make sure your email never
>> goes to spam again. Sorry. I'm seeing Hand pulled it, is that right?
>>
>> Hans: did you take the entire thing?
> 
> Andy send me a pull-req for the intel-gpio-v5.14-1 tag because that
> contained some dependencies for a new driver which I was merging into
> drivers/platform/x86.
> 
> Given the name of the tag (and the contents) I think it is the entire
> thing and not a topic branch with just the things which the driver needed,
> I assume the pull-req Andy send to you probably also was for that tag?
> 
> If that is right then this indeed has already landed in Linus' tree
> through the platform-drivers-x86 tree.

I just noticed that this email is part of the same thread as the
pull-req which I merged, IOW it is the same pull-req as which ended
up in your spam folder.

So yes I believe that I took the entire thing.

Regards,

Hans


  reply	other threads:[~2021-07-05  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 15:12 [GIT PULL] intel-gpio for 5.14-1 Andy Shevchenko
2021-06-14 15:08 ` Andy Shevchenko
2021-07-05  9:03   ` Bartosz Golaszewski
2021-07-05  9:16     ` Hans de Goede
2021-07-05  9:20       ` Hans de Goede [this message]
2021-07-05  9:35         ` Andy Shevchenko
2021-06-16 14:41 ` Hans de Goede

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=cb18b7d2-8636-feed-e9f8-212ce7aa7eff@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=djrscally@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.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.