From: Andrew Morton <akpm@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
Joe Perches <joe@perches.com>,
Paul Osmialowski <p.osmialowsk@samsung.com>,
Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>,
Petr Mladek <pmladek@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Mack <daniel@zonque.org>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-api@vger.kernel.org,
Richard Weinberger <richard.weinberger@gmail.com>,
Marcin Niesluchowski <m.niesluchow@samsung.com>,
Karol Lewandowski <k.lewandowsk@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [RFC v5 0/8] Additional kmsg devices
Date: Wed, 24 Feb 2016 14:59:44 -0800 [thread overview]
Message-ID: <20160224145944.d19fd3b66e183702b5ee13b1@linux-foundation.org> (raw)
In-Reply-To: <20151216152757.GH4026@mtj.duckdns.org>
On Wed, 16 Dec 2015 10:27:57 -0500 Tejun Heo <tj@kernel.org> wrote:
> On Wed, Dec 16, 2015 at 08:47:35AM +0100, Richard Weinberger wrote:
> > > Andrew? Are you or anyone else interested in picking up this patchset?
> >
> > I know I'm repeating myself. But this should be done in userspace.
>
> Nothing in this posting explains why this is being added. Kinda
> difficult to say yay or nay.
Yes, I've been rather scratching my head over all of that: what does it
all really do, why does it do it, what problem does it solve, what's
the end-user benefit, etc.
There doesn't appear to be a Documentation update in the patchset.
Perhaps rectifying that omission with a rather good documentation file
would help people to appreciate it all...
prev parent reply other threads:[~2016-02-24 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 10:28 Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 1/8] printk: extract kmsg-related routines from printk.c to kmsg.c Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 2/8] printk: add one function for storing log in proper format Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 3/8] kmsg: introduce additional kmsg devices support Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 4/8] kmsg: add additional buffers support to memory class Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 5/8] kmsg: add function for adding and deleting additional buffers Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 6/8] kmsg: add ioctl for adding and deleting kmsg* devices Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 7/8] kmsg: add ioctl for kmsg* devices operating on buffers Paul Osmialowski
2015-10-27 10:28 ` [RFC v5 8/8] kmsg: selftests Paul Osmialowski
2015-12-15 23:46 ` [RFC v5 0/8] Additional kmsg devices Joe Perches
2015-12-16 7:47 ` Richard Weinberger
2015-12-16 15:27 ` Tejun Heo
2016-02-24 22:59 ` Andrew Morton [this message]
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=20160224145944.d19fd3b66e183702b5ee13b1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=daniel@zonque.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=k.lewandowsk@samsung.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=m.niesluchow@samsung.com \
--cc=p.osmialowsk@samsung.com \
--cc=pmladek@suse.cz \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=shuahkh@osg.samsung.com \
--cc=tj@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
all inboxes | Powered by JetHome®