From: James Bottomley <jejb@linux.vnet.ibm.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>, Jens Axboe <axboe@fb.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: LSF/MM Schedule and improving discard support
Date: Thu, 07 Apr 2016 11:51:29 -0400 [thread overview]
Message-ID: <1460044289.2311.5.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <57067F19.3030404@sandisk.com>
On Thu, 2016-04-07 at 08:39 -0700, Bart Van Assche wrote:
> Hello James,
>
> Some time ago I proposed to discuss how to improve discard support
> during the LSF/MM (http://thread.gmane.org/gmane.linux.scsi/110048).
> I would appreciate it if this would be added to the LSF/MM agenda
> since there has been no progress yet for the patch series I posted in
> December 2015.
Well, adding a cc to the lsf@ list to interest the attendees might have
been a good idea.
The basic problem with this topic is that it didn't really garner any
interest when you proposed it. It also really just looks like there's
nothing to discuss: you just propose the unifying patch and people
discuss and modify that and it either gets accepted or not depending on
the level of the objections.
James
next prev parent reply other threads:[~2016-04-07 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:39 LSF/MM Schedule and improving discard support Bart Van Assche
2016-04-07 15:51 ` James Bottomley [this message]
2016-04-13 15:57 ` Bart Van Assche
2016-04-13 16:21 ` Martin K. Petersen
2016-04-13 16:29 ` Bart Van Assche
2016-04-13 16:43 ` [Lsf] " Martin K. Petersen
2016-04-13 16:57 ` Bart Van Assche
2016-04-13 17:13 ` Martin K. Petersen
2016-04-13 16:51 ` James Bottomley
2016-04-13 17:30 ` Darrick J. Wong
2016-04-13 22:04 ` Douglas Gilbert
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=1460044289.2311.5.camel@linux.vnet.ibm.com \
--to=jejb@linux.vnet.ibm.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=linux-block@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 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.