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 22:37:34 +0200 [thread overview]
Message-ID: <62d5c891.1c69fb81.cf50e.3d99@mx.google.com> (raw)
In-Reply-To: <62d572ed.1c69fb81.c7f5e.a109@mx.google.com>
On Mon, Jul 18, 2022 at 04:44:23PM +0200, Christian Marangi wrote:
> On Mon, Jul 18, 2022 at 03:42:06PM +0100, Mark Brown wrote:
> > 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?
>
> Ohh sorry, I was too generic in the patch comments and didn't mention it
> was an actual dependency.
>
> It's not too urgent, (I assume) but it was said that it was preferrable
> to have the changes done in 2 weeks window (the one in net-next about
> the working driver). Will ask on net-next and give you news ASAP.
>
Hi Mark,
sorry for the delay, I pointed out this problem with net-next and we
decided to adopt a workaround so this is not urgent anymore and we can
wait the merge window to have this change in net-next.
The required code will be updated later when this change is merged.
--
Ansuel
prev parent reply other threads:[~2022-07-18 20:54 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
2022-07-18 14:44 ` Christian Marangi
2022-07-18 20:37 ` Christian Marangi [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=62d5c891.1c69fb81.cf50e.3d99@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;
as well as URLs for NNTP newsgroup(s).