[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240201085205.GA3906@francesco-nb>
Date: Thu, 1 Feb 2024 09:52:05 +0100
From: Francesco Dolcini <francesco@...cini.it>
To: Carlos Song <carlos.song@....com>
Cc: Francesco Dolcini <francesco@...cini.it>,
"broonie@...nel.org" <broonie@...nel.org>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
dl-linux-imx <linux-imx@....com>,
"benjamin@...ler.one" <benjamin@...ler.one>,
"stefanmoring@...il.com" <stefanmoring@...il.com>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] spi: imx: fix the burst length at DMA mode and CPU
mode
On Thu, Feb 01, 2024 at 02:02:36AM +0000, Carlos Song wrote:
> > From: Francesco Dolcini <francesco@...cini.it>
> > Add #include <linux/bits.h> given you are using BITS_PER_BYTE
> >
> I found that <linux/property.h> has been included in spi-imx.c driver.
> And <linux/bits.h> has been included in <linux/property.h>.
> So I didn't add the "#include <linux/bits.h>" on purpose.
I think you should be explicit and include this header.
Code get refactored all the time and you can prevent issues this way.
Francesco
Powered by blists - more mailing lists