public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: green@linuxhacker.ru
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-next@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Anna Schumaker <Anna.Schumaker@Netapp.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	HPDD-discuss@ml01.01.org, Amir Shehata <amir.shehata@intel.com>,
	Oleg Drokin <oleg.drokin@intel.com>
Subject: Re: [PATCH] staging/lustre/o2iblnd: remove references to ib_reg_phsy_mr()
Date: Tue, 18 Aug 2015 19:53:11 -0700	[thread overview]
Message-ID: <20150819025311.GB4588@kroah.com> (raw)
In-Reply-To: <1439946275-1595274-1-git-send-email-green@linuxhacker.ru>

On Tue, Aug 18, 2015 at 09:04:35PM -0400, green@linuxhacker.ru wrote:
> From: Oleg Drokin <green@linuxhacker.ru>
> 
> Removed references to ib_reg_phsy_mr() and PMR which was added
> to deal with some Chelsio specific scenario, but no longer needed
> now.
> 
> Signed-off-by: Amir Shehata <amir.shehata@intel.com>
> Signed-off-by: Oleg Drokin <oleg.drokin@intel.com>
> ---
> This fixes a build failure in Lustre due to ib_reg_phys_mr being removed.

You forgot a reported-by line :(

I'll go add it...

  reply	other threads:[~2015-08-19  2:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  0:56 linux-next: build failure after merge of the nfs tree Stephen Rothwell
2015-08-19  0:05 ` Stephen Rothwell
2015-08-19  0:15   ` Drokin, Oleg
2015-08-19  1:04   ` [PATCH] staging/lustre/o2iblnd: remove references to ib_reg_phsy_mr() green
2015-08-19  2:53     ` Greg KH [this message]
2015-08-23 23:16 ` linux-next: build failure after merge of the nfs tree Stephen Rothwell
2015-08-24 14:17   ` Trond Myklebust
2015-08-24 14:48     ` Oleg Drokin

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=20150819025311.GB4588@kroah.com \
    --to=greg@kroah.com \
    --cc=Anna.Schumaker@Netapp.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=amir.shehata@intel.com \
    --cc=andreas.dilger@intel.com \
    --cc=chuck.lever@oracle.com \
    --cc=green@linuxhacker.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=trond.myklebust@fys.uio.no \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox