public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Michael Büsch" <m@bues.ch>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: event subsystem: Define conference event types
Date: Mon, 1 Apr 2013 12:04:57 -0700	[thread overview]
Message-ID: <20130401190457.GA22044@kroah.com> (raw)
In-Reply-To: <20130401140856.776f11f7@milhouse>

On Mon, Apr 01, 2013 at 02:08:56PM +0200, Michael Büsch wrote:
> In order to improve the media coverage of important developer
> conference events, extend the Linux event subsystem by corresponding
> event type numbers.
> 
> Instead of referring to events by cryptic acronyms that nobody
> knows the real meaning of, use even shorter acronyms defined to
> hexadecimal numbers that every real hacker is familiar with.
> 
> Signed-off-by: Michael Buesch <m@bues.ch>


Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Nicely done :)

      reply	other threads:[~2013-04-01 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 12:08 event subsystem: Define conference event types Michael Büsch
2013-04-01 19:04 ` Greg KH [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=20130401190457.GA22044@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m@bues.ch \
    /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