Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Jan Kara <jack@suse.cz>
Subject: Re: block for-next: zram build error
Date: Thu, 2 Feb 2017 16:56:50 -0700	[thread overview]
Message-ID: <57303c09-8bf3-3660-ca01-80d13fcca98c@fb.com> (raw)
In-Reply-To: <1486078839.2816.24.camel@sandisk.com>

On 02/02/2017 04:40 PM, Bart Van Assche wrote:
> Hello Jens,
> 
> I noticed accidentally that with the for-next branch of the block
> git repository that the zram driver doesn't build anymore:
> 
> 
> $ make M=drivers/block/zram
>   LD      drivers/block/zram/built-in.o
>   CC [M]  drivers/block/zram/zcomp.o
>   CC [M]  drivers/block/zram/zram_drv.o
> drivers/block/zram/zram_drv.c: In function ‘zram_revalidate_disk’:
> drivers/block/zram/zram_drv.c:120:37: error: ‘zram->disk->queue->backing_dev_info’ is a pointer; did you mean to use ‘->’?
>   zram->disk->queue->backing_dev_info.capabilities |=
>                                      ^
>                                      ->
> make[1]: *** [scripts/Makefile.build:294: drivers/block/zram/zram_drv.o] Error 1
> make: *** [Makefile:1490: _module_drivers/block/zram] Error 2
> 
> Compilation exited abnormally with code 2 at Thu Feb  2 15:37:19
> 
> 
> I have not yet tried to figure out which commit broke the build.

Thanks for catching that, Bart. I fixed it here after your report:

http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.11/next&id=e17354961bb50931ec7b33f59c0713dcf98ac7d2

It's caused by commit:

commit dc3b17cc8bf21307c7e076e7c778d5db756f7871
Author: Jan Kara <jack@suse.cz>
Date:   Thu Feb 2 15:56:50 2017 +0100

    block: Use pointer to backing_dev_info from request_queue

-- 
Jens Axboe


      reply	other threads:[~2017-02-02 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 23:40 block for-next: zram build error Bart Van Assche
2017-02-02 23:56 ` Jens Axboe [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=57303c09-8bf3-3660-ca01-80d13fcca98c@fb.com \
    --to=axboe@fb.com \
    --cc=Bart.VanAssche@sandisk.com \
    --cc=jack@suse.cz \
    --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