[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGngYiX4hgEM7cjeLE-sRswDXTff92OqdBWNgx5WGNmPjuqsUA@mail.gmail.com>
Date: Mon, 9 Dec 2019 08:44:18 -0500
From: Sven Van Asbroeck <thesven73@...il.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Grigoryev Denis <grigoryev@...twel.ru>,
Axel Lin <axel.lin@...ics.com>, Dan Murphy <dmurphy@...com>,
Mark Rutland <mark.rutland@....com>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org
Subject: Re: [PATCH v4 2/2] dt-bindings: mfd: update TI tps6105x chip bindings
Hi Lee, thank you for the review.
On Mon, Dec 9, 2019 at 7:32 AM Lee Jones <lee.jones@...aro.org> wrote:
>
> > Tree: next-20191118
>
> Why is this in your commit message?
I have been posting patches against various maintainer trees lately, which
will not apply to mainline or next. So I have been including base tree
information in the patch itself.
Base-tree info on patches is high on developers' wish list, but not yet
standardized. This was discussed at the 2019 kernel maintainers
summit:
https://lwn.net/Articles/803619/
Powered by blists - more mailing lists