All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,  ath11k@lists.infradead.org
Subject: Re: [bug report] ath11k: Fix pktlog lite rx events
Date: Wed, 22 Dec 2021 07:53:22 +0200	[thread overview]
Message-ID: <87wnjx2njh.fsf@kernel.org> (raw)
In-Reply-To: <e2df0d82a0ca520123c96e070cdabf56@codeaurora.org> (Anilkumar Kolli's message of "Wed, 22 Dec 2021 08:59:06 +0530")

Anilkumar Kolli <akolli@codeaurora.org> writes:

> On 2021-12-21 20:22, Kalle Valo wrote:
>> Anilkumar Kolli <akolli@codeaurora.org> writes:
>>
>>> Thanks for reporting issue. Could you please help in reproducing the
>>> issue,
>>>
>>> I tried to reproduce the warnings using command, but could not
>>>     make C=1 CHECK="smatch -p=kernel" -C.
>>> drivers/net/wireless/ath/ath11k/ modules
>>
>> I don't see why you need to reproduce the error. rx_buf_sz is
>> uninitialised as there's no else statement, like Dan mentioned above.
>>
>
> I thought this script is useful for ath11k.

Ah, yes it would be useful for us to run smatch checks. I'm just more
concerned about getting the bug Dan reported fixed.

>> Anil, can you send a patch?
>
> Sure Kalle, I will submit a patch.

Great, thank you.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      reply	other threads:[~2021-12-22  5:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 10:42 [bug report] ath11k: Fix pktlog lite rx events Dan Carpenter
2021-12-14 14:26 ` Anilkumar Kolli
2021-12-21 14:52   ` Kalle Valo
2021-12-22  3:29     ` Anilkumar Kolli
2021-12-22  5:53       ` 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=87wnjx2njh.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=akolli@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=dan.carpenter@oracle.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 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.