public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Chanwoo Choi <chanwoo@kernel.org>
Cc: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the bitmap tree with the devfreq tree
Date: Tue, 9 Sep 2025 12:46:27 -0400	[thread overview]
Message-ID: <aMBZ4zTyMZLdQWJx@yury> (raw)
In-Reply-To: <CAGTfZH3JyMGvjWni1Ge+a1=4nRPL30a84DCamj1AtXRLRMgzeQ@mail.gmail.com>

> > Dropping the bitmap tree changes of this driver is fine by me. I can
> > send a rebased patch of that for the next merge window to do the move
> > from the driver's own macro to the shared macro. The functional
> > change in the devfreq tree is more important to get in.
> 
> I think that you need to ask to drop your patch[1] on bitmap tree.
> [1] 414054a0bc1f ("PM / devfreq: rockchip-dfi: switch to FIELD_PREP_WM16 macro")

So I did.

Nicolas, please make sure resending the dropped patch
rebased shortly after merge window closing. I'd like to schedule it
for -rc2. 

Thanks,
Yury

> Before fixing this merge conflict, I'll drop the patches related to patch[2].
> [2] 7d9e29ed3f8e ("PM / devfreq: rockchip-dfi: add support for LPDDR5")
> 
> After resolving the merge conflict, I'll apply them again.
> 
> -- 
> Best Regards,
> Chanwoo Choi
> Samsung Electronics
> 

  reply	other threads:[~2025-09-09 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08  7:51 linux-next: manual merge of the bitmap tree with the devfreq tree Stephen Rothwell
2025-09-08 11:26 ` Nicolas Frattaroli
2025-09-08 14:22   ` Chanwoo Choi
2025-09-09 16:46     ` Yury Norov [this message]
2025-09-09 17:42       ` Nicolas Frattaroli
2025-09-09 22:09         ` Chanwoo Choi

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=aMBZ4zTyMZLdQWJx@yury \
    --to=yury.norov@gmail.com \
    --cc=chanwoo@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nicolas.frattaroli@collabora.com \
    --cc=sfr@canb.auug.org.au \
    /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