From: John Hubbard <jhubbard@nvidia.com>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: Anders Roxell <anders.roxell@linaro.org>, <bmt@zurich.ibm.com>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] rdma: siw: remove unused variable
Date: Mon, 29 Jul 2019 13:14:59 -0700 [thread overview]
Message-ID: <f7500581-c3df-a0cb-8229-b832f12fcf05@nvidia.com> (raw)
In-Reply-To: <b5775622b2e8360e77f90dddfff9aa84af48240e.camel@redhat.com>
On 7/29/19 12:45 PM, Doug Ledford wrote:
> On Mon, 2019-07-29 at 16:03 -0300, Jason Gunthorpe wrote:
>> On Mon, Jul 29, 2019 at 02:19:35PM -0400, Doug Ledford wrote:
>>> On Fri, 2019-07-26 at 11:25 +0200, Anders Roxell wrote:
>>>> The variable 'p' si no longer used and the compiler rightly
>>>> complains
>>>> that it should be removed.
>>>>
>>>> ../drivers/infiniband/sw/siw/siw_mem.c: In function
>>>> ‘siw_free_plist’:
>>>> ../drivers/infiniband/sw/siw/siw_mem.c:66:16: warning: unused
>>>> variable
>>>> ‘p’ [-Wunused-variable]
>>>> struct page **p = chunk->plist;
>>>> ^
>>>>
>>>> Rework to remove unused variable.
>>>>
>>>> Fixes: 8288d030447f ("mm/gup: add make_dirty arg to
>>>> put_user_pages_dirty_lock()")
>>>
>>> This commit hash and the commit subject does not exist in Linus'
>>> tree as
>>> of today. What tree is this being merged through, and is it slated
>>> to
>>> merge soon or is this a for-next item?
>>
>> This is though -mm, maybe John knows what is what
>
> Hmmm...if it's through -mm, doesn't that mean that we can't rely on the
> hash because the next time Andrew's tree rebases (using quilt or
> whatever it is he does) that the hash will change? It doesn't really
> matter too much...we can't take the fix anyway, it should probably be
> squashed into the patch that it's fixing, and if you follow Bernard's
> advice, you fix the problem by eliminating this function and changing
> the sole call site to just call put_user_pages_dirty_lock() directly.
>
Hi,
Although I don't know which tree has 8288d030447f, I did get a report
from linux-next last night with that report about the warning, and so
I believe that the patch flowed from Andrew's -mm tree (which has
speculatively added my patches), to linux-next
(+CC Andrew)
I also sent out a fix for it, as a reply-to the warning report:
https://lore.kernel.org/r/20190729074306.10368-1-jhubbard@nvidia.com
Pasting in my response (minus the trivial fix), to save you a click:
"This fixes the warning. Ideally this should be merged with the commit
that it fixes, if that's still possible.
"Andrew, would you also like a fixed version of this patch posted
as a new version of the 3-patch set that it came with?"
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2019-07-29 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 9:25 Anders Roxell
2019-07-26 16:06 ` Bernard Metzler
2019-07-29 18:19 ` Doug Ledford
2019-07-29 19:03 ` Jason Gunthorpe
2019-07-29 19:45 ` Doug Ledford
2019-07-29 20:14 ` John Hubbard [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=f7500581-c3df-a0cb-8229-b832f12fcf05@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=bmt@zurich.ibm.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@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®