mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christian Leber <christian@leber.de>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: beeping patch for debugging acpi sleep
Date: Wed, 13 Jun 2007 14:28:23 +0200	[thread overview]
Message-ID: <20070613122823.GA2390@elf.ucw.cz> (raw)
In-Reply-To: <1181734353.5012.12.camel@nigel.suspend2.net>

Hi!

> > > Ok. I'll take Pavel's silence as agreement too. I'll be a little slow
> > > (as usual, nowadays!), but will try to get it done next week. I think I
> > > can in clear conscience do it on Redhat time if I don't manage it
> > > beforehand.
> > 
> > Well, everyone wants it so what can I do... Stefan basically posted 3
> > liner to do that, and that one will probably work... so just test it.
> 
> As he admitted, it's a quick and dirty hack. I'd like to try something
> nicer.

Well, his hack + rename one variable and there's one very nice solution.

> > Oh, and please keep the macro, so it can be moved around .S file for
> > finding out where it crashes.
> 
> Are there other points you'd like to nominate? It would defeat the logic
> for implementing a nice interface if you still have to recompile your
> kernel to test beeping in another place.

Just before entering C would be another interesting point.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-06-13 12:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 21:37 [BUG] acpi double resume and fail Christian Leber
2007-05-18 22:45 ` Andrew Morton
2007-05-19 19:42   ` Christian Leber
2007-05-20 20:01 ` Pavel Machek
     [not found]   ` <20070602182014.GB29546@core>
2007-06-09 13:08     ` beeping patch for debugging acpi sleep Pavel Machek
2007-06-09 13:16       ` Jan-Benedict Glaw
2007-06-09 22:54         ` Pavel Machek
2007-06-09 23:27           ` Nigel Cunningham
2007-06-09 23:35             ` Pavel Machek
2007-06-11  8:56       ` Stefan Seyfried
2007-06-11 16:50         ` Pavel Machek
2007-06-11 19:00       ` Andrew Morton
2007-06-11 19:49         ` Matthieu CASTET
2007-06-12 15:12           ` Pavel Machek
2007-06-13 17:58             ` Stefan Seyfried
2007-06-11 21:26         ` Pavel Machek
2007-06-11 22:42         ` Nigel Cunningham
2007-06-12 12:11           ` Rafael J. Wysocki
2007-06-13  1:17             ` Nigel Cunningham
2007-06-13  8:24               ` Pavel Machek
2007-06-13 11:32                 ` Nigel Cunningham
2007-06-13 12:28                   ` Pavel Machek [this message]
2007-06-13 12:40                     ` Rafael J. Wysocki
2007-06-16 19:46       ` Christian Leber
2007-06-24 20:46         ` Christian Leber
2007-06-28 14:08           ` Pavel Machek
2007-08-12 21:37             ` Christian Leber
2007-05-22 22:16 ` [BUG] acpi double resume and fail Mark Lord

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=20070613122823.GA2390@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=christian@leber.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome