All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: olaf@aepfle.de
Cc: KY Srinivasan <kys@microsoft.com>,
	James Bottomley <JBottomley@Odin.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] storvsc: use small sg_tablesize on x86
Date: Mon, 16 May 2016 16:26:33 -0400	[thread overview]
Message-ID: <573A2CF9.5060702@canonical.com> (raw)

Replying to thread:
https://lkml.org/lkml/2016/2/26/1090


> -----Original Message-----
> From: James Bottomley [mailto:James.Bottomley@HansenPartnership.com]
> Sent: Thursday, January 28, 2016 7:37 AM
> To: Olaf Hering <olaf@aepfle.de>
> Cc: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
> <haiyangz@microsoft.com>; linux-kernel@vger.kernel.org; linux-
> scsi@vger.kernel.org
> Subject: Re: [PATCH] storvsc: use small sg_tablesize on x86
>
> On Thu, 2016-01-28 at 07:48 +0100, Olaf Hering wrote:
> > On Wed, Jan 27, James Bottomley wrote:
> >
> > > It's not really architecture independent, is it?  Just use the bit
> > > width config.
> >
> > Again: which one? This driver is not for mips|powerpc|score|sh.
>
> zgrep CONFIG_.*BIT /proc/config.gz
> [...]
> CONFIG_64BIT=y
>
> James

    Olaf,

    Would you be resubmitting this patch?

    Thanks,

    K. Y

Hello,

It doesn't appear this patch ever landed in Mainline.  Olaf, do you have
plans to submit this patch?

Thanks,

Joe





             reply	other threads:[~2016-05-16 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 20:26 Joseph Salisbury [this message]
2016-05-17 13:07 ` [PATCH] storvsc: use small sg_tablesize on x86 Olaf Hering
  -- strict thread matches above, loose matches on Subject: below --
2015-09-08 10:06 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-01 21:27       ` KY Srinivasan
2015-10-02 17:14     ` Olaf Hering
2016-01-25  8:35       ` Olaf Hering
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

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=573A2CF9.5060702@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=JBottomley@Odin.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /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.