From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL for v6.6] super fixes
Date: Fri, 1 Sep 2023 15:08:33 +0200 [thread overview]
Message-ID: <20230901-thank-you-7902fd09539c@brauner> (raw)
In-Reply-To: <169352176330.24475.9732725297267621963.pr-tracker-bot@kernel.org>
Thanks to both of you for helping with reviewing and fixing the
immediate remaining issues. Much appreciated.
next prev parent reply other threads:[~2023-09-01 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 11:04 [GIT PULL for v6.6] super fixes Christian Brauner
2023-08-31 22:42 ` pr-tracker-bot
2023-09-01 13:08 ` Christian Brauner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 10:51 Christian Brauner
2023-08-29 19:36 ` 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=20230901-thank-you-7902fd09539c@brauner \
--to=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).