public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dan Williams <dan.j.williams@gmail.com>
Cc: Christian Kujau <lists@nerdbynature.de>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	arjan@linux.intel.com, Cong Wang <xiyou.wangcong@gmail.com>,
	JBottomley@parallels.com
Subject: Re: [PATCH RESEND] Fix a dead loop in async_synchronize_full()
Date: Mon, 16 Jul 2012 18:57:10 -0700	[thread overview]
Message-ID: <20120717015710.GA2438@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAA9_cmf-5CW0KW=721Hh3GCKGgQYsJo1UX3AFbG+7c4fTGw-Yw@mail.gmail.com>

On Mon, Jul 16, 2012 at 04:01:33PM -0700, Dan Williams wrote:
> On Mon, Jul 16, 2012 at 11:32 AM, Christian Kujau <lists@nerdbynature.de> wrote:
> > Is this still scheduled to go into 3.5? I'm asking because -rc7 has been
> > released and does not contain this fix. W/o this fix, my powerpc system
> > won't boot[0] :-\
> 
> I don't expect James is going to push my async changes for 3.5.  So
> maybe we should go with Zhong's smaller fix for 3.5 and then replace
> with the ASYNC_DOMAIN patches in 3.6?

Makes sense to me!  I have been using Zhong's fix for my testing on
PowerPC for some weeks now with no trouble.

							Thanx, Paul


  reply	other threads:[~2012-07-17  1:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  7:04 [PATCH RESEND] Fix a dead loop in async_synchronize_full() Li Zhong
2012-07-11 22:42 ` Andrew Morton
2012-07-11 22:50   ` Dan Williams
2012-07-12  9:56     ` Li Zhong
2012-07-12 16:41       ` Dan Williams
2012-07-16 18:32       ` Christian Kujau
2012-07-16 23:01         ` Dan Williams
2012-07-17  1:57           ` Paul E. McKenney [this message]
2012-07-17  2:42             ` Li Zhong
2012-07-12  2:49   ` Li Zhong

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=20120717015710.GA2438@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=JBottomley@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=dan.j.williams@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=xiyou.wangcong@gmail.com \
    --cc=zhong@linux.vnet.ibm.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