LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Cc: "Tejun Heo" <teheo@suse.de>,
	linux@horizon.com, dan.j.williams@intel.com,
	linux-ide@vger.kernel.org, neilb@suse.de, cebbert@redhat.com,
	jens.axboe@oracle.com, linux-kernel@dale.us,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.20.3 AMD64 oops in CFQ code
Date: Thu, 5 Apr 2007 00:13:55 -0400	[thread overview]
Message-ID: <75b66ecd0704042113mebd1275w2fa40bf159416811@mail.gmail.com> (raw)
In-Reply-To: <46143338.3020808@tmr.com>

On 4/4/07, Bill Davidsen <davidsen@tmr.com> wrote:
> I won't say that's voodoo, but if I ever did it I'd wipe down my
> keyboard with holy water afterward. ;-)
>
> Well, I did save the message in my tricks file, but it sounds like a
> last ditch effort after something get very wrong.

Would it reallty be an impediment to development if the kernel
maintainers simply refuse to merge patches that add new sysfs entries
without corresponding documentation?

Lee

  reply	other threads:[~2007-04-05  4:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 12:38 linux
2007-03-22 18:41 ` Jens Axboe
2007-03-22 18:54   ` linux
2007-03-22 19:00     ` Jens Axboe
2007-03-22 23:59       ` Neil Brown
2007-03-23  0:31         ` Dan Williams
2007-03-23  0:33           ` Dan Williams
2007-03-23  0:44           ` Neil Brown
2007-03-23 17:46             ` linux
2007-04-03  5:49               ` Tejun Heo
2007-04-03 13:03                 ` linux
2007-04-03 13:11                   ` Tejun Heo
2007-04-04 23:22                 ` Bill Davidsen
2007-04-05  4:13                   ` Lee Revell [this message]
2007-04-05  4:29                     ` Tejun Heo
2007-03-22 18:43 ` Aristeu Sergio Rozanski Filho

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=75b66ecd0704042113mebd1275w2fa40bf159416811@mail.gmail.com \
    --to=rlrevell@joe-job.com \
    --cc=cebbert@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=davidsen@tmr.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@dale.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=neilb@suse.de \
    --cc=teheo@suse.de \
    --subject='Re: 2.6.20.3 AMD64 oops in CFQ code' \
    /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

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).