From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Doug Brown <doug@schmorgal.com>,
linux-wireless@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 1/4] wifi: libertas: add missing calls to cancel_work_sync()
Date: Tue, 01 Aug 2023 17:02:08 +0300 [thread overview]
Message-ID: <87bkfqyi73.fsf@kernel.org> (raw)
In-Reply-To: <87mszayj8x.fsf@kernel.org> (Kalle Valo's message of "Tue, 01 Aug 2023 16:39:26 +0300")
Kalle Valo <kvalo@kernel.org> writes:
> Dmitry Antipov <dmantipov@yandex.ru> writes:
>
>> On 8/1/23 13:23, Kalle Valo wrote:
>>
>>> Another problem I see that you don't always reply to review comments and
>>> that gives an impression that the comments are ignored. Please always
>>> try to reply something to the review comments, even if just a simple
>>> "ok" or "I don't agree because...".
>>
>> Looking through my e-mails for the previous month, I was unable to find an
>> unanswered review. Could you please provide an example? I'll fix it
>> ASAP.
>
> You have sent so many patches and I don't have time to start go through
> them. Maybe I noticed that with some of mwifiex patches, not sure. But
> that doesn't matter, I just hope that in the future you reply to
> comments.
While going through patches in patchwork I noticed this dicussion:
https://patchwork.kernel.org/project/linux-wireless/patch/20230726072114.51964-2-dmantipov@yandex.ru/
As there's no reply to Brian it gives a feeling that you are ignoring
our comments.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-08-01 14:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:44 [PATCH 1/4] wifi: libertas: add missing calls to cancel_work_sync() Dmitry Antipov
2023-07-24 8:44 ` [PATCH 2/4] wifi: libertas: use convenient lists to manage SDIO packets Dmitry Antipov
2023-07-24 8:44 ` [PATCH 3/4] wifi: libertas: simplify list operations in free_if_spi_card() Dmitry Antipov
2023-07-24 8:44 ` [PATCH 4/4] wifi: libertas: cleanup SDIO reset Dmitry Antipov
2023-07-24 8:54 ` [PATCH 1/4] wifi: libertas: add missing calls to cancel_work_sync() Kalle Valo
2023-07-24 8:57 ` Dmitry Antipov
2023-08-01 10:23 ` Kalle Valo
2023-08-01 11:47 ` Dmitry Antipov
2023-08-01 13:39 ` Kalle Valo
2023-08-01 14:02 ` Kalle Valo [this message]
2023-07-24 21:27 ` Dan Williams
2023-07-25 4:43 ` Dmitry Antipov
2023-07-25 6:04 ` [PATCH 1/6] [v2] " Dmitry Antipov
2023-07-25 6:04 ` [PATCH 2/6] [v2] wifi: libertas: use convenient lists to manage SDIO packets Dmitry Antipov
2023-07-25 6:04 ` [PATCH 3/6] [v2] wifi: libertas: simplify list operations in free_if_spi_card() Dmitry Antipov
2023-07-25 6:04 ` [PATCH 4/6] [v2] wifi: libertas: cleanup SDIO reset Dmitry Antipov
2023-07-25 6:04 ` [PATCH 5/6] [v2] wifi: libertas: handle possible spu_write_u16() errors Dmitry Antipov
2023-07-25 6:04 ` [PATCH 6/6] [v2] wifi: libertas: prefer kstrtoX() for simple integer conversions Dmitry Antipov
2023-07-31 13:25 ` [PATCH 1/6] [v2] wifi: libertas: add missing calls to cancel_work_sync() Dan Williams
2023-08-01 14:49 ` 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=87bkfqyi73.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=doug@schmorgal.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.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 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).