From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Harish Jenny K N <harish_kandiga@mentor.com>,
Avri Altman <Avri.Altman@wdc.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"shawn.lin@rock-chips.com" <shawn.lin@rock-chips.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vladimir_Zapolskiy@mentor.com" <Vladimir_Zapolskiy@mentor.com>
Subject: Re: [PATCH v6] mmc: Export host capabilities to debugfs.
Date: Wed, 07 Mar 2018 14:49:34 +0200 [thread overview]
Message-ID: <1520426974.10722.449.camel@linux.intel.com> (raw)
In-Reply-To: <af726c5a-edd4-94f9-7789-4527e9aff93d@mentor.com>
On Wed, 2018-03-07 at 12:34 +0530, Harish Jenny K N wrote:
> > > > > >
> > > +static int mmc_caps_show(struct seq_file *s, void *unused) {
> > > + struct mmc_host *host = s->private;
> > > + u32 caps = host->caps;
> > > +
> > > > > > + seq_puts(s, "\nMMC Host capabilities are:\n");
First of all, avoid leading '\n' in the messages.
> > > > > > + seq_puts(s,
> > >
"=============================================\n");
> > > + seq_printf(s, "Can the host do 4 bit transfers :\t%s\n",
> > > + ((caps & MMC_CAP_4_BIT_DATA) ? "Yes" : "No"));
> >
> > Maybe use a more compact form, and just call a macro with the
> > applicable (stringified) bit?
>
> Something like this ?
>
> #define YN(bit) ((caps & bit) ? "Yes" : "No")
> and then call
> seq_printf(s, "Can the host do 4 bit transfers :\t%s\n",
> YN(MMC_CAP_4_BIT_DATA));
>
I would rather say something like this:
static const char * const mmc_host_capabilities[] = {
"4-bit transfers allowed",
"...",
...
};
...
for_each_set_bit(i, caps)
seq_printf("%s\n", mmc_host_capabilities[i]);
...
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2018-03-07 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 5:37 [PATCH v6] mmc: Export host capabilities to debugfs Harish Jenny K N
2018-03-07 5:37 ` Harish Jenny K N
2018-03-07 6:40 ` Avri Altman
2018-03-07 7:04 ` Harish Jenny K N
2018-03-07 12:49 ` Andy Shevchenko [this message]
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=1520426974.10722.449.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Avri.Altman@wdc.com \
--cc=Vladimir_Zapolskiy@mentor.com \
--cc=adrian.hunter@intel.com \
--cc=harish_kandiga@mentor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--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 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.