All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Andre Przywara" <andre.przywara@arm.com>,
	"Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
	"Govindaraji Sivanantham" <Govindaraji.Sivanantham@in.bosch.com>,
	"Hannes Schmelzer" <hannes.schmelzer@br-automation.com>,
	"Heiko Schocher" <hs@denx.de>,
	"Hiremath Gireesh" <Gireesh.Hiremath@in.bosch.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Marcin Niestroj" <m.niestroj@grinn-global.com>,
	"Marek Behún" <marek.behun@nic.cz>,
	"Patrick Delaunay" <patrick.delaunay@foss.st.com>,
	"Priyanka Jain" <priyanka.jain@nxp.com>,
	"Quentin Schulz" <quentin.schulz@theobroma-systems.com>,
	"Rick Chen" <rick@andestech.com>,
	"Samuel Holland" <samuel@sholland.org>,
	"Simon Glass" <sjg@chromium.org>,
	"Sjoerd Simons" <sjoerd.simons@collabora.co.uk>,
	"Stefan Roese" <sr@denx.de>,
	"Stephan Gerhold" <stephan@gerhold.net>
Subject: Re: [PATCH 1/3] power: Rename CONFIG_POWER_TPS65217 with CONFIG_PMIC_TPS65217
Date: Fri, 11 Mar 2022 14:35:45 +0100	[thread overview]
Message-ID: <20220311143545.62227480@ktm> (raw)
In-Reply-To: <20220311121634.GR5020@bill-the-cat>

[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]

Hi Tom,

> On Fri, Mar 11, 2022 at 01:09:08PM +0100, Lukasz Majewski wrote:
> > Hi Tom,
> >   
> > > On Tue, Feb 22, 2022 at 09:03:58AM +0100, Lukasz Majewski wrote:  
> > > > Up till now the CONFIG_POWER_TPS65217 has been defined in
> > > > several header files for am335x SoC.
> > > > 
> > > > This patch renames it to CONFIG_PMIC_TPS65217, which better
> > > > reflects the role of this IC circuit.
> > > > 
> > > > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > > > Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
> > > > ---
> > > > 
> > > >  drivers/power/pmic/Makefile         | 2 +-
> > > >  include/configs/am335x_evm.h        | 2 +-
> > > >  include/configs/am335x_guardian.h   | 2 +-
> > > >  include/configs/am335x_shc.h        | 2 +-
> > > >  include/configs/am335x_sl50.h       | 2 +-
> > > >  include/configs/brppt1.h            | 2 +-
> > > >  include/configs/bur_am335x_common.h | 2 +-
> > > >  include/configs/chiliboard.h        | 2 +-
> > > >  scripts/config_whitelist.txt        | 2 +-
> > > >  9 files changed, 9 insertions(+), 9 deletions(-)    
> > > 
> > > This needs to be migrated to Kconfig fully / correctly as well,
> > > not just changing the whitelist entry.
> > >   
> > 
> > But there is follow up patch, which adds proper entry to Kconfig
> > with new name:
> > 
> > https://patchwork.ozlabs.org/project/uboot/patch/20220222080401.6859-2-lukma@denx.de/
> > 
> > The idea was to first rename the CONFIG_POWER_TPS65217 to
> > CONFIG_PMIC_TPS65217 (as a single patch) and then provide DM support
> > for TPS65217 with proper (renamed) Kconfig entry.  
> 
> Please re-order the series so we don't do what you're doing here and
> be sure to fully migrate everyone.  I noticed this as part of finding
> and fixing:
> https://patchwork.ozlabs.org/project/uboot/patch/20220311121248.2801589-1-trini@konsulko.com/
> yesterday and saw a bunch of PMIC symbols get listed.
> 

I can squash those two patches:
https://patchwork.ozlabs.org/project/uboot/patch/20220222080401.6859-1-lukma@denx.de/
https://patchwork.ozlabs.org/project/uboot/patch/20220222080401.6859-2-lukma@denx.de/

However, the drawback is that we would have the move to Kconfig type of
patch with the rename.

Would it be OK?


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-03-11 13:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220222080425epcas1p2d9b60c85b505dbc59fa34fdb61400d28@epcas1p2.samsung.com>
2022-02-22  8:03 ` [PATCH 1/3] power: Rename CONFIG_POWER_TPS65217 with CONFIG_PMIC_TPS65217 Lukasz Majewski
2022-02-22  8:03   ` [PATCH 2/3] power: pmic: Provide DM_PMIC support for tps65217 driver Lukasz Majewski
2022-03-06 23:14     ` Jaehoon Chung
2022-02-22  8:04   ` [PATCH 3/3] defconfig: Enable DM_PMIC and DM PMIC_TPS65217 on AM335x EVM board Lukasz Majewski
2022-03-03  9:29   ` [PATCH 1/3] power: Rename CONFIG_POWER_TPS65217 with CONFIG_PMIC_TPS65217 Lukasz Majewski
2022-03-06 23:13   ` Jaehoon Chung
2022-03-10 18:52   ` Tom Rini
2022-03-11 12:09     ` Lukasz Majewski
2022-03-11 12:16       ` Tom Rini
2022-03-11 13:35         ` Lukasz Majewski [this message]
2022-03-11 13:52           ` Tom Rini

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=20220311143545.62227480@ktm \
    --to=lukma@denx.de \
    --cc=Gireesh.Hiremath@in.bosch.com \
    --cc=Govindaraji.Sivanantham@in.bosch.com \
    --cc=andre.przywara@arm.com \
    --cc=enric.balletbo@collabora.com \
    --cc=hannes.schmelzer@br-automation.com \
    --cc=hs@denx.de \
    --cc=jh80.chung@samsung.com \
    --cc=m.niestroj@grinn-global.com \
    --cc=marek.behun@nic.cz \
    --cc=patrick.delaunay@foss.st.com \
    --cc=priyanka.jain@nxp.com \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=rick@andestech.com \
    --cc=samuel@sholland.org \
    --cc=sjg@chromium.org \
    --cc=sjoerd.simons@collabora.co.uk \
    --cc=sr@denx.de \
    --cc=stephan@gerhold.net \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.