linux-kernel - Re: [PATCH v2] mfd: syscon: Add syscon_regmap_lookup_by_phandle

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 17 Nov 2020 17:40:43 +0100
From:   Arnd Bergmann <arnd@...nel.org>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     Matthias Brugger <matthias.bgg@...il.com>,
        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 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.

      Arnd