From: "Krzysztof Wilczyński" <kw@linux.com>
To: marek.vasut@gmail.com
Cc: linux-pci@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Randy Dunlap <rdunlap@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Stephen Boyd <sboyd@kernel.org>, Wolfram Sang <wsa@the-dreams.de>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v4] PCI: rcar: Check if device is runtime suspended instead of __clk_is_enabled()
Date: Mon, 15 Nov 2021 22:59:34 +0100 [thread overview]
Message-ID: <YZLYRjZxTclKX9mJ@rocinante> (raw)
In-Reply-To: <20211115204641.12941-1-marek.vasut@gmail.com>
[+CC Adding Sasha for visibility]
Hi Marek,
Thank you for taking care about this. I am adding Sasha since this is
something we should most likely port to stable and long-term kernels,
especially since this isn't a new driver.
[...]
> - * Static copy of bus clock pointer, so we can check whether the clock
> - * is enabled or not.
> + * Static copy of pcie device pointer, so we can check whether the
> + * device is runtime suspended or not.
A small nitpick: it would be "PCIe" in the above comment. However,
probably not worth sending another version just for this.
Krzysztof
next prev parent reply other threads:[~2021-11-15 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 20:46 [PATCH v4] PCI: rcar: Check if device is runtime suspended instead of __clk_is_enabled() marek.vasut
2021-11-15 21:59 ` Krzysztof Wilczyński [this message]
2021-12-01 16:24 ` Lorenzo Pieralisi
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=YZLYRjZxTclKX9mJ@rocinante \
--to=kw@linux.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=sboyd@kernel.org \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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