From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Ulf Hansson <ulf.hansson@oss.qualcomm.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Ulf Hansson <ulfh@kernel.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: dw_mmc: add declaration of dw_mci_pmops
Date: Mon, 6 Jul 2026 19:25:49 +0100 [thread overview]
Message-ID: <80c8ef42-4c2b-4206-8cac-b2a32a4f2e6b@codethink.co.uk> (raw)
In-Reply-To: <CAPx+jO9BtwN+=Y_xLFXusTwFFv=5KDZCY_3QmSpRmskMch3W6A@mail.gmail.com>
On 06/07/2026 15:30, Ulf Hansson wrote:
> On Tue, Jun 23, 2026 at 12:24 PM Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>>
>> The dw_mci_pmops is exported out of dw_mmc.c so add a declaration of
>> it in dw_mmc.h to fix the following sparse warning:
>>
>> drivers/mmc/host/dw_mmc.c:3512:25: warning: symbol 'dw_mci_pmops' was not declared. Should it be static?
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>> ---
>> drivers/mmc/host/dw_mmc.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/mmc/host/dw_mmc.h b/drivers/mmc/host/dw_mmc.h
>> index 9ffcd3946cff..38610c89d54a 100644
>> --- a/drivers/mmc/host/dw_mmc.h
>> +++ b/drivers/mmc/host/dw_mmc.h
>> @@ -19,6 +19,8 @@
>> #include <linux/interrupt.h>
>> #include <linux/workqueue.h>
>>
>> +extern const struct dev_pm_ops dw_mci_pmops;
>> +
>
> It's already extern declared in drivers/mmc/host/dw_mmc-pltfm.h.
> Perhaps drop that then?
so just move it into dw_mmc.h?
>
>> enum dw_mci_state {
>> STATE_IDLE = 0,
>> STATE_SENDING_CMD,
>> --
>> 2.37.2.352.g3c44437643
>>
>
> Kind regards
> Uffe
>
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2026-07-06 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 10:23 Ben Dooks
2026-07-06 14:30 ` Ulf Hansson
2026-07-06 18:25 ` Ben Dooks [this message]
2026-07-07 10:21 ` Ulf Hansson
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=80c8ef42-4c2b-4206-8cac-b2a32a4f2e6b@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@oss.qualcomm.com \
--cc=ulfh@kernel.org \
/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
all inboxes | Powered by JetHome®