From: Krzysztof Kozlowski <krzk@kernel.org>
To: Robie Basak <robie@justgohome.co.uk>
Cc: Kukjin Kim <kgene@kernel.org>,
linux-samsung-soc@vger.kernel.org,
Nikolay Borisov <kernel@kyup.com>
Subject: Re: Regression: CONFIG_IP_MULTICAST must now be defined in exynos_defconfig
Date: Sun, 18 Dec 2016 18:49:45 +0200 [thread overview]
Message-ID: <20161218164945.GA3662@kozik-lap> (raw)
In-Reply-To: <20161218131912.GG4624@mal.justgohome.co.uk>
On Sun, Dec 18, 2016 at 01:19:12PM +0000, Robie Basak wrote:
> Kukjin/Krzysztof,
>
> Nikolay's commit dcd87999d ("igmp: net: Move igmp namespace init to
> correct file") regressed exynos_defconfig for me. In userspace (Ubuntu
> 14.04), I used libnss-mdns with v4.2(.x), but this commit stopped me
> from being able to resolve local names (eg. "foo.local") published using
> mDNS from elsewhere on the network in v4.9.
>
> It looks like the commit adds extra conditional code based on
> CONFIG_IP_MULTICAST. It turned out that exynos_defconfig doesn't have
> CONFIG_IP_MULTICAST defined. Defining it solved my problem.
>
> I'm using a Samsung ARM Chromebook.
>
> I can define CONFIG_IP_MULTICAST myself easily enough, but shouldn't
> this be defined in exynos_defconfig anyway?
(from my correct email address)
Hi Robie,
I don't have any objections against enabling IP_MULTICAST in
exynos_defconfig. It seems indeed essential.
You are more than welcomed to send a patch for this.
If you don't want to do that, I can prepare one with your "Reported-by"
credits.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-12-18 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 13:19 Regression: CONFIG_IP_MULTICAST must now be defined in exynos_defconfig Robie Basak
2016-12-18 16:49 ` Krzysztof Kozlowski [this message]
2016-12-19 0:52 ` Robie Basak
2016-12-19 0:56 ` [PATCH] ARM: exynos_defconfig: enable IP multicast Robie Basak
2016-12-29 14:06 ` Krzysztof Kozlowski
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=20161218164945.GA3662@kozik-lap \
--to=krzk@kernel.org \
--cc=kernel@kyup.com \
--cc=kgene@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robie@justgohome.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.