public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	sameo@linux.intel.com, marex@denx.de,
	ashish.jangam@kpitcummins.com, dchen@diasemi.com,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH v2] mfd: da9052-core:  Use regmap_irq_get_virq() and fix the probe
Date: Fri, 28 Sep 2012 11:35:15 +0000	[thread overview]
Message-ID: <201209281135.16201.arnd@arndb.de> (raw)
In-Reply-To: <20120928105212.GC30869@opensource.wolfsonmicro.com>

On Friday 28 September 2012, Mark Brown wrote:
> On Fri, Sep 28, 2012 at 06:42:05AM +0000, Arnd Bergmann wrote:
> > On Friday 28 September 2012, Fabio Estevam wrote:
> 
> > > I also plan to convert the other da9052 drivers to use regmap_irq_get_virq().
> 
> > Ok, I think they have to be submitted together though, because otherwise
> > the other drivers are more broken now.
> 
> Given that the drivers don't currently load I'm not sure it's worth the
> effort of arranging to get them all merged through one tree, probably
> easier to get as many fixes as possible merged as fast as possible.

Agreed. I didn't know the driver still had problems of this scale.

	Arnd

  reply	other threads:[~2012-09-28 11:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  1:57 [PATCH v2] mfd: da9052-core: Use regmap_irq_get_virq() and fix the probe Fabio Estevam
2012-09-28  6:42 ` Arnd Bergmann
2012-09-28 10:45   ` Fabio Estevam
2012-09-28 11:34     ` Arnd Bergmann
2012-09-28 10:52   ` Mark Brown
2012-09-28 11:35     ` Arnd Bergmann [this message]
2012-09-28 10:49 ` Mark Brown
2012-09-28 14:33   ` Fabio Estevam
2012-09-28 14:29     ` Mark Brown
2012-09-28 15:37       ` Fabio Estevam
2012-09-28 15:51         ` Mark Brown
2012-09-28 20:34           ` Fabio Estevam
2012-10-01 10:22             ` Mark Brown
2012-10-03 16:04               ` Fabio Estevam
2012-10-03 18:08                 ` Mark Brown

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=201209281135.16201.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=ashish.jangam@kpitcummins.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dchen@diasemi.com \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=sameo@linux.intel.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