From: Abel Vesa <abel.vesa@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: miles.chen@mediatek.com, festevam@gmail.com,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
mturquette@baylibre.com, s.hauer@pengutronix.de,
shawnguo@kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v3] clk: imx: use module_platform_driver
Date: Mon, 13 Dec 2021 13:27:23 +0200 [thread overview]
Message-ID: <YbcuG4nn4Dicdl9n@ryzen> (raw)
In-Reply-To: <20211203015714.4BCBCC00446@smtp.kernel.org>
On 21-12-02 17:57:13, Stephen Boyd wrote:
> Quoting Abel Vesa (2021-11-20 12:37:24)
> > On 21-11-05 13:59:32, miles.chen@mediatek.com wrote:
> > > From: Miles Chen <miles.chen@mediatek.com>
> > >
> > > Hi Stephen,
> > >
> > > >> Fixes: e0d0d4d86c766 ("clk: imx8qxp: Support building i.MX8QXP clock driver as module")
> > > >> Cc: Fabio Estevam <festevam@gmail.com>
> > > >> Cc: Stephen Boyd <sboyd@kernel.org>
> > > >> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> > >
> > > > Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> > >
> > > Thanks for doing the review, I cannot find this patch in clk-imx tree,
> > > Would you pick this patch, please?
> >
> > Sorry for the delay.
> >
> > Fixes are usually picked up directly by Stephen,
> > therefore they're not going through clk-imx tree.
> >
> > Stephen, can you pick this one up please?
> >
>
> It doesn't look like a very critical fix but ok. I suppose someone could
> try to use =m for these files?
Yes. I think this is for GKI.
WARNING: multiple messages have this Message-ID (diff)
From: Abel Vesa <abel.vesa@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: miles.chen@mediatek.com, festevam@gmail.com,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
mturquette@baylibre.com, s.hauer@pengutronix.de,
shawnguo@kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v3] clk: imx: use module_platform_driver
Date: Mon, 13 Dec 2021 13:27:23 +0200 [thread overview]
Message-ID: <YbcuG4nn4Dicdl9n@ryzen> (raw)
In-Reply-To: <20211203015714.4BCBCC00446@smtp.kernel.org>
On 21-12-02 17:57:13, Stephen Boyd wrote:
> Quoting Abel Vesa (2021-11-20 12:37:24)
> > On 21-11-05 13:59:32, miles.chen@mediatek.com wrote:
> > > From: Miles Chen <miles.chen@mediatek.com>
> > >
> > > Hi Stephen,
> > >
> > > >> Fixes: e0d0d4d86c766 ("clk: imx8qxp: Support building i.MX8QXP clock driver as module")
> > > >> Cc: Fabio Estevam <festevam@gmail.com>
> > > >> Cc: Stephen Boyd <sboyd@kernel.org>
> > > >> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> > >
> > > > Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> > >
> > > Thanks for doing the review, I cannot find this patch in clk-imx tree,
> > > Would you pick this patch, please?
> >
> > Sorry for the delay.
> >
> > Fixes are usually picked up directly by Stephen,
> > therefore they're not going through clk-imx tree.
> >
> > Stephen, can you pick this one up please?
> >
>
> It doesn't look like a very critical fix but ok. I suppose someone could
> try to use =m for these files?
Yes. I think this is for GKI.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Abel Vesa <abel.vesa@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: miles.chen@mediatek.com, festevam@gmail.com,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
mturquette@baylibre.com, s.hauer@pengutronix.de,
shawnguo@kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v3] clk: imx: use module_platform_driver
Date: Mon, 13 Dec 2021 13:27:23 +0200 [thread overview]
Message-ID: <YbcuG4nn4Dicdl9n@ryzen> (raw)
In-Reply-To: <20211203015714.4BCBCC00446@smtp.kernel.org>
On 21-12-02 17:57:13, Stephen Boyd wrote:
> Quoting Abel Vesa (2021-11-20 12:37:24)
> > On 21-11-05 13:59:32, miles.chen@mediatek.com wrote:
> > > From: Miles Chen <miles.chen@mediatek.com>
> > >
> > > Hi Stephen,
> > >
> > > >> Fixes: e0d0d4d86c766 ("clk: imx8qxp: Support building i.MX8QXP clock driver as module")
> > > >> Cc: Fabio Estevam <festevam@gmail.com>
> > > >> Cc: Stephen Boyd <sboyd@kernel.org>
> > > >> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> > >
> > > > Reviewed-by: Stephen Boyd <sboyd@kernel.org>
> > >
> > > Thanks for doing the review, I cannot find this patch in clk-imx tree,
> > > Would you pick this patch, please?
> >
> > Sorry for the delay.
> >
> > Fixes are usually picked up directly by Stephen,
> > therefore they're not going through clk-imx tree.
> >
> > Stephen, can you pick this one up please?
> >
>
> It doesn't look like a very critical fix but ok. I suppose someone could
> try to use =m for these files?
Yes. I think this is for GKI.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-13 11:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 23:54 [PATCH v3] clk: imx: use module_platform_driver Miles Chen
2021-09-04 23:54 ` Miles Chen
2021-09-04 23:54 ` Miles Chen
2021-09-05 0:44 ` Fabio Estevam
2021-09-05 0:44 ` Fabio Estevam
2021-09-05 0:44 ` Fabio Estevam
2021-09-05 20:42 ` Stephen Boyd
2021-09-05 20:42 ` Stephen Boyd
2021-09-05 20:42 ` Stephen Boyd
2021-11-05 5:59 ` miles.chen
2021-11-05 5:59 ` miles.chen
2021-11-05 5:59 ` miles.chen
2021-11-20 20:37 ` Abel Vesa
2021-11-20 20:37 ` Abel Vesa
2021-11-20 20:37 ` Abel Vesa
2021-12-03 1:57 ` Stephen Boyd
2021-12-03 1:57 ` Stephen Boyd
2021-12-03 1:57 ` Stephen Boyd
2021-12-13 11:27 ` Abel Vesa [this message]
2021-12-13 11:27 ` Abel Vesa
2021-12-13 11:27 ` Abel Vesa
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=YbcuG4nn4Dicdl9n@ryzen \
--to=abel.vesa@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=miles.chen@mediatek.com \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=wsd_upstream@mediatek.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 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.