From: Jayson King <dev@jaysonking.com>
To: gregkh@suse.de
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 00/48] 2.6.27.32-stable review
Date: Wed, 09 Sep 2009 09:30:29 -0500 [thread overview]
Message-ID: <4AA7BC05.7050507@jaysonking.com> (raw)
Greg KH wrote:
>I thought the second one would solve the problem.
>
>What happened here, I took the upstream patch, was it incorrect? If so,
>was there a patch, also upstream, that fixed this problem?
>
>totally confused,
No. The upstream patch was not incorrect, but it was incompletely
applied to 2.6.27. The missing line is not missing in the upstream
patch. The replacement for the patch I sent earlier puts the line back in.
Jayson R. King
(sorry if I am dropping anyone from CC. I am not subscribed to LKML)
next reply other threads:[~2009-09-09 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 14:30 Jayson King [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-08 14:47 [patch 00/48] 2.6.27.32-stable review Jayson King
2009-09-09 3:08 ` Greg KH
2009-09-09 7:31 ` Michael Tokarev
2009-09-09 13:23 ` Greg KH
2009-09-09 18:28 ` Joel Becker
2009-09-09 18:36 ` Greg KH
2009-09-09 19:20 ` Chuck Ebbert
2009-09-09 20:15 ` Greg KH
2009-09-04 20:11 Greg KH
2009-09-06 22:58 ` Tilman Schmidt
2009-09-10 22:33 ` 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=4AA7BC05.7050507@jaysonking.com \
--to=dev@jaysonking.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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.