All of lore.kernel.org
 help / color / mirror / Atom feed
* Add fustini riscv-config to linux-next
@ 2026-06-09  7:21 ` Drew Fustini
  0 siblings, 0 replies; 4+ messages in thread
From: Drew Fustini @ 2026-06-09  7:21 UTC (permalink / raw)
  To: broonie; +Cc: linux-next, linux-kernel, Conor Dooley, Arnd Bergmann,
	linux-riscv

Hi Mark,

I have a new tree where I will apply patches for riscv defconfigs. I
have trees for dt and clk for two riscv soc vendors in next but
defconfig patches don't belong in such branches. Conor has in the past
taken defconfig patches but he is happy for me to send pull requests
as needed based on my new defconfig branches.

Please add these to linux-next:

riscv-config https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-for-next
riscv-config-fixes https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-fixes

Thanks,
Drew

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Add fustini riscv-config to linux-next
@ 2026-06-09  7:21 ` Drew Fustini
  0 siblings, 0 replies; 4+ messages in thread
From: Drew Fustini @ 2026-06-09  7:21 UTC (permalink / raw)
  To: broonie; +Cc: linux-next, linux-kernel, Conor Dooley, Arnd Bergmann,
	linux-riscv

Hi Mark,

I have a new tree where I will apply patches for riscv defconfigs. I
have trees for dt and clk for two riscv soc vendors in next but
defconfig patches don't belong in such branches. Conor has in the past
taken defconfig patches but he is happy for me to send pull requests
as needed based on my new defconfig branches.

Please add these to linux-next:

riscv-config https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-for-next
riscv-config-fixes https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-fixes

Thanks,
Drew

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Add fustini riscv-config to linux-next
  2026-06-09  7:21 ` Drew Fustini
@ 2026-06-09 11:18   ` Mark Brown
  -1 siblings, 0 replies; 4+ messages in thread
From: Mark Brown @ 2026-06-09 11:18 UTC (permalink / raw)
  To: Drew Fustini
  Cc: linux-next, linux-kernel, Conor Dooley, Arnd Bergmann,
	linux-riscv

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On Tue, Jun 09, 2026 at 12:21:48AM -0700, Drew Fustini wrote:

> Please add these to linux-next:
> 
> riscv-config https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-for-next
> riscv-config-fixes https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-fixes

These should be added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Add fustini riscv-config to linux-next
@ 2026-06-09 11:18   ` Mark Brown
  0 siblings, 0 replies; 4+ messages in thread
From: Mark Brown @ 2026-06-09 11:18 UTC (permalink / raw)
  To: Drew Fustini
  Cc: linux-next, linux-kernel, Conor Dooley, Arnd Bergmann,
	linux-riscv


[-- Attachment #1.1: Type: text/plain, Size: 1158 bytes --]

On Tue, Jun 09, 2026 at 12:21:48AM -0700, Drew Fustini wrote:

> Please add these to linux-next:
> 
> riscv-config https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-for-next
> riscv-config-fixes https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-fixes

These should be added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-06-09 11:19 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-09  7:21 Add fustini riscv-config to linux-next Drew Fustini
2026-06-09  7:21 ` Drew Fustini
2026-06-09 11:18 ` Mark Brown
2026-06-09 11:18   ` Mark Brown

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.