From: Nathan Chancellor <natechancellor@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] SPI fixes for v5.10-rc2
Date: Fri, 6 Nov 2020 03:18:15 -0700 [thread overview]
Message-ID: <20201106101815.GA1403068@ubuntu-m3-large-x86> (raw)
In-Reply-To: <20201105164607.AD20021734@mail.kernel.org>
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
next prev parent reply other threads:[~2020-11-06 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 16:45 [GIT PULL] SPI fixes for v5.10-rc2 Mark Brown
2020-11-05 20:21 ` pr-tracker-bot
2020-11-06 10:18 ` Nathan Chancellor [this message]
2020-11-06 11:00 ` Mark Brown
2020-11-06 17:55 ` Nathan Chancellor
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=20201106101815.GA1403068@ubuntu-m3-large-x86 \
--to=natechancellor@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=torvalds@linux-foundation.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).