From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: manual merge of the tests tree
Date: Mon, 18 Aug 2008 10:12:35 +0530 [thread overview]
Message-ID: <20080818044235.GA3665@in.ibm.com> (raw)
In-Reply-To: <20080815145948.690f8529.sfr@canb.auug.org.au>
On Fri, Aug 15, 2008 at 02:59:48PM +1000, Stephen Rothwell wrote:
> Hi Ananth,
>
> Today's linux-next merge of the tests tree got a conflict in
> lib/Kconfig.debug between commit 67182ae1c42206e516f7efb292b745e826497b24
> ("rcu, debug: detect stalled grace periods") from the sched tree and
> commit 2b9b631dd2507b5480b752bcca946b9767b9bae1 ("Move rcutorture to
> tests/") from the tests tree.
>
> I sort of fixed it up.
Thanks Stephen.
> Ananth, you should try to get the testing stuff into Linus' tree ...
We've tried multiple times already (last attempt was
http://marc.info/?l=linux-kernel&m=121727532926590&w=2).
Guess as Andrew said, this is way below in the priority scale. I am not
sure at this point if we should just let things be as they are if there
isn't much interest in merging it upstream.
Ananth
next prev parent reply other threads:[~2008-08-18 4:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 4:59 linux-next: manual merge of the tests tree Stephen Rothwell
2008-08-18 4:42 ` Ananth N Mavinakayanahalli [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-15 6:05 Stephen Rothwell
2008-10-15 14:15 ` Ananth N Mavinakayanahalli
2008-11-05 2:52 ` Stephen Rothwell
2008-11-05 6:06 ` Sam Ravnborg
2008-11-05 14:11 ` Ananth N Mavinakayanahalli
2008-07-22 3:56 Stephen Rothwell
2008-07-22 12:29 ` Ananth N Mavinakayanahalli
2008-06-25 5:03 Stephen Rothwell
2008-06-25 5:20 ` Ananth N Mavinakayanahalli
2008-06-26 16:06 ` Paul E. McKenney
2008-06-17 6:22 Stephen Rothwell
2008-06-17 6:26 ` Ingo Molnar
2008-06-17 6:27 ` Ananth N Mavinakayanahalli
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=20080818044235.GA3665@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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).