linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Ulf Hansson <ulf.hansson@stericsson.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Per FORLIN <per.forlin@stericsson.com>,
	Johan RUDHOLM <johan.rudholm@stericsson.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 0/2] Improve handling of card removal
Date: Tue, 31 Jan 2012 15:56:43 +0200	[thread overview]
Message-ID: <4F27F31B.6020401@intel.com> (raw)
In-Reply-To: <4F27E5D5.1050906@stericsson.com>

On 31/01/12 15:00, Ulf Hansson wrote:
> Adrian Hunter wrote:
>> On 19/01/12 18:39, Ulf Hansson wrote:
>>> These patches is based upon the patch recently pushed to the mmc mailing
>>> list:
>>> mmc: core: Force a "detect" to handle non-properly removed cards
>>>
>>> According to Adrian Hunters comment about adding a CAP2 flag to enable
>>> this feature has been done.
>>>
>>> Patch 2 depends on patch 1; but patch 1 can also be discussed separately.
>>
>> There should only be 1 patch otherwise you are breaking bisectablility for
>> people not setting MMC_CAP2_DETECT_ON_ERR
> 
> The first patch "Prevent I/O as soon as possible..." does only make sure
> that I/O is prevented as soon as possible but still within the timeout for
> the scheduled detect work. Once the detect work (mmc_rescan) has run the
> "detect_change" flag is preventing any further I/O errors from directly
> trying to detect a card removal.
> 
> The second patch introduces the MMC_CAP2_DETECT_ON_ERR, as you suggested.

For drivers not using MMC_CAP2_DETECT_ON_ERR, the first patch introduces a
change in behaviour and the second patch removes it again.  Anyone doing a
git bisect that lands between the patches will see that change in behaviour.
 There is no reason for that - just make it one patch.

> 
>>
>>> Ulf Hansson (2):
>>>   mmc: core: Prevent I/O as soon as possible at card removal
>>>   mmc: core: Detect card removal on I/O error
>>>
>>>  drivers/mmc/core/core.c  |   19 ++++++++++++++++---
>>>  include/linux/mmc/host.h |    1 +
>>>  2 files changed, 17 insertions(+), 3 deletions(-)
>>>
>>
>>
> 
> Br
> Ulf Hansson
> 
> 


  reply	other threads:[~2012-01-31 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 16:39 [PATCH 0/2] Improve handling of card removal Ulf Hansson
2012-01-19 16:39 ` [PATCH 1/2] mmc: core: Prevent I/O as soon as possible at " Ulf Hansson
2012-01-20 11:55   ` Adrian Hunter
2012-01-31 12:54     ` Ulf Hansson
2012-01-31 13:56       ` Adrian Hunter
2012-01-31 15:23         ` Ulf Hansson
2012-02-01  3:02           ` Jaehoon Chung
2012-02-01  9:40             ` Ulf Hansson
2012-02-02  4:00               ` Jaehoon Chung
2012-01-19 16:39 ` [PATCH 2/2] mmc: core: Detect card removal on I/O error Ulf Hansson
2012-01-20 11:55 ` [PATCH 0/2] Improve handling of card removal Adrian Hunter
2012-01-31 13:00   ` Ulf Hansson
2012-01-31 13:56     ` Adrian Hunter [this message]
2012-01-31 15:40       ` Ulf Hansson
2012-02-01  9:37         ` Adrian Hunter
2012-02-01  9:44           ` Ulf Hansson

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=4F27F31B.6020401@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=cjb@laptop.org \
    --cc=johan.rudholm@stericsson.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=ulf.hansson@stericsson.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 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).