From: Jens Axboe <[email protected]>
To: Lukas Bulwahn <[email protected]>, [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH] io_uring: make spdxcheck.py happy
Date: Sat, 21 Mar 2020 14:04:21 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/21/20 5:19 AM, Lukas Bulwahn wrote:
> Commit bbbdeb4720a0 ("io_uring: dual license io_uring.h uapi header")
> uses a nested SPDX-License-Identifier to dual license the header.
>
> Since then, ./scripts/spdxcheck.py complains:
>
> include/uapi/linux/io_uring.h: 1:60 Missing parentheses: OR
>
> Add parentheses to make spdxcheck.py happy.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2020-03-21 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 11:19 [PATCH] io_uring: make spdxcheck.py happy Lukas Bulwahn
2020-03-21 20:04 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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