From: pr-tracker-bot@kernel.org
To: Tyler Hicks <code@tyhicks.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: Re: [GIT PULL] eCryptfs updates for 7.2-rc1
Date: Fri, 26 Jun 2026 15:45:37 +0000 [thread overview]
Message-ID: <178248873773.1001923.6407573170334196525.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <aj3p8nYWZPTbkUWW@yaupon>
The pull request you sent on Thu, 25 Jun 2026 21:54:42 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-7.2-rc1-updates
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c292ea294dde77ae442d3d764f53c251d2d6df90
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2026-06-26 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 2:54 [GIT PULL] eCryptfs updates for 7.2-rc1 Tyler Hicks
2026-06-26 15:45 ` pr-tracker-bot [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=178248873773.1001923.6407573170334196525.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=brauner@kernel.org \
--cc=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox