config SND_SOC_MEDIATEK tristate config SND_SOC_MT2701 tristate "ASoC support for Mediatek MT2701 chip" depends on ARCH_MEDIATEK select SND_SOC_MEDIATEK help This adds ASoC driver for Mediatek MT2701 boards that can be used with other codecs. Select Y if you have such device. If unsure select "N". config SND_SOC_MT2701_CS42448 tristate "ASoc Audio driver for MT2701 with CS42448 codec" depends on SND_SOC_MT2701 select SND_SOC_CS42XX8_I2C select SND_SOC_BT_SCO help This adds ASoC driver for Mediatek MT2701 boards with the CS42448 codecs. Select Y if you have such device. If unsure select "N". config SND_SOC_MT8173 tristate "ASoC support for Mediatek MT8173 chip" depends on ARCH_MEDIATEK select SND_SOC_MEDIATEK help This adds ASoC platform driver support for Mediatek MT8173 chip that can be used with other codecs. Select Y if you have such device. Ex: MT8173 config SND_SOC_MT8173_MAX98090 tristate "ASoC Audio driver for MT8173 with MAX98090 codec" depends on SND_SOC_MT8173 && I2C select SND_SOC_MAX98090 help This adds ASoC driver for Mediatek MT8173 boards with the MAX98090 audio codec. Select Y if you have such device. If unsure select "N". config SND_SOC_MT8173_RT5650 tristate "ASoC Audio driver for MT8173 with RT5650 codec" depends on SND_SOC_MT8173 && I2C select SND_SOC_RT5645 select SND_SOC_HDMI_CODEC help This adds ASoC driver for Mediatek MT8173 boards with the RT5650 audio codec. Select Y if you have such device. If unsure select "N". config SND_SOC_MT8173_RT5650_RT5514 tristate "ASoC Audio driver for MT8173 with RT5650 RT5514 codecs" depends on SND_SOC_MT8173 && I2C select SND_SOC_RT5645 select SND_SOC_RT5514 help This adds ASoC driver for Mediatek MT8173 boards with the RT5650 and RT5514 codecs. Select Y if you have such device. If unsure select "N". config SND_SOC_MT8173_RT5650_RT5676 tristate "ASoC Audio driver for MT8173 with RT5650 RT5676 codecs" depends on SND_SOC_MT8173 && I2C select SND_SOC_RT5645 select SND_SOC_RT5677 select SND_SOC_HDMI_CODEC help This adds ASoC driver for Mediatek MT8173 boards with the RT5650 and RT5676 codecs. Select Y if you have such device. If unsure select "N". 118d5234636ca3718f47ca2c8a3b117c19dfdffd'/>
path: root/net/mpls/af_mpls.c
diff options
context:
space:
mode:
authorRobert Shearman <rshearma@brocade.com>2015-08-06 11:04:56 +0100
committerDavid S. Miller <davem@davemloft.net>2015-08-09 22:51:42 -0700
commit118d5234636ca3718f47ca2c8a3b117c19dfdffd (patch)
tree165c54e4e2079c7dab2446535f1e1510df0de783 /net/mpls/af_mpls.c
parentd74a790d5237e7f56677030d932bc4f37ec36c92 (diff)
mpls: Enforce payload type of traffic sent using explicit NULL
RFC 4182 s2 states that if an IPv4 Explicit NULL label is the only label on the stack, then after popping the resulting packet must be treated as a IPv4 packet and forwarded based on the IPv4 header. The same is true for IPv6 Explicit NULL with an IPv6 packet following. Therefore, when installing the IPv4/IPv6 Explicit NULL label routes, add an attribute that specifies the expected payload type for use at forwarding time for determining the type of the encapsulated packet instead of inspecting the first nibble of the packet. Signed-off-by: Robert Shearman <rshearma@brocade.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/mpls/af_mpls.c')