From: Christian Marangi <ansuelsmth@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH] regmap: permit to set reg_update_bits with bulk implementation
Date: Mon, 18 Jul 2022 15:48:52 +0200 [thread overview]
Message-ID: <62d564c7.1c69fb81.9010e.da70@mx.google.com> (raw)
In-Reply-To: <165815182610.53791.17547202213321860152.b4-ty@kernel.org>
On Mon, Jul 18, 2022 at 02:43:46PM +0100, Mark Brown wrote:
> On Fri, 15 Jul 2022 22:10:32 +0200, Christian Marangi wrote:
> > A regmap may still require to set a custom reg_update_bits instead of
> > relying to the regmap_bus_read/write general function.
> >
> > Permit to set it in the map if provided by the regmap config.
> >
> >
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
>
> Thanks!
>
> [1/1] regmap: permit to set reg_update_bits with bulk implementation
> commit: 739f872e48d47c97fa17a86a7b3356771b75240c
>
Hi,
thanks, assuming everything went smooth with the merge to linux-next and
no problems arise, can you provide a signed tag?
This is needed for a net-next series that is currently in RFC state as
it does depends on this.
(I had this problem before and it was said that in this kind of
situation I had to ask for a signed tag to merge the related patch in
net-next branch)
Thanks for the help!
--
Ansuel
next prev parent reply other threads:[~2022-07-18 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 20:10 [PATCH] regmap: permit to set reg_update_bits with bulk implementation Christian Marangi
2022-07-18 13:43 ` Mark Brown
2022-07-18 13:48 ` Christian Marangi [this message]
2022-07-18 14:42 ` Mark Brown
2022-07-18 14:44 ` Christian Marangi
2022-07-18 20:37 ` Christian Marangi
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=62d564c7.1c69fb81.9010e.da70@mx.google.com \
--to=ansuelsmth@gmail.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