From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Nowak, Mateusz" <mateusz.nowak@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Wodkowski, PawelX" <pawelx.wodkowski@intel.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 0/2] mmc, block: override default max_dev_sectors
Date: Sat, 05 Mar 2016 16:58:57 -0500 [thread overview]
Message-ID: <yq1fuw44me6.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <07856956733C274AB06C493240019A2D76CDEC35@IRSMSX101.ger.corp.intel.com> (Mateusz Nowak's message of "Fri, 4 Mar 2016 10:49:29 +0000")
>>>>> "Mateusz" == Nowak, Mateusz <mateusz.nowak@intel.com> writes:
>> Past commit 5f009d ("block: Initialize max_dev_sectors to 0"), this
>> should not be needed.
Mateusz> I missed the fix you mention while rebasing from rc3. Thus
Mateusz> apologies for providing incorrectly described and not
Mateusz> necessarily needed patch set.
Mateusz> However, since some drivers may still want to override
Mateusz> max_dev_sectors, would the patches be good to be redone and
Mateusz> resubmitted as improvement?
Nothing prevents you from setting max_dev_sectors in the driver. That's
why it's there. The default being set in my original patch just had the
unfortunate side-effect of clamping the controller limit.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-03-05 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 8:54 [PATCH 0/2] mmc, block: override default max_dev_sectors Pawel Wodkowski
2016-03-02 8:55 ` [PATCH 1/2] block: Allow to set max_dev_sectors for a queue Pawel Wodkowski
2016-03-02 8:55 ` [PATCH 2/2] mmc/block: Override default max_dev_sectors Pawel Wodkowski
2016-03-02 17:12 ` [PATCH 0/2] mmc, block: override " Christoph Hellwig
2016-03-04 10:49 ` Nowak, Mateusz
2016-03-05 21:58 ` Martin K. Petersen [this message]
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=yq1fuw44me6.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mateusz.nowak@intel.com \
--cc=pawelx.wodkowski@intel.com \
/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.