linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julius Werner <jwerner@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Julius Werner <jwerner@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Thierry Escande <thierry.escande@collabora.com>,
	Dmitry Torokhov <dtor@chromium.org>,
	Aaron Durbin <adurbin@chromium.org>
Subject: Re: [PATCH v2 2/3] firmware: google: memconsole: Escape unprintable characters
Date: Tue, 2 May 2017 15:16:06 -0700	[thread overview]
Message-ID: <CAODwPW8PoBnZig20iThB-URwSL4bA1WWThfSbhMbnRv8KAGXAA@mail.gmail.com> (raw)
In-Reply-To: <20170502004249.GB4876@kroah.com>

> Binary sysfs files are supposed to be "pass through" only, the kernel
> should not be touching the data at all, it's up to userspace to do what
> it wants to do with things.  So don't escape anything at all, that's not
> the kernel's job here.

Okay, I'll drop this patch.

  reply	other threads:[~2017-05-02 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 20:42 [PATCH v2 0/3] Memconsole changes for new coreboot format Julius Werner
2017-04-28 20:42 ` [PATCH v2 1/3] firmware: google: memconsole: Make memconsole interface more flexible Julius Werner
2017-04-28 20:42 ` [PATCH v2 2/3] firmware: google: memconsole: Escape unprintable characters Julius Werner
2017-04-29  5:37   ` Greg Kroah-Hartman
2017-05-01 23:44     ` Julius Werner
2017-05-02  0:42       ` Greg Kroah-Hartman
2017-05-02 22:16         ` Julius Werner [this message]
2017-04-28 20:42 ` [PATCH v2 3/3] firmware: google: memconsole: Adapt to new coreboot ring buffer format Julius Werner

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=CAODwPW8PoBnZig20iThB-URwSL4bA1WWThfSbhMbnRv8KAGXAA@mail.gmail.com \
    --to=jwerner@chromium.org \
    --cc=adurbin@chromium.org \
    --cc=dtor@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.escande@collabora.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 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).