From: Ingo van Lil <inguin@gmx.de>
To: Peter Rosin <peda@axentia.se>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: [PATCH] ARM: dts: at91: Reenable UART TX pull-ups
Date: Tue, 3 Dec 2019 14:22:15 +0100 [thread overview]
Message-ID: <5b7ff913-bca7-2695-ab72-76350778a577@gmx.de> (raw)
In-Reply-To: <8e8dfc02-bdab-d6f1-f6e9-e1dba7e38bfd@axentia.se>
On 12/3/19 2:04 PM, Peter Rosin wrote:
> Sounds reasonable, and sorry for the breakage. However, perhaps a proper
> fixes tag (with the prescribed length of the commit hash) should be in
> there somewhere?
Sounds good, I will add one.
> Also, I think the same kind of change was made to the barebox bootloader
> at about the same time. Is there a fix for that queued up as well?
Sorry, I'm not familiar with Barebox. We use u-boot.
Regards,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo van Lil <inguin@gmx.de>
To: Peter Rosin <peda@axentia.se>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: [PATCH] ARM: dts: at91: Reenable UART TX pull-ups
Date: Tue, 3 Dec 2019 14:22:15 +0100 [thread overview]
Message-ID: <5b7ff913-bca7-2695-ab72-76350778a577@gmx.de> (raw)
In-Reply-To: <8e8dfc02-bdab-d6f1-f6e9-e1dba7e38bfd@axentia.se>
On 12/3/19 2:04 PM, Peter Rosin wrote:
> Sounds reasonable, and sorry for the breakage. However, perhaps a proper
> fixes tag (with the prescribed length of the commit hash) should be in
> there somewhere?
Sounds good, I will add one.
> Also, I think the same kind of change was made to the barebox bootloader
> at about the same time. Is there a fix for that queued up as well?
Sorry, I'm not familiar with Barebox. We use u-boot.
Regards,
Ingo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-03 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 10:06 [PATCH] ARM: dts: at91: Reenable UART TX pull-ups Ingo van Lil
2019-11-28 10:06 ` Ingo van Lil
2019-12-03 13:04 ` Peter Rosin
2019-12-03 13:04 ` Peter Rosin
2019-12-03 13:22 ` Ingo van Lil [this message]
2019-12-03 13:22 ` Ingo van Lil
2019-12-03 14:21 Ingo van Lil
2019-12-03 14:21 ` Ingo van Lil
2019-12-10 10:57 ` Alexandre Belloni
2019-12-10 10:57 ` Alexandre Belloni
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=5b7ff913-bca7-2695-ab72-76350778a577@gmx.de \
--to=inguin@gmx.de \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=peda@axentia.se \
/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.