From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Biju Das <biju.das@bp.renesas.com>,
Chris Paterson <Chris.Paterson2@renesas.com>
Subject: RE: [PATCH] clk: renesas: r8a774a1: Fix LAST_DT_CORE_CLK
Date: Mon, 25 Feb 2019 09:49:36 +0000 [thread overview]
Message-ID: <TY1PR01MB17702EBF61A0063B7CCE162FC07A0@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdUyf56_CnTS=b5UWxh8rWp9YF8sNR-BOThuB5Tpzf7BRQ@mail.gmail.com>
Hello Geert,
> From: linux-renesas-soc-owner@vger.kernel.org <linux-renesas-soc-owner@vger.kernel.org> On Behalf Of Geert Uytterhoeven
> Sent: 25 February 2019 09:48
> Subject: Re: [PATCH] clk: renesas: r8a774a1: Fix LAST_DT_CORE_CLK
>
> Hi Fabrizio,
>
> On Mon, Feb 25, 2019 at 10:44 AM Fabrizio Castro
> <fabrizio.castro@bp.renesas.com> wrote:
> > > From: Simon Horman <horms@verge.net.au>
> > > Sent: 25 February 2019 09:27
> > > Subject: Re: [PATCH] clk: renesas: r8a774a1: Fix LAST_DT_CORE_CLK
> > >
> > > On Fri, Feb 22, 2019 at 12:01:21PM +0000, Chris Paterson wrote:
> > > >
> > > > > From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> > > > > Sent: 22 February 2019 12:00
> > > > >
> > > > > Enum LAST_DT_CORE_CLK needs updating as R8A774A1_CLK_CANFD
> > > > > was recently added and it's the core clock with the highest
> > > > > index.
> > > > >
> > > > > Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> > > > Reviewed-by: Chris Paterson <chris.paterson2@renesas.com>
> > >
> > > I think this needs:
> > >
> > > Fixes: 9d034e151b40 ("clk: renesas: r8a774a1: Add missing CANFD clock")
> >
> > I naively thought I could only refer to commits from Torvald's, which is clearly wrong,
> > therefore thank you for fixing.
>
> FTR: You can refer to any commits in linux-next that are considered stable,
> i.e. on branches that are never rebased.
> This includes all for-next branches of maintainers who accept pull requests.
I see, thank you for the explanation!
Cheers,
Fab
>
> 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:[~2019-02-25 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:59 [PATCH] clk: renesas: r8a774a1: Fix LAST_DT_CORE_CLK Fabrizio Castro
2019-02-22 12:01 ` Chris Paterson
2019-02-25 9:27 ` Simon Horman
2019-02-25 9:32 ` Geert Uytterhoeven
2019-02-25 9:44 ` Fabrizio Castro
2019-02-25 9:47 ` Geert Uytterhoeven
2019-02-25 9:49 ` Fabrizio Castro [this message]
2019-02-25 17:13 ` Stephen Boyd
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=TY1PR01MB17702EBF61A0063B7CCE162FC07A0@TY1PR01MB1770.jpnprd01.prod.outlook.com \
--to=fabrizio.castro@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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 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.