From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Lucas Stach <l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: SPI regression in today's Linux next
Date: Tue, 17 Oct 2017 15:40:21 +0100 [thread overview]
Message-ID: <20171017144021.r7aydswer7anb5ha@sirena.co.uk> (raw)
In-Reply-To: <20171017143454.GA4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
On Tue, Oct 17, 2017 at 07:34:54AM -0700, Tony Lindgren wrote:
> Hi Lucas and Mark,
>
> Looks like commit 9ce70d49fa80 ("spi: fix IDR collision on systems with
> both fixed and dynamic SPI bus numbers") causes the following regression
> at least for omaps. Reverting commit 9ce70d49fa80 fixes it.
>
> Any ideas?
There's a fix already.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-10-17 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:34 SPI regression in today's Linux next Tony Lindgren
[not found] ` <20171017143454.GA4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-10-17 14:40 ` Mark Brown [this message]
[not found] ` <20171017144021.r7aydswer7anb5ha-7j8lgAiuQgnQXOPxS62xeg@public.gmane.org>
2017-10-17 14:59 ` Tony Lindgren
[not found] ` <20171017145901.GB4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-10-17 18:46 ` Mark Brown
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=20171017144021.r7aydswer7anb5ha@sirena.co.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).