From: Arnd Bergmann <arnd@arndb.de>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Olof Johansson <olof@lixom.net>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Daniel Mack <daniel@zonque.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>
Subject: Re: [PATCH 00/21] ARM: dts: Marvell SoC Device Tree updates
Date: Thu, 26 Mar 2020 20:42:50 +0100 [thread overview]
Message-ID: <CAK8P3a0175q9JvsSOW_gas_dHYrCFENW=0_CLzhCZdi9odUz9Q@mail.gmail.com> (raw)
In-Reply-To: <20200325114111.475258-1-lkundrak@v3.sk>
On Wed, Mar 25, 2020 at 12:41 PM Lubomir Rintel <lkundrak@v3.sk> wrote:
>
> Hi,
>
> I'm sending in these in hope of getting them queued into arm/dt.
>
> Apart from the last three MMP3 patches, they've been previously included
> in sets that aim to improve Marvell SoCc schema validation coverage, but
> are in fact independent of the actual binding schema changes.
>
> * DT: Improve validation for Marvell SoCs
> <https://lore.kernel.org/lkml/20200317093922.20785-1-lkundrak@v3.sk/>
> * NS 8250 UART Device Tree improvements
> <https://lore.kernel.org/lkml/20200320174107.29406-1-lkundrak@v3.sk/>
>
> As of today the patches happily apply on top of mainline master and
> next, so they're pretty unlikely to cause any conflicts.
Hi Lubomir,
I looked at the patches, and as these are mostly bugfixes, I have no
objection to merging them for v5.7. However, I'd like to point out
a few things about the process:
- If possible, try to avoid submitting patches this late during the release
cycle, it's better to send a subset even while you are still working
on some other fixes for the same release, or are still doing some
additional testing that may result in regression fixes later.
- For patches that address incorrect behavior (as opposed to fixing
stylistic mistakes), please consider whether these should be backported
into stable kernels. If so, please add a 'Cc: stable@vger.kernel.org' line.
- When you think the patches are ready for inclusion, the correct
procedure is to post them 'to:soc@kernel.org cc:linux-arm-kernel.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-03-26 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200325114111.475258-1-lkundrak@v3.sk>
[not found] ` <20200326185423.552288-1-lkundrak@v3.sk>
2020-03-26 19:01 ` [PATCH 00/21] ARM: dts: Marvell SoC Device Tree updates Lubomir Rintel
2020-03-26 19:42 ` Arnd Bergmann [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='CAK8P3a0175q9JvsSOW_gas_dHYrCFENW=0_CLzhCZdi9odUz9Q@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkundrak@v3.sk \
--cc=olof@lixom.net \
--cc=robert.jarzmik@free.fr \
/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).