From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH] Remove duplicated words in documentation and comments
Date: Fri, 14 Mar 2025 06:27:44 +0100 [thread overview]
Message-ID: <9d891dd7-849c-414a-b8d9-3284d96ef9c6@redhat.com> (raw)
In-Reply-To: <Z9OZEMY0iD9FNEO2@zatzit>
On 14/03/2025 03.48, David Gibson wrote:
> On Thu, Mar 13, 2025 at 08:05:27PM +0100, Thomas Huth wrote:
>> Let's avoid repeating single words here!
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>
> Applied, thanks.
>
> What brings you to making dtc patches?
I'm currently trying to clean the __ASSEMBLY__ vs. __ASSEMBLER__ stuff in
the kernel, where I saw that they have a copy of fdt.h in their tree, so the
origin needs to be fixed, too. While checking dtc, I noticed that I had this
long-forgotten patch here sitting in my local copy of the repo since years,
so I thought it would finally be a good point in time to finally send it out :-)
Thomas
prev parent reply other threads:[~2025-03-14 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 19:05 [PATCH] Remove duplicated words in documentation and comments Thomas Huth
2025-03-14 2:48 ` David Gibson
2025-03-14 5:27 ` Thomas Huth [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=9d891dd7-849c-414a-b8d9-3284d96ef9c6@redhat.com \
--to=thuth@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).