From: ijc@debian.org (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
Date: Wed, 06 May 2015 09:01:12 +0100 [thread overview]
Message-ID: <1430899272.15640.237.camel@debian.org> (raw)
In-Reply-To: <1430583695.15640.190.camel@hellion.org.uk>
On Sat, 2015-05-02 at 17:21 +0100, Ian Campbell wrote:
> We typically build RTCs statically (for this sort of reason) so it seems
> like the right thing for us to do here is to build both in.
Which I've now done in SVN. Rick, please test the next upload.
Also, Rick, I'm getting messages from my MTA about not being able to
deliver to rbthomas at cube.rcthomas.org, it's been queuing/retrying since
the weekend and says I shouldn't worry, but I thought I'd mention it
since I was here. Exim logs say:
2015-05-06 06:48:50 1YoZqj-0002JC-G0 == rbthomas at cube.rcthomas.org R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
Hopefully you will see this via some other route.
Ian.
next prev parent reply other threads:[~2015-05-06 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150410232854.23367.58862.reportbug@cube.rcthomas.org>
2015-04-11 0:08 ` Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks Ben Hutchings
2015-04-29 3:02 ` Fabio Estevam
2015-04-29 5:46 ` Rick Thomas
2015-04-29 5:48 ` Rick Thomas
2015-04-29 8:57 ` Russell King - ARM Linux
2015-05-02 16:01 ` Ian Campbell
2015-05-02 16:12 ` Russell King - ARM Linux
2015-05-02 16:21 ` Ian Campbell
2015-05-06 8:01 ` Ian Campbell [this message]
2015-05-06 10:00 ` Rick Thomas
2015-05-06 10:27 ` Ian Campbell
2015-05-06 10:35 ` Rick Thomas
2015-05-12 8:33 ` Rick Thomas
2015-05-12 9:11 ` Ian Campbell
2015-05-13 4:54 ` Rick Thomas
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=1430899272.15640.237.camel@debian.org \
--to=ijc@debian.org \
--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).