All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ben Whitten <ben.whitten@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] regmap: fix page selection for noinc reads
Date: Mon, 21 Sep 2020 22:40:47 +0100	[thread overview]
Message-ID: <160072444712.56996.10601329042842573406.b4-ty@kernel.org> (raw)
In-Reply-To: <20200917153405.3139200-1-dmitry.baryshkov@linaro.org>

On Thu, 17 Sep 2020 18:34:04 +0300, Dmitry Baryshkov wrote:
> Non-incrementing reads can fail if register + length crosses page
> border. However for non-incrementing reads we should not check for page
> border crossing. Fix this by passing additional flag to _regmap_raw_read
> and passing length to _regmap_select_page basing on the flag.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/2] regmap: fix page selection for noinc reads
      commit: 4003324856311faebb46cbd56a1616bd3f3b67c2
[2/2] regmap: fix page selection for noinc writes
      commit: 05669b63170771d554854c0e465b76dc98fc7c84

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

      parent reply	other threads:[~2020-09-21 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 15:34 [PATCH v2 1/2] regmap: fix page selection for noinc reads Dmitry Baryshkov
2020-09-17 15:34 ` [PATCH v2 2/2] regmap: fix page selection for noinc writes Dmitry Baryshkov
2020-09-21 21:40 ` 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=160072444712.56996.10601329042842573406.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=ben.whitten@gmail.com \
    --cc=dmitry.baryshkov@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.