* linux-next: Please add the fsi tree
@ 2018-06-22 1:53 Benjamin Herrenschmidt
2018-06-22 3:10 ` Stephen Rothwell
0 siblings, 1 reply; 2+ messages in thread
From: Benjamin Herrenschmidt @ 2018-06-22 1:53 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Linux-Next Mailing List, Linux Kernel Mailing List
Hi Stephen !
Please add the fsi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/benh/linux-fsi.git (master)
To linux-next. It contains the changes that I will send to Greg KH to the FSI
subsystem used by the service processor to communicate with IBM Power chips
(and eventually S390 as well).
Commits in there are intende to be merged via Greg's tree. Signed tags in
there have already been the subject of pull requests to Greg.
Thanks !
Cheers,
Ben.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: Please add the fsi tree
2018-06-22 1:53 linux-next: Please add the fsi tree Benjamin Herrenschmidt
@ 2018-06-22 3:10 ` Stephen Rothwell
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2018-06-22 3:10 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: Linux-Next Mailing List, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
Hi Ben,
On Fri, 22 Jun 2018 11:53:50 +1000 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> Please add the fsi tree at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/benh/linux-fsi.git (master)
>
> To linux-next. It contains the changes that I will send to Greg KH to the FSI
> subsystem used by the service processor to communicate with IBM Power chips
> (and eventually S390 as well).
>
> Commits in there are intende to be merged via Greg's tree. Signed tags in
> there have already been the subject of pull requests to Greg.
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.
--
Cheers,
Stephen Rothwell
sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-06-22 3:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-22 1:53 linux-next: Please add the fsi tree Benjamin Herrenschmidt
2018-06-22 3:10 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).