From: Raag Jadav <raag.jadav@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
mika.westerberg@linux.intel.com, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
mallikarjunappa.sangannavar@intel.com, bala.senthil@intel.com
Subject: Re: [PATCH v1 0/3] Use the standard _PM_OPS() export macro in Intel Tangier GPIO driver
Date: Tue, 14 Nov 2023 06:38:44 +0200 [thread overview]
Message-ID: <ZVL5tMZLTDKNLfP2@black.fi.intel.com> (raw)
In-Reply-To: <ZVJHqrj5OzoWav5Z@smile.fi.intel.com>
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 :)
Raag
next prev parent reply other threads:[~2023-11-14 4:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 13:15 [PATCH v1 0/3] Use the standard _PM_OPS() export macro in Intel Tangier GPIO driver Raag Jadav
2023-11-13 13:15 ` [PATCH v1 1/3] gpio: tangier: use EXPORT_NS_GPL_SIMPLE_DEV_PM_OPS() helper Raag Jadav
2023-11-13 13:15 ` [PATCH v1 2/3] gpio: elkhartlake: reuse pm_ops from Intel Tangier driver Raag Jadav
2023-11-13 13:16 ` [PATCH v1 3/3] gpio: tangier: unexport suspend/resume handles Raag Jadav
2023-11-13 15:58 ` [PATCH v1 0/3] Use the standard _PM_OPS() export macro in Intel Tangier GPIO driver Andy Shevchenko
2023-11-14 4:38 ` Raag Jadav [this message]
2023-11-14 11:49 ` Andy Shevchenko
2023-11-14 13:21 ` Raag Jadav
2023-11-14 11:59 ` Mika Westerberg
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=ZVL5tMZLTDKNLfP2@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bala.senthil@intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mika.westerberg@linux.intel.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 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.