public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	 palmer@dabbelt.com, aou@eecs.berkeley.edu, evan@rivosinc.com,
	 conor.dooley@microchip.com, apatel@ventanamicro.com
Subject: Re: [PATCH v1 2/6] RISC-V: Move the hwprobe syscall to its own file
Date: Thu, 12 Oct 2023 18:11:50 +0200	[thread overview]
Message-ID: <20231012-3dc2e811d6a57ffe90719d2a@orel> (raw)
In-Reply-To: <20231012-geologist-ramp-71c76a4305c7@spud>

On Thu, Oct 12, 2023 at 02:45:14PM +0100, Conor Dooley wrote:
> On Wed, Oct 11, 2023 at 03:56:13PM +0200, Andrew Jones wrote:
> 
> > +++ b/arch/riscv/kernel/sys_hwprobe.c
> > @@ -0,0 +1,276 @@
> > +// SPDX-License-Identifier: GPL-2.0-only
> > +/*
> > + * The hwprobe interface, for allowing userspace to probe to see which features
> > + * are supported by the hardware.  See Documentation/riscv/hwprobe.rst for more
> > + * details.
> > + *
> > + * Copyright (C) 2012 Regents of the University of California
> > + * Copyright (C) 2014 Darius Rad <darius@bluespec.com>
> > + * Copyright (C) 2017 SiFive
> 
> So uh, this is all new(ish) code, originally written last September,
> that is being moved, right?

Yeah, I just pulled the Copyrights over by standard practice of code
movement, but I agree they don't make much sense for the code I moved.
I suck at copyright management and would be happy for suggestions here.
If Rivos would like to put one here for the work Evan did, then I'll be
happy to add it. Or, if people prefer, I could add a Ventana copyright.

For me, whatever protects the open source code best is best :-)

Thanks,
drew

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

  reply	other threads:[~2023-10-12 16:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 13:56 [PATCH v1 0/6] RISC-V: hwprobe: Introduce which-cpus Andrew Jones
2023-10-11 13:56 ` [PATCH v1 1/6] RISC-V: hwprobe: Clarify cpus size parameter Andrew Jones
2023-10-12 13:38   ` Conor Dooley
2023-10-11 13:56 ` [PATCH v1 2/6] RISC-V: Move the hwprobe syscall to its own file Andrew Jones
2023-10-12 13:45   ` Conor Dooley
2023-10-12 16:11     ` Andrew Jones [this message]
2023-10-12 16:42       ` Evan Green
2023-10-12 17:02         ` Conor Dooley
2023-10-13  6:45           ` Andrew Jones
2023-10-13  7:39             ` Conor Dooley
2023-10-13 15:26               ` Evan Green
2023-10-11 13:56 ` [PATCH v1 3/6] RISC-V: hwprobe: Introduce which-cpus flag Andrew Jones
2023-10-12 17:40   ` Evan Green
2023-10-13  7:20     ` Andrew Jones
2023-10-19 17:16   ` Andrew Jones
2023-10-11 13:56 ` [PATCH v1 4/6] RISC-V: selftests: Statically link hwprobe test Andrew Jones
2023-10-11 13:56 ` [PATCH v1 5/6] RISC-V: selftests: Convert hwprobe test to kselftest API Andrew Jones
2023-10-11 13:56 ` [PATCH v1 6/6] RISC-V: selftests: Add which-cpus hwprobe test Andrew Jones

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=20231012-3dc2e811d6a57ffe90719d2a@orel \
    --to=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=evan@rivosinc.com \
    --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