linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Mitchell Erblich <erblichs@earthlink.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Scheduling Addition Notification : Hybrid Sleepers and Unfair scheduling
Date: Thu, 19 Mar 2015 04:59:03 +0100	[thread overview]
Message-ID: <1426737543.4168.54.camel@gmail.com> (raw)
In-Reply-To: <DF3A0BDD-0FFF-4E8A-9CA2-A719555DDD8F@earthlink.net>

On Wed, 2015-03-18 at 20:43 -0700, Mitchell Erblich wrote:

> This proposal was ONLY to resolve the legal issue with public domain
> code of notification when a patch was not offered.…

Ah, so completely off topic here.. but then you knew that.  How rude.

	-Mike


  reply	other threads:[~2015-03-19  3:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 23:25 Linux Kernel Scheduling Addition Notification : Hybrid Sleepers and Unfair scheduling Mitchell Erblich
2015-03-19  2:38 ` Mike Galbraith
2015-03-19  3:43   ` Mitchell Erblich
2015-03-19  3:59     ` Mike Galbraith [this message]
2015-03-19  4:32       ` Mitchell Erblich
2015-03-19  5:28         ` Mike Galbraith
2015-03-20  1:53         ` Theodore Ts'o

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=1426737543.4168.54.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=erblichs@earthlink.net \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).