From: Randy Dunlap <rdunlap@infradead.org>
To: Vladimir Oltean <olteanv@gmail.com>,
f.fainelli@gmail.com, vivien.didelot@gmail.com, andrew@lunn.ch,
sfr@canb.auug.org.au, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: tag_sja1105: Select CONFIG_PACKING
Date: Tue, 11 Jun 2019 18:56:13 -0700 [thread overview]
Message-ID: <005d0239-c0fa-7cd2-aed7-df9c46096b60@infradead.org> (raw)
In-Reply-To: <20190611184745.6104-1-olteanv@gmail.com>
On 6/11/19 11:47 AM, Vladimir Oltean wrote:
> The packing facility is needed to decode Ethernet meta frames containing
> source port and RX timestamping information.
>
> The DSA driver selects CONFIG_PACKING, but the tagger did not, and since
> taggers can be now compiled as modules independently from the drivers
> themselves, this is an issue now, as CONFIG_PACKING is disabled by
> default on all architectures.
>
> Fixes: e53e18a6fe4d ("net: dsa: sja1105: Receive and decode meta frames")
> Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
Thanks.
> ---
> net/dsa/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/dsa/Kconfig b/net/dsa/Kconfig
> index d449f78c1bd0..6e942dda1bcd 100644
> --- a/net/dsa/Kconfig
> +++ b/net/dsa/Kconfig
> @@ -106,6 +106,7 @@ config NET_DSA_TAG_LAN9303
> config NET_DSA_TAG_SJA1105
> tristate "Tag driver for NXP SJA1105 switches"
> select NET_DSA_TAG_8021Q
> + select PACKING
> help
> Say Y or M if you want to enable support for tagging frames with the
> NXP SJA1105 switch family. Both the native tagging protocol (which
>
--
~Randy
next prev parent reply other threads:[~2019-06-12 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:47 [PATCH net-next] net: dsa: tag_sja1105: Select CONFIG_PACKING Vladimir Oltean
2019-06-12 1:56 ` Randy Dunlap [this message]
2019-06-14 5:44 ` David Miller
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=005d0239-c0fa-7cd2-aed7-df9c46096b60@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=vivien.didelot@gmail.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).