All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@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 07:59:02 -0700	[thread overview]
Message-ID: <20171017145901.GB4394@atomide.com> (raw)
In-Reply-To: <20171017144021.r7aydswer7anb5ha-7j8lgAiuQgnQXOPxS62xeg@public.gmane.org>

* Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> [171017 07:41]:
> 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.

OK so with next-20171016, revert 9ce70d49fa80 and pick
226584aedd from the spi.git tree. Seems to work for me.

Thanks,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: SPI regression in today's Linux next
Date: Tue, 17 Oct 2017 07:59:02 -0700	[thread overview]
Message-ID: <20171017145901.GB4394@atomide.com> (raw)
In-Reply-To: <20171017144021.r7aydswer7anb5ha@sirena.co.uk>

* Mark Brown <broonie@kernel.org> [171017 07:41]:
> 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.

OK so with next-20171016, revert 9ce70d49fa80 and pick
226584aedd from the spi.git tree. Seems to work for me.

Thanks,

Tony

  parent reply	other threads:[~2017-10-17 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 14:34 SPI regression in today's Linux next Tony Lindgren
2017-10-17 14:34 ` Tony Lindgren
     [not found] ` <20171017143454.GA4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-10-17 14:40   ` Mark Brown
2017-10-17 14:40     ` Mark Brown
     [not found]     ` <20171017144021.r7aydswer7anb5ha-7j8lgAiuQgnQXOPxS62xeg@public.gmane.org>
2017-10-17 14:59       ` Tony Lindgren [this message]
2017-10-17 14:59         ` Tony Lindgren
     [not found]         ` <20171017145901.GB4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-10-17 18:46           ` Mark Brown
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=20171017145901.GB4394@atomide.com \
    --to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
    --cc=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 \
    /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.