From: Christoph Hellwig <hch@lst.de>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: fix indention for dma-buf checks
Date: Fri, 16 Oct 2026 11:29:33 +0200 [thread overview]
Message-ID: <20261016092933.GE23141@lst.de> (raw)
In-Reply-To: <be2b6881-75bd-4113-bfcf-c3ac9ed2b80c@gmail.com>
On Fri, Oct 16, 2026 at 10:22:37AM +0100, Pavel Begunkov wrote:
> On 10/16/26 10:20, Pavel Begunkov wrote:
>> There is a weird indention I botched while rebasing, fix it.
>>
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
>
> Can be squashed into the following commit, if that's preferred.
Either way looks fine, but I guess Jens doesn't really want to rebase
this late in the cycle..
next prev parent reply other threads:[~2026-10-16 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:20 [PATCH] block: fix indention for dma-buf checks Pavel Begunkov
2026-10-16 9:22 ` Pavel Begunkov
2026-10-16 9:29 ` Christoph Hellwig [this message]
2026-10-16 10:01 ` Pavel Begunkov
2026-10-16 14:28 ` Jens Axboe
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=20261016092933.GE23141@lst.de \
--to=hch@lst.de \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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