From: Cerrato Renaud <r.cerrato@til-technologies.fr>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/7] AT91 debug unit typo fix
Date: Wed, 13 Mar 2013 11:14:51 +0100 [thread overview]
Message-ID: <5140519B.6000103@til-technologies.fr> (raw)
In-Reply-To: <20130312165243.GB1568@game.jcrosoft.org>
Sorry. I should have read the posting guidelines beforehand. Should I start another subject for every patch I sent using [PATCH RESEND], or using a reply is acceptable?
Signed-off-by: Cerrato Renaud <r.cerrato@til-technologies.fr>
---
arch/arm/mach-at91/include/mach/debug_ll.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-at91/include/mach/debug_ll.h b/arch/arm/mach-at91/include/mach/debug_ll.h
index 1a85ae4..42728a4 100644
--- a/arch/arm/mach-at91/include/mach/debug_ll.h
+++ b/arch/arm/mach-at91/include/mach/debug_ll.h
@@ -11,7 +11,7 @@
#include <asm/io.h>
#include <mach/hardware.h>
-#ifdef COFNIG_HAVE_AT91_DBGU0
+#ifdef CONFIG_HAVE_AT91_DBGU0
#define UART_BASE AT91_BASE_DBGU0
#else
#define UART_BASE AT91_BASE_DBGU1
--
1.7.2.5
On 12/03/2013 17:52, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 16:39 Tue 12 Mar , Renaud C. wrote:
>> This patch fix the debug unit output by correcting a typo into an #ifdef
>> statement.
> please resend the whole patch with inline patch
>
> no review otherwise
>
> Best Regards,
> J.
>
>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-03-13 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 15:39 [PATCH 1/7] AT91 debug unit typo fix Renaud C.
2013-03-12 16:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-13 10:14 ` Cerrato Renaud [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=5140519B.6000103@til-technologies.fr \
--to=r.cerrato@til-technologies.fr \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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.