From: Lee Jones <lee@kernel.org>
To: Lorenzo Egidio <lorenzoegidioms@gmail.com>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: tests: clarify name conflict test
Date: Wed, 10 Jun 2026 11:51:23 +0100 [thread overview]
Message-ID: <20260610105123.GI4151951@google.com> (raw)
In-Reply-To: <CAFxreVGVdXkp2qLGHD30TOxVMCL5RvDaT9A1jmkz_wi5Cab7-A@mail.gmail.com>
On Tue, 09 Jun 2026, Lorenzo Egidio wrote:
> Hi
>
> I noticed that theLED_REJECT_NAME_CONFLICT test in the review of LED
> KUnit tests re-registers an already registeredled_classdev instance.
>
> This patch replaces the old led_classdev instance with a new one for
> the conflictrejection test, so the test case clearly and explicitly
> deals withname-conflict handling.
>
> Besides it, struct led_lookup_data is cleared to zero.
>
> Patch for your consideration is attached.
We don't open attachments. Please send patches with `git send-email` or `b4.
Also read Documentation/process/submitting-patches.rst et al.
--
Lee Jones
prev parent reply other threads:[~2026-06-10 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 17:40 [PATCH] leds: tests: clarify name conflict test Lorenzo Egidio
2026-06-10 10:51 ` Lee Jones [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=20260610105123.GI4151951@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lorenzoegidioms@gmail.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 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.