From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Minsuk Kang <linuxlovemin@yonsei.ac.kr>, netdev@vger.kernel.org
Cc: linma@zju.edu.cn, davem@davemloft.net, sameo@linux.intel.com,
dokyungs@yonsei.ac.kr, jisoo.jang@yonsei.ac.kr
Subject: Re: [PATCH net] nfc: pn533: Clear nfc_target in pn533_poll_dep_complete() before being used
Date: Tue, 13 Dec 2022 15:40:22 +0100 [thread overview]
Message-ID: <6149eb8e-74dc-46bd-029f-309c4224a005@linaro.org> (raw)
In-Reply-To: <20221213142053.GA107908@medve-MS-7D32>
On 13/12/2022 15:20, Minsuk Kang wrote:
>
>>> ==================================================================
>>>
>>> Fixes: 673088fb42d0 ("NFC: pn533: Send ATR_REQ directly for active device detection")
>>> Reported-by: Dokyung Song <dokyungs@yonsei.ac.kr>
>>> Reported-by: Jisoo Jang <jisoo.jang@yonsei.ac.kr>
>>> Reported-by: Minsuk Kang <linuxlovemin@yonsei.ac.kr>
>>
>> Reported-by is for crediting other people, not crediting yourself.
>> Otherwise all my patches would be reported-by, right? Please drop this
>> one and keep only credit for other people who actually reported it. It's
>> anyway weird to see three people reporting one bug.
>>
>> Additionally I really dislike private reports because they sometimes
>> cannot be trusted (see all the fake report credits from running
>> coccinelle by Hulk Robot and others)... Care to provide link to the
>> reports of this bug?
>>
>
> My intention was to credit all the people contributed to the
> modification of syzkaller that led to this bug. But I will drop them in
> v2.
Then shouldn't you also credit all authors of original syzkaller as
well? And people who wrote core libraries being used there? Let's don't
go that way...
Best regards,
Krzysztof
prev parent reply other threads:[~2022-12-13 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 1:41 [PATCH net] nfc: pn533: Clear nfc_target in pn533_poll_dep_complete() before being used Minsuk Kang
2022-12-13 10:45 ` Krzysztof Kozlowski
2022-12-13 14:20 ` Minsuk Kang
2022-12-13 14:40 ` Krzysztof Kozlowski [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=6149eb8e-74dc-46bd-029f-309c4224a005@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=davem@davemloft.net \
--cc=dokyungs@yonsei.ac.kr \
--cc=jisoo.jang@yonsei.ac.kr \
--cc=linma@zju.edu.cn \
--cc=linuxlovemin@yonsei.ac.kr \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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