LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Pascal Terjan <pterjan@mandriva.com>
Cc: dhowells@redhat.com,
	Rutger Nijlunsing <rutger.nijlunsing@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, stable <stable@kernel.org>,
	Steve French <smfrench@gmail.com>
Subject: Re: OOPS in request_key.c bisected (and then refound)
Date: Tue, 28 Oct 2008 14:28:48 +0000	[thread overview]
Message-ID: <3450.1225204128@redhat.com> (raw)
In-Reply-To: <1225200833.8039.26.camel@plop>

Pascal Terjan <pterjan@mandriva.com> wrote:

> This patch was confirmed by a user here to fix the oops (happened while
> using mount.cifs with kerberos).
> Is there a reason not to merge it (and into stable too) ?

I thought it was upstream, but I think I must've been looking at the wrong
GIT tree.  I'll push it now.

David

      parent reply	other threads:[~2008-10-28 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080817194532.GB15440@nospam.com>
2008-08-18  1:18 ` Steve French
2008-10-28 13:33   ` Pascal Terjan
2008-10-28 14:28   ` David Howells [this message]

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=3450.1225204128@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pterjan@mandriva.com \
    --cc=rutger.nijlunsing@gmail.com \
    --cc=smfrench@gmail.com \
    --cc=stable@kernel.org \
    --subject='Re: OOPS in request_key.c bisected (and then refound)' \
    /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).