[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42e50578-c122-e23b-f21f-c4723d008333@gmail.com>
Date: Wed, 18 Nov 2020 15:56:48 +0100
From: Matthias Brugger <matthias.bgg@...il.com>
To: Arnd Bergmann <arnd@...nel.org>, Lee Jones <lee.jones@...aro.org>
Cc: Enric Balletbo i Serra <enric.balletbo@...labora.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Collabora Kernel ML <kernel@...labora.com>,
Nicolas Boichat <drinkcat@...omium.org>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2] mfd: syscon: Add
syscon_regmap_lookup_by_phandle_optional() function.
On 17/11/2020 17:40, Arnd Bergmann wrote:
> On Tue, Nov 17, 2020 at 5:07 PM Lee Jones <lee.jones@...aro.org> wrote:
>> On Tue, 17 Nov 2020, Matthias Brugger wrote:
>>> On 17/11/2020 13:37, Lee Jones wrote:
>>>> On Tue, 17 Nov 2020, Matthias Brugger wrote:
>>>
>>> If you want to go the route for me rebasing my tree on top of for-mfd-next
>>> then I'd like to have at least a stable tag, so that it will be easier to
>>> provide the pull-request later on. Would that be a compromise?
>>
>> I don't usually provide immutable branches/tags unless I'm sharing
>> topic branches for other maintainers to pick-up, in order to avoid
>> merge conflicts.
>
> I think that's what Matthias is planning to do though. If he wants
> to send me a Mediatek specific branch for the soc tree, it needs to
> be based on a stable commit in the mtd tree to avoid duplicating
> the commit.
>
Exactly, I'm the maintainer of MediaTek SoCs and I would need to pull this patch
into my tree to be able to accept the series I mentioned [1]. Can you provide me
a stable tag/branch, against just that patch or against your whole tree?
Regards,
Matthias
[1]
https://lore.kernel.org/linux-mediatek/20201030113622.201188-1-enric.balletbo@collabora.com/
Powered by blists - more mailing lists