All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Manuel Fombuena <fombuena@outlook.com>
Cc: pavel@ucw.cz, corbet@lwn.net, linux-leds@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 1/5] leds: leds-st1202: fix NULL pointer access on race condition
Date: Thu, 20 Feb 2025 15:01:23 +0000	[thread overview]
Message-ID: <20250220150123.GD778229@google.com> (raw)
In-Reply-To: <CWLP123MB54739D3E587725A0E408E2E3C5FF2@CWLP123MB5473.GBRP123.PROD.OUTLOOK.COM>

On Thu, 13 Feb 2025, Manuel Fombuena wrote:

> On Thu, 13 Feb 2025, Lee Jones wrote:
> 
> > Then you need to separate the set into patches you expect to be
> > submitted to the -rcs and ones which can be applied during the next
> > cycle, then go to lengths to explain that either in the diff section of
> > each patch (preferred) or in the cover-letter.
> 
> One question so I don't take more of your time later on on this. Should I 
> continue the set with 5 patches as v2, applying the above and the other 
> comments, or would it be preferable to send this patch with its 
> cover letter separately and drop it from this set?

This and any other patches due for the -rcs need splitting out.

Please submit them all again.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-02-20 15:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-01 13:00 [PATCH RESEND 0/5] LED1202 / leds-st1202 fixes and improvements Manuel Fombuena
2025-02-01 13:02 ` [PATCH RESEND 1/5] leds: leds-st1202: fix NULL pointer access on race condition Manuel Fombuena
2025-02-11 13:31   ` Lee Jones
2025-02-12 16:28     ` Manuel Fombuena
2025-02-13 10:24       ` Lee Jones
2025-02-13 15:25         ` Manuel Fombuena
2025-02-20 15:01           ` Lee Jones [this message]
2025-02-11 13:34   ` Lee Jones
2025-02-12 13:16     ` Manuel Fombuena
2025-02-01 13:04 ` [PATCH RESEND 2/5] leds: leds-st1202: initialize hardware before DT node child operations Manuel Fombuena
2025-02-11 13:32   ` Lee Jones
2025-02-12 15:15     ` Manuel Fombuena
2025-02-01 13:04 ` [PATCH RESEND 3/5] leds: leds-st1202: spacing and proofreading editing Manuel Fombuena
2025-02-11 13:34   ` Lee Jones
2025-02-12 14:28     ` Manuel Fombuena
2025-02-01 13:05 ` [PATCH RESEND 4/5] leds: Kconfig: leds-st1202: add select for required LEDS_TRIGGER_PATTERN Manuel Fombuena
2025-02-01 13:07 ` [PATCH RESEND 5/5] Documentation: leds: remove .rst extension for leds-st1202 on index Manuel Fombuena
2025-02-13 10:41 ` [PATCH RESEND 0/5] LED1202 / leds-st1202 fixes and improvements Lee Jones
2025-02-13 15:54   ` Manuel Fombuena
2025-02-20 15:03     ` Lee Jones

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=20250220150123.GD778229@google.com \
    --to=lee@kernel.org \
    --cc=corbet@lwn.net \
    --cc=fombuena@outlook.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.