From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression in 3.7-rc3 on Marvell Kirkwood
Date: Sun, 4 Nov 2012 10:11:46 +0100 [thread overview]
Message-ID: <20121104091146.GF6832@lunn.ch> (raw)
In-Reply-To: <CAMW5UfZLYzCf357Z0Ncd6p5G7VYLwq3nhXVb=nAXZOxONa8yeQ@mail.gmail.com>
On Sat, Nov 03, 2012 at 09:39:55PM -0400, Josh Coombs wrote:
> As of now I can't reproduce, so I can only assume it was something
> with my config. Once I nail down exactly what triggers the behavior
> I'll post up. For now, ignore my suggestion that there is a
> regression.
O.K.
I also tried reproducing it. On my QNAP Kirkwood I made a fresh
checkout of the kernel and built it. No problems.
If you do see it again, please let us know.
Thanks
Andrew
next prev parent reply other threads:[~2012-11-04 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 8:03 Possible regression in 3.7-rc3 on Marvell Kirkwood Andrew Lunn
2012-11-03 12:54 ` Josh Coombs
2012-11-03 17:06 ` Andrew Lunn
2012-11-04 1:39 ` Josh Coombs
2012-11-04 9:11 ` Andrew Lunn [this message]
2012-11-04 12:05 ` Josh Coombs
-- strict thread matches above, loose matches on Subject: below --
2012-11-03 3:50 Josh Coombs
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=20121104091146.GF6832@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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).