netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2024-02-20
Date: Tue, 20 Feb 2024 19:03:49 +0200	[thread overview]
Message-ID: <87r0h7awzu.fsf@kernel.org> (raw)
In-Reply-To: <20240220165842.917CDC433F1@smtp.kernel.org> (Kalle Valo's message of "Tue, 20 Feb 2024 16:58:42 +0000 (UTC)")

Kalle Valo <kvalo@kernel.org> writes:

> Hi,
>
> here's a pull request to net-next tree, more info below. Please let me know if
> there are any problems.
>
> Kalle
>
> The following changes since commit b7198383ef2debe748118996f627452281cf27d7:
>
>   wifi: iwlwifi: mvm: fix a crash when we run out of stations (2024-02-08 14:55:39 +0100)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git tags/wireless-next-2024-02-20
>
> for you to fetch changes up to dd66185c23f71af36397bebfc99ede608dca07b6:
>
>   wifi: wilc1000: add missing read critical sections around vif list traversal (2024-02-19 18:21:36 +0200)
>
> ----------------------------------------------------------------
> wireless-next patches for v6.9
>
> The second "new features" pull request for v6.9.  Lots of iwlwifi and
> stack changes this time. And naturally smaller changes to other drivers.
>
> We also twice merged wireless into wireless-next to avoid conflicts
> between the trees.
>

[...]

>  drivers/net/dsa/mt7530.c                           |   34 +-
>  drivers/net/ethernet/engleder/tsnep_main.c         |    4 +-
>  drivers/net/ethernet/google/gve/gve.h              |  144 +-
>  drivers/net/ethernet/google/gve/gve_dqo.h          |   18 +-
>  drivers/net/ethernet/google/gve/gve_main.c         |  862 +++---
>  drivers/net/ethernet/google/gve/gve_rx.c           |  135 +-
>  drivers/net/ethernet/google/gve/gve_rx_dqo.c       |   91 +-
>  drivers/net/ethernet/google/gve/gve_tx.c           |  128 +-
>  drivers/net/ethernet/google/gve/gve_tx_dqo.c       |  108 +-
>  drivers/net/ethernet/google/gve/gve_utils.c        |   31 +
>  drivers/net/ethernet/google/gve/gve_utils.h        |    5 +

This diffstat shows extra (non-wireless) changes like the ones above but
then actually pulling the these are not shown. I assume 'git
pull-request' got again confused due to merging wireless into
wireless-next.

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

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

  reply	other threads:[~2024-02-20 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 16:58 pull-request: wireless-next-2024-02-20 Kalle Valo
2024-02-20 17:03 ` Kalle Valo [this message]
2024-02-21 11:51 ` patchwork-bot+netdevbpf
2024-02-21 22:35 ` Jakub Kicinski
2024-02-21 23:34   ` Jeff Johnson
2024-02-22  1:18     ` Jeff Johnson
2024-02-22  1:25       ` Jakub Kicinski
2024-02-22  5:11         ` Kalle Valo
2024-02-22 10:59           ` Kalle Valo
2024-02-22 23:17             ` Jakub Kicinski

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=87r0h7awzu.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.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).