From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfram Sang Subject: Re: linux-next: Fixes tag needs some work in the i2c tree Date: Wed, 24 Apr 2019 00:17:33 +0200 Message-ID: <20190423221733.GG5659@kunai> References: <20190424075535.7cdd5a73@canb.auug.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="O8XZ+2Hy8Kj8wLPZ" Return-path: Content-Disposition: inline In-Reply-To: <20190424075535.7cdd5a73@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell Cc: Linux Next Mailing List , Linux Kernel Mailing List , Anson Huang List-Id: linux-next.vger.kernel.org --O8XZ+2Hy8Kj8wLPZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > has these problem(s): >=20 > - missing space between the SHA1 and the subject Thanks, I missed that. Pushed out a new for-next with it fixed. --O8XZ+2Hy8Kj8wLPZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAly/jvkACgkQFA3kzBSg KbZnww//WlSZGKmE/Sypvtn7WUQl15QBQw6orXh9gPB4uSG6b9SnMLSxeKXdSCNT asnJ2ZSLdChDh4KKzTeNgzninagjcLbEb9RLV9yojOzxzUssxpR1RwVf5ld3p53H kVokrQvyL4JZf3zA/KBaWrJHjqWg63xuQVnEWjEbjWEl2HurntB7d0QFS1NuJvVn te1XAcp1OMURsTsaMQnEN0fmFCD0lOhlIVbsQN5f2iT/Rh9xUmXHE1B4xWt1Ur22 EcMK6f/K3Qv1O7QDKYZBajakfU8CDEnOafYAfZagd3bLLHyflg8JwhkcbZ3qlqJo gbv1AqP3n8bhNunFvAER0gG3XEXQibpFCC4Y0LCjSBwJI3uktA3ZcBHMgpt9trLU MaD4XTrp555BWngl+AAiCT6SPAhfDNpJJgUIPQsBmYJkPdm8Qhk+JmUkK2aXkcqf z1UVCnldkOOpN8Di2NeJl41z75fBUVWlC523T6VT2XHn18oJKISqUHOiM/aBn4/v YMfOlmnWFYcJ/D2AqA2/0STl7Dsl1UE3tW4citbajuAURs1VJq9G1XvsR4vb/CZp 0XZ0HkSLf7qmQy/eKW6f86DDN6FhRRmxpIQ8zfu2YnXu7HXgm1hzLWkr1lulucvj n4gGuvGK7b7jwXtQFc9nm5YAz3eLLnb/0W4MGJT8Cvf9tzCgXEc= =Xa0u -----END PGP SIGNATURE----- --O8XZ+2Hy8Kj8wLPZ--