mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Chris Ball <cjb@laptop.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Boot regression on Mackerel with current mainline
Date: Tue, 10 Jul 2012 09:46:30 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1207100945090.29825@axis700.grange> (raw)
In-Reply-To: <87r4skqe1n.fsf@octavius.laptop.org>

On Tue, 10 Jul 2012, Chris Ball wrote:

> Hi Guennadi,
> 
> On Tue, Jul 10 2012, Guennadi Liakhovetski wrote:
> >> > The latter one looks big because of a rename, but with "-M" it's pretty 
> >> > trivial. Chris, do you agree?
> >> 
> >> Is the minimal fix to just add "| IRQF_ONESHOT" to the request_threaded_irq
> >> argument?  If so, I'd rather push just that for 3.5, and I can take care of
> >> having that change appear simultaneously in linux-next so that there aren't
> >> any conflicts.  Is that okay with you?
> >
> > For that you'd have to rebase -next, right? you'd like to do that?
> 
> Yeah, I'm willing to rebase mmc-next for this -- I'd rather send the
> simplest possible fix this late in 3.5-rc, and the rebase is simple.
> Also, this fix is logically distinct from your rename patch.
> 
> I don't think I need you to send anything more, I'll add the initial
> patch adding "| IRQF_ONESHOT", rebase your "extend and rename" patch on
> top of that, push both to mmc-next, and then send the initial patch to
> Linus in a few days.

Great, thanks for taking care of this!

Regards
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

      reply	other threads:[~2012-07-10  7:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201207031218.24797.rjw@sisk.pl>
     [not found] ` <Pine.LNX.4.64.1207031336320.29890@axis700.grange>
2012-07-03 17:10   ` Rafael J. Wysocki
2012-07-04  9:39     ` Guennadi Liakhovetski
2012-07-10  4:04       ` Chris Ball
2012-07-10  6:49         ` Guennadi Liakhovetski
2012-07-10  7:19           ` Chris Ball
2012-07-10  7:46             ` Guennadi Liakhovetski [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=Pine.LNX.4.64.1207100945090.29825@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cjb@laptop.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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®