From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Boyd <sboyd@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 1/3] i.MX common clock changes for 5.2
Date: Fri, 26 Apr 2019 10:49:00 +0800 [thread overview]
Message-ID: <20190426024858.GA7980@dragon> (raw)
In-Reply-To: <155620706990.15276.27062523051743240@swboyd.mtv.corp.google.com>
On Thu, Apr 25, 2019 at 08:44:29AM -0700, Stephen Boyd wrote:
> Quoting Shawn Guo (2019-04-21 23:23:12)
> > The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> >
> > Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/clk-imx-5.2
> >
> > for you to fetch changes up to 48a15bb42df85d30e13281642a12fd27221668fa:
> >
> > clk: imx: Remove unused imx_get_clk_hw_fixed (2019-03-26 16:49:49 +0800)
> >
> > ----------------------------------------------------------------
>
> Pulled into clk-next, but next time please merge your branches together
> and send one pull request. Unless the code you're sending is for wildly
> different imx clk drivers I expect to see one PR or one PR and a
> followup PR later on.
Stephen,
Just make sure I understand your request correctly - it's good enough
for me to use just one single branch to collect all i.MX clock patches,
or multiple branches are better and I just need to merge them into one
(and one PR) before sending to you?
Shawn
_______________________________________________
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:[~2019-04-26 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 6:23 [GIT PULL 1/3] i.MX common clock changes for 5.2 Shawn Guo
2019-04-22 6:23 ` [GIT PULL 2/3] i.MX5 " Shawn Guo
2019-04-25 15:44 ` Stephen Boyd
2019-04-22 6:23 ` [GIT PULL 3/3] i.MX7UPL " Shawn Guo
2019-04-25 15:44 ` Stephen Boyd
2019-04-25 15:44 ` [GIT PULL 1/3] i.MX common " Stephen Boyd
2019-04-26 2:49 ` Shawn Guo [this message]
2019-04-26 17:38 ` 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=20190426024858.GA7980@dragon \
--to=shawnguo@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=sboyd@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 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).