linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: alexandre.belloni@bootlin.com, robh+dt@kernel.org,
	a.zummo@towertech.it, mpe@ellerman.id.au, leoyang.li@nxp.com,
	benh@kernel.crashing.org, Biwen Li <biwen.li@oss.nxp.com>
Cc: devicetree@vger.kernel.org, Biwen Li <biwen.li@nxp.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-rtc@vger.kernel.org
Subject: Re: [v3 1/2] dts: ppc: t4240rdb: remove interrupts property
Date: Wed,  9 Sep 2020 23:37:33 +1000 (AEST)	[thread overview]
Message-ID: <159965824243.811679.11439322992907877530.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200527034228.23793-1-biwen.li@oss.nxp.com>

On Wed, 27 May 2020 11:42:27 +0800, Biwen Li wrote:
> Since the interrupt pin for RTC DS1374 is not connected
> to the CPU on T4240RDB, remove the interrupt property
> from the device tree.
> 
> This also fix the following warning for hwclock.util-linux:
> $ hwclock.util-linux
> hwclock.util-linux: select() to /dev/rtc0
> to wait for clock tick timed out

Applied to powerpc/next.

[1/2] powerpc/dts/t4240rdb: remove interrupts property
      https://git.kernel.org/powerpc/c/8c7614d648037b0776e0b76cb62911be3b059ea4
[2/2] powerc/dtc/t1024rdb: remove interrupts property
      https://git.kernel.org/powerpc/c/843dc8ee23d1b353fa9cc24da3e52be0111d5931

cheers

      parent reply	other threads:[~2020-09-09 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  3:42 [v3 1/2] dts: ppc: t4240rdb: remove interrupts property Biwen Li
2020-05-27  3:42 ` [v3 2/2] dts: ppc: t1024rdb: " Biwen Li
2020-05-27 23:03   ` Li Yang
2020-05-27 23:02 ` [v3 1/2] dts: ppc: t4240rdb: " Li Yang
2020-09-09 13:37 ` Michael Ellerman [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=159965824243.811679.11439322992907877530.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=benh@kernel.crashing.org \
    --cc=biwen.li@nxp.com \
    --cc=biwen.li@oss.nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=robh+dt@kernel.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).