From: Luben Tuikov <luben.tuikov@amd.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/3] Use implicit kref infra
Date: Wed, 2 Sep 2020 15:04:05 -0400 [thread overview]
Message-ID: <fc9b026c-e7d8-3cf6-92e8-7ef0c389e36c@amd.com> (raw)
In-Reply-To: <CAPj87rMKNZfP1=kfsHPbRaJtHMAEKY+87p6uTAt=Hh76FwZVcw@mail.gmail.com>
On 2020-09-02 11:51 a.m., Daniel Stone wrote:
> Hi Luben,
>
> On Wed, 2 Sep 2020 at 16:16, Luben Tuikov <luben.tuikov@amd.com> wrote:
>> Not sure how I can do this when someone doesn't want to read up on
>> the kref infrastructure. Can you help?
>>
>> When someone starts off with "My understanding of ..." (as in the OP) you know you're
>> in trouble and in for a rough times.
>>
>> Such is the nature of world-wide open-to-everyone mailing lists where
>> anyone can put forth an argument, regardless of their level of understanding.
>> The more obfuscated an argument, the more uncertainty.
>>
>> If one knows the kref infrastructure, it just clicks, no explanation
>> necessary.
>
> Evidently there are more points of view than yours. Evidently your
> method of persuasion is also not working, because this thread is now
> getting quite long and not converging on your point of view (which you
> are holding to be absolutely objectively correct).
>
> I think you need to re-evaluate the way in which you speak to people,
> considering that it costs nothing to be polite and considerate, and
> also takes effort to be rude and dismissive.
Not sure how to help this:
> My understanding of the drm core code is like something below.
> struct B {
> strcut A
> }
> we initialize A firstly and initialize B in the end. But destroy B firstly and destory A in the end.
Regards,
Luben
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-09-02 19:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 1:06 [PATCH 0/3] Use implicit kref infra Luben Tuikov
2020-09-02 1:06 ` [PATCH 1/3] drm: No warn for drivers who provide release Luben Tuikov
2020-09-02 1:06 ` [PATCH 2/3] drm/amdgpu: Remove drmm final free Luben Tuikov
2020-09-02 1:06 ` [PATCH 3/3] drm/amdgpu: Remove superfluous NULL check Luben Tuikov
2020-09-02 6:59 ` Daniel Vetter
2020-09-02 7:21 ` Christian König
2020-09-02 1:42 ` [PATCH 0/3] Use implicit kref infra Pan, Xinhui
2020-09-02 3:46 ` Luben Tuikov
2020-09-02 4:43 ` Pan, Xinhui
2020-09-02 14:50 ` Luben Tuikov
2020-09-02 15:00 ` Daniel Stone
2020-09-02 15:16 ` Luben Tuikov
2020-09-02 15:51 ` Daniel Stone
2020-09-02 19:04 ` Luben Tuikov [this message]
2020-09-02 19:16 ` Alex Deucher
2020-09-02 19:55 ` Daniel Vetter
2020-09-02 19:59 ` Daniel Vetter
2020-09-03 1:57 ` Pan, Xinhui
2020-09-03 18:52 ` Luben Tuikov
2020-09-02 6:52 ` Daniel Vetter
2020-09-02 14:59 ` Luben Tuikov
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=fc9b026c-e7d8-3cf6-92e8-7ef0c389e36c@amd.com \
--to=luben.tuikov@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.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