linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Christie <mchristi@redhat.com>
To: Ulf Hansson <ulf.hansson@linaro.org>, Jens Axboe <axboe@fb.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	regressions@leemhuis.info,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: 4.8-rc1 REGRESSION mmc-blk triggers WARN_ON(!host->claimed), related to: "drivers: use req op accessor" ?
Date: Fri, 26 Aug 2016 03:25:16 -0500	[thread overview]
Message-ID: <57BFFCEC.6020909@redhat.com> (raw)
In-Reply-To: <CAPDyKFrZCNv9VWu1pVg02wE3Pth3z3J0uh5dCdeYU8LYd_wXJQ@mail.gmail.com>

On 08/26/2016 02:13 AM, Ulf Hansson wrote:
> BTW, for some reason I (and linux-mmc) was not cc:ed on the commit
> that caused the regression:
> 
> c2df40dfb8c015211ec55f4b1dd0587f875c7b34
> Author: Mike Christie <mchristi@redhat.com>
> Date:   Sun Jun 5 14:32:17 2016 -0500
>     drivers: use req op accessor
> 
> Even if I probably wouldn't noticed that the patch was incorrect, it
> would have helped to know that we changed some parts in the mmc block
> layer when trying to find the regression. Could you please keep on eye
> on this future wise so it doesn't happen again.

Sorry about that and the bug. Both were my fault. Will be more careful
in the future.

      reply	other threads:[~2016-08-26  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 15:15 4.8-rc1 REGRESSION mmc-blk triggers WARN_ON(!host->claimed), related to: "drivers: use req op accessor" ? Hans de Goede
2016-08-22 16:09 ` Mike Christie
2016-08-24  8:47   ` Hans de Goede
2016-08-25  8:19     ` Adrian Hunter
2016-08-25 14:16       ` Jens Axboe
2016-08-25 18:26       ` Hans de Goede
2016-08-25 20:12         ` Jens Axboe
2016-08-26  7:13           ` Ulf Hansson
2016-08-26  8:25             ` Mike Christie [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=57BFFCEC.6020909@redhat.com \
    --to=mchristi@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=axboe@fb.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=ulf.hansson@linaro.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).