From: Denis Osterland-Heim <denis.osterland@diehl.com>
To: "pavel@ucw.cz" <pavel@ucw.cz>,
"jacek.anaszewski@gmail.com" <jacek.anaszewski@gmail.com>
Cc: "dmurphy@ti.com" <dmurphy@ti.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"uwe@kleine-koenig.org" <uwe@kleine-koenig.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH v4 3/5] leds: pwm: check result of led_pwm_set() in led_pwm_add()
Date: Mon, 23 Mar 2020 06:09:02 +0000 [thread overview]
Message-ID: <ca8f7ca4226de19c910440fde0c6f1e34a807fc6.camel@diehl.com> (raw)
In-Reply-To: <566ac991-2e38-6c70-4b07-c8dd78d47a06@gmail.com>
Hi,
Am Sonntag, den 22.03.2020, 15:56 +0100 schrieb Jacek Anaszewski:
> 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@kleine-koenig.org>
> > > Signed-off-by: Denis Osterland-Heim <Denis.Osterland@diehl.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.
>
strange.
In the version I received by CC, there is no garbage, but also no auto appended footer.
I will send the mail just to linux-leds so we should all receive the same mail.
I wonder if the 'ö' in König causes this trouble in my send path.
Regards Denis
Diehl Connectivity Solutions GmbH
Geschäftsführung: Horst Leonberger
Sitz der Gesellschaft: Nürnberg - Registergericht: Amtsgericht
Nürnberg: HRB 32315
___________________________________________________________________________________________________
Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht.
Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt.
- Informationen zum Datenschutz, insbesondere zu Ihren Rechten, erhalten Sie unter https://www.diehl.com/group/de/transparenz-und-informationspflichten/
The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by
mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.
- For general information on data protection and your respective rights please visit https://www.diehl.com/group/en/transparency-and-information-obligations/
next prev parent reply other threads:[~2020-03-23 6:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 8:15 [PATCH v4 0/5] leds: pwm: add support for default-state device Denis Osterland-Heim
2020-03-21 8:15 ` [PATCH v4 5/5] leds: pwm: add reference to common leds for default-state Denis Osterland-Heim
2020-03-21 15:15 ` Pavel Machek
2020-03-22 7:59 ` Denis Osterland-Heim
2020-03-31 17:36 ` Rob Herring
2020-03-21 8:15 ` [PATCH v4 3/5] leds: pwm: check result of led_pwm_set() in led_pwm_add() Denis Osterland-Heim
2020-03-21 15:20 ` Pavel Machek
2020-03-21 17:13 ` Denis Osterland-Heim
2020-03-22 7:51 ` Denis Osterland-Heim
2020-03-22 14:56 ` Jacek Anaszewski
2020-03-23 6:09 ` Denis Osterland-Heim [this message]
2020-03-23 9:08 ` Denis Osterland-Heim
2020-03-21 8:15 ` [PATCH v4 2/5] leds: pwm: remove useless pwm_period_ns Denis Osterland-Heim
2020-03-21 8:15 ` [PATCH v4 1/5] leds: pwm: remove header Denis Osterland-Heim
2020-03-21 8:15 ` [PATCH v4 4/5] leds: pwm: add support for default-state device property Denis Osterland-Heim
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=ca8f7ca4226de19c910440fde0c6f1e34a807fc6.camel@diehl.com \
--to=denis.osterland@diehl.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.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).