> -----Original Message----- > From: Randy Dunlap <rdun...@infradead.org> > Sent: Sunday, January 31, 2021 6:14 PM > To: mgr...@linux.intel.com; markgr...@kernel.org; a...@arndb.de; b...@suse.de; > damien.lem...@wdc.com; dragan.cve...@xilinx.com; > gre...@linuxfoundation.org; cor...@lwn.net; palmerdabb...@google.com; > paul.walms...@sifive.com; peng....@nxp.com; robh...@kernel.org; > shawn...@kernel.org; jassisinghb...@gmail.com > Cc: linux-kernel@vger.kernel.org; C, Udhayakumar <udhayakuma...@intel.com> > Subject: Re: [PATCH v4 29/34] Intel tsens i2c slave driver. > > On 1/29/21 6:21 PM, mgr...@linux.intel.com wrote: > > diff --git a/drivers/misc/intel_tsens/Kconfig > > b/drivers/misc/intel_tsens/Kconfig > > index 8b263fdd80c3..be8d27e81864 100644 > > --- a/drivers/misc/intel_tsens/Kconfig > > +++ b/drivers/misc/intel_tsens/Kconfig > > @@ -14,6 +14,20 @@ config INTEL_TSENS_LOCAL_HOST > > Say Y if using a processor that includes the Intel VPU such as > > Keem Bay. If unsure, say N. > > > > +config INTEL_TSENS_I2C_SLAVE > > + bool "I2C slave driver for intel tsens" > > + depends on INTEL_TSENS_LOCAL_HOST > > + depends on I2C=y && I2C_SLAVE > > + help > > + This option enables tsens I2C slave driver. > > Good, it's OK now. > The repeat v3 and then v4 confused me.
Hmm, I'm confused too. I should have only sent v4 on Friday. I'll look over my history and logs to see how I could have sent to blasts one or V3 and then V4. Ugh. Sorry about mixing the V3 and V4 patches in the same batch. FWIW I make an outgoing directory and forgot to clean out the v3 patches that where there from the earlier posting. Resulting in a mixing of the old and current patch set. I'll write a script to automate the creation of the outgoing directory for next time that should correct future screw ups. I'm very sorry for the noise. --mark
