From: Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Steven Miao <realmz6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
adi-buildroot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi-bfin: Add missing gpio.h include
Date: Thu, 24 Apr 2014 08:34:32 -0400 [thread overview]
Message-ID: <20140424083432.70c80f64@gandalf.local.home> (raw)
In-Reply-To: <20140424113346.GM12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Thu, 24 Apr 2014 12:33:46 +0100
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> On Thu, Apr 24, 2014 at 11:33:29AM +0100, Mark Brown wrote:
> > On Wed, Apr 23, 2014 at 10:40:35PM -0400, Steven Rostedt wrote:
> > > Running my ktest.pl tests on all the archs, I stumbled over this for
> > > 3.15-rc2:
> >
> > Applied, thanks.
>
> Actually not - I already have a fix for this in -next (on a slightly
> different branch to the one I looked for it on). Anyway, it's fixed.
Heh, OK, I figured someone may have already fixed it, but still wanted
to let people know it was broken. It's amazing how long something like
this can take.
It's just annoying when my tests break on something that I'm not
testing ;-)
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-24 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 2:40 [PATCH] spi-bfin: Add missing gpio.h include Steven Rostedt
2014-04-24 10:33 ` Mark Brown
2014-04-24 11:33 ` Mark Brown
[not found] ` <20140424113346.GM12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-04-24 12:34 ` Steven Rostedt [this message]
2014-04-24 12:36 ` Mark Brown
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=20140424083432.70c80f64@gandalf.local.home \
--to=rostedt-nx8x9ylhiw1afugrpc6u6w@public.gmane.org \
--cc=adi-buildroot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=realmz6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).