All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: Nikolay Borisov <nborisov@suse.com>,
	Josef Bacik <josef@toxicpanda.com>,
	"linux-btrfs @ vger . kernel . org" <linux-btrfs@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v6 3/7] btrfs: use the page-cache for super block reading
Date: Tue, 11 Feb 2020 19:03:51 +0000	[thread overview]
Message-ID: <SN4PR0401MB359858A1EE89A18DFDB0B3B19B180@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200211185312.GF2902@twin.jikos.cz

On 11/02/2020 19:53, David Sterba wrote:
> fs/btrfs/volumes.c: In function ‘btrfs_scratch_superblocks’:
> fs/btrfs/volumes.c:7338:3: warning: ignoring return value of ‘write_one_page’, declared with attribute warn_unused_result [-Wunused-result]
>   7338 |   write_one_page(page);
> 
Damn, fixing.

  reply	other threads:[~2020-02-11 19:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 18:32 [PATCH v6 0/7] btrfs: remove buffer heads form superblock handling Johannes Thumshirn
2020-02-10 18:32 ` [PATCH v6 1/7] btrfs: Export btrfs_release_disk_super Johannes Thumshirn
2020-02-10 18:32 ` [PATCH v6 2/7] btrfs: don't kmap() pages from block devices Johannes Thumshirn
2020-02-10 18:32 ` [PATCH v6 3/7] btrfs: use the page-cache for super block reading Johannes Thumshirn
2020-02-11 18:53   ` David Sterba
2020-02-11 19:03     ` Johannes Thumshirn [this message]
2020-02-10 18:32 ` [PATCH v6 4/7] btrfs: use BIOs instead of buffer_heads from superblock writeout Johannes Thumshirn
2020-02-10 18:32 ` [PATCH v6 5/7] btrfs: remove btrfsic_submit_bh() Johannes Thumshirn
2020-02-10 18:32 ` [PATCH v6 6/7] btrfs: remove buffer_heads from btrfsic_process_written_block() Johannes Thumshirn
2020-02-10 18:32 ` [PATCH v6 7/7] btrfs: remove buffer_heads form superblock mirror integrity checking Johannes Thumshirn

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=SN4PR0401MB359858A1EE89A18DFDB0B3B19B180@SN4PR0401MB3598.namprd04.prod.outlook.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=dsterba@suse.cz \
    --cc=hch@lst.de \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.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 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.