devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Joe Perches <joe@perches.com>
Cc: netdev <netdev@vger.kernel.org>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Lee Jones <lee.jones@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	linux-kernel@vger.kernel.org,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org,
	Kumar Gala <galak@codeaurora.org>,
	Daniel Mack <daniel@zonque.org>
Subject: Re: unclear ipv6 redirect message (was Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board)
Date: Wed, 21 Jan 2015 16:46:41 +0000	[thread overview]
Message-ID: <20150121164641.GU26493@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1421858444.10574.14.camel@perches.com>

On Wed, Jan 21, 2015 at 08:40:44AM -0800, Joe Perches wrote:
> On Wed, 2015-01-21 at 16:11 +0000, Russell King - ARM Linux wrote:
> > On Wed, Jan 21, 2015 at 08:05:21AM -0800, Joe Perches wrote:
> > > (adding netdev)
> > 
> > I wasn't actually reporting that as an issue; I was using it as an
> > example.  It's from a very old kernel (2.6.27.21) which I run on one
> > of my old x86 machines.
> 
> It's still the same code.
> If the message can be improved, why not do it?

I assume you're taking the responsibility to test anything that comes
out of this then?

I'm not; I tried updating the kernel on the machine to 2.6.32 many
years ago and that was a no-go because of userspace (udev)
incompatibilities.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-01-21 16:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 11:00 [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Robert Jarzmik
2015-01-16 11:00 ` [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board Robert Jarzmik
     [not found]   ` <1421406010-14851-2-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2015-01-19  9:17     ` Lee Jones
2015-01-19 19:09       ` Robert Jarzmik
     [not found]         ` <87ppaah9k5.fsf-GANU6spQydw@public.gmane.org>
2015-01-20 10:29           ` Lee Jones
2015-01-20 11:56             ` Russell King - ARM Linux
2015-01-21  7:46               ` Robert Jarzmik
2015-01-21  8:16                 ` Lee Jones
2015-01-21  8:27                   ` Robert Jarzmik
     [not found]                     ` <87y4owedx1.fsf-GANU6spQydw@public.gmane.org>
2015-01-21 12:35                       ` Lee Jones
2015-01-21 13:02                         ` Russell King - ARM Linux
2015-01-21 13:36                         ` robert.jarzmik-GANU6spQydw
2015-01-21 15:10                           ` Lee Jones
2015-01-21 19:22                             ` Robert Jarzmik
2015-01-21  9:47                   ` Russell King - ARM Linux
2015-01-21  9:44                 ` Russell King - ARM Linux
2015-01-21 16:05                   ` unclear ipv6 redirect message (was Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board) Joe Perches
     [not found]                     ` <1421856321.10574.13.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2015-01-21 16:11                       ` Russell King - ARM Linux
2015-01-21 16:40                         ` Joe Perches
2015-01-21 16:46                           ` Russell King - ARM Linux [this message]
2015-01-16 11:00 ` [PATCH v3 3/3] ARM: pxa: lubbock: use new lubbock_io driver Robert Jarzmik
2015-01-19  8:35 ` [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Lee Jones
2015-01-19 19:29   ` Robert Jarzmik
2015-01-20 10:18     ` Lee Jones

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=20150121164641.GU26493@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arnd@arndb.de \
    --cc=daniel@zonque.org \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=joe@perches.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=robert.jarzmik@free.fr \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.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).