mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	sfi-devel@simplefirmware.org, x86@kernel.org
Subject: Re: linux-next: Tree for June 19
Date: Mon, 22 Jun 2009 01:54:27 +1000	[thread overview]
Message-ID: <20090622015427.c749a0d9.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0906201415400.4083@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]

Hi Len,

On Sat, 20 Jun 2009 14:27:59 -0400 (EDT) Len Brown <lenb@kernel.org> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > 
> > Is this 2.6.31 or 32 material?
> 
> yes:-)
> 
> Most that is in in sfi-test at this moment I hope to catch .31.
> There will be much more in .32 -- mostly things that depend on
> the first batch...

OK, so then don't add any (more) .32 material into that branch until
after Linus' releases 31-rc1, please.

> > Should I put just you as the contact, or add the mailing list as well?
> 
> The mailing list is fine (on cc), and I'm on that.
> It is redundant to send to both.

Then please ensure that I can post to that list (I don't want to
subscribe obviously).

> > Basically, this should be just what you would send to Linus (or ask him
> > to fetch).  It is allowed to be rebased if you deem it necessary.
> 
> The patches are tested on the pre-release platform that
> makes use of them.  There have been several internal reviews
> and re-writes, but since we just got permission to release the
> patches last week, they've not been publically vetted yet.
> 
> The content is quite close to what I plan to propose for upstream,
> but the format is not.  I'll be re-factoring the series into
> "clean history" and senting them to LKML on Sunday night.
> 
> I don't expect much comment on the generic part,
> but will want x86 maintainers to buy into the
> parts that touch their architecture.

OK, then I think I need to hear from the x86 maintainers, at least,
before we include this.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-21 15:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  7:26 Stephen Rothwell
2009-06-19 13:44 ` Nico -telmich- Schottelius
2009-06-19 17:38 ` [PATCH -next] dm: dm-log-userspace depends on NET Randy Dunlap
2009-06-19 18:31   ` [dm-devel] " Jonathan Brassow
2009-06-19 18:24 ` [PATCH -next] dm: fix dm-log-userspace printk format Randy Dunlap
2009-06-19 18:32   ` [dm-devel] " Jonathan Brassow
2009-06-20  4:16 ` linux-next: Tree for June 19 Len Brown
2009-06-20  5:04   ` Stephen Rothwell
2009-06-20  5:12     ` Stephen Rothwell
2009-06-20 18:27     ` Len Brown
2009-06-21 15:54       ` Stephen Rothwell [this message]
2009-06-29  5:25         ` Stephen Rothwell
2009-06-29  7:14         ` Ingo Molnar
2009-06-29  7:30           ` Stephen Rothwell
2009-06-23  6:34       ` Len Brown
2009-06-23  8:54         ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19  8:05 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=20090622015427.c749a0d9.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfi-devel@simplefirmware.org \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®