From: Stephen Boyd <sboyd@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>,
Stefan Agner <stefan@agner.ch>,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX clock fixes for 5.6, round 2
Date: Mon, 16 Mar 2020 11:27:54 -0700 [thread overview]
Message-ID: <158438327489.88485.18004315671422121263@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200316002239.GK29269@dragon>
Quoting Shawn Guo (2020-03-15 17:22:40)
> On Fri, Mar 06, 2020 at 01:11:19PM -0800, Stephen Boyd wrote:
> > Quoting Shawn Guo (2020-02-24 04:13:23)
> > > The following changes since commit 5eb40257047fb11085d582b7b9ccd0bffe900726:
> > >
> > > clk: imx8mn: Fix incorrect clock defines (2020-02-17 15:18:00 +0800)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-fixes-5.6-2
> > >
> > > for you to fetch changes up to 6fb9006abe37e44afaed4f2a5fd3a247a815bb8d:
> > >
> > > clk: imx8mp: Correct the enet_qos parent clock (2020-02-24 15:38:03 +0800)
> > >
> > > ----------------------------------------------------------------
Thanks. Pulled into clk-fixes.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Stefan Agner <stefan@agner.ch>,
linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <festevam@gmail.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX clock fixes for 5.6, round 2
Date: Mon, 16 Mar 2020 11:27:54 -0700 [thread overview]
Message-ID: <158438327489.88485.18004315671422121263@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200316002239.GK29269@dragon>
Quoting Shawn Guo (2020-03-15 17:22:40)
> On Fri, Mar 06, 2020 at 01:11:19PM -0800, Stephen Boyd wrote:
> > Quoting Shawn Guo (2020-02-24 04:13:23)
> > > The following changes since commit 5eb40257047fb11085d582b7b9ccd0bffe900726:
> > >
> > > clk: imx8mn: Fix incorrect clock defines (2020-02-17 15:18:00 +0800)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-fixes-5.6-2
> > >
> > > for you to fetch changes up to 6fb9006abe37e44afaed4f2a5fd3a247a815bb8d:
> > >
> > > clk: imx8mp: Correct the enet_qos parent clock (2020-02-24 15:38:03 +0800)
> > >
> > > ----------------------------------------------------------------
Thanks. Pulled into clk-fixes.
_______________________________________________
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:[~2020-03-16 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 12:13 [GIT PULL] i.MX clock fixes for 5.6, round 2 Shawn Guo
2020-02-24 12:13 ` Shawn Guo
2020-03-06 21:11 ` Stephen Boyd
2020-03-06 21:11 ` Stephen Boyd
2020-03-16 0:22 ` Shawn Guo
2020-03-16 0:22 ` Shawn Guo
2020-03-16 18:27 ` Stephen Boyd [this message]
2020-03-16 18:27 ` 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=158438327489.88485.18004315671422121263@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--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=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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.