All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Antipov, Dmitriy" <Dmitriy.Antipov@softline.com>
Cc: "khoroshilov@ispras.ru" <khoroshilov@ispras.ru>,
	 "dmantipov@yandex.ru" <dmantipov@yandex.ru>,
	 "quic_jjohnson@quicinc.com" <quic_jjohnson@quicinc.com>,
	 "linux-wireless@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	 "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	 "lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: Re: [lvc-project] [PATCH] [v2] wifi: ath10k: cleanup CE initialization
Date: Fri, 25 Aug 2023 10:47:00 +0300	[thread overview]
Message-ID: <877cpjh8cr.fsf@kernel.org> (raw)
In-Reply-To: <0eed7a68c03555cc815959b9fa32b37657f8aeda.camel@softline.com> (Dmitriy Antipov's message of "Wed, 23 Aug 2023 10:13:01 +0000")

"Antipov, Dmitriy" <Dmitriy.Antipov@softline.com> writes:

> On Wed, 2023-08-23 at 13:03 +0300, Alexey Khoroshilov wrote:
>
>> > v2: adjust to match series
>> 
>> Do mean that nothing has been changed in the patch regarding the
>> previous version?
>
> Usually it is, including the cases where some patch of the series
> is changed so the following ones are applied with offsets and thus
> better to be regenerated.

Saying something like "no changes" or "rebased only" would be more
understandable. It is assumed that when sending a new version of the
patchset that offsets can change so saying "no changes" is good enough.

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

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

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: "Antipov, Dmitriy" <Dmitriy.Antipov@softline.com>
Cc: "khoroshilov@ispras.ru" <khoroshilov@ispras.ru>,
	"dmantipov@yandex.ru" <dmantipov@yandex.ru>,
	"quic_jjohnson@quicinc.com" <quic_jjohnson@quicinc.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: Re: [lvc-project] [PATCH] [v2] wifi: ath10k: cleanup CE initialization
Date: Fri, 25 Aug 2023 10:47:00 +0300	[thread overview]
Message-ID: <877cpjh8cr.fsf@kernel.org> (raw)
In-Reply-To: <0eed7a68c03555cc815959b9fa32b37657f8aeda.camel@softline.com> (Dmitriy Antipov's message of "Wed, 23 Aug 2023 10:13:01 +0000")

"Antipov, Dmitriy" <Dmitriy.Antipov@softline.com> writes:

> On Wed, 2023-08-23 at 13:03 +0300, Alexey Khoroshilov wrote:
>
>> > v2: adjust to match series
>> 
>> Do mean that nothing has been changed in the patch regarding the
>> previous version?
>
> Usually it is, including the cases where some patch of the series
> is changed so the following ones are applied with offsets and thus
> better to be regenerated.

Saying something like "no changes" or "rebased only" would be more
understandable. It is assumed that when sending a new version of the
patchset that offsets can change so saying "no changes" is good enough.

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

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

  reply	other threads:[~2023-08-25  7:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  9:50 [PATCH] [v2] wifi: ath10k: cleanup CE initialization Dmitry Antipov
2023-08-23  9:50 ` Dmitry Antipov
2023-08-23  9:50 ` [PATCH 2/3] [v2] wifi: ath10k: simplify ath10k_peer_assoc_h_vht() Dmitry Antipov
2023-08-23  9:50   ` Dmitry Antipov
2023-08-23 14:55   ` Jeff Johnson
2023-08-23 14:55     ` Jeff Johnson
2023-08-23  9:50 ` [PATCH 3/3] [v2] wifi: ath10k: simplify ath10k_pci_pm_suspend() Dmitry Antipov
2023-08-23  9:50   ` Dmitry Antipov
2023-08-23 14:57   ` Jeff Johnson
2023-08-23 14:57     ` Jeff Johnson
2023-08-23 10:03 ` [lvc-project] [PATCH] [v2] wifi: ath10k: cleanup CE initialization Alexey Khoroshilov
2023-08-23 10:03   ` Alexey Khoroshilov
2023-08-23 10:13   ` Antipov, Dmitriy
2023-08-23 10:13     ` Antipov, Dmitriy
2023-08-25  7:47     ` Kalle Valo [this message]
2023-08-25  7:47       ` Kalle Valo
2023-08-23 14:53 ` Jeff Johnson
2023-08-23 14:53   ` Jeff Johnson
2023-08-24  5:51   ` [PATCH 1/6] [v3] wifi: ath10k: cleanup CE ring initialization Dmitry Antipov
2023-08-24  5:51     ` Dmitry Antipov
2023-08-24  5:51     ` [PATCH 2/6] [v3] wifi: ath10k: simplify ath10k_ce_init_pipe() Dmitry Antipov
2023-08-24  5:51       ` Dmitry Antipov
2023-08-24 15:26       ` Jeff Johnson
2023-08-24 15:26         ` Jeff Johnson
2023-08-24  5:51     ` [PATCH 3/6] [v3] wifi: ath10k: cleanup CE pipes initialization Dmitry Antipov
2023-08-24  5:51       ` Dmitry Antipov
2023-08-24 15:27       ` Jeff Johnson
2023-08-24 15:27         ` Jeff Johnson
2023-08-24  5:51     ` [PATCH 4/6] [v3] wifi: ath10k: do not ignore possible dma_alloc_coherent() error Dmitry Antipov
2023-08-24  5:51       ` Dmitry Antipov
2023-08-24 15:27       ` Jeff Johnson
2023-08-24 15:27         ` Jeff Johnson
2023-08-24  5:51     ` [PATCH 5/6] [v3] wifi: ath10k: simplify ath10k_peer_assoc_h_vht() Dmitry Antipov
2023-08-24  5:51       ` Dmitry Antipov
2023-08-24  5:51     ` [PATCH 6/6] [v3] wifi: ath10k: simplify ath10k_pci_pm_suspend() Dmitry Antipov
2023-08-24  5:51       ` Dmitry Antipov
2023-08-24 15:26     ` [PATCH 1/6] [v3] wifi: ath10k: cleanup CE ring initialization Jeff Johnson
2023-08-24 15:26       ` Jeff Johnson
2023-09-20 13:23     ` Kalle Valo
2023-09-20 13:23       ` Kalle Valo
2023-09-21  8:58       ` Dmitry Antipov
2023-09-21  8:58         ` Dmitry Antipov
2023-09-21  9:33         ` Kalle Valo
2023-09-21  9:33           ` 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=877cpjh8cr.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=Dmitriy.Antipov@softline.com \
    --cc=ath10k@lists.infradead.org \
    --cc=dmantipov@yandex.ru \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=quic_jjohnson@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.