All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Ayşe Melike Yurtoğlu" <aysemelikeyurtoglu@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2 1/4] Staging: lustre: Deleted space prohibited between function name and open parenthesis
Date: Thu, 26 Feb 2015 15:58:36 -0800	[thread overview]
Message-ID: <20150226235836.GA11653@kroah.com> (raw)
In-Reply-To: <CAPYvaxM7KhNmzThSQe285NmBv7v-zDkGFMgqT99ywdjivdTHqA@mail.gmail.com>


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top


On Fri, Feb 27, 2015 at 01:40:46AM +0200, Ayşe Melike Yurtoğlu wrote:
> I compile patch before sending. I wonder , am i doing  it wrong?
> I'm doing the compiling process as follows:
> make drivers/staging/lustre/lnet/klnds/socklnd/

A simple:
	make
should be all that is needed to rebuild any changed files.

I didn't build this, and really don't even remember what this patch was,
given that I just reviewed 700+ patches in the past few hours and have
the short-term memory of a squirrel.

If you think the patch is correct, great, please resend.

thanks,

greg k-h


      reply	other threads:[~2015-02-26 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 20:04 [PATCH v2 1/4] Staging: lustre: Deleted space prohibited between function name and open parenthesis Melike Yurtoglu
2015-02-20 20:04 ` [PATCH v2 2/4] Staging: lustre: removed suspect code indent for conditional statements Melike Yurtoglu
2015-02-20 20:04 ` [PATCH v2 3/4] Staging: lustre: Remove return in void function Melike Yurtoglu
2015-02-20 20:04 ` [PATCH v2 4/4] Staging: lustre: Add blank line after declarations Melike Yurtoglu
2015-02-26 18:20 ` [Outreachy kernel] [PATCH v2 1/4] Staging: lustre: Deleted space prohibited between function name and open parenthesis Greg KH
2015-02-26 23:40   ` Ayşe Melike Yurtoğlu
2015-02-26 23:58     ` Greg KH [this message]

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=20150226235836.GA11653@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aysemelikeyurtoglu@gmail.com \
    --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.