All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Linus Walleij <linusw@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	linux-arm-kernel@lists.infradead.org,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] ARM: zte: clean up zx297520v3 doc. warnings
Date: Fri, 22 May 2026 22:31:12 +0300	[thread overview]
Message-ID: <6270885.lOV4Wx5bFT@strix> (raw)
In-Reply-To: <503916c8-da3b-42dd-812e-356f519be47f@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 504 bytes --]

Hi Randy,

Am Freitag, 22. Mai 2026, 20:44:24 Ostafrikanische Zeit schrieben Sie:
> Does this mean that you will be merging this patch since you merged the
> original patch?

I am new to the kernel development process, so I don't know what's the 
preferred way. I guess for me it is easier if your patch gets merged as-is.

I can certainly submit a pull request myself though since I made myself the 
maintainer for this thing. Does that go to linux-doc@vger.kernel.org or the 
soc list?

Cheers,
Stefan

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]

  reply	other threads:[~2026-05-22 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 19:14 [PATCH] ARM: zte: clean up zx297520v3 doc. warnings Randy Dunlap
2026-05-21 23:26 ` Bagas Sanjaya
2026-05-22  7:09 ` Stefan Dösinger
2026-05-22 17:44   ` Randy Dunlap
2026-05-22 19:31     ` Stefan Dösinger [this message]
2026-05-22 21:20       ` Randy Dunlap
2026-05-26  8:58         ` Stefan Dösinger

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=6270885.lOV4Wx5bFT@strix \
    --to=stefandoesinger@gmail.com \
    --cc=corbet@lwn.net \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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 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.