mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jim Wylder <jwylder@google.com>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: regmap: Account for register length when chunking
Date: Wed, 17 May 2023 10:20:10 -0500	[thread overview]
Message-ID: <20230517152444.3690870-1-jwylder@google.com> (raw)
In-Reply-To: <ZGQqzlU7XPF+rS8c@finisterre.sirena.org.uk>

Sorry, I didn't intend to ignore your point about pad_bytes.  I had
misread the second half of the sentences as being the result of the
first half - rather than as an additional correction needed.

Thanks for the feedback.  



  reply	other threads:[~2023-05-17 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 14:39 [PATCH] " Jim Wylder
2023-05-15 14:59 ` Mark Brown
2023-05-16 15:52   ` Jim Wylder
2023-05-17  1:15     ` Mark Brown
2023-05-17 15:20       ` Jim Wylder [this message]
2023-05-17 15:20         ` Jim Wylder
2023-05-18 17:31           ` Mark Brown

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=20230517152444.3690870-1-jwylder@google.com \
    --to=jwylder@google.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    /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®