From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751935AbcBLW0J (ORCPT ); Fri, 12 Feb 2016 17:26:09 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:48550 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751850AbcBLW0G (ORCPT ); Fri, 12 Feb 2016 17:26:06 -0500 Date: Fri, 12 Feb 2016 22:25:56 +0000 From: Mark Brown To: Stephen Boyd Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Kenneth Westfield , Kevin Hilman Message-ID: <20160212222556.GC18988@sirena.org.uk> References: <1455298217-15744-1-git-send-email-sboyd@codeaurora.org> <20160212212600.GA18872@sirena.org.uk> <20160212220454.GF4847@codeaurora.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NKoe5XOeduwbEQHU" Content-Disposition: inline In-Reply-To: <20160212220454.GF4847@codeaurora.org> X-Cookie: Isn't this my STOP?! User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH] Revert "ASoC: qcom: Specify LE device endianness" X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --NKoe5XOeduwbEQHU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 12, 2016 at 02:04:54PM -0800, Stephen Boyd wrote: > On 02/12, Mark Brown wrote: > > So, I applied this to -next as that's where it applies but it seems that > > you're trying to revert a commit that's in Linus' tree so should go as a > > fix to him. Can you send a fix against Linus' tree too please? > Did you want me to send the fix directly to Linus? The patch > applies to both -next and Linus' tree, although you're right I > generated this patch against -next. If I apply it to Linus' tree > and then git format-patch it's exactly the same except for the > commit hash: No, of course not! Send it to me. What I'm looking for is something that I can apply - it doesn't apply to my current Qualcomm fixes branch. = =20 Looking again I see that the issue is that that branch is based on v4.4, I pulled it over now. --NKoe5XOeduwbEQHU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWvlvlAAoJECTWi3JdVIfQA/cH/it3XLvF955R2APke9Plrlfn EHur9hpRTeDPlSKPsyaCzF47/xs5BeDDgO9+1rezx7alZqBBmhZDkrwi/a9qwqWE jK9BjYX6iCo110ngFqd/RLVGMMjkNZy3JvW2qNhvSfTC1XELuY/y1b1OA1jeGI9G 3Uyqwc34507HjP08Ny3drD5NOCc65pvUGp9ja4m79Kfk+ZfWOnxwcCU3fIXoVPOY Tww9u/13fW3afmmfXsmNLcQ9D6N6bfvt8m11DFI44oGe+wnyau9uHseGrAW3lMnn tD6qYehd6QA9x7xHmabDqxK+rzP5fcBvlE+jGeY7xfPsMaFxCMMhF+cb/hqRpO0= =OW/s -----END PGP SIGNATURE----- --NKoe5XOeduwbEQHU--