[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190624.132456.2013417744691373807.davem@davemloft.net>
Date: Mon, 24 Jun 2019 13:24:56 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: megous@...ous.com
Cc: linux-sunxi@...glegroups.com, maxime.ripard@...tlin.com,
wens@...e.org, robh+dt@...nel.org, jernej.skrabec@...il.com,
airlied@...ux.ie, daniel@...ll.ch, mark.rutland@....com,
peppe.cavallaro@...com, alexandre.torgue@...com,
joabreu@...opsys.com, mcoquelin.stm32@...il.com,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com
Subject: Re: [PATCH v7 0/6] Add support for Orange Pi 3
From: Ondřej Jirman <megous@...ous.com>
Date: Mon, 24 Jun 2019 19:46:37 +0200
> This series was even longer before, with patches all around for various
> maintainers. I'd expect that relevant maintainers pick the range of patches
> meant for them. I don't know who's exactly responsible for what, but I think,
> this should work:
>
> - 2 stmmac patches should go together via some networking tree (is there
> something specific for stmmac?)
> - all DTS patches should go via sunxi
> - hdmi patches via some drm tree
Thank you. So I'll merge the first two patches that touch the stmmac
driver via my net-next tree.
Powered by blists - more mailing lists