From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexander Shiyan <shc_work@mail.ru>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Philipp Zabel <philipp.zabel@gmail.com>,
Daniel Mack <zonque@gmail.com>,
Marc Zyngier <marc.zyngier@arm.com>, jacopo <jacopo@jmondi.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Russell King <rmk+kernel@armlinux.org.uk>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>
Subject: Re: [PATCH v4] regulator: fixed: Convert to use GPIO descriptor only
Date: Fri, 13 Jul 2018 23:54:15 +0200 [thread overview]
Message-ID: <1942821.URBRV441KV@z50> (raw)
In-Reply-To: <CACRpkdZbT-CpvaG4ZG76T0vkU_uyt20W_=vD-n9T3=Xy_5WqOg@mail.gmail.com>
Hi Linus,
On Friday, July 13, 2018 9:35:06 AM CEST Linus Walleij wrote:
> On Tue, Jul 10, 2018 at 7:56 PM Janusz Krzysztofik <jmkrzyszt@gmail.com>
wrote:
> > > - .gpio = AMS_DELTA_GPIO_PIN_MODEM_NRESET,
> >
> > This is OK but not enough for clean build of board-ams-delta.c when merged
> > into current linux-next as one more struct fixed_voltage_config introduced
> > there recently - keybrd_pwr_config - needs removal of .gpio member
> > (respective lookup table with NULL function name is already there).
> >
> > > @@ -538,6 +546,7 @@ static struct gpiod_lookup_table
> > > *ams_delta_gpio_tables[] __initdata = {> >
> > > };
> > >
> > > static struct gpiod_lookup_table *late_gpio_tables[] __initdata = {
> > >
> > > + &ams_delta_nreset_gpiod_table,
> >
> > That is also OK but may raise a conflict when merged into current
> > linux-next where late_gpio_tables[] has been removed from
> > board-ams-delta.c and its content integrated into
> > ams_delta_gpio_tables[].
> >
> > > &ams_delta_lcd_gpio_table,
> > > &ams_delta_nand_gpio_table,
> > >
> > > };
> >
> > If that makes your life easier, I can prepare a fix for board-ams-delta.c
> > on top of your patch. In that case you can add my:
> > Reviewed-by: Janusz Krzysztofik <jmkrzyszt@gmail.com>
>
> Hm it's a bit of cross-tree conflict going on here I guess.
>
> Do you have some idea about how serious the conflicts will be?
> Is it just one patch to the ARM SoC OMAP tree or several?
Just one patch, so ...
> It's a bit of Mark's pick, there are several ways to go about it:
>
> 1. Simply defer this to the next kernel cycle when your change is upstream
> and avoid all fuzz (totally OK as long as one is not impatient).
> I'm definately not in a hurry.
>
> 2. Mark applies this, conflicts appear in linux-next, you help Stephen
> to solve it and later on Torvalds has to solve it. Then we need to
> know how serious the conflicts are.
>
> 3. Apply this patch with fixes to the ARM SoC tree. Which makes it hard to
> pull out so I'm not so sure about that.
>
> 4. An immutable branch with the ARM SoC change for Mark to pull
> before applying this so I can rebase this patch on that.
>
> 5. Pick some patch from ARM SoC and apply it *also* to the regulator
> tree and then this on top so I can rebase the changes and avoid
> all conflicts. (We do this sometimes as some last resort.)
>
> 6. ...?
6. The conflict can be easily avoided (or made resolvable automatically) if you
put the '&ams_delta_nreset_gpiod_table,' entry either at the end of
late_gpio_tables[] or at the beginning of ams_delta_gpio_tables[]. Then the
only thing left to do will be a fix removing obsolete .gpio member from the
board-ams-delta's new "keybrd_pwr" regulator setup.
> BTW I like your OMAP1 cleanups a lot!
Thank you :-),
Janusz
prev parent reply other threads:[~2018-07-13 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 6:11 [PATCH v4] regulator: fixed: Convert to use GPIO descriptor only Linus Walleij
2018-07-10 17:56 ` Janusz Krzysztofik
2018-07-13 7:35 ` Linus Walleij
2018-07-13 11:55 ` Mark Brown
2018-07-13 21:54 ` Janusz Krzysztofik [this message]
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=1942821.URBRV441KV@z50 \
--to=jmkrzyszt@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=haojian.zhuang@gmail.com \
--cc=jacopo@jmondi.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=philipp.zabel@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robert.jarzmik@free.fr \
--cc=rppt@linux.vnet.ibm.com \
--cc=shc_work@mail.ru \
--cc=zonque@gmail.com \
/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