From: Lee Jones <lee.jones@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v2 12/13] input: max77650: add onkey support
Date: Fri, 1 Feb 2019 09:11:14 +0000 [thread overview]
Message-ID: <20190201091114.GD783@dell> (raw)
In-Reply-To: <CAKdAkRQUAMsT7SA7oAaEmLrkZ6hOdAqCC9RC6HGRsjJ+TvASrQ@mail.gmail.com>
On Thu, 31 Jan 2019, Dmitry Torokhov wrote:
> On Thu, Jan 31, 2019 at 4:28 AM Mark Brown <broonie@kernel.org> wrote:
> >
> > On Thu, Jan 31, 2019 at 09:15:01AM +0100, Bartosz Golaszewski wrote:
> >
> > > I'm not sure what the policy is on merging MFD drivers, but I'm seeing
> > > that Mark Brown has already picked up the regulator part into his tree
> > > (including the binding document). I think you can just pick up the
> > > input patches and it will simply not show up in Kconfig until the core
> > > mfd module is upstream.
> >
> > > @Mark: could you please confirm it?
> >
> > Right, as it's a new MFD the Kconfig will stop it causing build breakage
> > until the MFD is merged. I'm doing it partly just to cut down on the
> > amount of mail from resends while the rest of the series gets reviewed.
>
> Ugh, I might have pulled it in if it did not reference the new header
> file. As a rule I try to enable all symbols that result in input
> devices being created so as much of input code is covered... I'd
> prefer input piece be merged with MFD.
That's no problem.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-02-01 9:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 13:35 [PATCH v2 00/13] mfd: add support for max77650 PMIC Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 01/13] dt-bindings: mfd: add DT bindings for max77650 Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH] gpio fixup domain Bartosz Golaszewski
2019-01-29 13:39 ` Bartosz Golaszewski
2019-01-30 9:42 ` Linus Walleij
2019-01-29 13:35 ` [PATCH v2 02/13] dt-bindings: regulator: add DT bindings for max77650 Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 03/13] dt-bindings: power: supply: " Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 04/13] dt-bindings: gpio: " Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 05/13] dt-bindings: leds: " Bartosz Golaszewski
2019-01-30 19:58 ` Jacek Anaszewski
2019-01-29 13:35 ` [PATCH v2 06/13] dt-bindings: input: " Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 07/13] mfd: max77650: new core mfd driver Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 08/13] regulator: max77650: add regulator support Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 09/13] power: supply: max77650: add support for battery charger Bartosz Golaszewski
2019-01-29 13:35 ` [PATCH v2 10/13] gpio: max77650: add GPIO support Bartosz Golaszewski
2019-01-30 9:40 ` Linus Walleij
2019-01-29 13:35 ` [PATCH v2 11/13] leds: max77650: add LEDs support Bartosz Golaszewski
2019-01-30 19:59 ` Jacek Anaszewski
2019-01-29 13:35 ` [PATCH v2 12/13] input: max77650: add onkey support Bartosz Golaszewski
2019-01-30 18:53 ` Dmitry Torokhov
2019-01-31 8:15 ` Bartosz Golaszewski
2019-01-31 12:28 ` Mark Brown
2019-01-31 19:18 ` Dmitry Torokhov
2019-02-01 9:11 ` Lee Jones [this message]
2019-01-29 13:35 ` [PATCH v2 13/13] MAINTAINERS: add an entry for max77650 mfd driver Bartosz Golaszewski
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=20190201091114.GD783@dell \
--to=lee.jones@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sre@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).