public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg•samsung.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
	linux-next@vger•kernel.org,
	greg Kroah-Hartman <gregkh@linuxfoundation•org>,
	fengguang.wu@intel•com, linux-api@vger•kernel.org,
	Shuah Khan <shuahkh@osg•samsung.com>
Subject: Re: Request to add linux-kselftest to linux-next
Date: Mon, 08 Sep 2014 17:07:41 -0600	[thread overview]
Message-ID: <540E36BD.4060607@osg.samsung.com> (raw)
In-Reply-To: <20140909085841.2ec2871e@canb.auug.org.au>

On 09/08/2014 04:58 PM, Stephen Rothwell wrote:
> Hi Shuah,
> 
> On Mon, 08 Sep 2014 08:52:45 -0600 Shuah Khan 
> <shuahkh@osg•samsung.com> wrote:
>> 
>> Could you please add linux-kselftest tree to linux-next. I plan 
>> to maintain two branches:
>> 
>> linux-kselftest for Kselftest Framework
>> 
>> fixes - Contains changes intended for merging before the next 
>> major release, including fixes for regressions introduced during
>>  merge window. next  - Contains changes intended for merging 
>> during the next merge window between a major release and -rc1.
> 
> Umm, a git URL would be helpful :-)
> 

Sorry: here it is:

https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git/

-- Shuah

-- 
Shuah Khan
Sr. Linux Kernel Developer
Samsung Research America (Silicon Valley)
shuahkh@osg•samsung.com | (970) 217-8978

  reply	other threads:[~2014-09-08 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <540DC2BD.7030506@osg.samsung.com>
2014-09-08 22:58 ` Request to add linux-kselftest to linux-next Stephen Rothwell
2014-09-08 23:07   ` Shuah Khan [this message]
     [not found]     ` <540E36BD.4060607-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2014-09-08 23:14       ` Stephen Rothwell
2014-09-08 23:23 ` Stephen Rothwell

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=540E36BD.4060607@osg.samsung.com \
    --to=shuahkh@osg$(echo .)samsung.com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=fengguang.wu@intel$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=linux-api@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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