All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] lib: tst_kconfig: Add runtime checks
Date: Thu, 26 Mar 2026 15:38:39 +0100	[thread overview]
Message-ID: <acVE76yDEM8pymPW@yuki.lan> (raw)
In-Reply-To: <20260205174756.GA338897@pevik>

Hi!
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> nit: please use /* */ otherwise checkpatch complains.

Hmm, so apparently kernel has a bit crazy rule that the SPDX has to be
between /* */ in headers and start with // in C sources. Because of some
tooling that parses kernel headers couldn't handle //.

I do not think that there will be any tooling parsing LTP internal
headers. Maybe we can silence that rule in checkpatch?

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2026-03-26 14:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 13:57 [LTP] [PATCH] lib: tst_kconfig: Add runtime checks Cyril Hrubis
2026-02-05 17:47 ` Petr Vorel
2026-02-06  7:58   ` Li Wang via ltp
2026-02-06  8:23     ` Petr Vorel
2026-02-06 12:23       ` Li Wang via ltp
2026-03-26 14:09         ` Cyril Hrubis
2026-03-26 14:16           ` Cyril Hrubis
2026-03-26 16:39           ` Petr Vorel
2026-02-06  8:23     ` Petr Vorel
2026-02-06  8:33     ` Cyril Hrubis
2026-02-06  9:31       ` Petr Vorel
2026-02-06  9:37       ` Petr Vorel
2026-02-06  9:45         ` Cyril Hrubis
2026-02-06 10:31           ` Petr Vorel
2026-03-26 14:38   ` Cyril Hrubis [this message]
2026-03-26 15:44     ` Petr Vorel
2026-03-11  8:59 ` Petr Vorel
2026-03-24  8:33 ` Andrea Cervesato via ltp
2026-03-26 14:17   ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2026-03-26 14:40 Cyril Hrubis
2026-03-26 15:15 ` Petr Vorel
2026-03-27  7:02 ` Li Wang via ltp
2026-03-27 11:06   ` Cyril Hrubis

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=acVE76yDEM8pymPW@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.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.