From: Kalle Valo <kvalo@codeaurora.org>
To: Ramon Fried <rfried@codeaurora.org>
Cc: k.eugene.e@gmail.com, wcn36xx@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wcn36xx: calculate DXE control registers values
Date: Sat, 10 Mar 2018 11:47:36 +0200 [thread overview]
Message-ID: <874llocldz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180304163134.4464-1-rfried@codeaurora.org> (Ramon Fried's message of "Sun, 4 Mar 2018 18:31:34 +0200")
Ramon Fried <rfried@codeaurora.org> writes:
> DXE descriptor control registers used hardcoded magic values. Added
> bit definitions of the control register and calculate this values in
> compilation for clarity.
>
> Signed-off-by: Ramon Fried <rfried@codeaurora.org>
I assume that the values are still the same and there are no functional
changes? If yes, I'll add that to the commit log when I commit this.
--
Kalle Valo
next prev parent reply other threads:[~2018-03-10 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 16:31 [PATCH] wcn36xx: calculate DXE control registers values Ramon Fried
2018-03-10 9:47 ` Kalle Valo [this message]
2018-03-10 16:45 ` Ramon Fried
2018-03-26 15:26 ` Kalle Valo
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=874llocldz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=k.eugene.e@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rfried@codeaurora.org \
--cc=wcn36xx@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.