From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: nigel@nigel.suspend2.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
Zan Lynx <zlynx@acm.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: echo mem > /sys/power/state
Date: Thu, 17 Jan 2008 23:27:13 +0100 [thread overview]
Message-ID: <200801172327.13961.rjw@sisk.pl> (raw)
In-Reply-To: <478FCC90.60605@nigel.suspend2.net>
On Thursday, 17 of January 2008, Nigel Cunningham wrote:
> Hi.
>
> Rafael J. Wysocki wrote:
> > On Thursday, 17 of January 2008, Andrew Morton wrote:
> >> On Thu, 17 Jan 2008 10:36:51 -0700 Zan Lynx <zlynx@acm.org> wrote:
> >>
> >>> On Wed, 2008-01-16 at 22:24 -0800, Andrew Morton wrote:
> >>>> So I take everyone's latest and greatest product and injudiciously type the
> >>>> above command. The result five minutes later is at
> >>>> http://userweb.kernel.org/~akpm/borkage.jpg. See if you can count all the bugs.
> >>>>
> >>>> Sorry, but I've had it with this stuff and I'm tired of fixing everyone else's
> >>>> stuff. I'm just going to ship it. Good luck.
> >>> Heh. Laptop suspend to anything has been so broken for so long in the
> >>> -mm series on my Compaq R3000 that I didn't even know it was ever
> >>> supposed to work.
> >> It gets broken more often than anything else. I do test each release on
> >> two laptops and I get to do a lot of bisection searching and
> >> grumpygramming as a result.
> >>
> >> Probably it would be more efficient to have the people who wrote the code
> >> also test it.
> >
> > Well, that would certainly help.
> >
> > I do test all of my patches and generally all of the patches I sign off, but
> > surely that's not enough.
>
> It is far too easy to take a cursory glance, say 'That looks okay' and
> move on to the next thing, isn't it? I was horrified when I saw the list
> of acks etc (including me) on the commit with the helper_unlock issue we
> just fixed. It's truly scary to think that none of us looked closely
> enough to pick that up at the time.
Well, the code in question was not in the patch, so if you didn't actually look
at the _patched_ kmod.c, you would have a little chance to spot it. I
overlooked it, even though I did look at the patched file ...
Still, this particular problem hasn't been triggering it testing for quite some
time.
Greetings,
Rafael
next prev parent reply other threads:[~2008-01-17 22:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 6:24 Andrew Morton
2008-01-17 17:36 ` Zan Lynx
2008-01-17 19:13 ` Andrew Morton
2008-01-17 21:38 ` Rafael J. Wysocki
2008-01-17 21:45 ` Nigel Cunningham
2008-01-17 22:27 ` Rafael J. Wysocki [this message]
2008-01-18 8:36 ` Ingo Molnar
2008-01-18 8:47 ` Andrew Morton
2008-01-18 9:04 ` Harvey Harrison
2008-01-18 12:18 ` Ingo Molnar
2008-01-18 14:26 ` Rafael J. Wysocki
2008-01-20 23:39 ` Pavel Machek
2008-01-20 23:42 ` Ingo Molnar
2008-01-21 0:31 ` Pavel Machek
2008-01-21 2:13 ` Johannes Weiner
2008-01-21 22:37 ` Pavel Machek
2008-01-22 14:42 ` Ingo Molnar
2008-01-23 21:27 ` Pavel Machek
2008-01-17 21:48 ` Jiri Slaby
2008-01-18 8:51 ` Ingo Molnar
2008-01-17 18:22 ` Rafael J. Wysocki
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=200801172327.13961.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nigel@nigel.suspend2.net \
--cc=tglx@linutronix.de \
--cc=zlynx@acm.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
all inboxes | Powered by JetHome®