public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Nariman Poushin <nariman@opensource•wolfsonmicro.com>,
	Mark Brown <broonie@kernel•org>, Lee Jones <lee.jones@linaro•org>,
	Liam Girdwood <lgirdwood@gmail•com>,
	Linux-Next <linux-next@vger•kernel.org>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	Richard Fitzgerald <rf@opensource•wolfsonmicro.com>,
	Charles Keepax <ckeepax@opensource•wolfsonmicro.com>
Subject: Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch
Date: Sat, 5 Sep 2015 16:08:06 +0200	[thread overview]
Message-ID: <CAMuHMdVST1TjkVSJGfKns_E4SZPyax5hOYuinbr8pY+gQWursw@mail.gmail.com> (raw)
In-Reply-To: <20150720115935.686b556e@canb.auug.org.au>

On Mon, Jul 20, 2015 at 3:59 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin <nariman@opensource•wolfsonmicro.com> wrote:
>> Introduced by:
>> commit 8019ff6cfc04
>> ("regmap: Use reg_sequence for multi_reg_write / register_patch")
>>
>> Interacting with:
>> commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
>> commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
>>
>> Signed-off-by: Nariman Poushin <nariman@opensource•wolfsonmicro.com>

Acked-by: Geert Uytterhoeven <geert@linux-m68k•org>

>> ---
>>  drivers/mfd/wm5110-tables.c | 2 +-
>>  drivers/mfd/wm8998-tables.c | 2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> I will apply both these patches as merge fix patches in linux-next
> today.  Thanks.

7 weeks later, the fix is still in -next only, hidden in:

commit 203903b3383c2dc8bcommit 203903b3383c2dc8b79277061341ec1c31ea75e3
Merge: f7ef70b70ccf13a9 90b1f7f5d2016031
Author: Stephen Rothwell <sfr@canb•auug.org.au>
Date:   Thu Sep 3 12:39:52 2015 +1000

    Merge remote-tracking branch 'regmap/for-next'

Worse, the problem is now in Linus' tree:

drivers/mfd/wm5110-tables.c: In function ‘wm5110_patch’:
drivers/mfd/wm5110-tables.c:281: warning: passing argument 2 of
‘regmap_register_patch’ from incompatible pointer type
drivers/mfd/wm8998-tables.c: In function ‘wm8998_patch’:
drivers/mfd/wm8998-tables.c:50: warning: passing argument 2 of
‘regmap_register_patch’ from incompatible pointer type

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2015-09-05 14:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  4:39 linux-next: build warnings after merge of the regmap tree Stephen Rothwell
2015-07-17  9:44 ` Nariman Poushin
2015-07-17 10:34   ` Mark Brown
2015-07-17 14:09     ` [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch Nariman Poushin
2015-07-17 17:57       ` Mark Brown
2015-07-20  1:59       ` Stephen Rothwell
2015-09-05 14:08         ` Geert Uytterhoeven [this message]
2015-09-18  3:50         ` Stephen Rothwell
2015-09-18  8:33           ` Charles Keepax
2015-09-18 10:25             ` Mark Brown
2015-07-17 14:11     ` [PATCH 2/2] ASoC: wm5110: Use reg_sequence for multi_reg_write/register_patch Nariman Poushin
2015-07-17 15:29     ` linux-next: build warnings after merge of the regmap tree Nariman Poushin
2015-07-17 16:45       ` Charles Keepax

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=CAMuHMdVST1TjkVSJGfKns_E4SZPyax5hOYuinbr8pY+gQWursw@mail.gmail.com \
    --to=geert@linux-m68k$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=ckeepax@opensource$(echo .)wolfsonmicro.com \
    --cc=lee.jones@linaro$(echo .)org \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=nariman@opensource$(echo .)wolfsonmicro.com \
    --cc=rf@opensource$(echo .)wolfsonmicro.com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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