linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-next@vger.kernel.org
Subject: Re: Tests tree not submitted?
Date: Mon, 19 May 2008 11:19:40 +0530	[thread overview]
Message-ID: <20080519054940.GB3473@in.ibm.com> (raw)
In-Reply-To: <20080518220003.5169892a.akpm@linux-foundation.org>

On Sun, May 18, 2008 at 10:00:03PM -0700, Andrew Morton wrote:
> On Mon, 19 May 2008 10:08:22 +0530 Ananth N Mavinakayanahalli <ananth@in.ibm.com> wrote:
> 
> > 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?
> 
> <brief panic>

Oops! Sorry Andrew :-)

> I don't even know what the "tests" tree _is_.
> 
> Searching the past seven weeks lmkl archives for From:.*ananth.* turns
> up zero hits.

http://marc.info/?l=linux-kernel&m=120285599718700&w=2 is Sam's mail to
lkml about it.

> So whatever this thing is, it's waaaaaaaaaaaaaaaaaaaaay too low-profile.

Yes, its nothing earth shattering :-) Just code consolidation.

> Did you even send Linus a pull request?  I have no record of one.

Sam did http://marc.info/?l=linux-kernel&m=120285599718700&w=2 again.

Ananth

      parent reply	other threads:[~2008-05-19  5:48 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
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 [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=20080519054940.GB3473@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 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).