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
Sascha Hauer (1):
spi: imx: fix runtime pm support for !CONFIG_PM
Zhao Qiang (1):
spi: fsl-dspi: fix wrong pointer in suspend/resume
drivers/spi/spi-bcm2835.c | 12 ------------
drivers/spi/spi-fsl-dspi.c | 10 ++++------
drivers/spi/spi-imx.c | 23 +++++++++++++++--------
3 files changed, 19 insertions(+), 26 deletions(-)
The pull request you sent on Thu, 05 Nov 2020 16:45:46 +0000:
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v5.10-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cf26c714874c14941953f6658ef85d7ce3446a0a
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
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/[email protected]/
It looks like there is a fix for it now:
https://lore.kernel.org/linux-spi/[email protected]/
Although I guess it is going to require a resend...
Cheers,
Nathan
On Fri, Nov 06, 2020 at 03:18:15AM -0700, Nathan Chancellor wrote:
> On Thu, Nov 05, 2020 at 04:45:46PM +0000, Mark Brown wrote:
> > Martin Hundeb?ll (1):
> > spi: bcm2835: fix gpio cs level inversion
> Why did this go in with two outstanding reports?
> It looks like there is a fix for it now:
> https://lore.kernel.org/linux-spi/[email protected]/
> Although I guess it is going to require a resend...
Erk, sorry - I remembered the issue being fixed but got confused and
thought that it was an incremental patch on top of something applied
rather than something that got fixed in a patch revision (got it
confused with another issue I think). The incremental fix is queued
now, I should send it out later today.
On Fri, Nov 06, 2020 at 11:00:53AM +0000, Mark Brown wrote:
> On Fri, Nov 06, 2020 at 03:18:15AM -0700, Nathan Chancellor wrote:
> > On Thu, Nov 05, 2020 at 04:45:46PM +0000, Mark Brown wrote:
>
> > > Martin Hundeb?ll (1):
> > > spi: bcm2835: fix gpio cs level inversion
>
> > Why did this go in with two outstanding reports?
>
> > It looks like there is a fix for it now:
>
> > https://lore.kernel.org/linux-spi/[email protected]/
>
> > Although I guess it is going to require a resend...
>
> Erk, sorry - I remembered the issue being fixed but got confused and
> thought that it was an incremental patch on top of something applied
> rather than something that got fixed in a patch revision (got it
> confused with another issue I think). The incremental fix is queued
> now, I should send it out later today.
No worries, I just wanted to make sure that you were still aware of the
issues with it. Obviously you have a lot on your plate constantly so it
is understandable that something falls through the cracks occasionally
:)
I see you have sent that pull already, thanks for the quick response!
Cheers,
Nathan