[GIT PULL] clk fixes for v4.7-rc8

[GIT PULL] clk fixes for v4.7-rc8

[Michael Turquette]

The following changes since commit 086347705be7530feabb6274a3ad81dd545e7914:

  Merge tag 'v4.7-rockchip-clk-fixes1' of git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip into clk-fixes (2016-06-20 17:01:45 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus

for you to fetch changes up to f96423f483b1a7854270335b319e8d1cdd6f3585:

  clk: at91: fix clk_programmable_set_parent() (2016-07-18 17:45:41 -0700)

----------------------------------------------------------------
Fix a bug in the at91 clk driver, two compile time warnings in sunxi clk
drivers, and one bug in a sunxi clk driver introduced in the 4.7 merge
window.

----------------------------------------------------------------
Arnd Bergmann (1):
      clk: sunxi: remove unused variable

Boris Brezillon (1):
      clk: at91: fix clk_programmable_set_parent()

Maxime Ripard (2):
      clk: sunxi: tcon-ch1: Do not return a negative error in get_parent
      clk: sunxi: display: Add per-clock flags

Michael Turquette (1):
      Merge tag 'sunxi-clk-fixes-for-4.7' of https://git.kernel.org/.../mripard/linux into clk-fixes

 drivers/clk/at91/clk-programmable.c    | 2 +-
 drivers/clk/sunxi/clk-sun4i-display.c  | 5 ++++-
 drivers/clk/sunxi/clk-sun4i-tcon-ch1.c | 4 ----
 3 files changed, 5 insertions(+), 6 deletions(-)

[GIT PULL] clk fixes for v4.7-rc8

[Michael Turquette]

The following changes since commit 086347705be7530feabb6274a3ad81dd545e7914:

  Merge tag 'v4.7-rockchip-clk-fixes1' of git://git.kernel.org/pub/scm/linu=
x/kernel/git/mmind/linux-rockchip into clk-fixes (2016-06-20 17:01:45 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixe=
s-for-linus

for you to fetch changes up to f96423f483b1a7854270335b319e8d1cdd6f3585:

  clk: at91: fix clk_programmable_set_parent() (2016-07-18 17:45:41 -0700)

----------------------------------------------------------------
Fix a bug in the at91 clk driver, two compile time warnings in sunxi clk
drivers, and one bug in a sunxi clk driver introduced in the 4.7 merge
window.

----------------------------------------------------------------
Arnd Bergmann (1):
      clk: sunxi: remove unused variable

Boris Brezillon (1):
      clk: at91: fix clk_programmable_set_parent()

Maxime Ripard (2):
      clk: sunxi: tcon-ch1: Do not return a negative error in get_parent
      clk: sunxi: display: Add per-clock flags

Michael Turquette (1):
      Merge tag 'sunxi-clk-fixes-for-4.7' of https://git.kernel.org/.../mri=
pard/linux into clk-fixes

 drivers/clk/at91/clk-programmable.c    | 2 +-
 drivers/clk/sunxi/clk-sun4i-display.c  | 5 ++++-
 drivers/clk/sunxi/clk-sun4i-tcon-ch1.c | 4 ----
 3 files changed, 5 insertions(+), 6 deletions(-)

Re: [GIT PULL] clk fixes for v4.7-rc8

[Linus Torvalds]

On Fri, Jul 22, 2016 at 9:47 AM, Michael Turquette
<mturquette@baylibre.com> wrote:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus

The pgp key you sign your pull requests with keep changing. Sometimes
it's your primary key, most often it seems to be your 4kb subkey, now
it's another 2kb subkey.

All the signatures look fine, but is there a reason for this odd behavior?

            Linus

Re: [GIT PULL] clk fixes for v4.7-rc8

[Michael Turquette]

Quoting Linus Torvalds (2016-07-22 20:01:24)
> On Fri, Jul 22, 2016 at 9:47 AM, Michael Turquette
> <mturquette@baylibre.com> wrote:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-=
fixes-for-linus
> =

> The pgp key you sign your pull requests with keep changing. Sometimes
> it's your primary key, most often it seems to be your 4kb subkey, now
> it's another 2kb subkey.
> =

> All the signatures look fine, but is there a reason for this odd behavior?

Yes. It's the result of fickleness and constant experimentation on my
part with GPG version, testing out various smart cards and other crypto
hardware (with various key size limitations), migrating keys to the card
versus generating new keys securely on-card, etc. Basically, screwin'
around.

I've settled on something that I will be sticking with for the
foreseeable future.

Regards,
Mike

> =

>             Linus