From: Mark Brown <broonie@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
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:42:06 +0100 [thread overview]
Message-ID: <YtVxPjzG2JrbPTKf@sirena.org.uk> (raw)
In-Reply-To: <62d564c7.1c69fb81.9010e.da70@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Mon, Jul 18, 2022 at 03:48:52PM +0200, Christian Marangi wrote:
> 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)
Oh, it would have been good to know about this when reviewing the patch
rather than after the fact - since this hadn't been mentioned it's now
applied on the main development branch with everything that's going into
the next release rather than on a separate branch for easy merging
elsewhere. How urgent is this, given that the merge window is likely to
open at the weekend so this'll get sent to Linus at that point - is the
driver otherwise near merging?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-18 14:42 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
2022-07-18 14:42 ` Mark Brown [this message]
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=YtVxPjzG2JrbPTKf@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ansuelsmth@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).