LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Greg KH <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Nick Piggin <npiggin@suse.de>
Subject: Re: inotify fixes in stable
Date: Mon, 10 Mar 2008 21:57:55 +0100	[thread overview]
Message-ID: <20080310215755.7e920738@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080310203116.GC5943@kroah.com>

On Mon, 10 Mar 2008 13:31:16 -0700
Greg KH <greg@kroah.com> wrote:

> On Mon, Mar 10, 2008 at 08:36:58PM +0100, Pierre Ossman wrote:
> > 
> > The system is an OpenSuse 10.3 system, so 2.6.22.y would be the
> > interesting one. I'll see if I can get a custom kernel in there (I've
> > been unable to reproduce the problem outside a production
> > environment).
> 
> 2.6.22.y is no longer being released by me, so it isn't interesting to
> me at all :)
> 

Oh? You made a release just 13 days ago, so I figured you were still giving it some love.

> What about 2.6.24?  Is this still an issue there?

Judging from the kernel bugzilla, it would seem so.

But in my specific case, the guy on site was going to try an updated kernel from Suse's build system. I'll probably now the results tomorrow or the day after that.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

  reply	other threads:[~2008-03-10 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  8:11 Pierre Ossman
2008-03-10 16:03 ` Greg KH
2008-03-10 19:36   ` Pierre Ossman
2008-03-10 20:31     ` Greg KH
2008-03-10 20:57       ` Pierre Ossman [this message]
2008-03-10 21:13         ` Greg KH
2008-03-11  4:12           ` Nick Piggin
2008-03-24 22:33             ` Chr
2008-03-25  0:42               ` Chris Wright
2008-03-25 13:15                 ` Chr

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=20080310215755.7e920738@mjolnir.drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --subject='Re: inotify fixes in stable' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).