From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757044AbcJNGMY (ORCPT ); Fri, 14 Oct 2016 02:12:24 -0400 Received: from smtp10.smtpout.orange.fr ([80.12.242.132]:30876 "EHLO smtp.smtpout.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753562AbcJNGMS (ORCPT ); Fri, 14 Oct 2016 02:12:18 -0400 X-ME-Helo: belgarion X-ME-Auth: amFyem1pay5yb2JlcnRAb3JhbmdlLmZy X-ME-Date: Fri, 14 Oct 2016 08:12:15 +0200 X-ME-IP: 109.220.223.51 From: Robert Jarzmik To: David Miller Cc: robh+dt@kernel.org, mark.rutland@arm.com, nico@fluxnic.net, linux@armlinux.org.uk, arnd@arndb.de, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] net: smc91x: isolate u16 writes alignment workaround References: <1476045227-2970-1-git-send-email-robert.jarzmik@free.fr> <20161013.095012.244532868281403236.davem@davemloft.net> X-URL: http://belgarath.falguerolles.org/ Date: Fri, 14 Oct 2016 08:12:11 +0200 In-Reply-To: <20161013.095012.244532868281403236.davem@davemloft.net> (David Miller's message of "Thu, 13 Oct 2016 09:50:12 -0400 (EDT)") Message-ID: <8760ov7938.fsf@belgarion.home> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org David Miller writes: > From: Robert Jarzmik > Date: Sun, 9 Oct 2016 22:33:45 +0200 > >> Writes to u16 has a special handling on 3 PXA platforms, where the >> hardware wiring forces these writes to be u32 aligned. >> >> This patch isolates this handling for PXA platforms as before, but >> enables this "workaround" to be set up dynamically, which will be the >> case in device-tree build types. >> >> This patch was tested on 2 PXA platforms : mainstone, which relies on >> the workaround, and lubbock, which doesn't. >> >> Signed-off-by: Robert Jarzmik > > Please resubmit this patch series: > > 1) Respun against net-next, these don't currently apply cleanly there. > > 2) With a proper "[PATCH 0/3] ..." posting explaining at a high level > what this patch series does, how it does it, and why it does it > that way. Sure, let me retest it after the rebase, and I'll post again. Cheers. -- Robert