From: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
To: airlied@redhat.com
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>
Subject: [PATCH] BRANCH_MARKER: work
Date: Mon, 16 Jan 2023 11:06:11 +0100 [thread overview]
Message-ID: <20230116100611.12712-2-jirislaby@kernel.org> (raw)
In-Reply-To: <20230116100611.12712-1-jirislaby@kernel.org>
From: Jiri Slaby <jslaby@suse.cz>
---
branch/work | 1 +
1 file changed, 1 insertion(+)
create mode 100644 branch/work
diff --git a/branch/work b/branch/work
new file mode 100644
index 000000000000..587be6b4c3f9
--- /dev/null
+++ b/branch/work
@@ -0,0 +1 @@
+x
--
2.39.0
next prev parent reply other threads:[~2023-01-16 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 10:06 [PATCH -resend] drm/nouveau/kms/nv50- (gcc13): fix nv50_wndw_new_ prototype Jiri Slaby (SUSE)
2023-01-16 10:06 ` Jiri Slaby (SUSE) [this message]
2023-01-16 10:07 ` [PATCH] BRANCH_MARKER: work Jiri Slaby
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=20230116100611.12712-2-jirislaby@kernel.org \
--to=jirislaby@kernel.org \
--cc=airlied@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@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