linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>, Lee Jones <lee.jones@linaro.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Collabora Kernel ML <kernel@collabora.com>,
	Nicolas Boichat <drinkcat@chromium.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] mfd: syscon: Add syscon_regmap_lookup_by_phandle_optional() function.
Date: Wed, 18 Nov 2020 15:56:48 +0100	[thread overview]
Message-ID: <42e50578-c122-e23b-f21f-c4723d008333@gmail.com> (raw)
In-Reply-To: <CAK8P3a3mPQzDr3gzdKAoWKLVKDzysfTvJuFNKR7FM7NWLZ0dDg@mail.gmail.com>



On 17/11/2020 17:40, Arnd Bergmann wrote:
> On Tue, Nov 17, 2020 at 5:07 PM Lee Jones <lee.jones@linaro.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/ 


  reply	other threads:[~2020-11-18 14:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 16:13 [PATCH v2] mfd: syscon: Add syscon_regmap_lookup_by_phandle_optional() function Enric Balletbo i Serra
2020-11-11 10:15 ` Arnd Bergmann
2020-11-13 10:19 ` Lee Jones
2020-11-17 12:05   ` Matthias Brugger
2020-11-17 12:37     ` Lee Jones
2020-11-17 15:17       ` Matthias Brugger
2020-11-17 16:05         ` Lee Jones
2020-11-17 16:40           ` Arnd Bergmann
2020-11-18 14:56             ` Matthias Brugger [this message]
2020-11-19  8:32               ` Lee Jones
2020-11-19 16:57                 ` Matthias Brugger
2020-11-19  8:33 ` [GIT PULL] Immutable branch between MFD and MediaTek due for the v5.11 merge window Lee Jones

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=42e50578-c122-e23b-f21f-c4723d008333@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=kernel@collabora.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@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).