linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Kuppuswamy Sathyanarayanan 
	<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: [PATCH v1 1/3] gpio: pca953x: Request IRQ after all initialisation done
Date: Tue, 4 Aug 2020 01:26:12 +0200	[thread overview]
Message-ID: <CACRpkdbx63cDuG7-wwroGsKuyGOdSxKxwAf7OdTRBGute2P0Kw@mail.gmail.com> (raw)
In-Reply-To: <20200728125504.27786-1-andriy.shevchenko@linux.intel.com>

On Tue, Jul 28, 2020 at 2:55 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:

> There is logically better to request IRQ when we initialise all structures.
> Align the driver with the rest on the same matter.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

I just applied these three (despite 2 & 3 hitting Intel drivers) since
we are in the
merge window and it needs to be in good shape for the merge.

Thanks!
Linus Walleij

  parent reply	other threads:[~2020-08-03 23:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 12:55 [PATCH v1 1/3] gpio: pca953x: Request IRQ after all initialisation done Andy Shevchenko
2020-07-28 12:55 ` [PATCH v1 2/3] gpio: crystalcove: Free IRQ on error path Andy Shevchenko
2020-07-28 12:55 ` [PATCH v1 3/3] gpio: wcove: Request IRQ after all initialisation done Andy Shevchenko
2020-08-03 23:26 ` Linus Walleij [this message]
2020-08-04  9:12   ` [PATCH v1 1/3] gpio: pca953x: " Andy Shevchenko

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=CACRpkdbx63cDuG7-wwroGsKuyGOdSxKxwAf7OdTRBGute2P0Kw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=sathyanarayanan.kuppuswamy@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;
as well as URLs for NNTP newsgroup(s).