All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Rob Landley <rob@landley.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: change example to existing Makefile fragment
Date: Mon, 08 Apr 2013 12:42:23 +0200	[thread overview]
Message-ID: <51629F0F.6070501@suse.cz> (raw)
In-Reply-To: <1364258406.15703.70@driftwood>

On 26.3.2013 01:40, Rob Landley wrote:
> On 03/25/2013 05:16:24 AM, Paul Bolle wrote:
>> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
>> ---
>>  Documentation/kbuild/makefiles.txt | 5 +++--
>>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> Acked-by: Rob Landley <rob@landley.net>
> 
> Please send through the kbuild tree.

Paul,

can you send me the patch?

Thanks,
Michal

  reply	other threads:[~2013-04-08 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 10:16 [PATCH] doc: change example to existing Makefile fragment Paul Bolle
2013-03-26  0:40 ` Rob Landley
2013-04-08 10:42   ` Michal Marek [this message]
2013-04-08 10:51     ` [PATCH v2] " Paul Bolle
2013-04-08 11:01       ` Michal Marek

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=51629F0F.6070501@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rob@landley.net \
    /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.