From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stephen Boyd <sboyd@kernel.org>,
Mike Turquette <mturquette@baylibre.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the clk tree
Date: Mon, 21 Dec 2020 09:07:07 +0100 [thread overview]
Message-ID: <CAMuHMdXbeFfGAkbVqA-EY4_2P7UDdh8Civb+M_nAjL4YNmQ17w@mail.gmail.com> (raw)
In-Reply-To: <20201221083518.5ef7357c@canb.auug.org.au>
Hi Stephen,
On Sun, Dec 20, 2020 at 10:35 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Thu, 10 Dec 2020 08:52:41 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > trees can be pulled into linux-next? That would find this earlier.
> >
> > That sounds like a great idea, also for pinctrl.
> > Can you please add the following:
> > git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
> > renesas-clk
> > git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
> > renesas-pinctrl
> > ?
>
> Added from today. Called clk-renesas and pinctrl-renesas respectively.
Thank you, the result looks good.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-12-21 8:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 22:05 linux-next: Fixes tag needs some work in the clk tree Stephen Rothwell
2020-12-08 8:37 ` Geert Uytterhoeven
2020-12-09 17:29 ` Stephen Boyd
2020-12-10 7:52 ` Geert Uytterhoeven
2020-12-20 21:35 ` Stephen Rothwell
2020-12-21 8:07 ` Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-23 11:46 Stephen Rothwell
2020-10-01 0:22 ` Stephen Boyd
2020-10-01 1:22 ` Stephen Rothwell
2020-03-06 6:58 Stephen Rothwell
2019-05-26 10:35 Stephen Rothwell
2019-01-15 21:34 Stephen Rothwell
2019-01-16 22:35 ` Stephen Boyd
2019-01-17 1:25 ` Fabio Estevam
2019-01-17 1:25 ` Fabio Estevam
2019-01-17 18:42 ` Stephen Boyd
2019-01-18 12:41 ` Michael Ellerman
2019-01-18 12:49 ` Fabio Estevam
2019-01-18 17:37 ` Stephen Boyd
2019-01-18 17:41 ` Nathan Chancellor
2019-01-18 18:36 ` Joe Perches
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=CAMuHMdXbeFfGAkbVqA-EY4_2P7UDdh8Civb+M_nAjL4YNmQ17w@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.