linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] storvsc: use small sg_tablesize on x86
Date: Mon, 25 Jan 2016 09:35:14 +0100	[thread overview]
Message-ID: <20160125083514.GA11991@gmail.com> (raw)
In-Reply-To: <20151002171415.GA30430@gmail.com>

On Fri, Oct 02, Olaf Hering wrote:

> On Thu, Oct 01, James Bottomley wrote:
> 
> > On Thu, 2015-10-01 at 20:30 +0000, KY Srinivasan wrote:
> 
> > > > +#if defined(CONFIG_X86_32)
> 
> > Um, this is a bit architecture specific (I know Azure is x86, but
> > still).  Can you make the define check CONFIG_32BIT rather than
> > CONFIG_X86_32?
> 
> According to arch/x86/Kconfig there is no such thing.

What is the status of this change? Looks like there is nothing more to
do on my side.

Olaf

  reply	other threads:[~2016-01-25  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 10:06 [PATCH] storvsc: use small sg_tablesize on x86 Olaf Hering
2015-10-01 20:30 ` KY Srinivasan
2015-10-01 20:51   ` James Bottomley
2015-10-01 21:27     ` KY Srinivasan
2015-10-02 17:14     ` Olaf Hering
2016-01-25  8:35       ` Olaf Hering [this message]
2016-01-27 23:09         ` KY Srinivasan
2016-01-28  6:00           ` James Bottomley
2016-01-28  6:48             ` Olaf Hering
2016-01-28 15:37               ` James Bottomley
2016-02-26 22:11                 ` KY Srinivasan
  -- strict thread matches above, loose matches on Subject: below --
2016-05-16 20:26 Joseph Salisbury
2016-05-17 13:07 ` Olaf Hering

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=20160125083514.GA11991@gmail.com \
    --to=olaf@aepfle.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 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).