All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Doug Ledford <dledford@redhat.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: linux-rdma@vger.kernel.org, target-devel@vger.kernel.org,
	Steve Wise <swise@opengridcomputing.com>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly
Date: Tue, 8 Dec 2015 20:13:00 +0200	[thread overview]
Message-ID: <56671DAC.7060001@dev.mellanox.co.il> (raw)
In-Reply-To: <56671A31.7090401@redhat.com>


> I've pulled these in.  Both of them failed to apply, and the first one
> was just flat baffling in terms of how Sagi is working from a source
> base so different than the one in the upstream kernel.  They should be
> double checked just to make sure I'm not missing something since they
> were so far off from applying to an upstream kernel.

Hi Doug,

I mentioned this in v1. This patch set is applied over Christoph's
device attributes patch. Will it go in as well?

  reply	other threads:[~2015-12-08 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 11:28 [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly Sagi Grimberg
2015-10-28 11:28 ` [PATCH v2 1/2] mlx4: Expose correct max_sge_rd limit Sagi Grimberg
2015-12-08 17:56   ` Doug Ledford
     [not found] ` <1446031696-19022-1-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-10-28 11:28   ` [PATCH v2 2/2] iser-target: Remove explicit mlx4 work-around Sagi Grimberg
2015-11-10 10:36   ` [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly Sagi Grimberg
     [not found]     ` <5641C8BC.40507-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-12-03 14:27       ` Christoph Hellwig
     [not found]         ` <20151203142730.GA20520-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-12-03 15:07           ` Sagi Grimberg
2015-12-08 17:01             ` Christoph Hellwig
     [not found]               ` <20151208170139.GA425-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-12-08 17:58                 ` Doug Ledford
2015-12-08 18:13                   ` Sagi Grimberg [this message]
2015-12-08 18:17                     ` Doug Ledford
     [not found]                       ` <56671EB8.6010207-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-08 18:18                         ` Doug Ledford
2015-12-09  9:33                           ` Sagi Grimberg

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=56671DAC.7060001@dev.mellanox.co.il \
    --to=sagig@dev.mellanox.co.il \
    --cc=dledford@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=ogerlitz@mellanox.com \
    --cc=swise@opengridcomputing.com \
    --cc=target-devel@vger.kernel.org \
    /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.