From: Mark Brown <broonie@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Belisko Marek <marek.belisko@gmail.com>,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
Jon Hunter <jonathanh@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Keerthy <j-keerthy@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Tero Kristo <t-kristo@ti.com>,
Thierry Reding <treding@nvidia.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Regression in v5.0-rc with regmap-irq level-irq changes
Date: Wed, 16 Jan 2019 12:52:10 +0000 [thread overview]
Message-ID: <20190116125210.GA7186@sirena.org.uk> (raw)
In-Reply-To: <20190116001025.GL5544@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Tue, Jan 15, 2019 at 04:10:25PM -0800, Tony Lindgren wrote:
> * Mark Brown <broonie@kernel.org> [190115 21:09]:
> > On Tue, Jan 15, 2019 at 11:28:40AM -0800, Tony Lindgren wrote:
> > > Any ideas what's needed? Some triggering mapping data to palmas.c
> > > driver?
> > There should be a fix in -next already waiting for me to send it to
> > Linus, can you check there (a couple actually, in my for-linus branch)?
> OK great, yes the two drivers/base/regmap patches fix the issue
> for me.
Excellent, thanks for testing - I'm aiming to send them off this week, I
was going to send them off earlier but then the second fix came in.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-16 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 19:28 Tony Lindgren
2019-01-15 21:09 ` Mark Brown
2019-01-16 0:10 ` Tony Lindgren
2019-01-16 12:52 ` Mark Brown [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=20190116125210.GA7186@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hns@goldelico.com \
--cc=j-keerthy@ti.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
--cc=treding@nvidia.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
Powered by JetHome