From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Kees Cook <keescook@chromium.org>, "Luck, Tony" <tony.luck@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Furquan Shaikh <furquan@google.com>,
Aaron Durbin <adurbin@chromium.org>,
Olof Johansson <olofj@chromium.org>,
Andrew Bresticker <abrestic@chromium.org>,
Puneet Kumar <puneetster@chromium.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.co.uk>,
"gustavo.padovan@collabora.co.uk"
<gustavo.padovan@collabora.co.uk>,
"emilio.lopez@collabora.co.uk" <emilio.lopez@collabora.co.uk>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Subject: Re: [PATCHv2 0/2] fs/pstore: Use memcpy_from/toio() instead of memcpy.
Date: Mon, 29 Feb 2016 09:04:30 +0100 [thread overview]
Message-ID: <56D3FB8E.30007@collabora.com> (raw)
In-Reply-To: <CAGXu5jJ9hvDL9wQBVsRtzKwGQ1r7-sEKSeM6jYMeLsx2T+rD+w@mail.gmail.com>
Hi all,
On 18/02/16 00:00, Kees Cook wrote:
> On Wed, Feb 17, 2016 at 2:57 PM, Luck, Tony <tony.luck@intel.com> wrote:
>>> Tony, are you able to pull these?
>>
>> I've been distracted ... I need to dig into the pile of pending pstore patches.
>>
>> Was there a consensus on the device tree ones? I saw a "you shouldn't do that",
>> and a "but it's really convenient and doesn't hurt anyone else" exchange.
>
> Honestly, I'm a bit unclear where the DT stuff stands... that thread
> got long. :)
>
> -Kees
>
There are more pstore related patches in these patch series, would be
good if you have a chance to look at these also, thanks.
https://lkml.org/lkml/2016/2/16/109
-Enric
next prev parent reply other threads:[~2016-02-29 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 8:19 [PATCHv2 0/2] fs/pstore: Use memcpy_from/toio() instead of memcpy Enric Balletbo i Serra
2016-02-15 8:19 ` [PATCHv2 1/2] fs/pstore: Use memcpy_toio " Enric Balletbo i Serra
2016-02-15 8:19 ` [PATCHv2 2/2] fs/pstore: Use memcpy_fromio() to save old ramoops buffer Enric Balletbo i Serra
2016-02-17 22:54 ` [PATCHv2 0/2] fs/pstore: Use memcpy_from/toio() instead of memcpy Kees Cook
2016-02-17 22:57 ` Luck, Tony
2016-02-17 23:00 ` Kees Cook
2016-02-29 8:04 ` Enric Balletbo i Serra [this message]
2016-02-29 16:12 ` Olof Johansson
2016-09-08 20:35 ` 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=56D3FB8E.30007@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=abrestic@chromium.org \
--cc=adurbin@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=emilio.lopez@collabora.co.uk \
--cc=furquan@google.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=puneetster@chromium.org \
--cc=sjoerd.simons@collabora.co.uk \
--cc=tomeu.vizoso@collabora.co.uk \
--cc=tony.luck@intel.com \
/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.