From: pr-tracker-bot@kernel.org
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] drm-fixes for 6.3-rc5
Date: Thu, 30 Mar 2023 21:11:03 +0000 [thread overview]
Message-ID: <168021066309.12065.2646138721732559028.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <ZCXnVLzzdzt4xX7E@phenom.ffwll.local>
The pull request you sent on Thu, 30 Mar 2023 21:47:32 +0200:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2023-03-30
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0d3ff8087b2c12ee012c547f3bde46a3f60d6f6f
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
WARNING: multiple messages have this Message-ID (diff)
From: pr-tracker-bot@kernel.org
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] drm-fixes for 6.3-rc5
Date: Thu, 30 Mar 2023 21:11:03 +0000 [thread overview]
Message-ID: <168021066309.12065.2646138721732559028.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <ZCXnVLzzdzt4xX7E@phenom.ffwll.local>
The pull request you sent on Thu, 30 Mar 2023 21:47:32 +0200:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2023-03-30
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0d3ff8087b2c12ee012c547f3bde46a3f60d6f6f
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
next prev parent reply other threads:[~2023-03-30 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 19:47 [PULL] drm-fixes for 6.3-rc5 Daniel Vetter
2023-03-30 19:47 ` Daniel Vetter
2023-03-30 21:11 ` pr-tracker-bot [this message]
2023-03-30 21:11 ` pr-tracker-bot
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=168021066309.12065.2646138721732559028.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.