From: "Luck, Tony" <tony.luck@intel.com>
To: Kees Cook <keescook@chromium.org>,
Matt Fleming <matt@codeblueprint.co.uk>
Cc: Geliang Tang <geliangtang@163.com>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 2/3] efi-pstore: implement efivars_pstore_exit()
Date: Wed, 11 Nov 2015 23:23:15 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32B86A52@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CAGXu5j+DADxC6LrHMSAnw5N2GRFbby6-iPTgkKC=BZotBqt-NQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 357 bytes --]
>>> module_init(efivars_pstore_init);
>>
>> Looks OK to me. Kees, are you picking this up?
>
> I can, though usually it goes through Tony.
Can I count that as "Acked-by" from both of you?
-Tony
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2015-11-11 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 4:43 [PATCH v2 0/3] pstore: resend three patches Geliang Tang
2015-11-07 4:43 ` [PATCH v2 1/3] pstore: check PSTORE_FLAGS_FRAGILE in pstore_unregister Geliang Tang
2015-11-07 4:43 ` [PATCH v2 2/3] efi-pstore: implement efivars_pstore_exit() Geliang Tang
2015-11-07 4:43 ` [PATCH v2 3/3] pstore: drop file opened reference count Geliang Tang
2015-11-11 16:59 ` [PATCH v2 2/3] efi-pstore: implement efivars_pstore_exit() Matt Fleming
2015-11-11 23:08 ` Kees Cook
2015-11-11 23:23 ` Luck, Tony [this message]
2015-11-11 23:24 ` Kees Cook
2016-06-02 7:26 ` Geliang Tang, Kees Cook
2016-06-02 18:26 ` Kees Cook
2015-11-12 12:22 ` Matt Fleming
2016-06-02 18:17 ` [PATCH v2 1/3] pstore: check PSTORE_FLAGS_FRAGILE in pstore_unregister Kees Cook
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=3908561D78D1C84285E8C5FCA982C28F32B86A52@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=geliangtang@163.com \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
/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).