public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Voluspa <lista1@telia.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	len.brown@intel.com
Subject: Re: [2.6.16-rc2] Error - nsxfeval - And uncool silence from kernel hackers.
Date: Fri, 10 Feb 2006 03:50:51 +0100	[thread overview]
Message-ID: <20060210035051.55dbb74a.lista1@telia.com> (raw)
In-Reply-To: <20060209233233.GB23971@kroah.com>

On Thu, 9 Feb 2006 15:32:33 -0800 Greg KH wrote:
> On Fri, Feb 10, 2006 at 12:01:01AM +0100, Voluspa wrote:
> > 
> > Booted 2.6.16-rc2 on my AMD x86_64 notebook and saw something new in the
> > log (different from 2.6.15):
> 
> So, 2.6.16-rc2 works just fine, with out your reversal of that one
> patch?

Eh, I bundled two issues in my rant. 1) nsxfeval, which the ACPI guys
have confirmed is pure noise and can be forgotten. 2) "PCI: Failed to
allocate mem resource" which has been there since the commit I pointed
to, and never has effected the machine negatively (as far as I can tell).
So yes, 2.6.16-rc2 seems fine, and I don't patch it for that PCI thing.
It's just that the message is present and will worry people 'forever'
if nothing is done.

There is another issue, but it's not a regression. I'll file a
bugzilla for that in a couple of days. Or a week...

> > "1) Silence is _not_ golden."
> > 
> > Please, we the users breathe and bleed just like you do.
> 
> Sorry, and like you, we are human and drop things on the floor all the
> time.  Sorry for not following up on this before.
> 
> Persistance is a good trait to have when dealing with overworked kernel
> developers :)

Yeah, I know, sorry if I jabbed too hard. I was caught up in a sadness for
anyone who's mail is ignored. There is a form of humiliation when that
happens on a high profile list like lkml or other kernel related lists.
A mirror of the defeat can be found on a small server in Korpilombolo for
the next two decades at least.

But I must say that during the years that I've read lkml, it _feels_ as if
the reply-rate has improved significantly. The list is not as terrifying as
it used to be.

Mvh
Mats Johannesson
--

  reply	other threads:[~2006-02-10  2:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 23:01 [2.6.16-rc2] Error - nsxfeval - And uncool silence from kernel hackers Voluspa
2006-02-09 23:32 ` Greg KH
2006-02-10  2:50   ` Voluspa [this message]
2006-02-10  4:24     ` Greg KH
2006-02-12 13:05       ` Tako Schotanus
2006-02-13 10:12         ` Erik Slagter
2006-02-13 12:20           ` Tako Schotanus
  -- strict thread matches above, loose matches on Subject: below --
2006-02-09 23:13 Moore, Robert
2006-02-10  2:15 ` Voluspa

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=20060210035051.55dbb74a.lista1@telia.com \
    --to=lista1@telia.com \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --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