All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 6/8] block: mark __bio_try_merge_page static
Date: Wed, 13 Oct 2021 04:21:09 +0000	[thread overview]
Message-ID: <f412c54b-a6b1-096d-ddf4-40e576c40baa@nvidia.com> (raw)
In-Reply-To: <20211012161804.991559-7-hch@lst.de>

On 10/12/2021 9:18 AM, Christoph Hellwig wrote:
> Mark __bio_try_merge_page static and move it up a bit to avoid the need
> for a forward declaration.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>



  reply	other threads:[~2021-10-13  4:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 16:17 decruft bio.h Christoph Hellwig
2021-10-12 16:17 ` [PATCH 1/8] block: remove BIO_BUG_ON Christoph Hellwig
2021-10-13  4:19   ` Chaitanya Kulkarni
2021-10-12 16:17 ` [PATCH 2/8] block: don't include <linux/ioprio.h> in <linux/bio.h> Christoph Hellwig
2021-10-13  4:19   ` Chaitanya Kulkarni
2021-10-12 16:17 ` [PATCH 3/8] block: move bio_mergeable out of bio.h Christoph Hellwig
2021-10-13  4:20   ` Chaitanya Kulkarni
2021-10-12 16:18 ` [PATCH 4/8] block: fold bio_cur_bytes into blk_rq_cur_bytes Christoph Hellwig
2021-10-13  4:20   ` Chaitanya Kulkarni
2021-10-12 16:18 ` [PATCH 5/8] block: move bio_full out of bio.h Christoph Hellwig
2021-10-13  4:20   ` Chaitanya Kulkarni
2021-10-12 16:18 ` [PATCH 6/8] block: mark __bio_try_merge_page static Christoph Hellwig
2021-10-13  4:21   ` Chaitanya Kulkarni [this message]
2021-10-12 16:18 ` [PATCH 7/8] block: move bio_get_{first,last}_bvec out of bio.h Christoph Hellwig
2021-10-13  4:21   ` Chaitanya Kulkarni
2021-10-12 16:18 ` [PATCH 8/8] block: mark bio_truncate static Christoph Hellwig
2021-10-13  4:22   ` Chaitanya Kulkarni
2021-10-12 19:47 ` decruft bio.h 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=f412c54b-a6b1-096d-ddf4-40e576c40baa@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --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 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.