From: Greg KH <gregkh@linuxfoundation.org>
To: Alissa Guo <guoalissa@gmail.com>
Cc: skhan@linuxfoundation.org, akpm@linux-foundation.org,
brauner@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation: key header files: fix member variable description warnings
Date: Wed, 31 Jul 2024 07:30:02 +0200 [thread overview]
Message-ID: <2024073138-attest-onset-473e@gregkh> (raw)
In-Reply-To: <20240731043609.9762-1-guoalissa@gmail.com>
On Tue, Jul 30, 2024 at 09:35:59PM -0700, Alissa Guo wrote:
> Signed-off-by: Alissa Guo <guoalissa@gmail.com>
For obvious reasons, we can't take changes with no changelog text at
all. Please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-31 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 4:35 [PATCH] documentation: key header files: fix member variable description warnings Alissa Guo
2024-07-31 5:30 ` Greg KH [this message]
2024-08-01 0:51 ` Alissa Guo
2024-08-01 17:42 ` Shuah Khan
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=2024073138-attest-onset-473e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=guoalissa@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox