From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH blktests] block/044: basic block error injection sanity test
Date: Sat, 27 Jun 2026 13:06:29 +0900 [thread overview]
Message-ID: <aj9KzVlDI29qvLWe@shinmob> (raw)
In-Reply-To: <20260626045650.GA8752@lst.de>
On Jun 26, 2026 / 06:56, Christoph Hellwig wrote:
> On Fri, Jun 26, 2026 at 01:31:06PM +0900, Shin'ichiro Kawasaki wrote:
> > > > Nit: Majority of the blktests test cases have GPL-3.0+. If you do not mind,
> > > > I suggest GPL-3.0+.
> > >
> > > Well a mix of licenses is obviously bad, although I hate the GPL 3 with
> > > passion.
> >
> > I see, I respoect author's choice.
>
> Well, if the common bits are GPLv3+ we can't actually legally combine
> them with test that have a pure GPLv2 license. So I need at least
> GPL-2.0+.
I see... I read back GPLv2 and v3. My understanding is that:
- GPL v3 adds additional restrictions on top of v2, such as section 6
"Installation information" or section 3 "Legal Rights from Antci-
Circumvention Law".
- The v3 additions conflict with the GPL v2 section6, that says:
"You may not impose any further restrictions on the recepients'
excercise of the rights granted here in."
>
> And we need to as a few authors to also fix this up for:
>
> block/029
> block/030
> block/031
> block/040
> block/042
> block/043
> block/044
Thanks. I will list up original authors and contributors of the test cases,
and then bring up license fix up discussion.
prev parent reply other threads:[~2026-06-27 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 16:08 [PATCH blktests] block/044: basic block error injection sanity test Christoph Hellwig
2026-06-25 6:36 ` Shin'ichiro Kawasaki
2026-06-25 11:54 ` Christoph Hellwig
2026-06-26 4:31 ` Shin'ichiro Kawasaki
2026-06-26 4:56 ` Christoph Hellwig
2026-06-27 4:06 ` Shin'ichiro Kawasaki [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=aj9KzVlDI29qvLWe@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@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 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.