All of lore.kernel.org
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Amlogic clock driver updates for 4.16 - 3rd round
Date: Tue, 2 Jan 2018 17:52:08 -0800	[thread overview]
Message-ID: <20180103015208.GU7997@codeaurora.org> (raw)
In-Reply-To: <1514569451.7439.3.camel@baylibre.com>

On 12/29, Jerome Brunet wrote:
> Dear clock maintainers
> 
> Here is a last round of update for meson clock for v4.16. There is just
> one simple fix
> 

Thanks, pulled into clk-next.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk <linux-clk@vger.kernel.org>,
	"open list:ARM/Amlogic Meson..."
	<linux-amlogic@lists.infradead.org>
Subject: Re: [GIT PULL] Amlogic clock driver updates for 4.16 - 3rd round
Date: Tue, 2 Jan 2018 17:52:08 -0800	[thread overview]
Message-ID: <20180103015208.GU7997@codeaurora.org> (raw)
In-Reply-To: <1514569451.7439.3.camel@baylibre.com>

On 12/29, Jerome Brunet wrote:
> Dear clock maintainers
> 
> Here is a last round of update for meson clock for v4.16. There is just
> one simple fix
> 

Thanks, pulled into clk-next.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2018-01-03  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 17:44 [GIT PULL] Amlogic clock driver updates for 4.16 - 3rd round Jerome Brunet
2017-12-29 17:44 ` Jerome Brunet
2018-01-03  1:52 ` Stephen Boyd [this message]
2018-01-03  1:52   ` 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=20180103015208.GU7997@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linus-amlogic@lists.infradead.org \
    /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.