From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@denx.de (Pavel Machek) Date: Fri, 30 Aug 2019 11:09:58 +0200 Subject: [cip-dev] [PATCH 4.19.y-cip v2 56/57] arm64: dts: Remove inconsistent use of 'arm, armv8' compatible string In-Reply-To: References: <1566999164-27898-1-git-send-email-fabrizio.castro@bp.renesas.com> <1566999164-27898-57-git-send-email-fabrizio.castro@bp.renesas.com> Message-ID: <20190830090958.GB18867@amd> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org Hi! > >It's not that important, but why is there a space between 'arm,' and 'armv8' > >in subject? > >Original subject does not have space. > > It is actually VERY, VERY, important, as the email I have sent out doesn't contain the space. > I have even run hexdump on the patch file on my disk, it confirms there is no space. > I am replying to my own email, and as you can see, there is no >space. Can you take a look at the email, as received from the mailinglist? I see a space in subject, between 'arm,' and 'armv8'. Can you send the original email, as a binary attachment? > >The following patch have similar problem. > >soc: renesas: rcar-sysc: Remove rcar_sysc_power_{down, up}() helpers > > Same thing here, there is no space in the email I have sent out, which means it's > probably down to patchwork? Somehow a space gets automatically added, I wonder if > this is happening with the code too? > > How do we find out if the problem is with patchwork? I don't think patchwork is responsible. It would have to be something in the mailing list. Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: