linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Chen Miao <chenmiao.ku@gmail.com>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	alexs@kernel.org, si.yanteng@linux.dev,
	skhan@linuxfoundation.org, mchehab@kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] docs: sphinx-pre-install: add macOS Homebrew support
Date: Mon, 10 Aug 2026 11:47:57 +0800	[thread overview]
Message-ID: <anlJ7YQzjJ9qlZfA@wyuan.org> (raw)
In-Reply-To: <87tsp2j543.fsf@trenco.lwn.net>

On Sun, Aug 09, 2026 at 04:34:04PM -0600, Jonathan Corbet wrote:
> Chen Miao <chenmiao.ku@gmail.com> writes:
> 
> > Thanks for the clarification. I'll first check whether the kernel documentation
> > already has something like a "macOS kernel development guide." If not, I think
> > it might be worth documenting this.
> >
> > In particular, macOS uses a case-insensitive APFS volume by default, which can
> > cause unexpected problems for newcomers working with the Linux kernel source
> > tree. It would be unfortunate if there were no documentation covering the
> > things developers need to be aware of when doing kernel development on macOS.
> > That said, I suspect this would be better handled in a separate patch series.
> >
> > Of course, if such documentation already exists, then that's even better, and
> > there would be no need to add another one.
> 
> There is no such guide now.
> 
> Correct me if I'm wrong, but I *think* that absence reflects the fact
> that Linux kernel development is mostly done on Linux systems?

Yes, I think so. But while macOS is not a common platform for kernel
development itself, it might still be worthwhile to make things a little
easier for people who want to contribute to the kernel *documentation*
from macOS.

That said, I don't have any data on how many people would actually want
to work on the documentation from macOS. In my own case, though, there
have been a few times when I only had an Apple machine available and
still needed to get some work done.

So overall, if supporting that use case is not too complicated and does
not create much of a maintenance burden, having one more option
available does not seem like a bad thing.

Thanks.

> We can certainly add such a guide if somebody is willing to write it,
> and if it would be useful to people.

  reply	other threads:[~2026-08-10  3:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 10:19 [PATCH v1 0/2] docs: sphinx-pre-install: improve dependency checks Chen Miao
2026-08-09 10:19 ` [PATCH v1 1/2] docs: sphinx-pre-install: add macOS Homebrew support Chen Miao
2026-08-09 13:02   ` Weijie Yuan
2026-08-09 13:21     ` Dongliang Mu
2026-08-09 14:11       ` Weijie Yuan
2026-08-09 19:07         ` Chen Miao
2026-08-09 22:34           ` Jonathan Corbet
2026-08-10  3:47             ` Weijie Yuan [this message]
2026-08-10  5:12               ` Chen Miao
2026-08-09 18:59     ` Chen Miao
2026-08-09 10:19 ` [PATCH v1 2/2] docs: sphinx-pre-install: check GNU Make version Chen Miao
2026-08-09 17:18   ` Mauro Carvalho Chehab
2026-08-09 19:11     ` Chen Miao

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=anlJ7YQzjJ9qlZfA@wyuan.org \
    --to=wy@wyuan.org \
    --cc=alexs@kernel.org \
    --cc=chenmiao.ku@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=si.yanteng@linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).