From: Greg KH <gregkh@suse.de>
To: Davidlohr Bueso <dave@gnu.org>
Cc: Greg KH <greg@kroah.com>,
Michal Nazarewicz <m.nazarewicz@samsung.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/2] USB: ffs-test: fix header path
Date: Thu, 17 Feb 2011 11:05:54 -0800 [thread overview]
Message-ID: <20110217190554.GA25833@suse.de> (raw)
In-Reply-To: <1297969052.21769.0.camel@offworld>
On Thu, Feb 17, 2011 at 03:57:32PM -0300, Davidlohr Bueso wrote:
> On Thu, 2011-02-17 at 10:42 -0800, Greg KH wrote:
> > On Sun, Feb 06, 2011 at 02:13:33PM -0300, Davidlohr Bueso wrote:
> > > From: Davidlohr Bueso <dave@gnu.org>
> > >
> > > When compiling this program the functionfs.h header cannot be found, producing:
> > > ffs-test.c:40: fatal error: linux/usb/functionfs.h: No such file or directory
> > >
> > > This patch also fixes the following warning:
> > > ffs-test.c:453: warning: format ‘%4d’ expects type ‘int’, but argument 3 has type ‘size_t’
> > >
> > > Signed-off-by: Davidlohr Bueso <dave@gnu.org>
> > > ---
> > > tools/usb/ffs-test.c | 4 ++--
> > > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > This patch doesn't apply properly to the linux-next branch, what did you
> > make it against?
> >
>
> It was against Linus' tree (did a pull right before submitting the
> patch).
Ah, so you think this is needed for Linus's tree now? Care to resend it
and I'll queue it up to the proper tree, sorry, I missed that.
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-17 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 17:13 [PATCH v2 1/2] USB: ffs-test: fix header path Davidlohr Bueso
2011-02-16 13:38 ` Davidlohr Bueso
2011-02-17 18:42 ` Greg KH
2011-02-17 18:57 ` Davidlohr Bueso
2011-02-17 19:05 ` Greg KH [this message]
2011-02-27 7:58 ` Davidlohr Bueso
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=20110217190554.GA25833@suse.de \
--to=gregkh@suse.de \
--cc=dave@gnu.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.nazarewicz@samsung.com \
/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