Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* Include krzk/linux-mem-ctrl (for drivers/memory) in next
@ 2020-07-27  8:29 Krzysztof Kozlowski
  2020-07-27 13:06 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Krzysztof Kozlowski @ 2020-07-27  8:29 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linux Next Mailing List, linux-kernel, Arnd Bergmann, Olof Johansson

Hi,

Please include in linux-next a new tree for drivers/memory:
URL: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git

branches:
1. for-next
   into next,
2. fixes
   into pending fixes (for current cycle),

The tree will have patches later send via pull-request to arm-soc (Arnd,
Olof).

Best regards,
Krzysztof

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

* Re: Include krzk/linux-mem-ctrl (for drivers/memory) in next
  2020-07-27  8:29 Include krzk/linux-mem-ctrl (for drivers/memory) in next Krzysztof Kozlowski
@ 2020-07-27 13:06 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2020-07-27 13:06 UTC (permalink / raw)
  To: Krzysztof Kozlowski
  Cc: Linux Next Mailing List, linux-kernel, Arnd Bergmann, Olof Johansson


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

Hi Krzysztof,

On Mon, 27 Jul 2020 10:29:38 +0200 Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> Please include in linux-next a new tree for drivers/memory:
> URL: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git
> 
> branches:
> 1. for-next
>    into next,
> 2. fixes
>    into pending fixes (for current cycle),
> 
> The tree will have patches later send via pull-request to arm-soc (Arnd,
> Olof).

I added the for-next branch today, I will add the fixes branch tomorrow.

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, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27  8:29 Include krzk/linux-mem-ctrl (for drivers/memory) in next Krzysztof Kozlowski
2020-07-27 13:06 ` Stephen Rothwell

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git