All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:39:26 +0300	[thread overview]
Message-ID: <87mszayj8x.fsf@kernel.org> (raw)
In-Reply-To: <0368ccdc-74f4-6ec1-1b7d-cfb5ebfd479d@yandex.ru> (Dmitry Antipov's message of "Tue, 1 Aug 2023 14:47:11 +0300")

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.

> I don't want to speculate around the workflow of others and realize
> that someone (especially the maintainer) may be overloaded and too
> busy. OTOH it's not quite clear why the trivial things like
> https://marc.info/?l=linux-wireless&m=169030215701718&w=2 stalls for
> almost a week. Should I consider this as "ignored" too?

A delay of week is business as usual, I have patches in queue which are
from last October:

https://patchwork.kernel.org/project/linux-wireless/list/?series=684424&state=*

Remember that this is not a 24/7 service and we just had a summer break.
I have 160 patches in patchwork right so expect long delays but you can
check the status from patchwork yourself:

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

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

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

  reply	other threads:[~2023-08-01 13:39 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 [this message]
2023-08-01 14:02           ` Kalle Valo
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=87mszayj8x.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 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.