From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS
Date: Mon, 23 Apr 2018 09:45:07 +0200 [thread overview]
Message-ID: <CAMuHMdUt3ExAD7KEiBhntcOoSWSLMnpNT1Oix4tNRMAM=8g9jQ@mail.gmail.com> (raw)
In-Reply-To: <20180420164811.GC22369@sirena.org.uk>
Hi Mark,
On Fri, Apr 20, 2018 at 6:48 PM, Mark Brown <broonie@kernel.org> wrote:
> On Fri, Apr 20, 2018 at 03:28:26PM +0200, Geert Uytterhoeven wrote:
>> The first 6 patches can be applied independently by subsystem
>> maintainers.
>> The last two patches depend on the first 6 patches, and are thus marked
>> RFC.
>
> Would it not make sense to try to apply everything en masse rather than
> delaying? I'm happy to apply the subsystem stuff but if it gets things
> done quicker or more efficiently I'm also happy to have the lot merged
> as one series.
In theory, yes.
However, this touches multiple subsystems, and it's non-critical, so I don't
want to spent the energy to get this done in a synchronized way.
It's way easier to postpone the last (RFC) patches when everything else
has been applied by subsystem maintainers.
So please apply your part, thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2018-04-23 7:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 13:28 [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS Geert Uytterhoeven
2018-04-20 13:28 ` [PATCH 1/8] arm: shmobile: " Geert Uytterhoeven
2018-04-20 14:53 ` Sergei Shtylyov
2018-04-23 7:50 ` Simon Horman
2018-04-20 13:28 ` [PATCH 2/8] dmaengine: shdmac: Change platform check to CONFIG_ARCH_RENESAS Geert Uytterhoeven
2018-04-23 7:53 ` Simon Horman
2018-04-25 9:18 ` Vinod Koul
2018-04-20 13:28 ` [PATCH 3/8] [media] v4l: rcar_fdp1: Change platform dependency to ARCH_RENESAS Geert Uytterhoeven
2018-04-21 8:07 ` Laurent Pinchart
2018-04-22 8:46 ` Laurent Pinchart
2018-04-23 8:08 ` Geert Uytterhoeven
2018-04-23 7:54 ` Simon Horman
2018-04-20 13:28 ` [PATCH 4/8] sh_eth: Change platform check to CONFIG_ARCH_RENESAS Geert Uytterhoeven
2018-04-20 15:22 ` Sergei Shtylyov
2018-04-23 7:56 ` Simon Horman
2018-04-20 13:28 ` [PATCH 5/8] staging: emxx_udc: Change platform dependency to ARCH_RENESAS Geert Uytterhoeven
2018-04-23 7:56 ` Simon Horman
2018-04-20 13:28 ` [PATCH 6/8] ASoC: sh: Update menu title and platform dependency Geert Uytterhoeven
2018-04-23 7:56 ` Simon Horman
2018-04-20 13:28 ` [PATCH/RFC 7/8] ARM: shmobile: Remove the ARCH_SHMOBILE Kconfig symbol Geert Uytterhoeven
2018-04-23 9:20 ` Simon Horman
2018-04-23 9:29 ` Simon Horman
2018-04-24 9:51 ` Geert Uytterhoeven
2018-04-20 13:28 ` [PATCH/RFC 8/8] arm64: renesas: " Geert Uytterhoeven
2018-04-20 13:40 ` [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS Arnd Bergmann
2018-04-20 16:48 ` Mark Brown
2018-04-23 7:45 ` Geert Uytterhoeven [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='CAMuHMdUt3ExAD7KEiBhntcOoSWSLMnpNT1Oix4tNRMAM=8g9jQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.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).