[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZVNetJdEEuWMxl2a@smile.fi.intel.com>
Date: Tue, 14 Nov 2023 13:49:08 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Raag Jadav <raag.jadav@...el.com>
Cc: linus.walleij@...aro.org, brgl@...ev.pl,
mika.westerberg@...ux.intel.com, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
mallikarjunappa.sangannavar@...el.com, bala.senthil@...el.com
Subject: Re: [PATCH v1 0/3] Use the standard _PM_OPS() export macro in Intel
Tangier GPIO driver
On Tue, Nov 14, 2023 at 06:38:44AM +0200, Raag Jadav wrote:
> On Mon, Nov 13, 2023 at 05:58:34PM +0200, Andy Shevchenko wrote:
> > On Mon, Nov 13, 2023 at 06:45:57PM +0530, Raag Jadav wrote:
> > > This series exports pm_ops structure from Intel Tangier GPIO driver using
> > > EXPORT_NS_GPL_SIMPLE_DEV_PM_OPS() helper and reuses it into its users.
> >
> > Yet you missed --base...
>
> My understanding is that we use --base only for the patches with explicit
> in-tree dependency, which this series doesn't have any AFAIK.
>
> Will start using it for every patch if it makes everyone happy :)
For single patches it's not so critical, only for the series as I'm using b4
to treat them as PRs, so cover letter goes to the merge commit and b4 tries
to guess the base (often wrongly).
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists