From: broonie@kernel.org
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regmap fixes for v5.8-rc2
Date: Mon, 22 Jun 2020 12:39:14 +0100 [thread overview]
Message-ID: <20200622114015.60DD1206BE@mail.kernel.org> (raw)
The following changes since commit 93b929922dba3a42b0439ef13144c6032b7733c8:
Merge series "regmap: provide simple bitops and use them in a driver" from Bartosz Golaszewski <brgl@bgdev.pl> Bartosz Golaszewski <bgolaszewski@baylibre.com>: (2020-05-29 14:00:44 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v5.8-rc2
for you to fetch changes up to 95b2c3ec4cb1689db2389c251d39f64490ba641c:
regmap: Fix memory leak from regmap_register_patch (2020-06-17 17:12:11 +0100)
----------------------------------------------------------------
regmap: Fixes for v5.8
A few small fixes, none of which are likely to have any substantial
impact here - the most substantial one is a fix for a long standing
memory leak on devices that use register patching which will only have
an impact if the device is removed and re-added.
----------------------------------------------------------------
Bartosz Golaszewski (1):
regmap: fix the kerneldoc for regmap_test_bits()
Charles Keepax (1):
regmap: Fix memory leak from regmap_register_patch
Jens Thoms Toerring (1):
regmap: fix alignment issue
drivers/base/regmap/regmap.c | 106 ++++++++++++++++++++-----------------------
1 file changed, 50 insertions(+), 56 deletions(-)
next reply other threads:[~2020-06-22 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 11:39 broonie [this message]
2020-06-22 12:09 ` [GIT PULL] regmap fixes for v5.8-rc2 Mark Brown
2020-06-22 16:46 ` Linus Torvalds
2020-06-22 16:59 ` Mark Brown
2020-06-22 16:55 ` pr-tracker-bot
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=20200622114015.60DD1206BE@mail.kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.