From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Lee Jones <lee.jones@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boris Brezillon <bbrezillon@kernel.org>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: linux-next: Tree for Mar 27 (sunxi clk & mfd)
Date: Mon, 1 Apr 2019 14:33:37 +0200 [thread overview]
Message-ID: <20190401123337.2nhppxyl5nzyofub@flea> (raw)
In-Reply-To: <20190401223624.6b4f8c42@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Mon, Apr 01, 2019 at 10:36:24PM +1100, Stephen Rothwell wrote:
> Hi Lee,
>
> On Mon, 1 Apr 2019 11:27:32 +0100 Lee Jones <lee.jones@linaro.org> wrote:
> >
> > On Thu, 28 Mar 2019, Stephen Rothwell wrote:
> >
> > > I reported that a while ago (x86_64 allmodconfig after the merge of the
> > > sunxi tree). Apparently there is a fix out there but it hasn't been
> > > applied yet.
> >
> > Where is the fix to be applied? SUNXI or MFD?
>
> Well, I only see the problem after applying the sunxi tree (which
> happens before I merge the mfd tree).
>
> Maxime said:
>
> > I've just sent a patch fixing this:
> > https://lore.kernel.org/lkml/20190322091650.5189-1-maxime.ripard@bootlin.com/
>
> So maybe if you (Lee) acked it, Maxime could apply it to the sunxi
> tree, so we keep the breakage and fix together? Assuming that the fix
> is acceptable (and works :-)).
That works for me
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-04-01 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 3:50 linux-next: Tree for Mar 27 Stephen Rothwell
2019-03-27 20:32 ` linux-next: Tree for Mar 27 (sunxi clk & mfd) Randy Dunlap
2019-03-27 22:50 ` Stephen Rothwell
2019-04-01 10:27 ` Lee Jones
2019-04-01 11:36 ` Stephen Rothwell
2019-04-01 12:33 ` Maxime Ripard [this message]
2019-04-03 10:02 ` Lee Jones
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=20190401123337.2nhppxyl5nzyofub@flea \
--to=maxime.ripard@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).