From: Randy Dunlap <rdunlap@xenotime.net>
To: Roland Dreier <roland@purestorage.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Marciniszyn <infinipath@qlogic.com>,
linux-rdma@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] infiniband: fix ipath_chip_init.c build errors
Date: Fri, 07 Oct 2011 15:05:44 -0700 [thread overview]
Message-ID: <4E8F77B8.3000805@xenotime.net> (raw)
In-Reply-To: <CAL1RGDXoiRfR1Ku67tRgbhxzyWQmDrjKCztnVd6wbwi0Uud90Q@mail.gmail.com>
On 10/07/11 14:21, Roland Dreier wrote:
> On Fri, Oct 7, 2011 at 1:59 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>> Add <linux/stat.h> to fix build errors:
>
> When did this break? I build ipath in my test config all the time...
First I saw it was in today's linux-next (20111007).
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-10-07 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111007174230.702f4a0bf1fe71dab5e10961@canb.auug.org.au>
[not found] ` <20111007174230.702f4a0bf1fe71dab5e10961-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-10-07 20:59 ` [PATCH -next] infiniband: fix ipath_chip_init.c build errors Randy Dunlap
[not found] ` <4E8F683D.9020604-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-10-07 21:21 ` Roland Dreier
2011-10-07 22:05 ` Randy Dunlap [this message]
[not found] ` <4E8F77B8.3000805-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-10-07 23:28 ` Stephen Rothwell
2011-10-10 19:02 ` Roland Dreier
2011-10-11 0:33 ` Stephen Rothwell
2011-10-10 18:57 ` Mike Marciniszyn
2011-10-10 19:02 ` Randy Dunlap
2011-10-11 13:06 ` Mike Marciniszyn
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=4E8F77B8.3000805@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=infinipath@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@purestorage.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox