linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arturas Moskvinas <arturas.moskvinas@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linus.walleij@linaro.org, biju.das.jz@bp.renesas.com,
	akaessens@gmail.com, thomas.preston@codethink.co.uk,
	preid@electromag.com.au, u.kleine-koenig@pengutronix.de,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	arturas.moskvinas@gmail.com
Subject: Re: [PATCH v2] pinctrl: mcp23s08: Check only GPIOs which have interrupts enabled
Date: Wed, 7 Feb 2024 12:50:51 +0200	[thread overview]
Message-ID: <0dab8d77-ea4e-4cea-99dd-2ffe7c9051d5@gmail.com> (raw)
In-Reply-To: <ZcDpDaclAXEa5ETN@smile.fi.intel.com>

On 2/5/24 15:56, Andy Shevchenko wrote:
>> Do you want that information to be added as part of commit message or
>> information in the mailing thread will be enough?
> Up to maintainers. I'm fine with this email. If Linus uses b4 to generate
> a Link tag to this discussion it will be enough (in my opinion).

Is there anything left for me to update/change? Or we're waiting for 
other reviewers and/or Linus to chime in?

Arturas Moskvinas

  reply	other threads:[~2024-02-07 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 13:56 [PATCH v2] pinctrl: mcp23s08: Check only GPIOs which have interrupts enabled Andy Shevchenko
2024-02-07 10:50 ` Arturas Moskvinas [this message]
2024-02-07 14:48   ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2024-02-01 14:14 Arturas Moskvinas
2024-02-01 14:30 ` Andy Shevchenko
2024-02-02 10:40   ` Arturas Moskvinas
2024-02-08 13:46 ` 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=0dab8d77-ea4e-4cea-99dd-2ffe7c9051d5@gmail.com \
    --to=arturas.moskvinas@gmail.com \
    --cc=akaessens@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preid@electromag.com.au \
    --cc=thomas.preston@codethink.co.uk \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).