From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Paul Boddie <paul@boddie.org.uk>
Cc: devicetree@vger.kernel.org, linux-mips@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v5 3/5] MIPS: DTS: CI20: fix interrupt for pcf8563 RTC
Date: Mon, 02 Mar 2020 15:44:15 +0000 [thread overview]
Message-ID: <20200302154415.D869F21D56@mail.kernel.org> (raw)
In-Reply-To: <32910df46c8723097830e002a13580904ac74a65.1583005548.git.hns@goldelico.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 73f2b940474d ("MIPS: CI20: DTS: Add I2C nodes").
The bot has tested the following trees: v5.5.7.
v5.5.7: Failed to apply! Possible dependencies:
5314215430e5 ("MIPS: DTS: CI20: fix PMU definitions for ACT8600")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-03-02 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 19:45 [PATCH v5 0/5] MIPS: Fixes and improvements for CI20 board (JZ4780) H. Nikolaus Schaller
2020-02-29 19:45 ` [PATCH v5 1/5] MIPS: DTS: CI20: add DT node for IR sensor H. Nikolaus Schaller
2020-02-29 19:45 ` [PATCH v5 2/5] MIPS: DTS: CI20: fix PMU definitions for ACT8600 H. Nikolaus Schaller
2020-03-03 10:18 ` Thomas Bogendoerfer
2020-03-03 12:10 ` H. Nikolaus Schaller
2020-03-03 12:32 ` Thomas Bogendoerfer
2020-03-03 12:36 ` H. Nikolaus Schaller
2020-02-29 19:45 ` [PATCH v5 3/5] MIPS: DTS: CI20: fix interrupt for pcf8563 RTC H. Nikolaus Schaller
2020-03-02 15:44 ` Sasha Levin [this message]
2020-02-29 19:45 ` [PATCH v5 4/5] MIPS: DTS: CI20: multiple DTS improvements H. Nikolaus Schaller
2020-02-29 19:45 ` [PATCH v5 5/5] MIPS: CI20: defconfig: multiple improvements H. Nikolaus Schaller
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=20200302154415.D869F21D56@mail.kernel.org \
--to=sashal@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-mips@vger.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).