From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752355AbdATPaQ (ORCPT ); Fri, 20 Jan 2017 10:30:16 -0500 Received: from david.siemens.de ([192.35.17.14]:47135 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752193AbdATPaO (ORCPT ); Fri, 20 Jan 2017 10:30:14 -0500 Subject: Re: [PATCH v3 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts To: Mark Brown , Andy Shevchenko References: <7b15a0910a3ad861fd32161c72559bafa7b71e29.1484592296.git.jan.kiszka@siemens.com> <87ziiqdstr.fsf@belgarion.home> <4d97e416-4d32-3b9f-0695-de116a4b26bd@siemens.com> <87r340eq28.fsf@belgarion.home> <20170118124645.6ugjwbfeq5vsh2to@sirena.org.uk> <7e5fb21d-35bd-6ac3-9e6f-cffed656997f@siemens.com> <20170119195701.kueutgmahr6bmxhq@sirena.org.uk> <1484856272.2133.253.camel@linux.intel.com> <20170120122129.6cn5phrobeldpikp@sirena.org.uk> Cc: Robert Jarzmik , linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Daniel Mack , Haojian Zhuang , linux-kernel@vger.kernel.org, Mika Westerberg , Jarkko Nikula , Sascha Weisenberger From: Jan Kiszka Message-ID: Date: Fri, 20 Jan 2017 16:29:28 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20170120122129.6cn5phrobeldpikp@sirena.org.uk> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tp2I6nifge93EDAU6Fhl5qIxBa1NFPgr0" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --tp2I6nifge93EDAU6Fhl5qIxBa1NFPgr0 Content-Type: multipart/mixed; boundary="V70RoBfQprV3sMGT6CKci46tx23nJKH0K"; protected-headers="v1" From: Jan Kiszka To: Mark Brown , Andy Shevchenko Cc: Robert Jarzmik , linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Daniel Mack , Haojian Zhuang , linux-kernel@vger.kernel.org, Mika Westerberg , Jarkko Nikula , Sascha Weisenberger Message-ID: Subject: Re: [PATCH v3 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts References: <7b15a0910a3ad861fd32161c72559bafa7b71e29.1484592296.git.jan.kiszka@siemens.com> <87ziiqdstr.fsf@belgarion.home> <4d97e416-4d32-3b9f-0695-de116a4b26bd@siemens.com> <87r340eq28.fsf@belgarion.home> <20170118124645.6ugjwbfeq5vsh2to@sirena.org.uk> <7e5fb21d-35bd-6ac3-9e6f-cffed656997f@siemens.com> <20170119195701.kueutgmahr6bmxhq@sirena.org.uk> <1484856272.2133.253.camel@linux.intel.com> <20170120122129.6cn5phrobeldpikp@sirena.org.uk> In-Reply-To: <20170120122129.6cn5phrobeldpikp@sirena.org.uk> --V70RoBfQprV3sMGT6CKci46tx23nJKH0K Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017-01-20 13:21, Mark Brown wrote: > On Thu, Jan 19, 2017 at 10:04:32PM +0200, Andy Shevchenko wrote: >> On Thu, 2017-01-19 at 19:57 +0000, Mark Brown wrote: >=20 >>> I'm missing patches 1 and 3, what's going on here? >=20 >> Patch 1 had been applied by you. I think Jan just needs to resend with= >> proper version and set of patches. >=20 > OK - Jan, the purpose of numbering patches in a series is so we can tel= l > what order they come in. That's it. If the set of patches gets change= d > due to things being added or removed the numbers will be different but > that's totally OK as their only relevance is in ordering things within = a > given posting. Sorry if the numbering was confusing for you, it was, of course, a selective update. Just tell me, if you need a new round with of patches 2 and 3 (as 1 and 2). Jan --=20 Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux --V70RoBfQprV3sMGT6CKci46tx23nJKH0K-- --tp2I6nifge93EDAU6Fhl5qIxBa1NFPgr0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAliCLNgACgkQitSsb3rl5xRMCACg7+24N1ST5uQ46mep2xJYiNFB EhsAoKu5REMieZU/8YzT990cozOd1hrR =5LMA -----END PGP SIGNATURE----- --tp2I6nifge93EDAU6Fhl5qIxBa1NFPgr0--