From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
pantelis.antoniou@konsulko.com, mark.rutland@arm.com,
pmladek@suse.com, andriy.shevchenko@linux.intel.com,
joe@perches.com, corbet@lwn.net, me@tobin.cc,
sergey.senozhatsky@gmail.com
Subject: Re: [PATCH 0/2] cowsay support
Date: Mon, 2 Apr 2018 10:57:16 +0900 [thread overview]
Message-ID: <20180402015716.GB3795@jagdpanzerIV> (raw)
In-Reply-To: <20180401085622.7754-1-richard@nod.at>
On (04/01/18 10:56), Richard Weinberger wrote:
> As the printk subsystem gains more and more popularity it is time to add
> the final missing feature to make it perfect, namely cowsay output.
> Currently only one type of cow is supported and the only user is kmsg,
> but I can see more use cases for it and the need for different cow types.
>
> Example of /dev/kmsg usage:
> [ 1.309561] _________________________________________
> [ 1.309561] < systemd[1]: Detected architecture x86-64. >
> [ 1.309561] -----------------------------------------
> [ 1.309561] \ ^__^
> [ 1.309561] \ (oo)\_______
> [ 1.309561] (__)\ )\/\
> [ 1.309561] ||----w |
> [ 1.309561] || ||
>
> Richard Weinberger (2):
> lib: vsprintf: Implement %pCOW
> printk: Use %pCOW for kmsg
>
___________________________________________________________
< Acked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com> >
-----------------------------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
-ss
prev parent reply other threads:[~2018-04-02 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 8:56 Richard Weinberger
2018-04-01 8:56 ` [PATCH 1/2] lib: vsprintf: Implement %pCOW Richard Weinberger
2018-04-01 9:15 ` Adam Borowski
2018-04-01 9:18 ` Richard Weinberger
2018-04-02 14:18 ` Andy Shevchenko
2018-04-03 9:15 ` Petr Mladek
2018-04-01 8:56 ` [PATCH 2/2] printk: Use %pCOW for kmsg Richard Weinberger
2018-04-02 1:57 ` Sergey Senozhatsky [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=20180402015716.GB3795@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=me@tobin.cc \
--cc=pantelis.antoniou@konsulko.com \
--cc=pmladek@suse.com \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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
all inboxes | Powered by JetHome®