Linux LED subsystem development
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Arunachalam <arun07172003@gmail.com>
Cc: Pavel Machek <pavel@kernel.org>,
	Andreas Werner <andreas.werner@men.de>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] leds: cobalt-raq: Add missing MODULE_DESCRIPTION
Date: Thu, 6 Aug 2026 14:53:01 +0100	[thread overview]
Message-ID: <20260806135301.GH2869284@google.com> (raw)
In-Reply-To: <20260725081349.8556-1-arun07172003@gmail.com>

On Sat, 25 Jul 2026, Arunachalam wrote:

> Add the missing MODULE_DESCRIPTION() macro, which is required by
> modpost and was missing from this driver.
> 
> Signed-off-by: Arunachalam <arun07172003@gmail.com>

This set is un-reviewable.

Please submit both sets again separately.

-- 
Lee Jones

  parent reply	other threads:[~2026-08-06 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  8:13 [PATCH v3 1/4] leds: cobalt-raq: Add missing MODULE_DESCRIPTION Arunachalam
2026-07-25  8:13 ` [PATCH v3 2/4] leds: lp8788: Convert to dev_err_probe() Arunachalam
2026-07-25  8:21   ` sashiko-bot
2026-07-25  8:13 ` [PATCH v3 3/4] leds: menf21bmc: " Arunachalam
2026-07-25  8:19   ` sashiko-bot
2026-07-25 17:51     ` [PATCH 1/2] leds: menf21bmc: Use brightness_set_blocking instead of brightness_set Arunachalam
2026-07-25  8:13 ` [PATCH v3 4/4] leds: 88pm860x: Convert to dev_err_probe() Arunachalam
2026-07-25  8:19   ` sashiko-bot
2026-07-25  8:20 ` [PATCH v3 1/4] leds: cobalt-raq: Add missing MODULE_DESCRIPTION sashiko-bot
2026-07-25 17:52   ` [PATCH 2/2] leds: cobalt-raq: Use devm_led_classdev_register() to fix use-after-unmap Arunachalam
2026-08-06 13:53 ` Lee Jones [this message]
2026-08-06 13:53   ` [PATCH v3 1/4] leds: cobalt-raq: Add missing MODULE_DESCRIPTION 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=20260806135301.GH2869284@google.com \
    --to=lee@kernel.org \
    --cc=andreas.werner@men.de \
    --cc=arun07172003@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    /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