public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>
Subject: Re: [PATCH 4/17] cpumask: remove the now-obsoleted pcibus_to_cpumask(): sh
Date: Mon, 15 Jun 2009 15:13:57 +0930	[thread overview]
Message-ID: <200906151513.57984.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090615024520.GA31902@linux-sh.org>

On Mon, 15 Jun 2009 12:15:20 pm Paul Mundt wrote:
> I've taken these in to the sh tree, thanks. They'll be included in the
> next round of updates for -rc1.
>
> I'm not sure how you want to handle the remaining patches. The
> outstanding ones obviously touch code all over the place and should
> probably go in in one go after the merge window has settled down a bit.

Thanks, that's the basic plan.  They'll sit in linux-next until then.

(The other option was for you to just ack them and they'll go with the rest to 
Linus; in fact, that's going to happen to maintainers who don't respond anyway 
:)

Cheers,
Rusty.


      reply	other threads:[~2009-06-15  5:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 13:03 [PATCH 5/13] cpumask: Use accessors for cpu_*_mask: sh Rusty Russell
2009-06-12 13:03 ` [PATCH 11/13] cpumask: use mm_cpumask() wrapper: sh Rusty Russell
2009-06-12 13:02   ` [PATCH 5/7] cpumask: arch_send_call_function_ipi_mask: sh Rusty Russell
2009-06-12 13:01     ` [PATCH 4/17] cpumask: remove the now-obsoleted pcibus_to_cpumask(): sh Rusty Russell
2009-06-15  2:45       ` Paul Mundt
2009-06-15  5:43         ` Rusty Russell [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=200906151513.57984.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=travis@sgi.com \
    /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