From: "Arnd Bergmann" <arnd@kernel.org>
To: "John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"D. Jeff Dionne" <djeffdionne@gmail.com>
Cc: linux-sh@vger.kernel.org, "Rich Felker" <dalias@libc.org>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
linux-kernel@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH 3/4] sh: remove superhyway bus support
Date: Thu, 03 Aug 2023 11:58:43 +0200 [thread overview]
Message-ID: <820f673e-f5d8-4e65-b72c-913320fe1616@app.fastmail.com> (raw)
In-Reply-To: <13c836b31909f2eb64dcf2a5feb22c2a3173bba2.camel@physik.fu-berlin.de>
On Thu, Aug 3, 2023, at 11:36, John Paul Adrian Glaubitz wrote:
> On Thu, 2023-08-03 at 11:19 +0200, Arnd Bergmann wrote:
>> I looked at the clk conversion in the past, as this is not just
>> needed for the DT work, but also to remove CONFIG_HAVE_LEGACY_CLK.
>> The patch series I did a while ago renames the sh clk interfaces
>> to no longer conflict with COMMON_CLK, which should allow it
>> to coexist with a DT-enabled platform in the same kernel build.
>> Let me know if you'd like me to dig out and rebase that series,
>> it probably still applies and may help you here.
>
> Yes, that would be greatly appreciated. Please go ahead.
>
> FWIW, I am currently on vacation until August 15th, so I might be a bit
> slow with open source stuff. I am using the free time to get things done
> on my TODO list.
Ok, I'll start my own vacation on August 15, but should be able to
send you what I had before then.
Arnd
next prev parent reply other threads:[~2023-08-03 9:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 18:48 [PATCH 1/4] sh: remove stale microdev board Arnd Bergmann
2023-08-02 18:48 ` [PATCH 2/4] sh: remove unused sh4-202 support Arnd Bergmann
2023-09-08 10:00 ` John Paul Adrian Glaubitz
2023-08-02 18:48 ` [PATCH 3/4] sh: remove superhyway bus support Arnd Bergmann
2023-08-03 7:58 ` D. Jeff Dionne
2023-08-03 8:44 ` John Paul Adrian Glaubitz
2023-08-03 9:19 ` Arnd Bergmann
2023-08-03 9:36 ` John Paul Adrian Glaubitz
2023-08-03 9:58 ` Arnd Bergmann [this message]
2023-09-08 10:02 ` John Paul Adrian Glaubitz
2023-08-02 18:48 ` [PATCH 4/4] sh: machvec: remove custom ioport_{un,}map() Arnd Bergmann
2023-09-08 10:10 ` John Paul Adrian Glaubitz
2023-09-08 10:20 ` Geert Uytterhoeven
2023-09-08 10:21 ` John Paul Adrian Glaubitz
2023-09-08 10:23 ` John Paul Adrian Glaubitz
2023-09-13 12:32 ` Geert Uytterhoeven
2023-09-13 14:08 ` Arnd Bergmann
2023-09-13 14:13 ` Geert Uytterhoeven
2023-09-13 14:30 ` Arnd Bergmann
2023-09-14 6:23 ` John Paul Adrian Glaubitz
2023-09-14 15:56 ` Arnd Bergmann
2023-09-15 15:41 ` Geert Uytterhoeven
2023-09-15 15:49 ` Arnd Bergmann
2023-09-21 7:45 ` John Paul Adrian Glaubitz
2023-09-21 8:52 ` Geert Uytterhoeven
2023-09-25 7:08 ` Yoshinori Sato
2023-09-25 7:36 ` Arnd Bergmann
2023-09-26 22:15 ` John Paul Adrian Glaubitz
2023-09-08 9:59 ` [PATCH 1/4] sh: remove stale microdev board John Paul Adrian Glaubitz
2023-09-09 22:06 ` John Paul Adrian Glaubitz
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=820f673e-f5d8-4e65-b72c-913320fe1616@app.fastmail.com \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=djeffdionne@gmail.com \
--cc=geert+renesas@glider.be \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®