All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-next@vger.kernel.org
Subject: Re: Tests tree not submitted?
Date: Mon, 19 May 2008 10:08:22 +0530	[thread overview]
Message-ID: <20080519043822.GA3473@in.ibm.com> (raw)
In-Reply-To: <20080519135436.34d6d593.sfr@canb.auug.org.au>

On Mon, May 19, 2008 at 01:54:36PM +1000, Stephen Rothwell wrote:
> Hi Ananth, Sam,

Hi Stephen,

> Is there some reason that the tests tree changes have not bee submitted
> to Linus yet?  They have been in linux-next for quite some time now
> (since February 24) without any changes.

When this was submitted last, the opinion was that since it was post
2.6.25-rc2 and since it had Kconfig changes, this should be deferred to
the next release. However I got busy during the merge time and couldn't
resumbit this.

I believe this being a code movement, its mostly benign. But if it needs
to wait for 2.6.27, thats fine too; also given that the -mm is now based
on -next, it'll get a lot more tested.

Andrew,

What is the best way forward here? Given the code has been in -next for
a few months, and given -mm is now based on -next, will you be pushing
these changes to Linus during the next merge window? Or, do you want me
to resubmit the patchset again later in the 2.6.26-rc cycle?

Ananth

  reply	other threads:[~2008-05-19  4:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19  3:54 Tests tree not submitted? Stephen Rothwell
2008-05-19  4:38 ` Ananth N Mavinakayanahalli [this message]
2008-05-19  5:00   ` Andrew Morton
2008-05-19  5:37     ` Stephen Rothwell
2008-05-19  6:30       ` Sam Ravnborg
2008-05-19  6:39         ` Stephen Rothwell
2008-05-19  5:49     ` 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=20080519043822.GA3473@in.ibm.com \
    --to=ananth@in.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-next@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.