public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: Add missing licenses
Date: Sat, 14 Sep 2024 08:13:11 +0000	[thread overview]
Message-ID: <172630159149.2498524.12159135435898265005.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240729-riscv_fence_license-v1-0-7d5648069640@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Mon, 29 Jul 2024 14:00:01 -0700 you wrote:
> I was poking around some files and noticed that vmalloc.h and fence.h
> were missing licenses. This series simply adds in those licenses.
> 
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> ---
> Charlie Jenkins (2):
>       riscv: Add license to fence.h
>       riscv: Add license to vmalloc.h
> 
> [...]

Here is the summary with links:
  - [1/2] riscv: Add license to fence.h
    https://git.kernel.org/riscv/c/097c72e1f2b5
  - [2/2] riscv: Add license to vmalloc.h
    https://git.kernel.org/riscv/c/4ffc8a342298

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2024-09-14  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 21:00 [PATCH 0/2] riscv: Add missing licenses Charlie Jenkins
2024-07-29 21:00 ` [PATCH 1/2] riscv: Add license to fence.h Charlie Jenkins
2024-07-29 21:00 ` [PATCH 2/2] riscv: Add license to vmalloc.h Charlie Jenkins
2024-09-14  8:13 ` patchwork-bot+linux-riscv [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=172630159149.2498524.12159135435898265005.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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