From: Rob Herring <robh@kernel.org>
To: Colin King <colin.king@canonical.com>
Cc: Andy Gross <agross@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bus: qcom: fix spelling mistake "ambigous" -> "ambiguous"
Date: Fri, 13 Sep 2019 17:01:38 -0500 [thread overview]
Message-ID: <20190913220138.GA17592@bogus> (raw)
In-Reply-To: <20190911153947.10203-1-colin.king@canonical.com>
On Wed, 11 Sep 2019 16:39:47 +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake on the documentation. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> Documentation/devicetree/bindings/bus/qcom,ebi2.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied, thanks.
Rob
prev parent reply other threads:[~2019-09-13 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:39 [PATCH] bus: qcom: fix spelling mistake "ambigous" -> "ambiguous" Colin King
2019-09-13 22:01 ` Rob Herring [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=20190913220138.GA17592@bogus \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=colin.king@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox