From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Gutson <daniel@eclypsium.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Derek Kiernan <derek.kiernan@xilinx.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Hughes <hughsient@gmail.com>,
Alex Bazhaniuk <alex@eclypsium.com>
Subject: Re: [PATCH] SPI LPC information kernel module
Date: Tue, 30 Jun 2020 17:00:14 +0200 [thread overview]
Message-ID: <CAK8P3a0WKODYvHzsf05QZ1dFh5uMQu2z7dzO1DMp1E9TWCrsPQ@mail.gmail.com> (raw)
In-Reply-To: <CAFmMkTGrnZt7ZaGyYCe-LCHET4yHz9DfanaZwsOS6HCxK40apQ@mail.gmail.com>
On Tue, Jun 30, 2020 at 4:43 PM Daniel Gutson <daniel@eclypsium.com> wrote:
> On Tue, Jun 30, 2020 at 5:56 AM Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>> On Mon, Jun 29, 2020 at 07:59:32PM -0300, Daniel Gutson wrote:
>> Why is this going in securityfs at all? Why not just sysfs as it is a
>> CPU attribute, right?
>
> Richard already discussed that, but "it" is not only (one) CPU attribute, are SPI chip
> settings and attributes coming from the firmware.
> Please note that I wanted to submit the minimum patch, but I need to add more attributes.
Why can't the SPI chip settings be attributes of the SPI chip device in sysfs?
Which firmware are you actually talking about here? Do you mean firmware running
on a device behind the SPI controller?
Arnd
next prev parent reply other threads:[~2020-06-30 15:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 22:59 [PATCH] SPI LPC information kernel module Daniel Gutson
2020-06-30 8:02 ` kernel test robot
2020-06-30 8:56 ` Greg Kroah-Hartman
2020-06-30 13:57 ` Richard Hughes
2020-06-30 14:24 ` Arnd Bergmann
2020-06-30 15:14 ` Greg Kroah-Hartman
[not found] ` <CAFmMkTGrnZt7ZaGyYCe-LCHET4yHz9DfanaZwsOS6HCxK40apQ@mail.gmail.com>
2020-06-30 15:00 ` Arnd Bergmann [this message]
2020-06-30 15:28 ` Greg Kroah-Hartman
2020-06-30 15:32 ` Greg Kroah-Hartman
[not found] ` <CAFmMkTGy7u8oNSPmBHf9+URzKeNOxy5TJtqF3FCruRkTgJ_wGQ@mail.gmail.com>
2020-06-30 16:55 ` Greg Kroah-Hartman
2020-06-30 8:58 ` Arnd Bergmann
[not found] ` <CAFmMkTHrQ4LZk4+-3kdJ+dc47MXR1Jd76AXbO-ceT2zsfDRFGQ@mail.gmail.com>
2020-06-30 20:57 ` Arnd Bergmann
[not found] ` <CAFmMkTE3z6OZQ_v3jx-4MzMr8v+4qcF2uLn0ASGydj5oqDnfjg@mail.gmail.com>
2020-07-06 9:20 ` Arnd Bergmann
2020-07-06 9:54 ` Arnd Bergmann
[not found] ` <CAFmMkTGkmBgmv6wmS1kNWxGm0ktN56u9pJVJQKyPvLipyHsgqw@mail.gmail.com>
2020-07-14 6:38 ` Greg Kroah-Hartman
2020-07-06 10:22 ` Arnd Bergmann
2020-06-30 8:58 ` Greg Kroah-Hartman
2020-06-30 8:59 ` Greg Kroah-Hartman
2020-06-30 9:00 ` Greg Kroah-Hartman
2020-07-01 7:35 ` kernel test robot
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=CAK8P3a0WKODYvHzsf05QZ1dFh5uMQu2z7dzO1DMp1E9TWCrsPQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=alex@eclypsium.com \
--cc=daniel@eclypsium.com \
--cc=derek.kiernan@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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;
as well as URLs for NNTP newsgroup(s).