mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] checkpatch: Adapt comment to mod_devicetable.h split
Date: Wed, 11 Nov 2026 10:08:45 +0100	[thread overview]
Message-ID: <avQwfW1HRIrMcp8i@monoceros> (raw)
In-Reply-To: <20260706090748.3809275-2-u.kleine-koenig@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Hello,

On Mon, Jul 06, 2026 at 11:07:48AM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> <linux/mod_devicetable.h> was split in commit v7.2-rc2~18^2~16 =
> ad428f5811bd ("mod_devicetable.h: Split into per subsystem headers").
> Adapt the comment in checkpatch.pl accordingly.
> 
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
>  scripts/checkpatch.pl | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 2b7a42bbdd94..5a3d0516c4ec 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -700,7 +700,7 @@ our $tracing_logging_tags = qr{(?xi:
>  	[\.\!:\s]*
>  )};
>  
> -# Device ID types like found in include/linux/mod_devicetable.h.
> +# Device ID types like found in include/linux/device-id/*.h.
>  our $dev_id_types = qr{\b[a-z]\w*_device_id\b};
>  
>  sub edit_distance_min {
> 
> base-commit: 8cdeaa50eae8dad34885515f62559ee83e7e8dda

This patch still applies fine to next-20261110, is it still on someone's
radar?

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

      reply	other threads:[~2026-11-11  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  9:07 Uwe Kleine-König (The Capable Hub)
2026-11-11  9:08 ` Uwe Kleine-König (The Capable Hub) [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=avQwfW1HRIrMcp8i@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®