From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Pali =?utf-8?q?Roh=C3=A1r?= To: Pavel Machek Subject: Re: [PATCH] bluetooth: Add hci_h4p driver Date: Wed, 21 Jan 2015 12:46:27 +0100 Cc: Marcel Holtmann , Sebastian Reichel , Sebastian Reichel , Linux Kernel Mailing List , "linux-arm-kernel" , "linux-omap" , Tony Lindgren , khilman@kernel.org, Aaro Koskinen , Ivaylo Dimitrov , linux-bluetooth@vger.kernel.org References: <20141223130219.GA5731@amd> <7522CAC7-AFD9-470F-B4F8-3C39942DBC04@holtmann.org> <20150121110131.GA19792@amd> In-Reply-To: <20150121110131.GA19792@amd> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2668218.qebEoV65DQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Message-Id: <201501211246.27449@pali> List-ID: --nextPart2668218.qebEoV65DQ Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Wednesday 21 January 2015 12:01:31 Pavel Machek wrote: > > > Strange, where do you see DOS style line breaks? > > > Checkpatch here does not warn about that, and they really > > > should not be there. > >=20 > > If that would be the only pieces, then I would have fixed it > > already. That is not the big deal. The rest of checkpatch > > is what I am not going to fix for you. >=20 > I can fix the checkpatch, but I'd like to understand how ^Ms > got there, because otherwise it will happen again. >=20 IIRC lines in email according to RFC2822 specification must be=20 delimited by CRLF. Maybe this is reason? =2D-=20 Pali Roh=C3=A1r pali.rohar@gmail.com --nextPart2668218.qebEoV65DQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAlS/kZMACgkQi/DJPQPkQ1KHNwCgirb0YAu/ipLdvsiz3UwuHR+y PYIAmweevr4kH+u6tyK2tvaHab42Ewdw =/x02 -----END PGP SIGNATURE----- --nextPart2668218.qebEoV65DQ--