From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932247AbcJMNua (ORCPT ); Thu, 13 Oct 2016 09:50:30 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:60840 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754955AbcJMNuU (ORCPT ); Thu, 13 Oct 2016 09:50:20 -0400 Date: Thu, 13 Oct 2016 09:50:12 -0400 (EDT) Message-Id: <20161013.095012.244532868281403236.davem@davemloft.net> To: robert.jarzmik@free.fr 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 From: David Miller In-Reply-To: <1476045227-2970-1-git-send-email-robert.jarzmik@free.fr> References: <1476045227-2970-1-git-send-email-robert.jarzmik@free.fr> X-Mailer: Mew version 6.6 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 13 Oct 2016 06:50:14 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2 1/3] net: smc91x: isolate u16 writes alignment workaround Date: Thu, 13 Oct 2016 09:50:12 -0400 (EDT) Message-ID: <20161013.095012.244532868281403236.davem@davemloft.net> References: <1476045227-2970-1-git-send-email-robert.jarzmik@free.fr> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, mark.rutland-5wv7dgnIgG8@public.gmane.org, nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org, linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org, arnd-r2nGTMty4D4@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: robert.jarzmik-GANU6spQydw@public.gmane.org Return-path: In-Reply-To: <1476045227-2970-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org 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. Thanks. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html