From: Takashi Iwai <tiwai@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 6.2-rc1 (#2)
Date: Sat, 24 Dec 2022 09:36:48 +0100 [thread overview]
Message-ID: <87tu1lxknz.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHk-=wgB054c1hX=2xco+S38cJQVZrj8ukSShLkM359THFQ2+Q@mail.gmail.com>
On Fri, 23 Dec 2022 20:20:50 +0100,
Linus Torvalds wrote:
>
> On Fri, Dec 23, 2022 at 2:41 AM Takashi Iwai <tiwai@suse.de> wrote:
> >
> > A few more updates for 6.2 since the last PR: most of changes are
> > about ASoC device-specific fixes.
> >
> > - Lots of ASoC Intel AVS extensions and refactoring
>
> Hmm. This doesn't exactly seem to be fixes.
>
> It does seem to have been in linux-next, so I don't hate it, but I'm
> not super-happy about the timing of this all.
>
> I really was hoping that the last few days of the merge window had
> been for actual fixes rather than for new development.
To be fair, those patches have been submitted and merged to ASoC
subtree already before the merge window opened, but it was slipped
from my first PR that was sent earlier due to my vacation, and now
they were caught in this second PR. So it'd be only me to be blamed
to submit a PR at a late date and not mention that.
In anyway, those should have been cooked enough long in linux-next,
so I don't think we need to worry too much.
thanks,
Takashi
next prev parent reply other threads:[~2022-12-24 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 10:40 Takashi Iwai
2022-12-23 19:20 ` Linus Torvalds
2022-12-24 8:36 ` Takashi Iwai [this message]
2022-12-23 19:23 ` 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=87tu1lxknz.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®