From: John Keeping <john@metanate.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] rockchip: i2c: fix >32 byte writes
Date: Thu, 18 Aug 2016 20:08:39 +0100 [thread overview]
Message-ID: <20160818190842.25094-1-john@metanate.com> (raw)
The first two patches are just cleanup that I noticed while in the area,
the point of the series is the final patch which fixes an error when
trying to write more than 32 bytes via the Rockchip I2C driver.
John Keeping (3):
rockchip: i2c: use named constant when appropriate
rockchip: i2c: move register write out of inner loop
rockchip: i2c: fix >32 byte writes
drivers/i2c/rk_i2c.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--
2.9.3.728.g30b24b4.dirty
next reply other threads:[~2016-08-18 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 19:08 John Keeping [this message]
2016-08-18 19:08 ` [U-Boot] [PATCH 1/3] rockchip: i2c: use named constant when appropriate John Keeping
2016-09-06 1:03 ` Simon Glass
2016-08-18 19:08 ` [U-Boot] [PATCH 2/3] rockchip: i2c: move register write out of inner loop John Keeping
2016-09-06 1:03 ` Simon Glass
2016-08-18 19:08 ` [U-Boot] [PATCH 3/3] rockchip: i2c: fix >32 byte writes John Keeping
2016-09-06 1:03 ` Simon Glass
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=20160818190842.25094-1-john@metanate.com \
--to=john@metanate.com \
--cc=u-boot@lists.denx.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