The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Chen Miao <chenmiao.ku@gmail.com>, Weijie Yuan <wy@wyuan.org>
Cc: 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: Sun, 09 Aug 2026 16:34:04 -0600	[thread overview]
Message-ID: <87tsp2j543.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAKxVwgdjNjDLWpR2WPOdsXKhusobwq_52ioB5J15gdD2C=obvQ@mail.gmail.com>

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?

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

Thanks,

jon

  reply	other threads:[~2026-08-09 22:34 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 [this message]
2026-08-10  3:47             ` Weijie Yuan
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=87tsp2j543.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=chenmiao.ku@gmail.com \
    --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 \
    --cc=wy@wyuan.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