From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] regmap updates for v5.11
Date: Wed, 16 Dec 2020 18:25:09 +0000 [thread overview]
Message-ID: <20201216182509.GD4861@sirena.org.uk> (raw)
In-Reply-To: <CAHk-=whOwGP7G-6rn8ZPwQJHhGiS1MxW06n7YY0TO=P8xHwf8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Tue, Dec 15, 2020 at 03:47:47PM -0800, Linus Torvalds wrote:
> On Mon, Dec 14, 2020 at 6:47 AM Mark Brown <broonie@kernel.org> wrote:
> > There was also an addition and revert of use of the new Soundwire
> > support for RT715 due to build issues with the driver built in, my tests
> > only covered building it as a module, the patch wasn't just dropped as
> > it had already been merged elsewhere.
> Ok, this made my diffstat look very odd and very different from yours
> - because I had already gotten that driver from the sound tree, so my
> diffstat looked very different from the one you have - and instead of
> being the no-op that it was for you (add and then delete), it showed
> up as just a delete for me.
Yes, that looks good - it matches what was in -next. I had actually
meant the add to go through instead but I'd not noticed that the delete
was winning (I think I checked this in -next at the wrong point), I'll
make sure things go through for v5.12.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-16 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 14:47 [GIT PULL] regmap updates for v5.11 Mark Brown
2020-12-15 23:47 ` Linus Torvalds
2020-12-16 18:25 ` Mark Brown [this message]
2020-12-16 1:00 ` pr-tracker-bot
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=20201216182509.GD4861@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--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).