From: Mary Strodl <mstrodl@csh.rit.edu>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpio: mpsse: support bryx radio interface kit
Date: Wed, 10 Sep 2025 10:39:30 -0400 [thread overview]
Message-ID: <aMGNoqRaUf722QrF@ada.csh.rit.edu> (raw)
In-Reply-To: <CAMRc=MfSOTTBv3spbyiedpMifMyfmTkpmbvuDuKcbs5S1B+Esg@mail.gmail.com>
On Wed, Sep 10, 2025 at 03:46:03PM +0200, Bartosz Golaszewski wrote:
> If these are bugfixes that should be backported to stable then they
> should indeed come first.
Yeah I agree... I'll try my best :)
To be fair, in practice this can never happen with the hardware that
implements this since it can't do hotplug.
...With that said, I think you can bind it to another device with
new_id so maybe it would still be good to backport? Dunno.
On Wed, Sep 10, 2025 at 03:46:03PM +0200, Bartosz Golaszewski wrote:
> FYI: Maybe consider also adding lock guards for rcu read locks if you're at it?
I'll take a look! I didn't notice there were guards for rcu when I
was working on this.
Thank you!
next prev parent reply other threads:[~2025-09-10 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 17:38 [PATCH] gpio: mpsse: support bryx radio interface kit Mary Strodl
2025-09-09 13:32 ` kernel test robot
2025-09-10 12:47 ` Mary Strodl
2025-09-10 13:15 ` Bartosz Golaszewski
2025-09-10 13:29 ` Mary Strodl
2025-09-10 13:46 ` Bartosz Golaszewski
2025-09-10 14:39 ` Mary Strodl [this message]
2025-09-10 14:55 ` Geert Uytterhoeven
2025-09-10 14:59 ` Mary Strodl
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=aMGNoqRaUf722QrF@ada.csh.rit.edu \
--to=mstrodl@csh.rit.edu \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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