From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the tests tree
Date: Wed, 5 Nov 2008 07:06:31 +0100 [thread overview]
Message-ID: <20081105060631.GA17079@uranus.ravnborg.org> (raw)
In-Reply-To: <20081105135211.52bbbd8d.sfr@canb.auug.org.au>
On Wed, Nov 05, 2008 at 01:52:11PM +1100, Stephen Rothwell wrote:
> Hi Ananth,
>
> On Wed, 15 Oct 2008 17:05:03 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the tests tree got a conflicts in lib/Kconfig.debug.
> >
> > You need to determine if this tree is ever going to be merged into Linus'
> > tree. I am going to drop it until you decide.
>
> Given the discussion, I am dropping the tests tree until something is
> decided. (in which case, I assume the tree will have its conflicts with
> Linus' tree fixed up)
Agreed. We can revisit this when we have a proper framework to execute
small user space test programs.
Ananth - thanks for your effort but I will drop the tree too.
Sam
next prev parent reply other threads:[~2008-11-05 6:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 6:05 linux-next: manual merge of the tests tree Stephen Rothwell
2008-10-15 14:15 ` Ananth N Mavinakayanahalli
2008-11-05 2:52 ` Stephen Rothwell
2008-11-05 6:06 ` Sam Ravnborg [this message]
2008-11-05 14:11 ` Ananth N Mavinakayanahalli
-- strict thread matches above, loose matches on Subject: below --
2008-08-15 4:59 Stephen Rothwell
2008-08-18 4:42 ` 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=20081105060631.GA17079@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ananth@in.ibm.com \
--cc=linux-next@vger.kernel.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).