All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chris Metcalf <cdmetcalf@comcast.net>,
	linux-next@vger.kernel.org,
	Michael Ellerman <michael@ellerman.id.au>
Subject: Re: kisskb.ellerman.id.au email notifications?
Date: Wed, 06 Jun 2012 17:17:50 -0600	[thread overview]
Message-ID: <4FCFE51E.6060405@wwwdotorg.org> (raw)
In-Reply-To: <20120607082644.9ad38680045c6af921ad1b4c@canb.auug.org.au>

On 06/06/2012 04:26 PM, Stephen Rothwell wrote:
> Hi Chris,
> 
> On Wed, 06 Jun 2012 11:54:21 -0400 Chris Metcalf
> <cdmetcalf@comcast.net> wrote:
>> 
>> I noticed when I merged up to 3.4-rc1 that there were some build
>> issues with tilegx (I've pushed the fixes to my tree for
>> linux-next).  Googling around a little and referring to some
>> earlier discussions, I realized that http://kisskb.ellerman.id.au
>> tracks the build successes and failures for various branches and
>> architectures, including tilegx on linux-next.
>> 
>> My question is whether there's a way to get email notification
>> when a particular build does fail.  I'd like to know when things
>> break the tilegx build, in between the times when I actually sync
>> up and check it myself. Is there a mechanism for that, or should
>> I stick with periodically checking the website manually - which
>> of course is much better than nothing! :-)
> 
> Indeed, there is an email notification available.  I will get it
> set up for you.  Do you want them sent to this address or your
> tilera.com one (or both)?

In that case, could I please be notified of the Tegra build status?
The from address on this email is fine.

Thanks very much!

      parent reply	other threads:[~2012-06-06 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06 15:54 kisskb.ellerman.id.au email notifications? Chris Metcalf
2012-06-06 22:26 ` Stephen Rothwell
2012-06-06 22:44   ` Chris Metcalf
2012-06-06 23:17   ` Stephen Warren [this message]

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=4FCFE51E.6060405@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=cdmetcalf@comcast.net \
    --cc=linux-next@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=sfr@canb.auug.org.au \
    /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.