public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Tejun Heo <tj@kernel.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-ide@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Revert "ata: sata_mv: Convert to devm_ioremap_resource()"
Date: Tue, 30 May 2017 16:55:48 +0300	[thread overview]
Message-ID: <1496152548.28981.25.camel@linux.intel.com> (raw)
In-Reply-To: <20170530135256.9966-1-linus.walleij@linaro.org>

On Tue, 2017-05-30 at 15:52 +0200, Linus Walleij wrote:
> This reverts commit 368e5fbdfc60732643f34f538823ed4bc8829827.
> 
> My NAS stopped to mount root when I went from some v4.10-rc1
> to v4.12-rc3. Investigation of the bootlog yields this:
> 
> sata_mv f1080000.sata: can't request region for resource [mem
> 0xf1080000-0xf1084fff]
> sata_mv: probe of f1080000.sata failed with error -16
> 
> Reverting this offending patch makes the sata_mv probe and
> my SATA drive can mount root again, hooray!

It's already in upstream (ata tree).

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-05-30 13:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 13:52 [PATCH] Revert "ata: sata_mv: Convert to devm_ioremap_resource()" Linus Walleij
2017-05-30 13:55 ` Andy Shevchenko [this message]
2017-05-30 23:53   ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2017-05-23 23:39 Andrew Lunn
2017-05-24 13:01 ` Gregory CLEMENT
2017-05-24 13:12   ` Andrew Lunn
2017-05-24 13:36   ` Andy Shevchenko
2017-05-24 13:41     ` Andrew Lunn
2017-05-24 14:00       ` Andy Shevchenko
2017-05-24 14:11         ` Gregory CLEMENT
2017-05-24 14:29         ` Andrew Lunn
2017-05-25 12:53           ` Andy Shevchenko
2017-05-25 13:26             ` Andrew Lunn
2017-05-25 13:34               ` Andy Shevchenko
2017-05-24 15:07 ` Tejun Heo

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=1496152548.28981.25.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox