All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Wen Gong <quic_wgong@quicinc.com>
Cc: <ath11k@lists.infradead.org>,  <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] wifi: ath11k: reduce the timeout value back for hw scan from 10 seconds to 1 second
Date: Fri, 13 Jan 2023 14:14:41 +0200	[thread overview]
Message-ID: <87k01qd426.fsf@kernel.org> (raw)
In-Reply-To: <73908049-4a69-e65c-665b-97d068f1fef7@quicinc.com> (Wen Gong's message of "Fri, 13 Jan 2023 14:54:50 +0800")

Wen Gong <quic_wgong@quicinc.com> writes:

> Should I change commit log with below explanation and send v4?

Please stop spamming the same question over and over, it's really
annoying. If I don't have time to look at something, spamming me won't
help, quite the opposite. It would be a lot better if you would help
with the other upstream related tasks we have, that way I might have
more time to look at your patches.

To answer your question I need to look at this patchset in detail and I
don't know when I'm able to do that. But at this moment I don't trust
this patchset is the right approach and I'm not willing to take it.

-- 
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

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Wen Gong <quic_wgong@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] wifi: ath11k: reduce the timeout value back for hw scan from 10 seconds to 1 second
Date: Fri, 13 Jan 2023 14:14:41 +0200	[thread overview]
Message-ID: <87k01qd426.fsf@kernel.org> (raw)
In-Reply-To: <73908049-4a69-e65c-665b-97d068f1fef7@quicinc.com> (Wen Gong's message of "Fri, 13 Jan 2023 14:54:50 +0800")

Wen Gong <quic_wgong@quicinc.com> writes:

> Should I change commit log with below explanation and send v4?

Please stop spamming the same question over and over, it's really
annoying. If I don't have time to look at something, spamming me won't
help, quite the opposite. It would be a lot better if you would help
with the other upstream related tasks we have, that way I might have
more time to look at your patches.

To answer your question I need to look at this patchset in detail and I
don't know when I'm able to do that. But at this moment I don't trust
this patchset is the right approach and I'm not willing to take it.

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

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

  reply	other threads:[~2023-01-13 12:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  7:24 [PATCH v3 0/2] wifi: ath11k: reduce the timeout value for hw scan Wen Gong
2022-10-11  7:24 ` Wen Gong
2022-10-11  7:24 ` [PATCH v3 1/2] wifi: ath11k: change to set 11d state instead of start 11d scan while disconnect Wen Gong
2022-10-11  7:24   ` Wen Gong
2022-10-11  7:24 ` [PATCH v3 2/2] wifi: ath11k: reduce the timeout value back for hw scan from 10 seconds to 1 second Wen Gong
2022-10-11  7:24   ` Wen Gong
2022-11-08 10:20   ` Kalle Valo
2022-11-08 10:20     ` Kalle Valo
2022-11-18 10:29     ` Wen Gong
2022-11-18 10:29       ` Wen Gong
2022-11-23  3:41       ` Wen Gong
2022-11-23  3:41         ` Wen Gong
2022-12-16  3:08         ` Wen Gong
2022-12-16  3:08           ` Wen Gong
2023-01-13  6:54           ` Wen Gong
2023-01-13  6:54             ` Wen Gong
2023-01-13 12:14             ` Kalle Valo [this message]
2023-01-13 12:14               ` Kalle Valo
2023-01-31  2:40               ` Wen Gong
2023-01-31  2:40                 ` Wen Gong

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=87k01qd426.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --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.