From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: [PATCH] mmc: rtsx: Fix build errors/warnings for unused variable
Date: Tue, 1 Mar 2022 22:26:37 +0100 [thread overview]
Message-ID: <Yh6PjZ9/HAiyZ09M@kroah.com> (raw)
In-Reply-To: <20220301115300.64332-1-ulf.hansson@linaro.org>
On Tue, Mar 01, 2022 at 12:53:00PM +0100, Ulf Hansson wrote:
> The struct device *dev, is no longer needed at various functions, let's
> therefore drop it to fix the build errors/warnings.
>
> Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Fixes: 7570fb41e450 ("mmc: rtsx: Let MMC core handle runtime PM"
Forgot the trailing ')' character :(
I've fixed this up and ignored the obviously incorrect kbuild
warnings...
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-01 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 11:53 [PATCH] mmc: rtsx: Fix build errors/warnings for unused variable Ulf Hansson
2022-03-01 15:45 ` kernel test robot
2022-03-01 15:55 ` kernel test robot
2022-03-01 21:26 ` Greg Kroah-Hartman [this message]
2022-03-02 10:33 ` 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=Yh6PjZ9/HAiyZ09M@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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