public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Serge Semin <fancer.lancer@gmail.com>
Cc: wuyonggang001@208suo.com, mturquette@baylibre.com,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: baikal-t1: Using div64_ Ul replaces do_ Div() function
Date: Fri, 28 Jul 2023 20:24:19 -0700	[thread overview]
Message-ID: <f4bb6c51f66325c388a43b9336ffa45b.sboyd@kernel.org> (raw)
In-Reply-To: <vnps4c6o6nsvazyggdqhhqedwsf7vrucc2kpiwpuozi7e2e7tc@celmt367ov73>

Quoting Serge Semin (2023-07-27 05:28:47)
> On Mon, Jul 24, 2023 at 05:11:23PM +0300, Serge Semin wrote:
> > On Mon, Jul 24, 2023 at 03:38:49PM +0200, Geert Uytterhoeven wrote:
> > > > >
> > > > > Likewise.
> > > >
> > > > Right. This will also break the driver.
> 
> No news from Yonggang meanwhile the patch will certainly break the
> driver. Is it still possible to drop it from the clk-cleanup and
> clk-next branches then before it gets to the mainline kernel?
> 

I've dropped it.

  reply	other threads:[~2023-07-29  3:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230612033904.34921-1-zhanglibing@cdjrlc.com>
     [not found] ` <0dc9409b662180ed29cbc281f0f076b7@208suo.com>
2023-06-14  5:45   ` [PATCH] clk: baikal-t1: Using div64_ Ul replaces do_ Div() function wuyonggang001
2023-07-19 22:08     ` Stephen Boyd
2023-07-24 10:04     ` Geert Uytterhoeven
2023-07-24 13:13       ` Serge Semin
2023-07-24 13:38         ` Geert Uytterhoeven
2023-07-24 14:01           ` David Laight
2023-07-24 14:11           ` Serge Semin
2023-07-27 12:28             ` Serge Semin
2023-07-29  3:24               ` Stephen Boyd [this message]
2023-07-31 23:55                 ` Serge Semin

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=f4bb6c51f66325c388a43b9336ffa45b.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=wuyonggang001@208suo.com \
    /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