mbox series

[GIT,PULL,1/3] i.MX common clock changes for 5.2

Message ID 20190422062314.1354-1-shawnguo@kernel.org
State New
Headers show
Series [GIT,PULL,1/3] i.MX common clock changes for 5.2 | expand

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/clk-imx-5.2

Message

Shawn Guo April 22, 2019, 6:23 a.m. UTC
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)

----------------------------------------------------------------
i.MX common clock changes for 5.2:
 - Clean up unused imx_get_clk_hw_fixed() inline function.

----------------------------------------------------------------
Abel Vesa (1):
      clk: imx: Remove unused imx_get_clk_hw_fixed

 drivers/clk/imx/clk.h | 5 -----
 1 file changed, 5 deletions(-)

Comments

Stephen Boyd April 25, 2019, 3:44 p.m. UTC | #1
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.
Shawn Guo April 26, 2019, 2:49 a.m. UTC | #2
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
Stephen Boyd April 26, 2019, 5:38 p.m. UTC | #3
Quoting Shawn Guo (2019-04-25 19:49:00)
> 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?
> 

I'd go with one branch unless you need to do something more complicated.
That's what the "wildly different" part is about above.