From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: removal of the cisco tree
Date: Fri, 30 Apr 2021 17:47:33 +1000 [thread overview]
Message-ID: <20210430174733.5a31d0c6@canb.auug.org.au> (raw)
In-Reply-To: <20210430044931.GA22125@fifo99.com>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Hi Daniel,
On Thu, 29 Apr 2021 21:49:31 -0700 Daniel Walker <dwalker@fifo99.com> wrote:
>
> Can you re-instate this tree ? I had planned to start using again, at least for
> a little while.
>
>
> On Tue, Jun 16, 2020 at 03:00:09PM +1000, Stephen Rothwell wrote:
> > Hi,
> >
> > I have removed the cisco tree
> > (https://github.com/daniel-walker/cisco-linux.git#for-next)
> > from linux-next because it has not been updated in more than a year.
> > If you would like it reinstated, please just reply and let me know.
I have reinstated it from tomorrow. Please do not add any v5.14
related material to this branch until after v5.13-rc1 has been released.
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 --]
prev parent reply other threads:[~2021-04-30 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 5:00 linux-next: removal of the cisco tree Stephen Rothwell
2020-06-16 19:34 ` Daniel Walker
2021-04-30 4:49 ` Daniel Walker
2021-04-30 7:47 ` Stephen Rothwell [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=20210430174733.5a31d0c6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).