From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Timur Tabi <timur@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: qualcomm: Remove QDF24xx support
Date: Tue, 23 Jan 2024 18:59:29 +0100 [thread overview]
Message-ID: <4c37d84f-ee46-4557-b25d-01ad9af4e950@linaro.org> (raw)
In-Reply-To: <CAOZdJXXCmZi8Qx-y2D_NhJiafnGhvma2OY6F+KauqYcNAAQNCQ@mail.gmail.com>
On 1/22/24 21:34, Timur Tabi wrote:
> On Mon, Jan 22, 2024 at 6:02 AM Konrad Dybcio <konrad.dybcio@linaro.org> 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.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>
> Sad day indeed, but understandable.
>
> Acked-by: Timur Tabi <timur@kernel.org>
>
> If you're looking for other QDF stuff to remove, the QDF2400 hacks in
> the SBSA UART driver really should go.
I have a branch completely axing it, but it looks like Qualcomm
apparently still uses some internally [1].. I'm not super happy,
but let's wait on this one.
Konrad
[1] https://lore.kernel.org/linux-arm-msm/52479377-ff61-7537-e4aa-064ab4a77c03@quicinc.com/
next prev parent reply other threads:[~2024-01-23 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 12:02 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 [this message]
2024-01-24 1:30 ` patchwork-bot+netdevbpf
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=4c37d84f-ee46-4557-b25d-01ad9af4e950@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®