[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <566ac991-2e38-6c70-4b07-c8dd78d47a06@gmail.com>
Date: Sun, 22 Mar 2020 15:56:45 +0100
From: Jacek Anaszewski <jacek.anaszewski@...il.com>
To: Pavel Machek <pavel@....cz>,
Denis Osterland-Heim <denis.osterland@...hl.com>
Cc: "dmurphy@...com" <dmurphy@...com>,
"mark.rutland@....com" <mark.rutland@....com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"uwe@...ine-koenig.org" <uwe@...ine-koenig.org>
Subject: Re: [PATCH v4 3/5] leds: pwm: check result of led_pwm_set() in
led_pwm_add()
On 3/21/20 4:20 PM, Pavel Machek wrote:
> Hi!
>
>> led_pwm_set() now returns an error when setting the PWM fails.
>>
>> Cc: Uwe Kleine-König <uwe@...ine-koenig.org>
>> Signed-off-by: Denis Osterland-Heim <Denis.Osterland@...hl.com>
>
> I applied 1 and 2, but 3 failed for me. I'll push updated -next, can
> you see what is going on there?
Check the contents of the patch after writing it on a disk.
In my case it contains a block of random characters.
It is probably due to Content-Transfer-Encoding: base64.
--
Best regards,
Jacek Anaszewski
Powered by blists - more mailing lists