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 10:55:47 -0700 [thread overview]
Message-ID: <20201106175547.GA2959494@ubuntu-m3-large-x86> (raw)
In-Reply-To: <20201106110053.GA5532@sirena.org.uk>
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/20201105090615.620315-1-martin@geanix.com/
>
> > 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
prev parent reply other threads:[~2020-11-06 17:55 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
2020-11-06 11:00 ` Mark Brown
2020-11-06 17:55 ` Nathan Chancellor [this message]
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=20201106175547.GA2959494@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).