mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chunhai Guo <guochunhai@vivo.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
	"chao@kernel.org" <chao@kernel.org>,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] block: export symbol blk_flush_plug
Date: Mon, 4 Sep 2023 16:10:18 +0800	[thread overview]
Message-ID: <86605698-bc85-42b5-b7e9-2da547ec1d4f@vivo.com> (raw)
In-Reply-To: <ZPWImKGXZbz6HUJs@infradead.org>



在 2023/9/4 15:34, Christoph Hellwig 写道:
> [????????? hch@infradead.org ????????? https://aka.ms/LearnAboutSenderIdentification?????????????]
> 
> On Mon, Sep 04, 2023 at 03:24:10PM +0800, Chunhai Guo wrote:
>> Could you please detail why blk_flush_plug() can not be used by a file
>> system?
> 
> Can you detail why it is a good idea to use it?  Beause you nee to make
> the argument why something should be exported.

Hi Christoph,
Got it. This could be a topic too big to discuss here.
Thanks.



Hi Jaegeuk,
As per Christoph's suggestion, could you please assist with reverting 
the commit e1e9b8062c74 ("f2fs: replace blk_finish_plug() with 
blk_flush_plug()")?
Thanks.

      reply	other threads:[~2023-09-04  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  4:22 Chunhai Guo
2023-09-04  6:15 ` Christoph Hellwig
2023-09-04  7:24   ` Chunhai Guo
2023-09-04  7:34     ` Christoph Hellwig
2023-09-04  8:10       ` Chunhai Guo [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=86605698-bc85-42b5-b7e9-2da547ec1d4f@vivo.com \
    --to=guochunhai@vivo.com \
    --cc=axboe@kernel.dk \
    --cc=chao@kernel.org \
    --cc=hch@infradead.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    /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
all inboxes | Powered by JetHome®