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: Wed, 16 Sep 2009 14:09:56 -0700 [thread overview]
Message-ID: <20090916210956.GB24567@kroah.com> (raw)
In-Reply-To: <200909112223.n8BMMSHG002530@hera.kernel.org>
On Sat, Sep 12, 2009 at 12:22:22AM +0200, Tilman Schmidt wrote:
> [On holiday, answering from my nominally internet capable cellphone - please make allowances ...]
>
> The stable patch claiming to correspond to Linus' tree patch
> 56f7efe48d57dda9e59e23ab161c118271cce815 and merged in 2.6.27.sth
> (eyact version not at hand) and 2.6.28.10 differs from the backported
> patch I submitted for stable myself. It breaks the driver completely,
> causing an oops and system malfunctions as soon as the device is
> connected. (Sorry for not noticing the vital difference at the time.)
No problem.
> The attached patch would fix the error by moving the code inswrted at
> the wrong place by the broken backported patch,, to the correct place
> where it went in the original patch.
I see no patch attached here :(
> Alternativelyy, the broken backported could be reverted and my
> original bacport merged instead, if you can still find it.
I can not.
> Sorry for lack of references as i don't have acces to my development
> machine from here. Hope to have Cleared up the situation, anyway.
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?
thanks,
greg k-h
next parent reply other threads:[~2009-09-16 21:35 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 ` Greg KH [this message]
2009-09-18 7:02 ` [Stable-review] [stable] [patch 00/48] 2.6.27.32-stable review Stefan Bader
2009-09-18 13:15 ` Tilman Schmidt
2009-10-01 15:30 ` Greg KH
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=20090916210956.GB24567@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox