From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
Ming Lei <ming.lei@redhat.com>, Ming Lei <tom.leiming@gmail.com>,
Keith Busch <kbusch@kernel.org>, Yi Zhang <yi.zhang@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Li Zhijian <lizhijian@fujitsu.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
John Pittman <jpittman@redhat.com>
Subject: Re: blktests: call for agreement to relicense GPL-2.0 files
Date: Mon, 27 Jul 2026 13:10:41 +0900 [thread overview]
Message-ID: <ama1svBbdVfyEKz1@shinmob> (raw)
In-Reply-To: <akyeX0hlcrnOC0nT@shinmob>
Three weeks have passed since my call for agreement. Thank you very much to
those who responded. There was no objection to the change. I conclude that
the agreement has been made, and would like to take the next step for the fix.
- John Pittman did not respond, but I confirmed off-list that he has no
objection to the change.
- I did not get a response from Yi Zhang's Red Hat address. I tried to reach Yi
Zhang via the e-mail address on Yi Zhang's GitHub account, but received no
response there either. I concluded it is not productive to wait any longer.
Yi Zhang's contributions to the relevant source files are the two commits
below:
A) 38fc272ee91f ("tests/block: add the missing _have_fio check for block/029 block/031")
B) 06cd1d595571 ("block/031: remove the fio verify.state file")
These are small changes that added a couple of _have_fio calls and a fio
option. I think it is reasonable to consider the changes as "de minimis"
and they do not prevent the relicense.
Bart, Ming and Keith,
May I ask you to create and post a patch to change the license of the files
you authored from GPL-2.0 to GPL-3.0+?
- Bart: block/029,030,031
Contributors: Christoph Hellwig <hch@lst.de>
Li Zhijian <lizhijian@fujitsu.com>
Akinobu Mita <akinobu.mita@gmail.com>
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
- Ming: block/040
- Keith: block/042,043, src/dio-offsets.c
Contributors: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
John Pittman <jpittman@redhat.com>
Bart Van Assche <bvanassche@acm.org>
If you are too busy, please let me know. I can create the patch on your
behalf, but since this is a license change, it's better if you author it
yourselves.
Bart and Keith,
When you post the patch, please CC the contributors, so that they can
provide their Acked-by tags.
Contributors,
When you receive the CCed patches, please respond with your Acked-by tag
to record your agreement to the relicense.
Bart,
Could you please note in the commit message that Yi Zhang's two commits A)
and B) above are regarded as "de minimis"? I drafted the description as
below:
Because Yi Zhang did not respond to the relicensing request (contacted via
e-mail addresses on Red Hat and on the GitHub account), and commits A) and
B) by Yi Zhang are regarded as de minimis, acknowledgement by Yi Zhang is
not expected.
Thanks in advance for your cooperation.
On Jul 07, 2026 / 15:38, Shin'ichiro Kawasaki wrote:
> Hello blktests contributors,
>
> Recent discussion unveiled a license inconsistency [1]. Currently, each file of
> blktests has one of the licenses: GPL-2.0, GPL-2.0+ or GPL-3.0+. Majority of the
> blktests code has GPL-3.0+, so the effective main license is GPL-3.0+ (e.g.,
> check, common/rc). However, GPL-2.0 and GPL-3.0 are not compatible with each
> other [2]. Because the majority of blktests is GPL-3.0+, blktests cannot contain
> GPL-2.0 files. All files shall be GPL-2.0+ or GPL-3.0+.
>
> [1] https://lore.kernel.org/linux-block/20260626045650.GA8752@lst.de/
> [2] https://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility
>
> As of July 2026, seven files below have GPL-2.0. It is desired to change their
> license to GPL-2.0+ (or GPL-3.0+). The list below shows Authors and Contributors
> of each file. "Author" means the original file creator who set the license
> GPL-2.0. "Contributor" means those who made changes to the files later on.
>
> 1) block/029
> Author: Bart Van Assche <bvanassche@acm.org>
> Contributors: Yi Zhang <yi.zhang@redhat.com>
> Christoph Hellwig <hch@lst.de>
> Li Zhijian <lizhijian@fujitsu.com>
>
> 2) block/030
> Author: Bart Van Assche <bvanassche@acm.org>
> Contributors: Christoph Hellwig <hch@lst.de>
> Li Zhijian <lizhijian@fujitsu.com>
> Akinobu Mita <akinobu.mita@gmail.com>
>
> 3) block/031
> Author: Bart Van Assche <bvanassche@acm.org>
> Contributors: Yi Zhang <yi.zhang@redhat.com>
> Christoph Hellwig <hch@lst.de>
> Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
>
> 4) block/040
> Author: Ming Lei <ming.lei@redhat.com>
>
> 5) block/042
> Author: Keith Busch <kbusch@kernel.org>
> Contributors: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> John Pittman <jpittman@redhat.com>
>
> 6) block/043
> Author: Keith Busch <kbusch@kernel.org>
> Contributors: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
>
> 7) src/dio-offsets.c
> Author: Keith Busch <kbusch@kernel.org>
> Contributors: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> Bart Van Assche <bvanassche@acm.org>
>
>
> To the authors and the contributors,
>
> I would like to call for your responses. Please let us know if you agree to
> modify the license of the files from GPL-2.0 to GPL-2.0+ (or GPL-3.0+).
>
>
> I will wait for a few weeks to gather responses. Once agreement gets
> estabilished, I will ask the authors to submit patches to make the license
> change. Any other general comments on this topic will be appreciated also.
>
> And as one of the contributors, here I express my agreement to change the
> license of the files :)
prev parent reply other threads:[~2026-07-27 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 6:38 blktests: call for agreement to relicense GPL-2.0 files Shin'ichiro Kawasaki
2026-07-07 16:23 ` Ming Lei
2026-07-07 16:53 ` Bart Van Assche
2026-07-07 16:55 ` Keith Busch
2026-07-08 2:34 ` Zhijian Li (Fujitsu)
2026-07-08 8:06 ` Christoph Hellwig
2026-07-09 0:50 ` Akinobu Mita
2026-07-27 4:10 ` 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=ama1svBbdVfyEKz1@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=akinobu.mita@gmail.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=jpittman@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=ming.lei@redhat.com \
--cc=tom.leiming@gmail.com \
--cc=yi.zhang@redhat.com \
/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