public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andriy Shevencho <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee@kernel.org>
Cc: Jonathan Brophy <Professor_jonny@hotmail.com>,
	Jonathan Brophy <professorjonny98@gmail.com>,
	Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Radoslav Tsvetkov <rtsvetkov@gradotech.eu>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH v5 0/7] leds: Add virtual LED group driver with priority arbitration
Date: Thu, 15 Jan 2026 18:58:44 +0200	[thread overview]
Message-ID: <aWkcxGHINusTftex@smile.fi.intel.com> (raw)
In-Reply-To: <20260115150725.GF2842980@google.com>

On Thu, Jan 15, 2026 at 03:07:25PM +0000, Lee Jones wrote:
> On Tue, 13 Jan 2026, Jonathan Brophy wrote:
> 
> > >>  drivers/leds/rgb/Kconfig                      |   17 +
> > >>  drivers/leds/rgb/Makefile                     |    1 +
> > >>  drivers/leds/rgb/leds-group-virtualcolor.c    | 3360 +++++++++++++++++
> > 
> > >This is an unreasonable request to ask of any reviewer.  I certainly don't have the time to go through this in any level of detail.
> > 
> > >--
> > >Lee Jones [李琼斯]
> > 
> > Hi Yes it Is a big lump of code
> > I will break this down into features and separate the driver in to sub 600 lines of code in a future patch.
> > 
> > I'm a junior coder It is easier for me to compute as a single file but yes you are correct it is daunting.
> > 
> > Ill finish additions and features first then send an update patch with the driver separated for ease of review in the future.
> > I expect the code to split nicely into separate sections as the below layout: 
> > core.c
> > arbitration.c
> > phys.c
> > vled.c
> > debugfs.c
> > virtualcolor.h
> > 
> > Would this be a better arrangement ?
> 
> Patches should build on each other in terms of functionality, not filename.

While I am 100% with Lee here, the filenames strictly speaking are orthogonal
to the patch split. But they are still helpful for the end result. So think
about both file split and patch split (and the latter one in terms like Lee
described below).

> The first patch should provide just enough functionality to be useful.
> 
> Then build it up one piece at a time.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2026-01-15 16:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  8:23 [PATCH v5 0/7] leds: Add virtual LED group driver with priority arbitration Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 1/7] dt-bindings: leds: add function virtual_status to led common properties Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 2/7] dt-bindings: leds: Add virtual LED class bindings Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 3/7] dt-bindings: leds: Add virtual LED group controller bindings Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 4/7] ABI: Add sysfs documentation for leds-group-virtualcolor Jonathan Brophy
2025-12-30 11:52   ` Andriy Shevencho
2025-12-30  8:23 ` [PATCH v5 5/7] leds: Add driver " Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 6/7] leds: Add fwnode_led_get() for firmware-agnostic LED resolution Jonathan Brophy
2025-12-30 12:00   ` Andriy Shevencho
2025-12-31  2:30   ` kernel test robot
2025-12-31 23:37   ` kernel test robot
2025-12-31 23:45   ` kernel test robot
2026-01-02 12:20   ` kernel test robot
2026-01-02 15:07   ` kernel test robot
2026-01-02 16:29   ` kernel test robot
2025-12-30  8:23 ` [PATCH v5 7/7] leds: Add virtual LED group driver with priority arbitration Jonathan Brophy
2025-12-30 12:19   ` Andriy Shevencho
2026-01-03  8:22     ` [PATCH v5 7/7] leds: Add virtual LED group driver Jonathan Brophy
2026-01-03 12:56       ` Andriy Shevencho
2026-01-06 16:59 ` [PATCH v5 0/7] leds: Add virtual LED group driver with priority arbitration Rob Herring
2026-01-13 11:52   ` Lee Jones
2026-01-13 11:57 ` Lee Jones
2026-01-13 20:35   ` Jonathan Brophy
2026-01-15 15:07     ` Lee Jones
2026-01-15 16:58       ` Andriy Shevencho [this message]

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=aWkcxGHINusTftex@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Professor_jonny@hotmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=professorjonny98@gmail.com \
    --cc=robh@kernel.org \
    --cc=rtsvetkov@gradotech.eu \
    /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