All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
	jsimmons@infradead.org, paf@cray.com, namit@vmware.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	lustre-devel@lists.lustre.org
Subject: [lustre-devel] [BUG] staging: lustre: Possible null function pointer in ctx_refresh_timeout()
Date: Thu, 26 Jul 2018 16:12:27 +0200	[thread overview]
Message-ID: <20180726141227.GA12445@kroah.com> (raw)
In-Reply-To: <6920e093-ad62-56dc-6f58-36cf8d7ed3b4@gmail.com>

On Thu, Jul 26, 2018 at 10:02:22PM +0800, Jia-Ju Bai wrote:
> In Linux-4.16, drivers/staging/lustre/lustre/ptlrp/sec.c,

Please look at the 4.18-rc6 release for this file.

In short, nothing to worry about anymore :)

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
	jsimmons@infradead.org, paf@cray.com, namit@vmware.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	lustre-devel@lists.lustre.org
Subject: Re: [BUG] staging: lustre: Possible null function pointer in ctx_refresh_timeout()
Date: Thu, 26 Jul 2018 16:12:27 +0200	[thread overview]
Message-ID: <20180726141227.GA12445@kroah.com> (raw)
In-Reply-To: <6920e093-ad62-56dc-6f58-36cf8d7ed3b4@gmail.com>

On Thu, Jul 26, 2018 at 10:02:22PM +0800, Jia-Ju Bai wrote:
> In Linux-4.16, drivers/staging/lustre/lustre/ptlrp/sec.c,

Please look at the 4.18-rc6 release for this file.

In short, nothing to worry about anymore :)

thanks,

greg k-h

  reply	other threads:[~2018-07-26 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 14:02 [lustre-devel] [BUG] staging: lustre: Possible null function pointer in ctx_refresh_timeout() Jia-Ju Bai
2018-07-26 14:02 ` Jia-Ju Bai
2018-07-26 14:12 ` Greg KH [this message]
2018-07-26 14:12   ` Greg KH
2018-07-26 14:18   ` [lustre-devel] " Jia-Ju Bai
2018-07-26 14:18     ` Jia-Ju Bai

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=20180726141227.GA12445@kroah.com \
    --to=greg@kroah.com \
    --cc=andreas.dilger@intel.com \
    --cc=baijiaju1990@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=namit@vmware.com \
    --cc=oleg.drokin@intel.com \
    --cc=paf@cray.com \
    /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.