linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] bcm2835 clk changes for 4.6 maybe
Date: Tue, 29 Mar 2016 16:39:23 -0700	[thread overview]
Message-ID: <20160329233923.GR18567@codeaurora.org> (raw)
In-Reply-To: <1458265130-30734-1-git-send-email-eric@anholt.net>

On 03/17, Eric Anholt wrote:
> This is late, so feel free to drop it, but I figured I'd send it to
> you in case you were still open to merges.  I've pounded on it a bit
> today (modesets to all sorts of resolutions on HDMI, used it for
> testing the DPI panel support that I'm hoping to have for 4.7, and did
> a whole lot of browsing of clk_summary as I debugged DPI), and kbuild
> test robot came back clean, so I'm pretty happy with it.
> 
> The following changes since commit 4d3ac6662452060721599a3392bc2f524af984cb:
> 
>   clk: bcm2835: fix check of error code returned by devm_ioremap_resource() (2016-03-15 18:14:11 -0700)
> 
> are available in the git repository at:
> 
>   git at github.com:anholt/linux.git tags/bcm2835-clk-next-2016-03-17

Please make sure to use a proper URL here. I don't have access to
git at github.com, but I can fetch this from
git://github.com/anholt/linux.git. The tag and the contents match
so I'm fairly confident all is well.

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

  reply	other threads:[~2016-03-29 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  1:38 [GIT PULL] bcm2835 clk changes for 4.6 maybe Eric Anholt
2016-03-29 23:39 ` Stephen Boyd [this message]
2016-03-30  5:12   ` Eric Anholt
2016-04-02  1:08     ` 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=20160329233923.GR18567@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-arm-kernel@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 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).