linux-rtc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: shawnguo@kernel.org, robh+dt@kernel.org, leoyang.li@nxp.com,
	Biwen Li <biwen.li@oss.nxp.com>,
	mark.rutland@arm.com
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	jiafei.pan@nxp.com, Biwen Li <biwen.li@nxp.com>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] rtc: pcf2127: fix a bug when not specify interrupts property
Date: Tue, 15 Sep 2020 12:26:07 +0200	[thread overview]
Message-ID: <160016555162.333730.37689786875063582.b4-ty@bootlin.com> (raw)
In-Reply-To: <20200915073213.12779-1-biwen.li@oss.nxp.com>

On Tue, 15 Sep 2020 15:32:09 +0800, Biwen Li wrote:
> Fix a bug when not specify interrupts property in dts
> as follows,
>     rtc-pcf2127-i2c 1-0051: failed to request alarm irq
>     rtc-pcf2127-i2c: probe of 1-0051 failed with error -22

Applied, thanks!

[1/1] rtc: pcf2127: fix a bug when not specify interrupts property
      commit: 35425bafc772ee189e3c3790d7c672b80ba65909

Best regards,
-- 
Alexandre Belloni <alexandre.belloni@bootlin.com>

      parent reply	other threads:[~2020-09-15 10:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  7:32 [PATCH 1/5] rtc: pcf2127: fix a bug when not specify interrupts property Biwen Li
2020-09-15  7:32 ` [PATCH 2/5] arm64: dts: lx2160a-rdb: remove useless property of rtc Biwen Li
2020-09-22  3:02   ` Shawn Guo
2020-09-22  3:12     ` [EXT] " Biwen Li
2020-09-22  3:28       ` Leo Li
2020-09-22  3:31         ` Biwen Li
2020-09-22 22:28           ` Li Yang
2020-09-15  7:32 ` [PATCH 3/5] arm64: dts: ls1088a-rdb: " Biwen Li
2020-09-15  7:32 ` [PATCH 4/5] arm64: dts : ls1088a-qds: " Biwen Li
2020-09-15  7:32 ` [PATCH 5/5] arm64: dts: ls1046a-qds: " Biwen Li
2020-09-15 10:26 ` Alexandre Belloni [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=160016555162.333730.37689786875063582.b4-ty@bootlin.com \
    --to=alexandre.belloni@bootlin.com \
    --cc=biwen.li@nxp.com \
    --cc=biwen.li@oss.nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jiafei.pan@nxp.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@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).