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 09:29:36 -0400 [thread overview]
Message-ID: <aMF9QFIvXC5kI_9J@ada.csh.rit.edu> (raw)
In-Reply-To: <CAMRc=McBdJ16RYvJM_R7pL+u3zcs_+A0nj5_5twP7KxWhW6VDw@mail.gmail.com>
On Wed, Sep 10, 2025 at 03:15:46PM +0200, Bartosz Golaszewski wrote:
> I cannot really give you much feedback because this patch should be
> first split into smaller chunks that explain what each change is
> doing. As it is: it's so complex, I simply don't understand it and
> don't have enough time to try and decipher it. Please try to make it
> into a series of smaller patches.
Got it. That's why I offered to break it up.
Here's the order I did the work in:
1. Add quirk support + brik quirk
2. Label format (Only a few lines, could go into 1 or 3 if preferred)
3. RCU stuff
Is this a reasonable order for the series? This would be the easiest
way for me to do it given what I have in git.
In a perfect world, I would like to have had:
1. RCU stuff (These are effectively bugfixes)
2. Label stuff
3. Quirks
4. Brik quirk (possibly squashed into 3)
Let me know what you think... Thank you!
next prev parent reply other threads:[~2025-09-10 13:29 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 [this message]
2025-09-10 13:46 ` Bartosz Golaszewski
2025-09-10 14:39 ` Mary Strodl
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=aMF9QFIvXC5kI_9J@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