public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Nick Krause <xerofoify@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build Errors when building usb directory
Date: Fri, 18 Jul 2014 16:29:32 -0700	[thread overview]
Message-ID: <53C9ADDC.7060506@infradead.org> (raw)
In-Reply-To: <CAPDOMVhUd+cF8PWmWJOEsuCdDuON5_KpO-pZA-aT4n351FgOWg@mail.gmail.com>

On 07/18/2014 12:59 PM, Nick Krause wrote:
> On Fri, Jul 18, 2014 at 2:10 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 07/18/2014 10:45 AM, Nick Krause wrote:
>>> Hey Greg and others,
>>> When I built the usb directory today to check a patch I am also
>>> sending to. I seem to hitting
>>> a few compiler errors and a lot of warnings.  I am going to attach a
>>> file of my log of this build.
>>> Cheers Nick
>>>
>>
>> Hi,
>>
>> What command(s) did you use to build the usb directory?
>>
>> thanks,
>> --
>> ~Randy
> I used make M=drivers/usb to build it.
> Cheers Nick


I'm not seeing any of these warnings, but I am testing 3.16-rc5.

Nick, are you using a current git tree?  If so, which one?
You should always specify what kernel it is that you are testing.


-- 
~Randy

  reply	other threads:[~2014-07-18 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 17:45 Build Errors when building usb directory Nick Krause
2014-07-18 18:10 ` Randy Dunlap
2014-07-18 19:59   ` Nick Krause
2014-07-18 23:29     ` Randy Dunlap [this message]
2014-07-19  2:12       ` Nick Krause

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=53C9ADDC.7060506@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=xerofoify@gmail.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