All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: timur@kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com,
	marijn.suijten@somainline.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: qualcomm: Remove QDF24xx support
Date: Wed, 24 Jan 2024 01:30:31 +0000	[thread overview]
Message-ID: <170605983124.14933.9916722082205803213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240122-topic-qdf_cleanup_net-v1-1-caf0d9c4408a@linaro.org>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 22 Jan 2024 13:02:22 +0100 you wrote:
> This SoC family was destined for server use, featuring Qualcomm's very
> interesting Kryo cores (before "Kryo" became a marketing term for Arm
> cores with small modifications). It did however not leave the labs of
> Qualcomm and presumably some partners, nor was it ever productized.
> 
> Remove the related drivers, as they seem to be long obsolete.
> 
> [...]

Here is the summary with links:
  - net: ethernet: qualcomm: Remove QDF24xx support
    https://git.kernel.org/netdev/net-next/c/a2a7f98aeeec

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-01-24  1:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 12:02 [PATCH] net: ethernet: qualcomm: Remove QDF24xx support Konrad Dybcio
2024-01-22 12:25 ` Denis Kirjanov
2024-01-22 15:36   ` Konrad Dybcio
2024-01-22 21:09     ` Jakub Kicinski
2024-01-22 20:34 ` Timur Tabi
2024-01-23 17:59   ` Konrad Dybcio
2024-01-24  1:30 ` patchwork-bot+netdevbpf [this message]
2024-01-24 12:38   ` Konrad Dybcio
2024-01-24 15:35     ` Jakub Kicinski
2024-01-24 17:52       ` Konrad Dybcio

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=170605983124.14933.9916722082205803213.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=timur@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 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.