[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201106101815.GA1403068@ubuntu-m3-large-x86>
Date: Fri, 6 Nov 2020 03:18:15 -0700
From: Nathan Chancellor <natechancellor@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] SPI fixes for v5.10-rc2
On Thu, Nov 05, 2020 at 04:45:46PM +0000, Mark Brown wrote:
> The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
>
> Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v5.10-rc2
>
> for you to fetch changes up to 9bd77a9ce31dd242fece27219d14fbee5068dd85:
>
> spi: fsl-dspi: fix wrong pointer in suspend/resume (2020-11-04 17:50:24 +0000)
>
> ----------------------------------------------------------------
> spi: Fixes for v5.10
>
> A small collection of driver specific fixes that have come in since the
> merge window, nothing too major here but all good to ahve.
>
> ----------------------------------------------------------------
> Mark Brown (1):
> Merge tag 'v5.10-rc1' into spi-5.10
>
> Martin Hundebøll (1):
> spi: bcm2835: fix gpio cs level inversion
Why did this go in with two outstanding reports?
https://lore.kernel.org/linux-spi/20201030090621.GA3594676@ubuntu-m3-large-x86/
https://lore.kernel.org/linux-spi/ad239665-e342-cdef-71c0-4eba06b76797@canonical.com/
It looks like there is a fix for it now:
https://lore.kernel.org/linux-spi/20201105090615.620315-1-martin@geanix.com/
Although I guess it is going to require a resend...
Cheers,
Nathan
Powered by blists - more mailing lists