From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] ASoC fixes for v6.5-rc1-2
Date: Thu, 20 Jul 2023 16:31:37 +0200 [thread overview]
Message-ID: <87sf9iirhy.wl-tiwai@suse.de> (raw)
In-Reply-To: <3cda87c3-f502-4034-99a5-394c8e4195cc@sirena.org.uk>
On Thu, 20 Jul 2023 16:07:06 +0200,
Mark Brown wrote:
>
> On Thu, Jul 20, 2023 at 03:20:17PM +0200, Takashi Iwai wrote:
> > On Thu, 20 Jul 2023 15:05:08 +0200,
>
> > The shortlog is confusing as if this contains so many changes,
> > although it's basically only three no-merge commits.
>
> It got confused since I sent you an earlier pull request that hasn't
> gone to Linus yet - not sure what the best way of handling that is, just
> using your branch as the base blows up badly if I merge Linus' tree to
> get platform fixes.
It's no big problem, but it'd be helpful if you can tell me that for
avoiding a surprise at the next time.
thanks,
Takashi
prev parent reply other threads:[~2023-07-20 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 13:05 [GIT PULL] ASoC fixes for v6.5-rc1-2 Mark Brown
2023-07-20 13:20 ` Takashi Iwai
2023-07-20 14:07 ` Mark Brown
2023-07-20 14:31 ` Takashi Iwai [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=87sf9iirhy.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
/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