From mboxrd@z Thu Jan 1 00:00:00 1970 From: LW@KARO-electronics.de (Lothar =?UTF-8?B?V2HDn21hbm4=?=) Date: Tue, 4 Nov 2014 11:29:12 +0100 Subject: net: fec: fix regression on i.MX28 introduced by rx_copybreak support In-Reply-To: <20141031063210.69004315@ipc1.ka-ro> References: <1414502584-10583-1-git-send-email-LW@KARO-electronics.de> <20141029.153430.1036004676442879956.davem@davemloft.net> <20141030075104.05e44b43@ipc1.ka-ro> <20141030.121710.1524000348187962764.davem@davemloft.net> <20141031063210.69004315@ipc1.ka-ro> Message-ID: <20141104112912.2be8bf1a@ipc1.ka-ro> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi David, Lothar Wa?mann wrote: > David Miller wrote: > > From: Lothar Wa?mann > > Date: Thu, 30 Oct 2014 07:51:04 +0100 > > > > >> Also, I don't thnk your DIV_ROUND_UP() eliminate for the loop > > >> in swap_buffer() is valid. The whole point is that the current > > >> code handles buffers which have a length which is not a multiple > > >> of 4 properly, after your change it will no longer do so. > > >> > > > Do you really think so? > > > > Yes, because you're rounding down so you'll miss the final > > partial word (if any). > > > Nope. DIV_ROUND_UP() would give '1' as upper bound for lengths from 1 to > 4, '2' for lengths from 5 to 8 and so on. > > The loop with increment 4 and i < len does exactly the same. > Try it for yourself, if you don't believe it. > > Do you still think, the loop without DIV_ROUND_UP() is incorrect, or can this patch be applied? Lothar Wa?mann -- ___________________________________________________________ Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10 Gesch?ftsf?hrer: Matthias Kaussen Handelsregistereintrag: Amtsgericht Aachen, HRB 4996 www.karo-electronics.de | info at karo-electronics.de ___________________________________________________________