From: Christoph Hellwig <hch@lst.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: hch@lst.de, xen-devel@lists.xenproject.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [bug report] x86/xen: open code alloc_vm_area in arch_gnttab_valloc
Date: Thu, 24 Sep 2020 12:10:13 +0200 [thread overview]
Message-ID: <20200924101013.GA21907@lst.de> (raw)
In-Reply-To: <20200924085044.GA1569000@mwanda>
On Thu, Sep 24, 2020 at 11:50:44AM +0300, Dan Carpenter wrote:
> Hello Christoph Hellwig,
>
> The patch a0e7ac6b4907: "x86/xen: open code alloc_vm_area in
> arch_gnttab_valloc" from Sep 23, 2020, leads to the following static
> checker warning:
>
> arch/x86/xen/grant-table.c:110 arch_gnttab_valloc()
> warn: did you mean to pass the address of 'area->ptes'
This has been fixed up an done a bit differently in the current
version:
http://git.infradead.org/users/hch/misc.git/commitdiff/a44f0087ead305bc91cac704b99cbf27b4cca92a
prev parent reply other threads:[~2020-09-24 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 8:50 [bug report] x86/xen: open code alloc_vm_area in arch_gnttab_valloc Dan Carpenter
2020-09-24 10:10 ` Christoph Hellwig [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=20200924101013.GA21907@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-mm@kvack.org \
--cc=xen-devel@lists.xenproject.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.