From: Stephan von Krawczynski <skraw@ithnet.com>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, ja@ssi.bg, gregkh@suse.de, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [stable] Re: Linux 2.6.16.13 / Problem
Date: Thu, 4 May 2006 08:40:54 +0200 [thread overview]
Message-ID: <20060504084054.fbb0167e.skraw@ithnet.com> (raw)
In-Reply-To: <20060503213408.GA14090@kroah.com>
On Wed, 3 May 2006 14:34:08 -0700
Greg KH <greg@kroah.com> wrote:
> On Wed, May 03, 2006 at 11:09:06PM +0200, Stephan von Krawczynski wrote:
> > On Wed, 3 May 2006 11:54:09 -0700
> > Greg KH <greg@kroah.com> wrote:
> >
> > > On Wed, May 03, 2006 at 03:45:32PM +0200, Stephan von Krawczynski wrote:
> > > > Hi Greg,
> > > >
> > > > unfortunately I see some problem regarding 2.6.16.13:
> > >
> > > Makes sense, as nothing in .13 was for something like this :)
> >
> > Sorry, didn't get that joke (no native englishman), you may explain in private
> > to me having spare time. Do you mean this is a _new_ story completely
> > unrelated to .13?
>
> No, meaning that .13 fixed a totally different problem from what you are
> reporting, so it is expected that the same problem you see with .12 is
> also in .13.
The problem is: I do not see it with .12 (or .11, or .10 (all tested)), but
only with .13. So maybe the .13-patch isn't as unrelated as it looks on first
sight...
(I used merely all 2.6.16.X, downloaded them always as complete archives)
--
Regards,
Stephan
next prev parent reply other threads:[~2006-05-04 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 22:28 Linux 2.6.16.13 Greg KH
2006-05-02 22:30 ` Greg KH
2006-05-03 13:45 ` Linux 2.6.16.13 / Problem Stephan von Krawczynski
2006-05-03 18:54 ` [stable] " Greg KH
2006-05-03 21:09 ` Stephan von Krawczynski
2006-05-03 21:34 ` Greg KH
2006-05-04 6:40 ` Stephan von Krawczynski [this message]
2006-05-04 7:05 ` Greg KH
2006-05-03 19:58 ` Bill Davidsen
2006-05-03 21:04 ` Stephan von Krawczynski
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=20060504084054.fbb0167e.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=ja@ssi.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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.