[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180819180930.18f2dfc1@archlinux>
Date: Sun, 19 Aug 2018 18:09:30 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Stefan Popa <stefan.popa@...log.com>, lars@...afoo.de,
Michael.Hennerich@...log.com, knaack.h@....de, pmeerw@...erw.net,
mark.rutland@....com, davem@...emloft.net,
mchehab+samsung@...nel.org, gregkh@...uxfoundation.org,
akpm@...ux-foundation.org, robh+dt@...nel.org,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Crestez Dan Leonard <leonard.crestez@...el.com>
Subject: Re: [PATCH v6 3/6] regmap: Add regmap_noinc_read API
On Fri, 10 Aug 2018 11:38:56 +0100
Mark Brown <broonie@...nel.org> wrote:
> On Fri, Aug 10, 2018 at 11:46:20AM +0300, Stefan Popa wrote:
> > From: Crestez Dan Leonard <leonard.crestez@...el.com>
> >
> > The regmap API usually assumes that bulk read operations will read a
> > range of registers but some I2C/SPI devices have certain registers for
> > which a such a read operation will return data from an internal FIFO
> > instead. Add an explicit API to support bulk read without range semantics.
>
> Please don't resubmit patches that have already been applied, you should
> submit patches against current code in the tree you're expecting things
> to be applied to. If any updates are needed to a patch that's already
> been applied you should submit incremental patches which make those
> updates. This avoids having to change published git commits which could
> cause problems for people working against git.
I've merged the regmap branch in question into iio.git. To add to Mark's
comment it would have been helpful to have the cover letter mention the
need to do that with a copy of what Mark replied with when he took this
patch (as it gives me the details I need to pick up that branch).
Jonathan
Powered by blists - more mailing lists