All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Greg KH <gregkh@linuxfoundation.org>, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: vt6656: replace memcpy by ether_addr_copy
Date: Fri, 27 Feb 2015 07:53:49 +0200	[thread overview]
Message-ID: <20150227055349.GA22452@waves> (raw)
In-Reply-To: <alpine.DEB.2.10.1502270644080.2709@hadrien>

On Fri, Feb 27, 2015 at 06:45:35AM +0100, Julia Lawall wrote:
> > > It's usually just easiest to build the whole tree, you can do it quicker
> > > by doing:
> > > 	make -j16
> > >
> > > replace the number with 2x the number of cpus you have, and you should
> > > be fine.
> > >
> > > good luck,
> > >
> > > greg k-h
> >
> > ok, Thanks!
> 
> I guess that the problem would have been seen by just compiling make
> foo/bar/file.o?
> 
Yup! works for me and my poor old CPU :-D Thanks!
> julia

-- 
Kind Regards,
Aya Saif El-yazal Mahfouz


  reply	other threads:[~2015-02-27  5:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 20:00 [PATCH] staging: vt6656: replace memcpy by ether_addr_copy Aya Mahfouz
2015-02-26 18:28 ` [Outreachy kernel] " Greg KH
2015-02-26 20:32   ` Aya Mahfouz
2015-02-26 20:35     ` Julia Lawall
2015-02-26 20:41       ` Aya Mahfouz
2015-02-26 20:59     ` Greg KH
2015-02-27  1:32       ` Aya Mahfouz
2015-02-27  1:55         ` Greg KH
2015-02-27  1:59           ` Aya Mahfouz
2015-02-27  5:45             ` Julia Lawall
2015-02-27  5:53               ` Aya Mahfouz [this message]
2015-02-27  8:53                 ` Arnd Bergmann
2015-02-27 10:23                   ` Aya Mahfouz
  -- strict thread matches above, loose matches on Subject: below --
2015-02-21 11:32 [PATCH] Staging: " Yeliz Taneroglu
2015-02-21 14:22 ` [Outreachy kernel] " Julia Lawall

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=20150227055349.GA22452@waves \
    --to=mahfouz.saif.elyazal@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@lip6.fr \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.