From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Joe Perches <joe@perches.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH v2 1/1] docs: Update documentation to avoid mentioning of kernel.h
Date: Sun, 28 Dec 2025 20:02:01 +0200 [thread overview]
Message-ID: <aVFwmfInXYL_ZByA@smile.fi.intel.com> (raw)
In-Reply-To: <87fr9218jr.fsf@trenco.lwn.net>
On Mon, Dec 22, 2025 at 03:00:24PM -0700, Jonathan Corbet wrote:
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
>
> > For several years, and still ongoing, the kernel.h is being split
> > to smaller and narrow headers to avoid "including everything" approach
> > which is bad in many ways. Since that, documentation missed a few
> > required updates to align with that work. Do it here.
> >
> > Note, language translations are left untouched and if anybody willing
> > to help, please provide path(es) based on the updated English variant.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> > ---
> >
> > v2: collected tag (Randy), fixed util_macros k-doc (Randy, me), fixed spelling (Randy)
> >
> > Documentation/core-api/kobject.rst | 2 +-
> > Documentation/dev-tools/checkpatch.rst | 2 +-
> > Documentation/driver-api/basics.rst | 17 ++++++++++++++++-
> > .../driver-api/driver-model/design-patterns.rst | 2 +-
> > Documentation/process/coding-style.rst | 10 +++++++---
> > Documentation/staging/rpmsg.rst | 7 +++++--
> > include/linux/util_macros.h | 2 +-
> > 7 files changed, 32 insertions(+), 10 deletions(-)
>
> Applied (finally) thanks.
Thank you! I leave the translations to the respective maintainers and native
speakers to decide.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-12-28 18:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 21:46 Andy Shevchenko
2025-11-27 0:26 ` Randy Dunlap
2025-11-29 15:24 ` Andy Shevchenko
2025-11-29 15:54 ` Jonathan Corbet
2025-11-29 17:46 ` Andy Shevchenko
2025-11-27 17:34 ` Joe Perches
2025-11-27 18:19 ` Andy Shevchenko
2025-12-05 11:15 ` [PATCH] Doc:it_IT: Do not reference kernel.h anymore Andi Shyti
2025-12-15 0:30 ` Federico Vaga
2025-12-15 16:14 ` Andi Shyti
2025-12-17 22:48 ` Federico Vaga
2025-12-22 22:01 ` Jonathan Corbet
2025-12-23 21:22 ` Federico Vaga
2025-12-23 21:34 ` Jonathan Corbet
2025-12-05 15:25 ` [PATCH v2 1/1] docs: Update documentation to avoid mentioning of kernel.h Mathieu Poirier
2025-12-22 22:00 ` Jonathan Corbet
2025-12-28 18:02 ` Andy Shevchenko [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=aVFwmfInXYL_ZByA@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andersson@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dwaipayanray1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@treblig.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mathieu.poirier@linaro.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=workflows@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