U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Cc: Matthew Garrett <mgarrett@aurora.tech>,
	Emil Kronborg <emil.kronborg@protonmail.com>,
	Francis Laniel <francis.laniel@amarulasolutions.com>,
	Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Jerome Forissier <jerome.forissier@linaro.org>,
	Jonas Karlman <jonas@kwiboo.se>,
	Maxim Moskalets <maximmosk4@gmail.com>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Wang Jie <dave.wang@rock-chips.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 3/8] doc: test: Add docs and test for part_find
Date: Mon, 16 Dec 2024 09:05:42 +0100	[thread overview]
Message-ID: <33FA4F32-AD4F-438C-BE53-F89DA5FCC86B@gmx.de> (raw)
In-Reply-To: <CAFLszThPgtngJM16oCcOD1oCJNzpdn7We0=OB6E41XRHokxDuA@mail.gmail.com>

Am 16. Dezember 2024 01:29:04 MEZ schrieb Simon Glass <sjg@chromium.org>:
>Hi Tom,
>
>On Tue, 10 Dec 2024 at 10:09, Tom Rini <trini@konsulko.com> wrote:
>>
>> On Tue, Dec 10, 2024 at 09:16:57AM -0700, Simon Glass wrote:
>> > Hi Heinrich,
>> >
>> > On Tue, 10 Dec 2024 at 01:16, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>> > >
>> > > On 09.12.24 17:27, Simon Glass wrote:
>> > > > Add some documentation and a test for this new command.
>> > >
>> > > Shouldn't this be two patches?
>> >
>> > Often we put the new command, its docs and tests in the same commit,
>> > since the question I always ask when looking at a command is, where
>> > are the docs and tests!
>> >
>> > >
>> > > >
>> > > > Signed-off-by: Simon Glass <sjg@chromium.org>
>> > > > ---
>> > > >
>> > > >   doc/usage/cmd/part_find.rst | 119 ++++++++++++++++++++++++++++++++++++
>> > > >   doc/usage/index.rst         |   1 +
>> > > >   test/cmd/Makefile           |   1 +
>> > > >   test/cmd/part_find.c        |  42 +++++++++++++
>> > > >   4 files changed, 163 insertions(+)
>> > > >   create mode 100644 doc/usage/cmd/part_find.rst
>> > > >   create mode 100644 test/cmd/part_find.c
>> > > >
>> > > > diff --git a/doc/usage/cmd/part_find.rst b/doc/usage/cmd/part_find.rst
>> > > > new file mode 100644
>> > > > index 00000000000..fd5bd6578d5
>> > > > --- /dev/null
>> > > > +++ b/doc/usage/cmd/part_find.rst
>> > > > @@ -0,0 +1,119 @@
>> > > > +.. SPDX-License-Identifier: GPL-2.0+:
>> > >
>> > > This is not a valid SPDX identifier.
>> > > Cf. https://spdx.org/licenses/GPL-2.0-or-later.html
>> >
>> > I have seen this point made a few times, but I'm afraid I still don't
>> > fully understand it:
>> >
>> > The Licenses/README lists the licenses and GPL-2.0+ appears in there.
>> > In the source tree:
>> >
>> > $ git grep GPL-2.0+ |wc -l
>> > 13406
>> > $ git grep GPL-2.0-or-later |wc -l
>> > 1847
>> >
>> > I have to say I much prefer GPL-2.0+ as it is easier to remember.
>> >
>> > But if we are planning to change, could you update checkpatch to throw
>> > a warning?
>>
>> As I've said before too, GPL-2.0+ is deprecated by SPDX and
>> GPL-2.0-or-later is the correct tag. But we aren't, sadly, right now a
>> best practices example for SPDX anyhow and so it's not a deal breaker to
>> use the old tag, just something that should be avoided.
>
>OK, I will try to remember this.
>
>At minimum, if this is important, Licenses/README should be updated to
>drop the old license?
>
>Heinrich, please update checkpatch to warn about this.
>
>Regards,
>Simon

See
<https://lore.kernel.org/u-boot/20241215023732.68902-1-heinrich.schuchardt@canonical.com/>


  reply	other threads:[~2024-12-16  8:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 16:27 [PATCH 0/8] efi: Add docs and tests and a few tweaks Simon Glass
2024-12-09 16:27 ` [PATCH 1/8] fdtdec: Correct devicetree symbol for EFI app Simon Glass
2024-12-09 16:27 ` [PATCH 2/8] part_find: Enable for sandbox and correct radix and calls Simon Glass
2024-12-09 16:27 ` [PATCH 3/8] doc: test: Add docs and test for part_find Simon Glass
2024-12-10  8:15   ` Heinrich Schuchardt
2024-12-10 16:16     ` Simon Glass
2024-12-10 17:08       ` Tom Rini
2024-12-16  0:29         ` Simon Glass
2024-12-16  8:05           ` Heinrich Schuchardt [this message]
2024-12-09 16:27 ` [PATCH 4/8] efi: Drop config.h Simon Glass
2024-12-09 16:27 ` [PATCH 5/8] cmd: Refactor part_find() into separate functions Simon Glass
2024-12-09 16:27 ` [PATCH 6/8] addr_find: Use a simple lmb allocation Simon Glass
2024-12-09 16:28 ` [PATCH 7/8] doc: test: Add docs and test for addr_find Simon Glass
2024-12-09 16:28 ` [PATCH 8/8] efi: Avoid a memory leak in efi_bind_block() on error path Simon Glass
2024-12-10  8:10   ` Heinrich Schuchardt
2024-12-16 15:15     ` Simon Glass

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=33FA4F32-AD4F-438C-BE53-F89DA5FCC86B@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=dave.wang@rock-chips.com \
    --cc=emil.kronborg@protonmail.com \
    --cc=francis.laniel@amarulasolutions.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jerome.forissier@linaro.org \
    --cc=jonas@kwiboo.se \
    --cc=maximmosk4@gmail.com \
    --cc=mgarrett@aurora.tech \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=sebastian.reichel@collabora.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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