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 v9] mmc: Export host capabilities to debugfs.
Date: Mon, 12 Mar 2018 16:20:36 +0200 [thread overview]
Message-ID: <1520864436.10722.592.camel@linux.intel.com> (raw)
In-Reply-To: <9923a92c-f76d-ad87-a648-da212b6b39de@mentor.com>
On Mon, 2018-03-12 at 19:37 +0530, Harish Jenny K N wrote:
> Can anyone please respond to my previous request?
>
> > Before sending new patch , I would like to inform that I have been
> > sending this patch with the following checkpatch warning, just to
> > keep it same as other usages of debugfs_create_file in the
> > drivers/mmc/core/debugfs.c file.
> > WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUSR' are not
> > preferred. Consider using octal permissions '0400'.
> > Do I need to address this or keep it same as S_IRUSR ?
Please, do.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-03-12 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 4:31 [PATCH v9] mmc: Export host capabilities to debugfs Harish Jenny K N
2018-03-12 10:07 ` Andy Shevchenko
2018-03-12 10:27 ` Harish Jenny K N
2018-03-12 10:45 ` Avri Altman
2018-03-12 11:16 ` Harish Jenny K N
2018-03-12 11:32 ` Avri Altman
2018-03-12 12:30 ` Harish Jenny K N
2018-03-12 13:03 ` Andy Shevchenko
2018-03-12 13:34 ` Harish Jenny K N
2018-03-12 14:07 ` Harish Jenny K N
2018-03-12 14:20 ` Andy Shevchenko [this message]
2018-03-12 14:22 ` Andy Shevchenko
2018-03-12 14:27 ` Andy Shevchenko
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=1520864436.10722.592.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox