subject:"\[PATCH\] NFC\: trf7970a\: fix check of clock frequencies, use \&\& instead of \|\|"

Re: [PATCH] NFC: trf7970a: fix check of clock frequencies, use && instead of ||

2017-06-22 Thread Samuel Ortiz

Hi Colin, On Mon, Apr 24, 2017 at 02:36:02PM +0100, Colin King wrote: > From: Colin Ian King > > The "or" condition (clk_freq != TRF7970A_27MHZ_CLOCK_FREQUENCY) || > (clk_freq != TRF7970A_13MHZ_CLOCK_FREQUE) will always be true because > clk_freq cannot be equal to two

Re: [PATCH] NFC: trf7970a: fix check of clock frequencies, use && instead of ||

2017-04-27 Thread Mark Greer

> From: Colin Ian King Hi Colin. [I completely missed this patch and don't have it to directly respond to anymore so I probably missed some addresses from the CC list.] > The "or" condition (clk_freq != TRF7970A_27MHZ_CLOCK_FREQUENCY) || > (clk_freq !=

Re: [PATCH] NFC: trf7970a: fix check of clock frequencies, use && instead of ||

2017-04-25 Thread Geoff Lansberry

On Mon, Apr 24, 2017 at 9:36 AM, Colin King wrote: > From: Colin Ian King > > The "or" condition (clk_freq != TRF7970A_27MHZ_CLOCK_FREQUENCY) || > (clk_freq != TRF7970A_13MHZ_CLOCK_FREQUE) will always be true because > clk_freq cannot be equal

[PATCH] NFC: trf7970a: fix check of clock frequencies, use && instead of ||

2017-04-24 Thread Colin King

From: Colin Ian King The "or" condition (clk_freq != TRF7970A_27MHZ_CLOCK_FREQUENCY) || (clk_freq != TRF7970A_13MHZ_CLOCK_FREQUE) will always be true because clk_freq cannot be equal to two different values at the same time. Use the && operator instead of || to fix