All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	stable-review@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [stable] [patch 00/48] 2.6.27.32-stable review
Date: Thu, 1 Oct 2009 08:30:17 -0700	[thread overview]
Message-ID: <20091001153017.GA6058@kroah.com> (raw)
In-Reply-To: <4AB387E3.6030709@imap.cc>

On Fri, Sep 18, 2009 at 03:15:15PM +0200, Tilman Schmidt wrote:
> Am 16.09.2009 23:09 schrieb Greg KH:
> > Can you send me what you need applied to the latest 2.6.27-stable tree
> > to fix this up so we can finally resolve this?
> 
> The patch that should have been applied is here:
> 
> http://patchwork.kernel.org/patch/13845/
> 
> I'm including it below for completeness.
> 
> The patch that was applied to 2.6.27-stable instead is this:
> 
> http://patchwork.kernel.org/patch/20855/
> (commit 221418f9a25cd96aff99d6aba41c177f6eb00853)
> 
> The difference is in blob 5 which inserts the new code at the wrong place.
> I have no idea who or what caused that change.
> 
> So commit 221418f9a25cd96aff99d6aba41c177f6eb00853 should be reverted and
> my original patch below applied instead. The patch by Stefan Bader is
> equivalent to that but additionally backports two pr_err() calls from
> mainline.

I took Stefan's patch as it was simpler.  Let me know if the problem is
still present.

thanks,

greg k-h

  reply	other threads:[~2009-10-01 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200909112223.n8BMMSHG002530@hera.kernel.org>
2009-09-16 21:09 ` [stable] [patch 00/48] 2.6.27.32-stable review Greg KH
2009-09-18  7:02   ` [Stable-review] " Stefan Bader
2009-09-18 13:15   ` Tilman Schmidt
2009-10-01 15:30     ` Greg KH [this message]
2009-10-02 22:36       ` Tilman Schmidt
2009-10-02 23:00         ` Greg KH

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=20091001153017.GA6058@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-review@kernel.org \
    --cc=stable@kernel.org \
    --cc=tilman@imap.cc \
    --cc=torvalds@linux-foundation.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.