From: Enrico Mioso <mrkiko.rs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Enrico Mioso <mrkiko.rs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH RFC 0/2] cdc_ncm refactoring
Date: Tue, 2 Jun 2015 11:08:33 +0200 [thread overview]
Message-ID: <1433236115-5594-1-git-send-email-mrkiko.rs@gmail.com> (raw)
I changed my mind, and decided to try in following this new way.
This series splits the cdc_ncm_ndp function in two parts:
- one that finds NDP blocks already present in the SKB being sent out
- one that pushes new ones, starting from where the _find function left.
After this splitting it seems more easy to modify the location where the NDP is
disposed.
What do you think about this?
>From now on, I need a little bit of help: I think we might work on the
cdc_ncm_ndp16_push function, still I am open to any suggestion.
Let me know if you like this.
Enrico
Enrico Mioso (2):
cdc_ncm: add the currently processed NDP frame to global driver data
cdc_ncm: split the cdc_ncm_ndp funciton
drivers/net/usb/cdc_ncm.c | 30 +++++++++++++++++++++---------
include/linux/usb/cdc_ncm.h | 1 +
2 files changed, 22 insertions(+), 9 deletions(-)
--
2.4.2
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-06-02 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 9:08 Enrico Mioso [this message]
[not found] ` <1433236115-5594-1-git-send-email-mrkiko.rs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-02 9:08 ` [PATCH RFC 1/2] cdc_ncm: add the currently processed NDP frame to global driver data Enrico Mioso
2015-06-02 9:08 ` [PATCH RFC 2/2] cdc_ncm: split the cdc_ncm_ndp funciton Enrico Mioso
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=1433236115-5594-1-git-send-email-mrkiko.rs@gmail.com \
--to=mrkiko.rs-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).