From: Stephen Boyd <sboyd@kernel•org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora•com>,
"Stephen Rothwell" <sfr@canb•auug.org.au>
Cc: linux-kernel@vger•kernel.org, kernel@collabora•com,
linux-next@vger•kernel.org
Subject: Re: Adding SPMI tree to linux-next
Date: Wed, 06 Dec 2023 15:59:47 -0800 [thread overview]
Message-ID: <87b4577efc5e0e0baf4fcc52d47404a6.sboyd@kernel.org> (raw)
In-Reply-To: <facc6759-b222-4912-9d78-deebecc977db@notapiano>
Quoting Nícolas F. R. A. Prado (2023-11-29 13:49:21)
> Hi Stephen,
>
> I've noticed your spmi-next [1] branch is not currently tracked by linux-next
> [2]. Could you please consider adding it?
I tried[3] but it didn't get added. Maybe it will work this time?
>
> There's a machine (MT8195 Tomato Chromebook) that relies on a fix from that
> branch to reliably boot, and since the machine is hooked up to KernelCI to run
> tests on top of linux-next, having the fix integrated into next would make the
> test results more useful, the machine's current upstream support easily
> verifiable and regressions detectable.
>
> Thanks,
> Nícolas
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git/log/?h=spmi-next
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/diff/Next/Trees
[3] https://lore.kernel.org/r/fb12cab33d27c582125a22390e9c3b12.sboyd@kernel.org/
next parent reply other threads:[~2023-12-06 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <facc6759-b222-4912-9d78-deebecc977db@notapiano>
2023-12-06 23:59 ` Stephen Boyd [this message]
2023-12-07 2:17 ` Adding SPMI tree to linux-next 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=87b4577efc5e0e0baf4fcc52d47404a6.sboyd@kernel.org \
--to=sboyd@kernel$(echo .)org \
--cc=kernel@collabora$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nfraprado@collabora$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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