linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: richard -rw- weinberger <richard.weinberger@gmail.com>
To: wang.bo116@zte.com.cn
Cc: cui.yunfeng@zte.com.cn, LKML <linux-kernel@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	liu.dong3@zte.com.cn
Subject: Re: Re: Re: Re: [PATCH] UBI: fix memory leak when use fastmap
Date: Thu, 23 May 2013 14:13:27 +0200	[thread overview]
Message-ID: <CAFLxGvw5gj-dfQeMKQVJpHPAXi4ZeNTaG3u3yXOAkshJRavXVA@mail.gmail.com> (raw)
In-Reply-To: <OF6992CC88.316C799B-ON48257B74.0040CED8-48257B74.0041FF6F@zte.com.cn>

On Thu, May 23, 2013 at 2:00 PM,  <wang.bo116@zte.com.cn> wrote:
> richard -rw- weinberger <richard.weinberger@gmail.com>  2013-05-13
> 16:08:35:
>
>>
>> I tried to apply/test your patch.
>> It has lots of white spaces damages.
>> Can you please resend it using git send-email?
>> And also run checkpatch.pl before sending.
>>
>> --
>> Thanks,
>> //richard
>
> hello:
>         I use git to remake a patch, and pass the checkpatch.pl's test.
> But my email client is lotus notes, and the patch's format may be damage
> by the client.

This explains the broken patch.
You can also send me the patch as attachment. :)

--
Thanks,
//richard

  reply	other threads:[~2013-05-23 12:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02  8:30 Re: [PATCH] UBI: fix memory leak when use fastmap wang.bo116
2013-05-02 19:21 ` richard -rw- weinberger
2013-05-03  3:31   ` wang.bo116
2013-05-13  8:08     ` richard -rw- weinberger
2013-05-23 12:00       ` wang.bo116
2013-05-23 12:13         ` richard -rw- weinberger [this message]
2013-05-27  8:02           ` [PATCH] UBI: Fastmap: Fix memory leak Thomas Weber
2013-05-27  8:10             ` Richard Weinberger
2013-05-27  8:22               ` Thomas Weber
2013-05-29 12:27               ` Artem Bityutskiy
2013-05-29 12:28                 ` Richard Weinberger

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=CAFLxGvw5gj-dfQeMKQVJpHPAXi4ZeNTaG3u3yXOAkshJRavXVA@mail.gmail.com \
    --to=richard.weinberger@gmail.com \
    --cc=cui.yunfeng@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=liu.dong3@zte.com.cn \
    --cc=wang.bo116@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).