From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Paul Boddie <paul@boddie.org.uk>,
Paul Cercueil <paul@crapouillou.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paulburton@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Andi Kleen <ak@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-mips@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH v5 2/5] MIPS: DTS: CI20: fix PMU definitions for ACT8600
Date: Tue, 3 Mar 2020 13:32:14 +0100 [thread overview]
Message-ID: <20200303123214.GA15333@alpha.franken.de> (raw)
In-Reply-To: <85F9D066-EAF6-4840-8F54-24E6D8A534DC@goldelico.com>
On Tue, Mar 03, 2020 at 01:10:22PM +0100, H. Nikolaus Schaller wrote:
> > And please seperate fixes from improvments, thank you.
>
> What do you mean by "separate"? Two separate patches?
> This patch only contains fixes (which I would consider
> all of them to be improvements).
There are two patches with Fixes tag, which IMHO should go
into 5.6 via mips-fixes branch. All others are going
via mips-next into 5.7. So it helps me, if they come in different
patch series (or as single patches).
I see other DT changes in your other patch series. Are the changes
there independent from each other or do they require correct order
when appling them ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-03-03 12:32 UTC|newest]
Thread overview: 10+ 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 [this message]
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-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=20200303123214.GA15333@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=ak@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=geert+renesas@glider.be \
--cc=hns@goldelico.com \
--cc=keescook@chromium.org \
--cc=krzk@kernel.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=miquel.raynal@bootlin.com \
--cc=paul@boddie.org.uk \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=stable@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).