From: Julien Massot <julien.massot@iot.bzh>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH 0/5] clk: renesas: Add MFIS clock
Date: Fri, 11 Dec 2020 14:06:10 +0100 [thread overview]
Message-ID: <85ac5ee3-c5c6-79f7-702d-68dc6499ac7f@iot.bzh> (raw)
In-Reply-To: <CAMuHMdVhVViA4zyiHNMdc_Y1NR7GXp=-wYtWvy1pTbFhFNkfZg@mail.gmail.com>
> Is it OK if I postpone applying this (possibly squashed into a single commit)
> until you have posted an MFIS driver?
Yes it does make sense, the mailbox driver could take longer
to be reviewed. I was more looking at how to break dependencies if
the mailbox driver will go into a different tree.
Thanks for your time,
Have a nice weekend too !
Julien
next prev parent reply other threads:[~2020-12-11 13:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 14:20 [PATCH 0/5] clk: renesas: Add MFIS clock Julien Massot
2020-12-10 14:20 ` [PATCH 1/5] clk: renesas: r8a7795: " Julien Massot
2020-12-11 12:48 ` Geert Uytterhoeven
2020-12-10 14:20 ` [PATCH 2/5] clk: renesas: r8a7796: " Julien Massot
2020-12-11 12:49 ` Geert Uytterhoeven
2020-12-10 14:20 ` [PATCH 3/5] clk: renesas: r8a77965: " Julien Massot
2020-12-11 12:50 ` Geert Uytterhoeven
2020-12-10 14:20 ` [PATCH 4/5] clk: renesas: r8a77990: " Julien Massot
2020-12-11 12:50 ` Geert Uytterhoeven
2020-12-10 14:20 ` [PATCH 5/5] clk: renesas: r8a77995: " Julien Massot
2020-12-11 12:50 ` Geert Uytterhoeven
2020-12-10 14:57 ` [PATCH 0/5] clk: renesas: " Biju Das
2020-12-10 15:03 ` Julien Massot
2020-12-10 15:44 ` Biju Das
2020-12-11 12:48 ` Geert Uytterhoeven
2020-12-11 15:49 ` Biju Das
2020-12-11 12:52 ` Geert Uytterhoeven
2020-12-11 13:06 ` Julien Massot [this message]
2023-02-01 13:41 ` Geert Uytterhoeven
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=85ac5ee3-c5c6-79f7-702d-68dc6499ac7f@iot.bzh \
--to=julien.massot@iot.bzh \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).