All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>, Nick Piggin <npiggin@suse.de>
Subject: Re: inotify fixes in stable
Date: Mon, 10 Mar 2008 14:13:46 -0700	[thread overview]
Message-ID: <20080310211346.GA6622@kroah.com> (raw)
In-Reply-To: <20080310215755.7e920738@mjolnir.drzeus.cx>

On Mon, Mar 10, 2008 at 09:57:55PM +0100, Pierre Ossman wrote:
> 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.

In that release, I said it was going to be my last.

> > 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.

Please let us know.

thanks,

greg k-h

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  8:11 inotify fixes in stable 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
2008-03-10 21:13         ` Greg KH [this message]
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=20080310211346.GA6622@kroah.com \
    --to=greg@kroah.com \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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.