From: "Theodore Ts'o" <tytso@mit.edu>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: Re: SPDX tag and top of file comment cleanups for the loop driver
Date: Tue, 10 May 2022 09:58:52 -0400 [thread overview]
Message-ID: <YnpvnMk+1jd7fq0z@mit.edu> (raw)
In-Reply-To: <c393d0dd-05a9-2a12-92a2-eebd8d49c2dd@kernel.dk>
On Tue, May 10, 2022 at 06:29:52AM -0600, Jens Axboe wrote:
> On 5/10/22 1:22 AM, Christoph Hellwig wrote:
> > Jens,
> >
> > are the comments from Ted here enough to apply the series? Or do
> > we need a formal Acked-by to be on the safe side?
>
> Looks conclusive enough to me - if not, Ted, please holler. I'll
> queue it up.
Sounds good, thanks so much Jens!
- Ted
prev parent reply other threads:[~2022-05-10 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 6:32 SPDX tag and top of file comment cleanups for the loop driver Christoph Hellwig
2022-04-19 6:33 ` [PATCH 1/4] loop: remove loop.h Christoph Hellwig
2022-04-19 22:32 ` Chaitanya Kulkarni
2022-05-10 12:30 ` Jens Axboe
2022-04-19 6:33 ` [PATCH 2/4] loop: add a SPDX header Christoph Hellwig
2022-04-19 6:33 ` [PATCH 3/4] loop: remove most the top-of-file boilerplate comment Christoph Hellwig
2022-04-19 22:33 ` Chaitanya Kulkarni
2022-04-19 6:33 ` [PATCH 4/4] loop: remove most the top-of-file boilerplate comment from the UAPI header Christoph Hellwig
2022-05-03 20:06 ` SPDX tag and top of file comment cleanups for the loop driver Theodore Ts'o
2022-05-03 20:13 ` Christoph Hellwig
2022-05-03 21:35 ` tytso
2022-05-10 7:22 ` Christoph Hellwig
2022-05-10 12:29 ` Jens Axboe
2022-05-10 13:58 ` Theodore Ts'o [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=YnpvnMk+1jd7fq0z@mit.edu \
--to=tytso@mit.edu \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-spdx@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).