From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Wessel <jason.wessel@windriver•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: removal of the kgdb tree
Date: Fri, 16 Sep 2016 07:49:07 +1000 [thread overview]
Message-ID: <20160916074907.3355feff@canb.auug.org.au> (raw)
In-Reply-To: <8767b8c5-d156-9b5a-5376-cc313652bb2f@windriver.com>
Hi Jason,
On Thu, 15 Sep 2016 07:16:18 -0500 Jason Wessel <jason.wessel@windriver•com> wrote:
>
> On 03/08/2016 11:16 PM, Stephen Rothwell wrote:
> >
> > I noticed that the kgdb tree
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git branch kgdb-next
> >
> > has not been updated since March 2015. I am going to remove it from
> > linux-next tomorrow unless I hear that it may be useful. It can always
> > be easily added back if it proves useful in the future.
> >
>
> The time has finally arrived. :-)
>
> Could you please add the kgdb-next branch back to linux-next.
Done 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
prev parent reply other threads:[~2016-09-15 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 5:16 linux-next: removal of the kgdb tree Stephen Rothwell
2016-09-15 12:16 ` Jason Wessel
2016-09-15 21:49 ` 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=20160916074907.3355feff@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jason.wessel@windriver$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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