From: Thierry Reding <thierry.reding@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: linux-next: Add Tegra fixes branch
Date: Fri, 28 Aug 2026 16:28:41 +0200 [thread overview]
Message-ID: <apGZ3emy2duQxLri@orome> (raw)
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Hi Mark,
So far I've been carrying fixes patches as part of the regular for-next
branch, but I'm thinking of changing the process a little bit and having
a separate fixes branch that feeds into linux-next would be cleaner to
separate things.
Can you add this branch:
https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git#fixes
to linux-next, please?
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2026-08-28 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 14:28 Thierry Reding [this message]
2026-08-28 15:07 ` linux-next: Add Tegra fixes branch Mark Brown
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=apGZ3emy2duQxLri@orome \
--to=thierry.reding@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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