From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] leds: pm8058: Make ledtype pointer sized type
Date: Fri, 1 Dec 2017 21:35:16 +0100 [thread overview]
Message-ID: <44fd0b17-67af-63cf-cca9-da64daad40a3@gmail.com> (raw)
In-Reply-To: <20171201075613.vvwvrkl73pd7rg62@dell>
On 12/01/2017 08:56 AM, Lee Jones wrote:
> On Thu, 30 Nov 2017, Jacek Anaszewski wrote:
>
>> On 11/30/2017 09:31 AM, Lee Jones wrote:
>>> On Thu, 30 Nov 2017, Lee Jones wrote:
>>>
>>>> On Wed, 29 Nov 2017, Bjorn Andersson wrote:
>>>>
>>>>> The pointer returned by of_device_get_match_data() doesn't have the same
>>>>> size as u32 on 64-bit architectures, causing issues when compile testing
>>>>> the driver on such platform. Make ledtype unsigned long instead, to
>>>>> solve this problem.
>>>>>
>>>>> Fixes: 7f866986e705 ("leds: add PM8058 LEDs driver")
>>>>> Cc: Linus Walleij <linus.walleij@linaro.org>
>>>>> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>>>>> ---
>>>>> drivers/leds/leds-pm8058.c | 4 ++--
>>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> Hi Bjorn,
>>>>
>>>> (Nice to see you) :)
>>>>
>>>> I'm going to apply this *before* Linus' fix.
>>>>
>>>> Applied, thanks.
>>>
>>> After I rx an Ack from Richard, Jacek or Pavel of course. :)
>>>
>>> Will send a pull-request.
>>
>> Huh? This is for LED subsystem AFAICS.
>
> Right, hence why I said I'd sent out a pull-request.
>
> The problem, however, arose due to a change in its parent driver's
> Kconfig entry, which has been applied to the MFD tree. We need to
> ensure this patch is applied *before* the other 'fix' to quash the
> warning before it starts, so to speak.
Ah, I hadn't seen the MFD patch and understood that you was
talking about pull request for 4.15-rc2, which looked a bit
strange out of context.
For v2:
Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2017-12-01 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 0:35 linux-next: build warning after merge of the mfd tree Stephen Rothwell
2017-11-30 3:05 ` [PATCH] leds: pm8058: Make ledtype pointer sized type Bjorn Andersson
2017-11-30 8:29 ` Lee Jones
2017-11-30 8:31 ` Lee Jones
2017-11-30 22:02 ` Jacek Anaszewski
2017-12-01 7:56 ` Lee Jones
2017-12-01 20:35 ` Jacek Anaszewski [this message]
2017-11-30 9:18 ` Linus Walleij
2017-11-30 9:41 ` Lee Jones
2017-11-30 9:40 ` Pavel Machek
2017-11-30 21:58 ` Jacek Anaszewski
2017-11-30 22:34 ` Pavel Machek
2017-11-30 23:14 ` Stephen Rothwell
2017-12-01 0:28 ` Pavel Machek
2017-12-01 5:10 ` Bjorn Andersson
2017-11-30 22:18 ` Bjorn Andersson
2017-11-30 8:28 ` linux-next: build warning after merge of the mfd tree Lee Jones
2017-12-01 5:16 ` [PATCH v2] leds: pm8058: Silence pointer to integer size warning Bjorn Andersson
2017-12-01 7:57 ` Lee Jones
2017-12-01 8:36 ` Pavel Machek
2017-12-01 8:56 ` Lee Jones
2017-12-01 8:56 ` Lee Jones
2017-12-01 9:01 ` [GIT PULL] Immutable branch between MFD and LED due for the v4.16 merge window 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=44fd0b17-67af-63cf-cca9-da64daad40a3@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=sfr@canb.auug.org.au \
/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).