From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thierry Reding <treding@nvidia.com>
Cc: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the tegra tree
Date: Fri, 30 Jun 2023 22:36:01 +1000 [thread overview]
Message-ID: <20230630223601.370a228d@canb.auug.org.au> (raw)
In-Reply-To: <ZJ65XCYh3cr2OMLM@orome>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi Thierry,
On Fri, 30 Jun 2023 13:15:40 +0200 Thierry Reding <treding@nvidia.com> wrote:
> Stephen, do you want me to force-push an old version of the dt-bindings
> stuff to my for-next branch, or is it okay if I just push out an update
> after v6.5-rc1?
Up to you, I just send these in case you accidentally rebased after
having your branch merged by your upstream.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-06-30 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:47 linux-next: duplicate patches in the tegra tree Stephen Rothwell
2023-06-30 11:15 ` Thierry Reding
2023-06-30 12:36 ` Stephen Rothwell [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=20230630223601.370a228d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ccross@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=treding@nvidia.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