public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: asml.silence@gmail.com, Tim Bird <tim.bird@sony.com>
Cc: linux-spdx@vger.kernel.org, io-uring@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring: Add SPDX id lines to remaining source files
Date: Wed, 04 Feb 2026 07:24:34 -0700	[thread overview]
Message-ID: <177021507413.12691.2658326702670917313.b4-ty@kernel.dk> (raw)
In-Reply-To: <20260203234624.1722921-1-tim.bird@sony.com>


On Tue, 03 Feb 2026 16:46:24 -0700, Tim Bird wrote:
> Some io_uring files are missing SPDX-License-Identifier lines.
> Add lines with GPL-2.0 license IDs to these files.
> 
> 

Applied, thanks!

[1/1] io_uring: Add SPDX id lines to remaining source files
      commit: ccd18ce290726053faff75b6fc3e541301ac99f9

Best regards,
-- 
Jens Axboe




      reply	other threads:[~2026-02-04 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 23:46 [PATCH] io_uring: Add SPDX id lines to remaining source files Tim Bird
2026-02-04 14:24 ` 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 \
    --in-reply-to=177021507413.12691.2658326702670917313.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tim.bird@sony.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