From: Xiayu Zhang <xiayu.zhang@mediatek.com>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Cc: "Loic Poulain" <loic.poulain@linaro.org>,
"David Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Johannes Berg" <johannes@sipsolutions.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Haijun Liu (刘海军)" <haijun.liu@mediatek.com>,
"Zhaoping Shu (舒召平)" <Zhaoping.Shu@mediatek.com>,
"HW He (何伟)" <HW.He@mediatek.com>,
srv_heupstream <srv_heupstream@mediatek.com>
Subject: Re: [PATCH] Add Multiple TX/RX Queues Support for WWAN Network Device
Date: Fri, 17 Dec 2021 16:05:55 +0800 [thread overview]
Message-ID: <66e7d51bb776b4127f0675ade249ef33eb54fad8.camel@mediatek.com> (raw)
In-Reply-To: <CAHNKnsTMCbjS_vRZ=-sbtu6fxeDFph=r9kVuqnOVm7Y4RRJHag@mail.gmail.com>
Hi Sergey,
Looks like I can only submit new WWAN APIs until I find a real in-tree
user or submit a new driver.
Anyway, thanks a lot for your help.
On Thu, 2021-12-16 at 20:39 +0800, Sergey Ryazanov wrote:
> This is not a good idea. Simulator is intended to test the API that
> is
> used by other drivers for real hardware. But not for experiments with
> an otherwise "userless" API.
>
> If you need to configure the number of queues for an already in-tree
> driver, then just submit a patch for it. If you plan to submit a new
> driver and you need an infrastructure for it, then include patches
> with a new API into a series with the driver.
prev parent reply other threads:[~2021-12-17 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 4:04 [PATCH] Add Multiple TX/RX Queues Support for WWAN Network Device xiayu.zhang
2021-12-09 1:53 ` Jakub Kicinski
2021-12-09 23:11 ` Sergey Ryazanov
2021-12-13 6:06 ` Xiayu Zhang
2021-12-15 0:23 ` Sergey Ryazanov
2021-12-15 8:44 ` Xiayu Zhang
2021-12-15 9:29 ` Loic Poulain
2021-12-15 14:16 ` Sergey Ryazanov
2021-12-16 12:13 ` Xiayu Zhang
2021-12-16 12:39 ` Sergey Ryazanov
2021-12-17 8:05 ` Xiayu Zhang [this message]
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=66e7d51bb776b4127f0675ade249ef33eb54fad8.camel@mediatek.com \
--to=xiayu.zhang@mediatek.com \
--cc=HW.He@mediatek.com \
--cc=Zhaoping.Shu@mediatek.com \
--cc=davem@davemloft.net \
--cc=haijun.liu@mediatek.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=ryazanov.s.a@gmail.com \
--cc=srv_heupstream@mediatek.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 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).