From: Mark Brown <broonie@kernel.org>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Irina Tirdea <irina.tirdea@intel.com>
Subject: Re: [PATCH v3 0/4] regmap: i2c block support
Date: Sat, 29 Aug 2015 10:35:48 +0100 [thread overview]
Message-ID: <20150829093548.GY12027@sirena.org.uk> (raw)
In-Reply-To: <1440657872-24554-1-git-send-email-mpa@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Thu, Aug 27, 2015 at 08:44:28AM +0200, Markus Pargmann wrote:
> Hi,
>
> This series adds support for i2c block read/writes. To support the maximum 32
> byte read/write operations, the regmap core is extended by max_raw_read and
> max_raw_write. bulk operations are splitted depending of the size of
> max_raw_read/write.
...and reverted because it broke the build, probably because it was not
a patch against current development trees:
http://kernelci.org/build/broonie-regmap/kernel/v4.2-rc8-34-gd535ae53edec/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-08-29 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 6:44 Markus Pargmann
2015-08-27 6:44 ` [PATCH v3 1/4] regmap: Introduce max_raw_read/write for regmap_bulk_read/write Markus Pargmann
2015-08-27 6:44 ` [PATCH v3 2/4] regmap: regmap max_raw_read/write getter functions Markus Pargmann
2015-08-27 6:44 ` [PATCH v3 3/4] regmap: Add raw_write/read checks for max_raw_write/read sizes Markus Pargmann
2015-08-27 6:44 ` [PATCH v3 4/4] regmap-i2c: Add smbus i2c block support Markus Pargmann
2018-09-06 9:06 ` Nikolaus Voss
2015-08-28 17:33 ` [PATCH v3 0/4] regmap: " Mark Brown
2015-08-29 9:35 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150829093548.GY12027@sirena.org.uk \
--to=broonie@kernel.org \
--cc=irina.tirdea@intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®