From: Kalle Valo <kvalo@codeaurora.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Jakub Kicinski <kubakici@wp.pl>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mt7601u: make write with mask access atomic
Date: Wed, 28 Feb 2018 17:07:33 +0200 [thread overview]
Message-ID: <87vaehqhje.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAJ0CqmU6w9k_3ZZwHiB5eLZ_4H_8OqS-P58Uwbioa4qe4xhM2A@mail.gmail.com> (Lorenzo Bianconi's message of "Wed, 28 Feb 2018 16:04:58 +0100")
Lorenzo Bianconi <lorenzo.bianconi@redhat.com> writes:
>> Lorenzo Bianconi <lorenzo.bianconi@redhat.com> writes:
>>
>>>> On Thu, 15 Feb 2018 23:59:24 +0100, Lorenzo Bianconi wrote:
>>>>> Introduce __mt7601u_rr and __mt7601u_vendor_single_wr routines in order
>>>>> to make mt7601u_rmw and mt7601u_rmc atomic since it is possible that
>>>>> read and write accesses of mt7601u_rmw/mt7601u_rmc can be interleaved
>>>>> with a different write operation on the same register.
>>>>> Moreover move write trace point in __mt7601u_vendor_single_wr
>>>>>
>>>>> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
>>>>
>>>> Could you provide an example of which accesses make it problematic?
>>>> Is this fixing an actual bug?
>>>
>>> it is not an issue I had experimented, I noticed a theoretical race
>>> reviewing the code.
>>
>> The commit log should always answer the question "Why?". If you find a
>> theoretical issue in the code document that clearly in the commit log.
>> That helps to choose correct tree and sending to stable releases etc.
>>
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#commit_log_does_not_answer_why
>
> I have already sent a v2: https://patchwork.kernel.org/patch/10225849/
> Is the commit message ok?
Yeah, I already applied it.
--
Kalle Valo
prev parent reply other threads:[~2018-02-28 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1518734856.git.lorenzo.bianconi@redhat.com>
2018-02-15 22:59 ` [PATCH] mt7601u: make write with mask access atomic Lorenzo Bianconi
2018-02-15 23:14 ` Jakub Kicinski
2018-02-16 0:02 ` Lorenzo Bianconi
2018-02-16 0:35 ` Jakub Kicinski
2018-02-16 9:06 ` Lorenzo Bianconi
2018-02-16 21:08 ` Jakub Kicinski
2018-02-28 14:51 ` Kalle Valo
2018-02-28 15:04 ` Lorenzo Bianconi
2018-02-28 15:07 ` Kalle Valo [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=87vaehqhje.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=kubakici@wp.pl \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.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;
as well as URLs for NNTP newsgroup(s).