From: Jakub Kicinski <kuba@kernel.org>
To: "moises.veleta" <moises.veleta@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
johannes@sipsolutions.net, ryazanov.s.a@gmail.com,
loic.poulain@linaro.org, m.chetan.kumar@intel.com,
chandrashekar.devegowda@intel.com, linuxwwan@intel.com,
haijun.liu@mediatek.com, andriy.shevchenko@linux.intel.com,
ilpo.jarvinen@linux.intel.com, ricardo.martinez@linux.intel.com,
sreehari.kancharla@intel.com, dinesh.sharma@intel.com
Subject: Re: [PATCH net-next 1/1] net: wwan: t7xx: Add port for modem logging
Date: Tue, 24 May 2022 11:04:26 -0700 [thread overview]
Message-ID: <20220524110426.5f339585@kernel.org> (raw)
In-Reply-To: <b9cc320f-12b1-7460-5591-4ddc8b7f417f@linux.intel.com>
On Mon, 23 May 2022 22:11:00 -0700 moises.veleta wrote:
> Is the issue with using the debugfs to send random data to the modem an
> issue with validation?
> If so, what if the modem itself is validating the input string would
> that suffice to allow this debugfs control port to act as the medium
> between user space applications and the modem? Leaving the driver blind
> to that process.
> Or is it preferable to have the driver do the validation on the user
> space input to the modem?
Yes, the driver is not supposed to be blind to the process.
prev parent reply other threads:[~2022-05-24 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 18:27 [PATCH net-next 1/1] net: wwan: t7xx: Add port for modem logging Moises Veleta
2022-05-20 8:33 ` Kumar, M Chetan
2022-05-20 20:37 ` moises.veleta
2022-05-20 17:37 ` Jakub Kicinski
2022-05-20 17:42 ` moises.veleta
2022-05-20 17:48 ` Jakub Kicinski
2022-05-20 18:01 ` moises.veleta
2022-05-20 18:15 ` Jakub Kicinski
[not found] ` <dc07d0a9-793b-5b76-cf10-d8fad77c04ea@linux.intel.com>
[not found] ` <20220520144630.56841d21@kernel.org>
2022-05-20 22:00 ` moises.veleta
2022-05-24 5:11 ` moises.veleta
2022-05-24 18:04 ` Jakub Kicinski [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=20220524110426.5f339585@kernel.org \
--to=kuba@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=davem@davemloft.net \
--cc=dinesh.sharma@intel.com \
--cc=haijun.liu@mediatek.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=moises.veleta@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.com \
--cc=sreehari.kancharla@intel.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.