From: Andy Gross <andy.gross@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH] arm64: dts: msm8996: fix blsp2_uart1 4-pin pinconfig
Date: Thu, 14 Feb 2019 10:14:07 -0600 [thread overview]
Message-ID: <20190214161407.GA18332@hector.attlocal.net> (raw)
In-Reply-To: <20190213090544.GE28278@localhost>
On Wed, Feb 13, 2019 at 10:05:44AM +0100, Johan Hovold wrote:
> That's funny, submitted six days before mine for a 2+ year old issue.
I can't tell you how many times I've seen this happen (to myself and others).
Andy
prev parent reply other threads:[~2019-02-14 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 16:17 [PATCH] arm64: dts: msm8996: fix blsp2_uart1 4-pin pinconfig Johan Hovold
2019-02-11 9:37 ` Johan Hovold
2019-02-12 21:06 ` Andy Gross
2019-02-13 9:05 ` Johan Hovold
2019-02-14 16:14 ` Andy Gross [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=20190214161407.GA18332@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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