Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: "André Draszik" <andre.draszik@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	 Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Kees Cook <kees@kernel.org>,
	"Gustavo A. R. Silva"	 <gustavoars@kernel.org>,
	Peter Griffin <peter.griffin@linaro.org>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Will McVicker <willmcvicker@google.com>,
		kernel-team@android.com, linux-kernel@vger.kernel.org,
		devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
		linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2 5/6] gpio: max77759: add Maxim MAX77759 gpio driver
Date: Fri, 28 Feb 2025 11:37:30 +0000	[thread overview]
Message-ID: <e6ab03fb87c14b1596c4f201485b49d0602c91b7.camel@linaro.org> (raw)
In-Reply-To: <d06058296a194a4f2c9fcbcc5c24816ecb1f51b1.camel@linaro.org>

On Fri, 2025-02-28 at 10:58 +0000, André Draszik wrote:
> Hi Linus,
> 
> Thanks for you review!
> 
> On Fri, 2025-02-28 at 08:10 +0100, Linus Walleij wrote:
> > Hi André,
> > 
> > thanks for your patch!
> > 
> > mostly looks fine, given the MFD design is accepted.
> > Nitpicks below:
> > 
> > On Wed, Feb 26, 2025 at 6:51 PM André Draszik <andre.draszik@linaro.org> wrote:
> > 
> > > +static irqreturn_t max77759_gpio_irqhandler(int irq, void *data)
> > > +{
> > > +       int handled = 0;
> > 
> > bool handled = false;
> > 
> > (...)
> > > +               for_each_set_bit(offset, &pending, MAX77759_N_GPIOS) {
> > > +                       unsigned int virq;
> > 
> > I usually just call this "irq", as it's not any more virtual than any other
> > Linux magic number, and it can confuse people working with
> > actual virtualization when we call things virtual like this.
> 
> Calling it 'irq' would shadow the first argument of this irq
> handler function, which is also and usually called irq and which
> I'd like to avoid shadowing.
> 
> Are you OK with 'subirq'? Or any other preference?

Actually, there's no real need for that variable, I'll just
drop it altogether:

			handle_nested_irq(irq_find_mapping(gc->irq.domain,
							   offset));

A.


  reply	other threads:[~2025-02-28 11:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 17:51 [PATCH v2 0/6] Maxim Integrated MAX77759 PMIC MFD-based drivers André Draszik
2025-02-26 17:51 ` [PATCH v2 1/6] dt-bindings: gpio: add max77759 binding André Draszik
2025-02-26 20:30   ` Rob Herring (Arm)
2025-02-27 11:19     ` André Draszik
2025-02-27 12:51       ` Rob Herring
2025-02-27 12:56         ` André Draszik
2025-02-27 13:01   ` Rob Herring (Arm)
2025-02-26 17:51 ` [PATCH v2 2/6] dt-bindings: nvmem: " André Draszik
2025-02-26 20:30   ` Rob Herring (Arm)
2025-02-27 13:05   ` Rob Herring (Arm)
2025-02-26 17:51 ` [PATCH v2 3/6] dt-bindings: mfd: " André Draszik
2025-02-27 13:04   ` Rob Herring
2025-02-27 13:13     ` André Draszik
2025-02-28 13:01       ` Rob Herring
2025-02-28 13:59         ` André Draszik
2025-02-26 17:51 ` [PATCH v2 4/6] mfd: max77759: add Maxim MAX77759 core mfd driver André Draszik
2025-02-26 17:51 ` [PATCH v2 5/6] gpio: max77759: add Maxim MAX77759 gpio driver André Draszik
2025-02-28  7:10   ` Linus Walleij
2025-02-28 10:58     ` André Draszik
2025-02-28 11:37       ` André Draszik [this message]
2025-02-26 17:51 ` [PATCH v2 6/6] nvmem: max77759: add Maxim MAX77759 NVMEM driver André Draszik

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=e6ab03fb87c14b1596c4f201485b49d0602c91b7.camel@linaro.org \
    --to=andre.draszik@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavoars@kernel.org \
    --cc=kees@kernel.org \
    --cc=kernel-team@android.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tudor.ambarus@linaro.org \
    --cc=willmcvicker@google.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