From: "Pavel Machek" <pavel@ucw.cz>
To: "Johnson CH Chen (陳昭勳)" <JohnsonCH.Chen@moxa.com>
Cc: "nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>,
"pavel@denx.de" <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev][PATCH 4.4.y-cip 1/2] ARM: DTS: am33xx: Use the new DT bindings for the eDMA3
Date: Fri, 5 Jun 2020 23:18:13 +0200 [thread overview]
Message-ID: <20200605211813.GA8852@amd> (raw)
In-Reply-To: <HK2PR01MB32816B8BCBF222E046FE5524FA860@HK2PR01MB3281.apcprd01.prod.exchangelabs.com>
[-- Attachment #1.1: Type: text/plain, Size: 1827 bytes --]
Hi!
> From: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> commit b5e5090660742c838ddc0b5d1a001e6fe3d5bfd5 upstream.
I get quite a lot of complains here, if I try to apply patch
automatically using git-am.
Applying: ARM: DTS: am33xx: Use the new DT bindings for the eDMA3
.git/rebase-apply/patch:17: trailing whitespace.
dmas = <&edma_xbar 12 0 1
.git/rebase-apply/patch:18: trailing whitespace.
&edma_xbar 13 0 2>;
.git/rebase-apply/patch:58: trailing whitespace.
dmas = <&edma_xbar 12 0 1
.git/rebase-apply/patch:59: trailing whitespace.
&edma_xbar 13 0 2>;
.git/rebase-apply/patch:71: trailing whitespace.
edma_xbar: dma-router@f90 {
error: patch failed: arch/arm/boot/dts/am335x-evm.dts:743
error: arch/arm/boot/dts/am335x-evm.dts: patch does not apply
error: patch failed: arch/arm/boot/dts/am335x-pepper.dts:339
error: arch/arm/boot/dts/am335x-pepper.dts: patch does not apply
error: patch failed: arch/arm/boot/dts/am33xx.dtsi:162
error: arch/arm/boot/dts/am33xx.dtsi: patch does not apply
Patch failed at 0001 ARM: DTS: am33xx: Use the new DT bindings for the eDMA3
The copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
And it seems to me problem is in CR/LF line endings in the patch:
pavel@amd:~/cip/k$ file .git/rebase-apply/patch
.git/rebase-apply/patch: unified diff output, ASCII text, with CRLF
line terminators
I believe I could somehow convince git to apply it, anyway; or maybe
to cherry-pick commits from mainline, but... Could I ask for a patch
series that can be applied using git am?
Thanks and best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4727): https://lists.cip-project.org/g/cip-dev/message/4727
Mute This Topic: https://lists.cip-project.org/mt/74689397/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-06-05 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 9:35 [cip-dev][PATCH 4.4.y-cip 1/2] ARM: DTS: am33xx: Use the new DT bindings for the eDMA3 johnsonch.chen@moxa.com
2020-06-05 21:18 ` Pavel Machek [this message]
2020-06-06 11:49 ` johnsonch.chen@moxa.com
2020-06-06 13:48 ` SZ Lin
2020-06-07 23:35 ` Nobuhiro Iwamatsu
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=20200605211813.GA8852@amd \
--to=pavel@ucw.cz \
--cc=JohnsonCH.Chen@moxa.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.