From: Loic Poulain <loic.poulain@linaro.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Bjørn Mork" <bjorn@mork.no>, "Dan Williams" <dcbw@redhat.com>,
"Network Development" <netdev@vger.kernel.org>,
"Carl Yin(殷张成)" <carl.yin@quectel.com>
Subject: Re: [PATCH net-next v2 1/3] net: mhi: Add RX/TX fixup callbacks
Date: Thu, 4 Feb 2021 08:54:30 +0100 [thread overview]
Message-ID: <CAMZdPi_knLw3MQUr35khbrT7M6JjOVNi2f-+-6hrgEehubCmRQ@mail.gmail.com> (raw)
In-Reply-To: <20210203150843.06506420@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Hi Jakub,
On Thu, 4 Feb 2021 at 00:08, Jakub Kicinski <kuba@kernel.org> wrote:
>
> Please put the maintainers or the list thru which you expect the patch
> to be applied in the To: field of your emails.
>
> On Mon, 1 Feb 2021 22:05:40 +0100 Loic Poulain wrote:
> > + if (proto && proto->tx_fixup) {
> > + skb = proto->tx_fixup(mhi_netdev, skb);
> > + if (unlikely(!skb))
> > + goto exit_drop;
> > + }
>
> > @@ -170,7 +193,11 @@ static void mhi_net_dl_callback(struct mhi_device *mhi_dev,
> > }
> >
> > skb_put(skb, mhi_res->bytes_xferd);
> > - netif_rx(skb);
> > +
> > + if (proto && proto->rx_fixup)
> > + proto->rx_fixup(mhi_netdev, skb);
> > + else
> > + netif_rx(skb);
> > }
>
> There us a slight asymmetry between tx_fixup and rx_fixup.
> tx_fixup just massages the frame and then mhi_net still takes
> care of transmission. On Rx side rx_fixup actually does the
> netif_rx(skb). Maybe s/rx_fixup/rx/ ?
Yes, that makes sense.
Loic
prev parent reply other threads:[~2021-02-04 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 21:05 [PATCH net-next v2 1/3] net: mhi: Add RX/TX fixup callbacks Loic Poulain
2021-02-01 21:05 ` [PATCH net-next v2 2/3] net: mhi: Add dedicated folder Loic Poulain
2021-02-01 21:05 ` [PATCH net-next v2 3/3] net: mhi: Add mbim proto Loic Poulain
2021-02-03 23:19 ` Jakub Kicinski
2021-02-03 23:08 ` [PATCH net-next v2 1/3] net: mhi: Add RX/TX fixup callbacks Jakub Kicinski
2021-02-04 7:54 ` Loic Poulain [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=CAMZdPi_knLw3MQUr35khbrT7M6JjOVNi2f-+-6hrgEehubCmRQ@mail.gmail.com \
--to=loic.poulain@linaro.org \
--cc=bjorn@mork.no \
--cc=carl.yin@quectel.com \
--cc=dcbw@redhat.com \
--cc=kuba@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).