[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <160763551118.1580929.6120205249234917665@swboyd.mtv.corp.google.com>
Date: Thu, 10 Dec 2020 13:25:11 -0800
From: Stephen Boyd <swboyd@...omium.org>
To: Doug Anderson <dianders@...omium.org>
Cc: Adrian Hunter <adrian.hunter@...el.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Veerabhadrarao Badiganti <vbadigan@...eaurora.org>,
Taniya Das <tdas@...eaurora.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux MMC List <linux-mmc@...r.kernel.org>
Subject: Re: [PATCH] mmc: sdhci-msm: Warn about overclocking SD/MMC
Quoting Doug Anderson (2020-12-10 13:20:03)
> On Thu, Dec 10, 2020 at 1:03 PM Stephen Boyd <swboyd@...omium.org> wrote:
> >
> >
> > Can we use dev_warn?
>
> What's here matches other prints including other ones in the same
> function and in much of the MMC subsystem. mmc_hostname() shows
> "mmc1"
>
> > dev_warn(mmc_dev(mmc)
> > dev_warn(&msm_host->pdev->dev
>
> This show "sdhci_msm 7c4000.sdhci"
>
> I'm going to keep with tradition and keep using mmc_hostname(). In
> some parts of this file they use both (a dev_warn that also includes
> the mmc_hostname()) but that feels overkill.
Ok. This driver should be cleaned up I suppose.
Powered by blists - more mailing lists