From: Denis Osterland-Heim <denis.osterland@gmail.com>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 0/2] raspi: pass additional VC values via dtb
Date: Thu, 28 Sep 2023 14:57:32 +0200 [thread overview]
Message-ID: <a6e68c463cdc13eb4ce31b994ff252d58af65d92.camel@gmail.com> (raw)
In-Reply-To: <20230926113653.GB637806@pengutronix.de>
Hi Sascha,
Thanks for your fixup.
I use git-send-mail with a local transport and evolution to actually
send the mail.
Sounds like a HTML email "optimization".
I will check my setup, maybe I find something in the preference.
There is an option to reencode the mail before send.
Hopefully this prevents gmail from reencode.
I reviewed the patches on next and there is a unintended change in the
pr_err statement, which changes '\n' to 'n'.
In the mail, this is part of the context.
Shall I try to send a fixup?
Regards, Denis
> Hi Denis,
>
> On Mon, Sep 25, 2023 at 01:09:36PM +0200, Denis Osterland-Heim wrote:
> > v2: fix whitespace error, add acked-by of Ahmad, fix line of 80
> > chars
> >
> > Denis OSTERLAND-HEIM (2):
> > raspi: support to read vc values via dt-2nd boot
> > raspi: fixup additional vc created nodes
> >
> > arch/arm/boards/raspberry-pi/rpi-common.c | 69
> > ++++++++++++++++++++++-
> > --------
> > 1 file changed, 49 insertions(+), 20 deletions(-)
>
> The patches are still mangled. There are additional linebreaks,
> spaces
> are replaced by UTF-8 character 0xc2a0 and tabs are replaced by
> multiple
> 0xc2a0. I fixed this up by hand this time, but please check your
> setup
> for the next time. Are you using git send-email? If not, I'd
> recommend
> doing so.
>
> Sascha
>
next prev parent reply other threads:[~2023-09-28 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 11:09 Denis Osterland-Heim
2023-09-26 11:36 ` Sascha Hauer
2023-09-28 12:57 ` Denis Osterland-Heim [this message]
2023-09-28 13:10 ` Sascha Hauer
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=a6e68c463cdc13eb4ce31b994ff252d58af65d92.camel@gmail.com \
--to=denis.osterland@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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