From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] gpiolib: acpi: Add support to ignore programming an interrupt
Date: Mon, 29 Aug 2022 22:26:00 +0300 [thread overview]
Message-ID: <Yw0SyH9nwpk6Ymsw@smile.fi.intel.com> (raw)
In-Reply-To: <MN0PR12MB610137D56D08C873C7647A9CE2769@MN0PR12MB6101.namprd12.prod.outlook.com>
On Mon, Aug 29, 2022 at 06:16:45PM +0000, Limonciello, Mario wrote:
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Friday, August 26, 2022 12:32
> > On Wed, Aug 03, 2022 at 05:07:15PM +0200, Hans de Goede wrote:
> > > On 8/3/22 06:24, Mario Limonciello wrote:
...
> > > Thanks, patch looks good to me:
> > >
> > > Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> >
> > Pushed to my review and testing queue, thanks!
> Just to double check, you meant you took both patches, not just the first right?
Yes, I took 2 patches. To reduce a confusion I highly recommend to send a
series with a cover letter, so the answer to it will definitely be equal to
"yes, I have took all of them" if nothing else specified.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-08-29 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 4:24 [PATCH v2 1/2] gpiolib: acpi: Add support to ignore programming an interrupt Mario Limonciello
2022-08-03 4:25 ` [PATCH v2 2/2] gpiolib: acpi: Add a quirk for Asus UM325UAZ Mario Limonciello
2022-08-03 9:50 ` Mika Westerberg
2022-08-03 9:47 ` [PATCH v2 1/2] gpiolib: acpi: Add support to ignore programming an interrupt Mika Westerberg
2022-08-03 15:07 ` Hans de Goede
2022-08-26 17:31 ` Andy Shevchenko
2022-08-29 18:16 ` Limonciello, Mario
2022-08-29 19:26 ` Andy Shevchenko [this message]
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=Yw0SyH9nwpk6Ymsw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Mario.Limonciello@amd.com \
--cc=brgl@bgdev.pl \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox