linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dinguyen@altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: dw_apb_timer compatible string change
Date: Tue, 10 Dec 2013 09:51:28 -0600	[thread overview]
Message-ID: <1386690688.6211.3.camel@linux-builds1> (raw)
In-Reply-To: <20131209104547.GC705@tarshish>

Hi Baruch,

On Mon, 2013-12-09 at 12:45 +0200, Baruch Siach wrote:
> Hi Dinh,
> 
> In commit 620f5e1cbf (dts: Rename DW APB timer compatible strings) you changed 
> the DesignWare APB timer documented compatible string to "dw-apb-timer", and 
> deprecated the old ones. This commit went into v3.12 through the ARM SoC tree. 
> The driver itself, however, doesn't seems to have been updated to recognize 
> this newly documented compatible string as of v3.13-rc3.
> 
> Do you know whether there is a patch fixing the driver in some patch queue?

It is is Daniel's tree, and hopefully, it should be going into
3.13-fixes soon.

Dinh
> 
> baruch
> 

      reply	other threads:[~2013-12-10 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 10:45 dw_apb_timer compatible string change Baruch Siach
2013-12-10 15:51 ` Dinh Nguyen [this message]

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=1386690688.6211.3.camel@linux-builds1 \
    --to=dinguyen@altera.com \
    --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).