All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Adam Borowski <kilobyte@angband.pl>
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 1/2] lib: vsprintf: Implement %pCOW
Date: Sun, 01 Apr 2018 11:18:56 +0200	[thread overview]
Message-ID: <4175240.C9idGaHF5e@blindfold> (raw)
In-Reply-To: <20180401091549.lvtqox3adp73mgwk@angband.pl>

Am Sonntag, 1. April 2018, 11:15:49 CEST schrieb Adam Borowski:
> On Sun, Apr 01, 2018 at 10:56:21AM +0200, Richard Weinberger wrote:
> > +		.cow_lines = {
> > +			"\\   ^__^",
> > +			" \\  (oo)\\_______",
> > +			"    (__)\\       )\\/\\",
> > +			"        ||----w |",
> > +			"        ||     ||",
> 
> Userspace cowsay(6) knows of different cows.  What about using those as a
> visual indication of message level?

Yeah, this will be implemented for April 1st 2019 if we get funding.
I think of a eBPF cow engine such that usespace can load different cow types.

Thanks,
//richard

  reply	other threads:[~2018-04-01  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-01  8:56 [PATCH 0/2] cowsay support 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 [this message]
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 ` [PATCH 0/2] cowsay support Sergey Senozhatsky

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=4175240.C9idGaHF5e@blindfold \
    --to=richard@nod.at \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=kilobyte@angband.pl \
    --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=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 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.