All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible suspend/resume regression in .32-rc?
Date: Wed, 13 Jan 2010 07:33:29 -0800	[thread overview]
Message-ID: <20100113153329.GA1276@suse.de> (raw)
In-Reply-To: <1263390161.5419.9.camel@hammer.suse.cz>

On Wed, Jan 13, 2010 at 02:42:41PM +0100, Stanislav Brabec wrote:
> Daniel Mack wrote:
> 
> > It seems Stanislav's patch is still unmerged in the current git HEAD.
> > Any idea why it is held back? I have it applied locally since quite a
> > while here, and it works well. So if it helps, take my Tested-by: for
> > it.
> 
> It seems to be on the right way:
> 
> From: gregkh at suse.de
> Subject: patch serial-core-resume-serial-hardware-with-no_console_suspend.patch added to gregkh-2.6 tree
> Date: Tue, 22 Dec 2009 12:22:35 -0800
> 
> This is a note to let you know that I've just added the patch titled
> 
>     Subject: serial-core: resume serial hardware with no_console_suspend
> 
> to my gregkh-2.6 tree.  Its filename is
> 
>     serial-core-resume-serial-hardware-with-no_console_suspend.patch
> 
> This tree can be found at 
> 
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/

Ah, I missed that this was fixing a regression, so I'll move it to my
"apply before .32 is out" queue.  Sorry about that.

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Stanislav Brabec <utx@penguin.cz>
Cc: Daniel Mack <daniel@caiaq.de>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Eric <eric.y.miao@gmail.com>,
	Pavel Machek <pavel@ucw.cz>,
	dbaryshkov@gmail.com, Cyril Hrubis <metan@ucw.cz>,
	arminlitzel@web.de, Haojian Zhuang <haojian.zhuang@marvell.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	dsaxena@laptop.org, lenz@cs.wisc.edu, rpurdie@rpsys.net,
	omegamoon@gmail.com, thommycheck@gmail.com, Dirk@opfer-online.de,
	linux-arm-kernel@lists.infradead.org, alan@linux.intel.com
Subject: Re: Possible suspend/resume regression in .32-rc?
Date: Wed, 13 Jan 2010 07:33:29 -0800	[thread overview]
Message-ID: <20100113153329.GA1276@suse.de> (raw)
In-Reply-To: <1263390161.5419.9.camel@hammer.suse.cz>

On Wed, Jan 13, 2010 at 02:42:41PM +0100, Stanislav Brabec wrote:
> Daniel Mack wrote:
> 
> > It seems Stanislav's patch is still unmerged in the current git HEAD.
> > Any idea why it is held back? I have it applied locally since quite a
> > while here, and it works well. So if it helps, take my Tested-by: for
> > it.
> 
> It seems to be on the right way:
> 
> From: gregkh@suse.de
> Subject: patch serial-core-resume-serial-hardware-with-no_console_suspend.patch added to gregkh-2.6 tree
> Date: Tue, 22 Dec 2009 12:22:35 -0800
> 
> This is a note to let you know that I've just added the patch titled
> 
>     Subject: serial-core: resume serial hardware with no_console_suspend
> 
> to my gregkh-2.6 tree.  Its filename is
> 
>     serial-core-resume-serial-hardware-with-no_console_suspend.patch
> 
> This tree can be found at 
> 
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/

Ah, I missed that this was fixing a regression, so I'll move it to my
"apply before .32 is out" queue.  Sorry about that.

greg k-h

  reply	other threads:[~2010-01-13 15:33 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31  1:34 Possible suspend/resume regression in .32-rc? Daniel Mack
2009-10-31 12:56 ` Eric Miao
2009-10-31 16:39 ` Robert Jarzmik
2009-11-01  0:48   ` Ben Dooks
2009-11-01 19:54 ` Ryan Mallon
2009-11-01 20:22 ` Uwe Kleine-König
2009-11-01 20:54 ` Daniel Mack
2009-11-01 21:33   ` Pavel Machek
2009-11-01 21:33     ` Pavel Machek
2009-11-01 22:03     ` Pavel Machek
2009-11-01 22:03       ` Pavel Machek
2009-11-02  9:22       ` Haojian Zhuang
2009-11-02  9:22         ` Haojian Zhuang
2009-11-02  9:29         ` Daniel Mack
2009-11-02  9:29           ` Daniel Mack
2009-11-02  9:38         ` Pavel Machek
2009-11-02  9:38           ` Pavel Machek
2009-11-02  9:54           ` Eric Miao
2009-11-02  9:54             ` Eric Miao
2009-11-02 10:48           ` Haojian Zhuang
2009-11-02 10:48             ` Haojian Zhuang
2009-11-02 10:51             ` Pavel Machek
2009-11-02 10:51               ` Pavel Machek
2009-11-02 11:18               ` Haojian Zhuang
2009-11-02 11:18                 ` Haojian Zhuang
2009-11-02 11:27                 ` Daniel Mack
2009-11-02 11:27                   ` Daniel Mack
2009-11-02 12:22                 ` Pavel Machek
2009-11-02 12:22                   ` Pavel Machek
2009-11-02  9:57         ` Stanislav Brabec
2009-11-02  9:57           ` Stanislav Brabec
2009-11-03  3:31           ` Haojian Zhuang
2009-11-03  3:31             ` Haojian Zhuang
2009-11-03  9:50             ` Stanislav Brabec
2009-11-03  9:50               ` Stanislav Brabec
2009-11-05  5:06               ` Haojian Zhuang
2009-11-05  5:06                 ` Haojian Zhuang
2010-01-13 11:46                 ` Daniel Mack
2010-01-13 11:46                   ` Daniel Mack
2010-01-13 13:42                   ` Stanislav Brabec
2010-01-13 13:42                     ` Stanislav Brabec
2010-01-13 15:33                     ` Greg KH [this message]
2010-01-13 15:33                       ` Greg KH
2009-11-01 21:13 ` Pavel Machek
2009-11-01 21:16   ` Daniel Mack

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=20100113153329.GA1276@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-arm-kernel@lists.infradead.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 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.