Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1286782
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support |
| Date | 2015-12-08 20:20 +0100 |
| Message-ID | <qDvXP-6mP-3@gated-at.bofh.it> (permalink) |
| References | <qwfl8-6tM-5@gated-at.bofh.it> <qyoDH-262-95@gated-at.bofh.it> <qBXlx-2ur-33@gated-at.bofh.it> <qDa6Z-st-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Mon, Dec 07, 2015 at 01:58:47PM -0600, Andrew F. Davis wrote: > As all of this driver should be taken though the MFD tree how > can this gpiolib change be handled? If we have gpio.parent it > will not build on MFD, with gpio.dev it will fail to build when > the changes are merged from the gpio subsystem. As the change > has not been merged into linux-next as far a I can tell maybe > this should be taken as is, then when the gpiolib change is > made this can be changed with all the other drivers? Do a cross tree merge in one direction or the other between MFD and GPIO.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support Mark Brown <broonie@kernel.org> - 2015-12-04 13:10 +0100
Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support "Andrew F. Davis" <afd@ti.com> - 2015-12-07 21:00 +0100
Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support Mark Brown <broonie@kernel.org> - 2015-12-08 20:20 +0100
Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support Linus Walleij <linus.walleij@linaro.org> - 2015-12-09 13:40 +0100
csiph-web