From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the sound-asoc tree
Date: Mon, 24 Mar 2025 16:24:05 +0000 [thread overview]
Message-ID: <Z+GHJcUpHnttzIqD@opensource.cirrus.com> (raw)
In-Reply-To: <Z-FlYC2Rg7eX1qxw@finisterre.sirena.org.uk>
On Mon, Mar 24, 2025 at 02:00:00PM +0000, Mark Brown wrote:
> On Mon, Mar 24, 2025 at 09:18:23AM +0000, Charles Keepax wrote:
>
> > Bit weird, not sure if Mark is in the middle of re-ordering his
> > tree or if a script has gone a bit off the rails there. Looks
> > like it had the right SHA when I sent the patch up but it go
> > changed as the patch was applied.
>
> I don't rebase so it'd be very suprising if anything got changed in my
> tree, I'd expect to remember if that had happened.
Super weird, I mean I guess its merged now so there probably
isn't much action to take but really unsure what has happened.
Thanks,
Charles
next prev parent reply other threads:[~2025-03-24 16:24 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 10:29 linux-next: Fixes tag needs some work in the sound-asoc tree Stephen Rothwell
2025-03-24 9:18 ` Charles Keepax
2025-03-24 14:00 ` Mark Brown
2025-03-24 16:24 ` Charles Keepax [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-07 23:58 Stephen Rothwell
2023-11-13 20:58 Stephen Rothwell
2023-09-28 21:41 Stephen Rothwell
2022-07-19 22:22 Stephen Rothwell
2022-05-17 22:01 Stephen Rothwell
2022-04-28 0:57 Stephen Rothwell
2022-04-28 3:04 ` Tinghan Shen
2022-03-08 21:32 Stephen Rothwell
2022-03-02 21:01 Stephen Rothwell
2021-12-01 21:25 Stephen Rothwell
2021-12-02 9:29 ` Charles Keepax
2021-06-14 22:11 Stephen Rothwell
2021-05-12 22:40 Stephen Rothwell
2021-04-14 22:01 Stephen Rothwell
2020-07-29 22:04 Stephen Rothwell
2020-04-06 21:49 Stephen Rothwell
2020-03-29 0:09 Stephen Rothwell
2020-03-14 10:50 Stephen Rothwell
2020-03-16 8:21 ` Kai Vehmanen
2020-03-01 5:45 Stephen Rothwell
2020-02-24 22:30 Stephen Rothwell
2019-10-15 11:30 Stephen Rothwell
2019-10-15 11:35 ` Peter Ujfalusi
2019-08-20 22:25 Stephen Rothwell
2019-08-20 21:04 Stephen Rothwell
2019-08-20 22:27 ` Stephen Rothwell
2019-08-15 21:59 Stephen Rothwell
2019-08-15 21:34 Stephen Rothwell
2019-07-25 21:27 Stephen Rothwell
2019-07-26 6:04 ` Peter Ujfalusi
2019-07-26 12:11 ` Mark Brown
2019-07-29 5:57 ` Peter Ujfalusi
2019-07-10 16:13 Stephen Rothwell
2019-07-11 0:40 ` Tzung-Bi Shih
2019-06-30 21:49 Stephen Rothwell
2019-06-26 13:42 Stephen Rothwell
2019-05-30 22:02 Stephen Rothwell
2019-05-21 21:31 Stephen Rothwell
2019-05-17 11:12 Stephen Rothwell
2019-05-17 2:41 S.j. Wang
2019-05-16 22:34 Stephen Rothwell
2019-03-18 11:18 Stephen Rothwell
2019-03-17 1:34 Stephen Rothwell
[not found] <CGME20190317012907epcas3p129240b3dcef7d974c2fea23c26a76f2a@epcas3p1.samsung.com>
2019-03-17 1:28 ` Stephen Rothwell
2019-03-18 10:08 ` Sylwester Nawrocki
2019-01-28 20:27 Stephen Rothwell
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=Z+GHJcUpHnttzIqD@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.