mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yuehaibing <yuehaibing@huawei.com>
To: David Howells <dhowells@redhat.com>
Cc: <jannh@google.com>, <axboe@kernel.dk>,
	<james.morris@microsoft.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] misc: watch_queue: Fix build error
Date: Tue, 8 Oct 2019 14:43:17 +0800	[thread overview]
Message-ID: <5f6acfef-2eda-e33a-f7cb-37f3735e60a0@huawei.com> (raw)
In-Reply-To: <32674.1567599622@warthog.procyon.org.uk>

On 2019/9/4 20:20, David Howells wrote:
> Thanks, I've folded that in.

This issue still occur in linux-next 20191008 :

drivers/misc/watch_queue.c: In function ‘watch_queue_account_mem’:
drivers/misc/watch_queue.c:315:38: error: ‘struct user_struct’ has no member named ‘locked_vm’; did you mean ‘locked_shm’?
  cur_pages = atomic_long_read(&user->locked_vm);
                                      ^~~~~~~~~
                                      locked_shm
drivers/misc/watch_queue.c:321:50: error: ‘struct user_struct’ has no member named ‘locked_vm’; did you mean ‘locked_shm’?
  } while (atomic_long_try_cmpxchg_relaxed(&user->locked_vm, &cur_pages,
                                                  ^~~~~~~~~
                                                  locked_shm
drivers/misc/watch_queue.c: In function ‘watch_queue_unaccount_mem’:
drivers/misc/watch_queue.c:333:44: error: ‘struct user_struct’ has no member named ‘locked_vm’; did you mean ‘locked_shm’?
   atomic_long_sub(wqueue->nr_pages, &user->locked_vm);
                                            ^~~~~~~~~
                                            locked_shm
scripts/Makefile.build:265: recipe for target 'drivers/misc/watch_queue.o' failed

> 
> David
> 
> .
> 


      reply	other threads:[~2019-10-08  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  7:37 YueHaibing
2019-09-04 12:20 ` David Howells
2019-10-08  6:43   ` Yuehaibing [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=5f6acfef-2eda-e33a-f7cb-37f3735e60a0@huawei.com \
    --to=yuehaibing@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=dhowells@redhat.com \
    --cc=james.morris@microsoft.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®