[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161013.095012.244532868281403236.davem@davemloft.net>
Date: Thu, 13 Oct 2016 09:50:12 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: robert.jarzmik@...e.fr
Cc: robh+dt@...nel.org, mark.rutland@....com, nico@...xnic.net,
linux@...linux.org.uk, arnd@...db.de, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] net: smc91x: isolate u16 writes alignment
workaround
From: Robert Jarzmik <robert.jarzmik@...e.fr>
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 <robert.jarzmik@...e.fr>
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.
Powered by blists - more mailing lists