From: Dan Carpenter <dan.carpenter@oracle.com>
To: Carl Huang <quic_cjhuang@quicinc.com>, lkp@intel.com
Cc: Kalle Valo <quic_kvalo@quicinc.com>,
kbuild@lists.01.org, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
ath11k@lists.infradead.org, Wen Gong <quic_wgong@quicinc.com>
Subject: Re: [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex'.
Date: Thu, 5 May 2022 08:58:17 +0300 [thread overview]
Message-ID: <20220505055817.GQ4031@kadam> (raw)
In-Reply-To: <fd76aa54-4d05-a4b0-b3b4-11c8a5be799c@quicinc.com>
On Thu, May 05, 2022 at 09:29:40AM +0800, Carl Huang wrote:
> Hi Kalle,
>
> Is the below the same fix that you have already applied to ath.git?
>
> [-next] ath11k: fix missing unlock on error in ath11k_wow_op_resume() -
> Patchwork (kernel.org) <https://patchwork.kernel.org/project/linux-wireless/patch/20220408030912.3087293-1-yangyingliang@huawei.com/
> >
That looks good. It's sort of annoying for me to send a bug report a
month after the fix has been applied... Sorry about that.
1) These are kbuild warnings. The zero day bot generates the
warnings and I look them over and hit send. I don't know why the kbuild
bot seems to get confused by -mm. The subject says 408/8237 which is
pretty crazy. Maybe I should just ignore the -mm patches?
2) The blamed patch came from a git tree but it had a Link tag to
lore.kernel.org so we could have used that as an In-Reply-to tag.
In an ideal world, all the bug reports for a patch would go to a
standard location.
Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang@quicinc.com
3) Another idea is that the kbuild bot could search lore for Fixes to
the original commit and include links to those threads?
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Carl Huang <quic_cjhuang@quicinc.com>, lkp@intel.com
Cc: Kalle Valo <quic_kvalo@quicinc.com>,
kbuild@lists.01.org, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
ath11k@lists.infradead.org, Wen Gong <quic_wgong@quicinc.com>
Subject: Re: [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex'.
Date: Thu, 5 May 2022 08:58:17 +0300 [thread overview]
Message-ID: <20220505055817.GQ4031@kadam> (raw)
In-Reply-To: <fd76aa54-4d05-a4b0-b3b4-11c8a5be799c@quicinc.com>
On Thu, May 05, 2022 at 09:29:40AM +0800, Carl Huang wrote:
> Hi Kalle,
>
> Is the below the same fix that you have already applied to ath.git?
>
> [-next] ath11k: fix missing unlock on error in ath11k_wow_op_resume() -
> Patchwork (kernel.org) <https://patchwork.kernel.org/project/linux-wireless/patch/20220408030912.3087293-1-yangyingliang@huawei.com/
> >
That looks good. It's sort of annoying for me to send a bug report a
month after the fix has been applied... Sorry about that.
1) These are kbuild warnings. The zero day bot generates the
warnings and I look them over and hit send. I don't know why the kbuild
bot seems to get confused by -mm. The subject says 408/8237 which is
pretty crazy. Maybe I should just ignore the -mm patches?
2) The blamed patch came from a git tree but it had a Link tag to
lore.kernel.org so we could have used that as an In-Reply-to tag.
In an ideal world, all the bug reports for a patch would go to a
standard location.
Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang@quicinc.com
3) Another idea is that the kbuild bot could search lore for Fixes to
the original commit and include links to those threads?
regards,
dan carpenter
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild@lists.01.org
Subject: Re: [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex'.
Date: Thu, 05 May 2022 08:58:17 +0300 [thread overview]
Message-ID: <20220505055817.GQ4031@kadam> (raw)
In-Reply-To: <fd76aa54-4d05-a4b0-b3b4-11c8a5be799c@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Thu, May 05, 2022 at 09:29:40AM +0800, Carl Huang wrote:
> Hi Kalle,
>
> Is the below the same fix that you have already applied to ath.git?
>
> [-next] ath11k: fix missing unlock on error in ath11k_wow_op_resume() -
> Patchwork (kernel.org) <https://patchwork.kernel.org/project/linux-wireless/patch/20220408030912.3087293-1-yangyingliang@huawei.com/
> >
That looks good. It's sort of annoying for me to send a bug report a
month after the fix has been applied... Sorry about that.
1) These are kbuild warnings. The zero day bot generates the
warnings and I look them over and hit send. I don't know why the kbuild
bot seems to get confused by -mm. The subject says 408/8237 which is
pretty crazy. Maybe I should just ignore the -mm patches?
2) The blamed patch came from a git tree but it had a Link tag to
lore.kernel.org so we could have used that as an In-Reply-to tag.
In an ideal world, all the bug reports for a patch would go to a
standard location.
Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang(a)quicinc.com
3) Another idea is that the kbuild bot could search lore for Fixes to
the original commit and include links to those threads?
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex'.
Date: Thu, 05 May 2022 08:58:17 +0300 [thread overview]
Message-ID: <20220505055817.GQ4031@kadam> (raw)
In-Reply-To: <fd76aa54-4d05-a4b0-b3b4-11c8a5be799c@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Thu, May 05, 2022 at 09:29:40AM +0800, Carl Huang wrote:
> Hi Kalle,
>
> Is the below the same fix that you have already applied to ath.git?
>
> [-next] ath11k: fix missing unlock on error in ath11k_wow_op_resume() -
> Patchwork (kernel.org) <https://patchwork.kernel.org/project/linux-wireless/patch/20220408030912.3087293-1-yangyingliang@huawei.com/
> >
That looks good. It's sort of annoying for me to send a bug report a
month after the fix has been applied... Sorry about that.
1) These are kbuild warnings. The zero day bot generates the
warnings and I look them over and hit send. I don't know why the kbuild
bot seems to get confused by -mm. The subject says 408/8237 which is
pretty crazy. Maybe I should just ignore the -mm patches?
2) The blamed patch came from a git tree but it had a Link tag to
lore.kernel.org so we could have used that as an In-Reply-to tag.
In an ideal world, all the bug reports for a patch would go to a
standard location.
Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang(a)quicinc.com
3) Another idea is that the kbuild bot could search lore for Fixes to
the original commit and include links to those threads?
regards,
dan carpenter
next prev parent reply other threads:[~2022-05-05 5:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:36 [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex' kernel test robot
2022-05-04 8:46 ` Dan Carpenter
2022-05-04 8:46 ` Dan Carpenter
2022-05-04 16:23 ` Kalle Valo
2022-05-04 16:23 ` Kalle Valo
2022-05-04 16:23 ` Kalle Valo
2022-05-05 1:29 ` Carl Huang
2022-05-05 1:29 ` Carl Huang
2022-05-05 5:58 ` Dan Carpenter [this message]
2022-05-05 5:58 ` Dan Carpenter
2022-05-05 5:58 ` Dan Carpenter
2022-05-05 5:58 ` Dan Carpenter
2022-05-06 8:46 ` Kalle Valo
2022-05-06 8:46 ` Kalle Valo
2022-05-06 8:46 ` Kalle Valo
2022-05-06 9:58 ` [kbuild-all] " Chen, Rong A
2022-05-06 9:58 ` Chen, Rong A
2022-05-06 10:24 ` Dan Carpenter
2022-05-06 10:24 ` Dan Carpenter
2022-05-06 10:24 ` [kbuild-all] " Dan Carpenter
2022-05-06 10:24 ` Dan Carpenter
2022-05-06 13:25 ` Kalle Valo
2022-05-06 13:25 ` Kalle Valo
2022-05-06 13:25 ` 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=20220505055817.GQ4031@kadam \
--to=dan.carpenter@oracle.com \
--cc=ath11k@lists.infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=quic_cjhuang@quicinc.com \
--cc=quic_kvalo@quicinc.com \
--cc=quic_wgong@quicinc.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.