From: David Reaver <me@davidreaver.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Dave Jiang <dave.jiang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: ABI: sysfs-bus-nvdimm: fix unexpected indentation error
Date: Thu, 27 Jul 2023 08:36:46 -0700 [thread overview]
Message-ID: <86mszhjrfr.fsf@davidreaver.com> (raw)
In-Reply-To: <87o7jx5q4d.fsf@meer.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
>
> Thanks for the patch. This problem is already fixed in docs-next,
> though, and thus in linux-next as well.
>
> jon
Ah, sorry Jonathan. I was using Linus' tree, and I must have messed up
the search query I used against https://lore.kernel.org. I'll try to
remember to use docs-next for future docs patches.
Thanks,
David
prev parent reply other threads:[~2023-07-27 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 15:22 [PATCH] docs: ABI: sysfs-bus-nvdimm: fix unexpected indentation error David Reaver
2023-07-27 15:30 ` Jonathan Corbet
2023-07-27 15:36 ` David Reaver [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=86mszhjrfr.fsf@davidreaver.com \
--to=me@davidreaver.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).