From: "Christian König" <christian.koenig@amd.com>
To: Arnd Bergmann <arnd@arndb.de>, "kernelci.org bot" <bot@kernelci.org>
Cc: Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Hellstrom <thellstrom@vmware.com>,
Dave Airlie <airlied@redhat.com>, Roger He <Hongbo.He@amd.com>,
Maarten Lankhorst <maarten.lankhorst@canonical.com>,
Francisco Jerez <currojerez@riseup.net>,
Viresh Kumar <vireshk@kernel.org>,
Shiraz Hashim <shiraz.linux.kernel@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: next/master build: 198 builds: 1 failed, 197 passed, 1 error, 148 warnings (next-20180110)
Date: Wed, 10 Jan 2018 16:54:22 +0100 [thread overview]
Message-ID: <7558007d-3699-f456-7ddf-2f96339a7f98@amd.com> (raw)
In-Reply-To: <CAK8P3a0WzGpB1sPLzEYHYO7r8zPSXeroq7fKYptdRzC1Sxck3Q@mail.gmail.com>
Hi Arnd,
Am 10.01.2018 um 16:45 schrieb Arnd Bergmann:
>> 14 drivers/gpu/drm/ttm/ttm_page_alloc_dma.c:1186:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result [-Wunused-result]
>> 14 drivers/gpu/drm/ttm/ttm_page_alloc.c:485:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result [-Wunused-result]
> ttm and kvm are now the last user of register_shrinker that doesn't
> propagate the return code to its
> caller, all other callers got fixed in one way or another.
>
> I tried to fix this one too, but couldn't come up with a proper way of
> unwinding both
> kobject_init_and_add() and ttm_pool_mm_shrink_init():
>
> ret = kobject_init_and_add(&_manager->kobj, &ttm_pool_kobj_type,
> &glob->kobj, "pool");
> if (unlikely(ret != 0)) {
> kobject_put(&_manager->kobj);
> _manager = NULL;
> return ret;
> }
>
> ttm_pool_mm_shrink_init(_manager);
>
> Calling kobject_put() after a failed kobject_init_and_add() seemed wrong,
> and it also appears to be missing a kfree(), so I didn't want to mess it
> up any further. Added a few people to Cc that touched this file most,
> maybe one of them can have a look, or they already have a patch waiting
> to get merged.
That isn't urgent, isn't it? So I would say I put it on my TODO list and
I'm going to take care of it no later than 4.17.
Otherwise Roger or me could take a look tomorrow.
Regards,
Christian.
next prev parent reply other threads:[~2018-01-10 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a55b9ce.0e8d500a.edcf8.3a08@mx.google.com>
2018-01-10 15:45 ` Arnd Bergmann
2018-01-10 15:54 ` Christian König [this message]
2018-01-10 16:18 ` Arnd Bergmann
2018-01-11 5:59 ` Viresh Kumar
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=7558007d-3699-f456-7ddf-2f96339a7f98@amd.com \
--to=christian.koenig@amd.com \
--cc=Hongbo.He@amd.com \
--cc=airlied@redhat.com \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=currojerez@riseup.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=shiraz.linux.kernel@gmail.com \
--cc=thellstrom@vmware.com \
--cc=vireshk@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®