From: Henrik Austad <haustad@cisco.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, henrik@austad.us
Subject: Re: [PATCH] ether: add AVB frame type ETH_P_AVB
Date: Fri, 06 Jun 2014 12:13:02 +0200 [thread overview]
Message-ID: <5391942E.8020507@cisco.com> (raw)
In-Reply-To: <1402047773-2320-1-git-send-email-haustad@cisco.com>
David,
I messed up the keys on my keyboard and shipped the patch without CC to
you. Sorry!
- Henrik
On 06/06/2014 11:42 AM, Henrik Austad wrote:
> Audio/Video Bridging over layer-2 transport protocol uses 0x22F0 as
> packet type. This type is used for both AVB control data as well as AVB
> media streams.
>
CC: "David S. Miller" <davem@davemloft.net>
> Signed-off-by: Henrik Austad <haustad@cisco.com>
> ---
> include/uapi/linux/if_ether.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/if_ether.h b/include/uapi/linux/if_ether.h
> index 0f8210b..c8147de 100644
> --- a/include/uapi/linux/if_ether.h
> +++ b/include/uapi/linux/if_ether.h
> @@ -48,6 +48,7 @@
> #define ETH_P_BPQ 0x08FF /* G8BPQ AX.25 Ethernet Packet [ NOT AN OFFICIALLY REGISTERED ID ] */
> #define ETH_P_IEEEPUP 0x0a00 /* Xerox IEEE802.3 PUP packet */
> #define ETH_P_IEEEPUPAT 0x0a01 /* Xerox IEEE802.3 PUP Addr Trans packet */
> +#define ETH_P_AVB 0x22F0 /* IEEE 1722 AVB frame [ NOT AN OFFICIALLY REGISTERED ID ] */
> #define ETH_P_BATMAN 0x4305 /* B.A.T.M.A.N.-Advanced packet [ NOT AN OFFICIALLY REGISTERED ID ] */
> #define ETH_P_DEC 0x6000 /* DEC Assigned proto */
> #define ETH_P_DNA_DL 0x6001 /* DEC DNA Dump/Load */
>
--
Henrik Austad
Software Engineer
TIPBU Eng, Performance
Sent from my computer
next parent reply other threads:[~2014-06-06 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1402047773-2320-1-git-send-email-haustad@cisco.com>
2014-06-06 10:13 ` Henrik Austad [this message]
2014-06-25 5:59 ` [PATCH] ether: add AVB frame type ETH_P_AVB Henrik Austad
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=5391942E.8020507@cisco.com \
--to=haustad@cisco.com \
--cc=davem@davemloft.net \
--cc=henrik@austad.us \
--cc=linux-kernel@vger.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).