All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jan Scholz <scholz@fias.uni-frankfurt.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, Adrian Bunk <bunk@kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [regression, bisected] adb trackpad disappears after suspend to ram
Date: Wed, 7 Oct 2009 22:18:22 +0200	[thread overview]
Message-ID: <200910072218.22357.rjw@sisk.pl> (raw)
In-Reply-To: <878wfnt9je.fsf@scholz.fias.uni-frankfurt.de>

On Wednesday 07 October 2009, Jan Scholz wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> 
> >> Alternatively, you could introduce a new flag IRQF_NOSUSPEND and use that
> >> instead of IRQF_TIMER.  That would be cleaner than using IRQF_TIMER for
> >> non-timer interrupts IMHO.
> >
> > I totally agree. The current patch is still good for stable though.
> >
> > I'll send it to Greg after I've upstreamed it, we can introduce IRQF_NOSUSPEND
> > in a second patch.
> 
> How's upstreaming going? I can neither find the patch in Linus branch,
> nor in linux-next. Could it be that it got lost?

More likely Ben didn't have the time to work on it.

Best,
Rafael

WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jan Scholz <scholz@fias.uni-frankfurt.de>
Cc: Adrian Bunk <bunk@kernel.org>,
	linux-kernel@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Ingo Molnar <mingo@elte.hu>,
	pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [regression, bisected] adb trackpad disappears after suspend to ram
Date: Wed, 7 Oct 2009 22:18:22 +0200	[thread overview]
Message-ID: <200910072218.22357.rjw@sisk.pl> (raw)
In-Reply-To: <878wfnt9je.fsf@scholz.fias.uni-frankfurt.de>

On Wednesday 07 October 2009, Jan Scholz wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> 
> >> Alternatively, you could introduce a new flag IRQF_NOSUSPEND and use that
> >> instead of IRQF_TIMER.  That would be cleaner than using IRQF_TIMER for
> >> non-timer interrupts IMHO.
> >
> > I totally agree. The current patch is still good for stable though.
> >
> > I'll send it to Greg after I've upstreamed it, we can introduce IRQF_NOSUSPEND
> > in a second patch.
> 
> How's upstreaming going? I can neither find the patch in Linus branch,
> nor in linux-next. Could it be that it got lost?

More likely Ben didn't have the time to work on it.

Best,
Rafael

  reply	other threads:[~2009-10-07 20:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 15:44 [regression] adb trackpad disappears after suspend to ram Jan Scholz
2009-05-28  7:59 ` [regression, bisected] " Jan Scholz
2009-05-28 16:58   ` Rafael J. Wysocki
2009-05-28 16:58   ` Rafael J. Wysocki
2009-05-28 22:23     ` Benjamin Herrenschmidt
2009-05-28 22:39       ` Jan Scholz
2009-05-28 22:39       ` Jan Scholz
2009-05-29 18:10         ` Rafael J. Wysocki
2009-05-29 18:10         ` Rafael J. Wysocki
2009-06-01 13:44           ` Jan Scholz
2009-06-01 16:36             ` Rafael J. Wysocki
2009-06-01 16:36             ` Rafael J. Wysocki
2009-06-01 22:34               ` Jan Scholz
2009-06-01 22:42                 ` Rafael J. Wysocki
2009-06-01 22:42                 ` Rafael J. Wysocki
2009-06-01 22:52                   ` Benjamin Herrenschmidt
2009-06-01 22:52                   ` Benjamin Herrenschmidt
2009-06-03 10:02                 ` Rafael J. Wysocki
2009-06-03 12:18                   ` Jan Scholz
2009-06-03 20:00                     ` Rafael J. Wysocki
2009-06-03 20:20                       ` Rafael J. Wysocki
2009-06-03 22:17                         ` [linux-pm] " Jan Scholz
2009-06-03 22:17                         ` Jan Scholz
2009-09-23  3:32                       ` Benjamin Herrenschmidt
2009-09-23  3:32                         ` Benjamin Herrenschmidt
2009-09-23 13:38                         ` Rafael J. Wysocki
2009-09-23 13:38                         ` Rafael J. Wysocki
2009-09-23 21:28                           ` Benjamin Herrenschmidt
2009-09-23 21:28                           ` Benjamin Herrenschmidt
2009-10-07 17:10                             ` Jan Scholz
2009-10-07 17:10                               ` Jan Scholz
2009-10-07 20:18                               ` Rafael J. Wysocki [this message]
2009-10-07 20:18                                 ` Rafael J. Wysocki
2009-09-23 23:12                           ` Jan Scholz
2009-09-23 23:12                           ` Jan Scholz
2009-10-09 21:27                       ` [PATCH] powerpc/pmac: Fix issues with sleep on some powerbooks Benjamin Herrenschmidt
2009-06-03 12:18                   ` [regression, bisected] adb trackpad disappears after suspend to ram Jan Scholz
2009-06-01 22:34               ` Jan Scholz
2009-06-02  4:49               ` Benjamin Herrenschmidt
2009-06-02  4:49                 ` Benjamin Herrenschmidt
2009-06-01 13:44           ` Jan Scholz
2009-05-28 22:23     ` Benjamin Herrenschmidt

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=200910072218.22357.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=benh@kernel.crashing.org \
    --cc=bunk@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=scholz@fias.uni-frankfurt.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.