linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 11:27:03 +0100	[thread overview]
Message-ID: <1430908023.2660.203.camel@debian.org> (raw)
In-Reply-To: <64A51823-C50B-48D5-8180-CBC44F691CCB@pobox.com>

Control: submitter -1 Rick Thomas <rbthomas@pobox.com>

On Wed, 2015-05-06 at 03:00 -0700, Rick Thomas wrote:
> OK, How will I identify the upload when I see it?  The box is running
> Debian/Sid and I do regular updates.  So presumably, I?ll see a
> ?linux-image-3.16.0-4-armmp? package go by sometime soon?

I think the next thing to hit Sid will be some 4.0.x per
https://lists.debian.org/debian-kernel/2015/05/msg00047.html

I also committed to the Jessie branch so eventually (I don't know when)
a new 3.16 based thing should appear in jessie-proposed-updates (staging
area for a point release). I'm not sure if the BTS will say anything
when this happens nor how else one might get notified.

It would be preferable to test the thing in Sid before the upload to
jessie-proposed-updates

> And I?ll know I?ve got it when I see two /dev/rtc* devices?

Yes, I suppose.

> As for ?rbthomas at cube.rcthomas.org? ? I?m afraid it?s bogus.  I had
> exim4 configured wrong when I submitted the original bugreport  /-:.
> I?m subscribed to the bugreport with my proper address
> (?rbthomas at pobox.com?) now; so you can either just send stuff for me
> to the bugreport directly or to the ?@pobox.com? address, and delete
> (or simply ignore) ?rbthomas at cube.rcthomas.org? whenever it raises its
> head.

I think the line at the top should have reset the submitter to your
proper address too. If you wanted to do that yourself you could use "!"
as a shorthand for the address in the From: line.

Ian.

  reply	other threads:[~2015-05-06 10:27 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
2015-05-06 10:00             ` Rick Thomas
2015-05-06 10:27               ` Ian Campbell [this message]
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=1430908023.2660.203.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).