From: Javier Martinez Canillas <javier@dowhile0.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Richard Hughes <hughsient@gmail.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: Export LPC attributes for the system SPI chip
Date: Thu, 7 May 2020 19:28:55 +0200 [thread overview]
Message-ID: <CABxcv=mz560QHEKMtf8PYH2pstScSm=5tZZg-9FOuDB5=CuXuw@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VfuKJXz1QO45gDcu1YL_jJy2oz4==zVgsT+2GoLkkm7zQ@mail.gmail.com>
On Thu, May 7, 2020 at 7:22 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Thu, May 7, 2020 at 8:06 PM Javier Martinez Canillas
> <javier@dowhile0.org> wrote:
> > On Wed, May 6, 2020 at 5:52 PM Richard Hughes <hughsient@gmail.com> wrote:
>
> > I wonder if these new entries should be documented in
> > Documentation/ABI/. Or maybe that's not a requirement for securityfs?
>
> ABI must be documented. There is no exceptions.
>
Thanks for the clarification. That's what I thought but wasn't sure.
Best regards,
Javier
next prev parent reply other threads:[~2020-05-07 17:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 15:52 [PATCH] platform/x86: Export LPC attributes for the system SPI chip Richard Hughes
2020-05-06 16:29 ` Andy Shevchenko
2020-05-06 16:39 ` Richard Hughes
2020-05-07 17:05 ` Javier Martinez Canillas
2020-05-07 17:22 ` Andy Shevchenko
2020-05-07 17:28 ` Javier Martinez Canillas [this message]
2020-05-07 17:45 ` Mario.Limonciello
2020-05-07 18:47 ` Richard Hughes
2020-05-07 19:22 ` Mario.Limonciello
2020-05-07 19:49 ` Richard Hughes
2020-05-07 20:03 ` Mario.Limonciello
2020-05-08 8:20 ` Mika Westerberg
2020-05-08 16:15 ` Richard Hughes
2020-05-11 10:45 ` Mika Westerberg
2020-05-11 15:40 ` Richard Hughes
2020-05-11 16:28 ` Mika Westerberg
2020-05-11 20:08 ` Richard Hughes
2020-05-12 6:44 ` Mika Westerberg
2020-05-12 20:37 ` Richard Hughes
2020-05-08 17:27 ` Mario.Limonciello
2020-05-11 10:41 ` Mika Westerberg
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='CABxcv=mz560QHEKMtf8PYH2pstScSm=5tZZg-9FOuDB5=CuXuw@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=andy.shevchenko@gmail.com \
--cc=hughsient@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--cc=platform-driver-x86@vger.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).