Linux-LEDs Archive on lore.kernel.org
 help / color / Atom feed
From: Denis Osterland-Heim <denis.osterland@diehl.com>
To: "dmurphy@ti.com" <dmurphy@ti.com>, "pavel@ucw.cz" <pavel@ucw.cz>,
	"jacek.anaszewski@gmail.com" <jacek.anaszewski@gmail.com>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH v4] leds: pwm: check result of led_pwm_set() in led_pwm_add()
Date: Tue, 24 Mar 2020 07:36:47 +0000
Message-ID: <c8d1e1986c1e0a503d109b7e2e1cff1ef352d2c4.camel@diehl.com> (raw)
In-Reply-To: <e50f13f9-9d96-857f-7b1c-9ef5195be636@gmail.com>

Hi Jacek,

Am Montag, den 23.03.2020, 22:41 +0100 schrieb Jacek Anaszewski:
> Hi Denis,
> 
> Now it is better, it is:
> Content-Transfer-Encoding: quoted-printable.
> 
> Nonetheless there are still some problems with charset.
> See e.g. the line:
> 
> "if (ret =3D=3D 0) "
I see

> 
> Are you using git send-email for sending patches?
> I suspect not since patches arrive unordered by the
> position in the patch set.
Well, delivery path is:
git send-email
-> local postfix
-> Gnome Evolution
-> MS Exchange server
-> your servers

Normally it works quite well...

Headers after postfix:
Message-Id: <20200323091243.23140-1-Denis.Osterland@diehl.com>
X-Mailer: git-send-email 2.25.2
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Headers after Evolution:
Message-ID: <20200323091243.23140-1-Denis.Osterland@diehl.com>
X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
MIME-Version: 1.0

Headers after Exchange:
Message-ID: <20200323091243.23140-1-Denis.Osterland@diehl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-MS-Exchange-Organization-AuthSource: RCDC-Mail16.corp.diehl.com
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
x-mailer: Evolution 3.28.5-0ubuntu0.18.04.1 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

This is also where the transformation from '\x3d' to "=3D" and '\x20' to "=20" happens
and in the original case where the base64 encoding happens.

I can reproduce the problem with the apply of original message now.
At first try I used 'save as mbox' from Evolution UI, which does the conversation
from base64 to normal text. When I copy it local inbox I can use the original version
directly from maildir.

The mail 1/5 and 2/5 also have the conversions from '\x20' to "=20", so Pavel should now
be able to apply the patch. At least I can do so.

I can apply the base64 encode version as well, with:
patch -p1 < .git/rebase-apply/patch
but with warning:
(Stripping trailing CRs from patch; use --binary to disable.)

Regards Denis

> 
> Best regards,
> Jacek Anaszewski
> 


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/

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23  9:14 Denis Osterland-Heim
2020-03-23 21:41 ` Jacek Anaszewski
2020-03-24  7:36   ` Denis Osterland-Heim [this message]
2020-03-23 15:27 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=c8d1e1986c1e0a503d109b7e2e1cff1ef352d2c4.camel@diehl.com \
    --to=denis.osterland@diehl.com \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

Linux-LEDs Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-leds/0 linux-leds/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-leds linux-leds/ https://lore.kernel.org/linux-leds \
		linux-leds@vger.kernel.org
	public-inbox-index linux-leds

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-leds


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git