public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] malloc: Remove control-L in malloc.h
Date: Mon, 30 May 2016 22:37:22 +0200	[thread overview]
Message-ID: <574CA482.1050001@denx.de> (raw)
In-Reply-To: <20160530201518.76EB0100C66@atlas.denx.de>

On 05/30/2016 10:15 PM, Wolfgang Denk wrote:
> Dear Marek,
> 
> In message <1464621732-7617-1-git-send-email-marex@denx.de> you wrote:
>> Remove what must've been a typo.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Tom Rini <trini@konsulko.com>
>> Cc: Simon Glass <sjg@chromium.org>
>> ---
>>  include/malloc.h | 1 -
>>  1 file changed, 1 deletion(-)
>>
>> diff --git a/include/malloc.h b/include/malloc.h
>> index 8175c75..e065473 100644
>> --- a/include/malloc.h
>> +++ b/include/malloc.h
>> @@ -215,7 +215,6 @@
>>  
>>  */
>>  
>> -

>>  #ifndef __MALLOC_H__
>>  #define __MALLOC_H__
> 
> This is most likely NOT a typo, but an intentional page break (yes,
> there was a time when people used to _print_ source code on dead
> wood).  And I bet if comes from the original imported dlmalloc code,
> so please check twice befoire introducing an unneeded difference.

Urgh, ok, feel free to drop this patch, I don't really care.

> Best regards,
> 
> Wolfgang Denk
> 


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2016-05-30 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 15:22 [U-Boot] [PATCH] malloc: Remove control-L in malloc.h Marek Vasut
2016-05-30 19:18 ` Måns Rullgård
2016-05-30 20:15 ` Wolfgang Denk
2016-05-30 20:37   ` Marek Vasut [this message]
2016-05-30 20:38     ` Marek Vasut
2016-05-31 10:27       ` Måns Rullgård
2016-06-02 13:31         ` Wolfgang Denk

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=574CA482.1050001@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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