All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org
Subject: Re: [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse	possible
Date: Wed, 12 Aug 2009 06:10:29 +0000	[thread overview]
Message-ID: <4A825CD5.3060209@kernel.org> (raw)
In-Reply-To: <4A7B01B8.8000902@kernel.org>

Tejun Heo wrote:
> Ingo Molnar wrote:
>> for the x86 bits:
>>
>>  Acked-by: Ingo Molnar <mingo@elte.hu>
>>
>> Once Dave acks it i suspect you can send it to Linus directly?

Aieeeee, no response.  I'll push these two patches into linux-next
today.  Wait a few days and then push them to Linus.  :-(

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org
Subject: Re: [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse	possible cpu map handling
Date: Wed, 12 Aug 2009 15:10:29 +0900	[thread overview]
Message-ID: <4A825CD5.3060209@kernel.org> (raw)
In-Reply-To: <4A7B01B8.8000902@kernel.org>

Tejun Heo wrote:
> Ingo Molnar wrote:
>> for the x86 bits:
>>
>>  Acked-by: Ingo Molnar <mingo@elte.hu>
>>
>> Once Dave acks it i suspect you can send it to Linus directly?

Aieeeee, no response.  I'll push these two patches into linux-next
today.  Wait a few days and then push them to Linus.  :-(

Thanks.

-- 
tejun

  reply	other threads:[~2009-08-12  6:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  9:33 [PATCH 1/2 2.6.31-rc5 REPOST] init: set nr_cpu_ids before setup_per_cpu_areas() Tejun Heo
2009-08-06  9:33 ` Tejun Heo
2009-08-06  9:36 ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible Tejun Heo
2009-08-06  9:36   ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible cpu map handling Tejun Heo
2009-08-06 11:57   ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse Ingo Molnar
2009-08-06 11:57     ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible cpu map handling Ingo Molnar
2009-08-06 16:15     ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible Tejun Heo
2009-08-06 16:15       ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible cpu map handling Tejun Heo
2009-08-12  6:10       ` Tejun Heo [this message]
2009-08-12  6:10         ` Tejun Heo
2009-08-12 23:25         ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse David Miller
2009-08-12 23:25           ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible cpu map handling David Miller
2009-08-14  4:26           ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible Tejun Heo
2009-08-14  4:26             ` [PATCH 2/2 2.6.31-rc5 REPOST] percpu, sparc64: fix sparse possible cpu map handling Tejun Heo
2009-08-14  4:27             ` [PATCH 2/2 2.6.31-rc5 UPDATED] percpu, sparc64: fix sparse possible Tejun Heo
2009-08-14  4:27               ` [PATCH 2/2 2.6.31-rc5 UPDATED] percpu, sparc64: fix sparse possible cpu map handling Tejun Heo

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=4A825CD5.3060209@kernel.org \
    --to=tj@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sparclinux@vger.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 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.