From: Jani Nikula <jani.nikula@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>, "Bityutskiy\,
Artem" <artem.bityutskiy@intel.com>
Subject: Re: [git pull] drm for v4.7
Date: Wed, 25 May 2016 11:28:36 +0300 [thread overview]
Message-ID: <8737p6czij.fsf@intel.com> (raw)
In-Reply-To: <20160525120318.407c3aa0@canb.auug.org.au>
On Wed, 25 May 2016, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> My bad. That warning turned up in linux-next last Wednesday but I
> didn't notice (I have other stuff to do and don't carefully watch all
> the builds all day - and there are quite a few warnings to filter new
> ones out out of). Maybe I need some automated way to flag new warnings.
There may be better ones out there, but Artem's "aiaiai" has some
helpers [1] for diffing build logs, if you want something simple to
integrate into existing scripts.
BR,
Jani.
[1] http://git.infradead.org/users/dedekind/aiaiai.git/tree/HEAD:/helpers
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-05-25 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 6:41 [git pull] drm for v4.7 Dave Airlie
2016-05-23 18:59 ` Linus Torvalds
2016-05-23 19:10 ` Linus Torvalds
2016-05-25 2:03 ` Stephen Rothwell
2016-05-25 8:28 ` Jani Nikula [this message]
2016-05-25 16:13 ` Linus Torvalds
2016-05-25 16:49 ` Emil Velikov
2016-05-23 19:20 ` Dave Airlie
2016-05-23 19:23 ` Dave Airlie
2016-05-23 19:55 ` Dave Airlie
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=8737p6czij.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=artem.bityutskiy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).