public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Joe Perches <joe@perches.com>,
	Paul Osmialowski <p.osmialowsk@samsung.com>,
	Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Petr Mladek <pmladek@suse.cz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Daniel Mack <daniel@zonque.org>,
	Kay Sievers <kay.sievers@vrfy.org>, Tejun Heo <tj@kernel.org>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-api@vger.kernel.org
Cc: 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, 16 Dec 2015 08:47:35 +0100	[thread overview]
Message-ID: <56711717.60704@nod.at> (raw)
In-Reply-To: <1450223166.4142.34.camel@perches.com>

Am 16.12.2015 um 00:46 schrieb Joe Perches:
> On Tue, 2015-10-27 at 11:28 +0100, Paul Osmialowski wrote:
>> Dear All,
>>
>> This is the fifth iteration of Marcin Niesluchowski's serie of patches
>> extending kmsg interface with ability to dynamically create (and destroy)
>> kmsg-like devices which can be used by userspace for logging.
>>
>> This iteration introduces two changes:
>>
>> 1. selftests are rearranged to use kselftest.h API
>>
>> 2. A disputed  patch "add predefined _PID, _TID, _COMM keywords to kmsg*
>>    log dict" is removed - no chance it will be ever accepted. It is not
>>    critical for this patchset as a whole.
>>
>> Best regards,
>> Paul
>>
>> Marcin Niesluchowski (6):
>>   printk: add one function for storing log in proper format
>>   kmsg: introduce additional kmsg devices support
>>   kmsg: add additional buffers support to memory class
>>   kmsg: add function for adding and deleting additional buffers
>>   kmsg: add ioctl for adding and deleting kmsg* devices
>>   kmsg: add ioctl for kmsg* devices operating on buffers
>>
>> Paul Osmialowski (2):
>>   printk: extract kmsg-related routines from printk.c to kmsg.c
>>   kmsg: selftests
>>
> 
> 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.

Thanks,
//richard

  reply	other threads:[~2015-12-16  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 10:28 [RFC v5 0/8] Additional kmsg devices 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 [this message]
2015-12-16 15:27     ` Tejun Heo
2016-02-24 22:59       ` Andrew Morton

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=56711717.60704@nod.at \
    --to=richard@nod.at \
    --cc=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=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