From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 650C3C001E0 for ; Thu, 27 Jul 2023 15:38:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231799AbjG0PiI (ORCPT ); Thu, 27 Jul 2023 11:38:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233368AbjG0PiE (ORCPT ); Thu, 27 Jul 2023 11:38:04 -0400 Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A0BC61FFC; Thu, 27 Jul 2023 08:38:03 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 19C5B5C0167; Thu, 27 Jul 2023 11:38:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 27 Jul 2023 11:38:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=davidreaver.com; h=cc:cc:content-type:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1690472283; x= 1690558683; bh=gSa2UE+tG+6ppJSX7+/fH6rMPkCm1rn2JSAsjLzC194=; b=e wEh34iZWiAQ2T7UejitYODzQ5DWGyK+gPKwM6HTiqIJrTLWUtxT0jc0GqJ++6fTE 117LEiBg5HA+GUebwrfjkhEiSEf49KWLF2y1a/PvUApW8y8fFV5vesb2jpqTXXGA y6e84vNkq5E7pojrfdI+1igrbc0yZa1NcTRU888wK3Bc8qArxeXAEBkWXtU8BvoD gfg0iHXCcWBzVFg03w9TVmuSxaS5JBTLiMTkVbPLqw+5KF7oDIYb/HkhXcIBBisO 2nWX8lfIGuORPyUh9lY7PDozRScNjZZOLWVMN3YA7bcfZVzYZt+u73/Kq73oVoxU rF9wyy0MkRHoEVrTECmlA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1690472283; x=1690558683; bh=gSa2UE+tG+6pp JSX7+/fH6rMPkCm1rn2JSAsjLzC194=; b=YcPsXyNfVHw4nWK00SBx/jXr5Syt9 5TrA+JDktsPKJSCuCHzHpr0uMNUQIdXfLyWnNjF/v/1t4GRXtlfLidmSa+SiuSBU 12TE4NH3+lxiDrLnsDJFfbMn5sDJbFC22GzXgoKNk8NU3b7UemokiUFZRDcLaBhO jdMNwom+RrkQXmC1XpuVasC8h7jriKhMprjj+BcrmQrr3c6w+bVAS/A5p7N0JJg/ iD63K0a2TAkATR2nYjl0qRGf+LNk8cF1kBh+TSsxwoOzws6QOIllE3VnGPs/3EJA 2tRVYJXQNXtHrGaSjvtYWY1I8+xzLAKEVi049InIbmXKksDTtTs6kLQmA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrieeggdeihecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpehffgfhvfevufffjgfkgggtsehttdertddtredtnecuhfhrohhmpeffrghvihgu ucftvggrvhgvrhcuoehmvgesuggrvhhiughrvggrvhgvrhdrtghomheqnecuggftrfgrth htvghrnhepvefhleffvedtfeduuddviefhheetvedugeeludfhgfevveetgeffkeetvedu uedtnecuffhomhgrihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmvgesuggrvhhiughrvggrvhgvrhdrtgho mh X-ME-Proxy: Feedback-ID: i67e946c9:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 27 Jul 2023 11:38:01 -0400 (EDT) References: <20230727152234.86923-1-me@davidreaver.com> <87o7jx5q4d.fsf@meer.lwn.net> User-agent: mu4e 1.10.4; emacs 28.2 From: David Reaver To: Jonathan Corbet Cc: Dave Jiang , Dan Williams , Jonathan Cameron , 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 In-reply-to: <87o7jx5q4d.fsf@meer.lwn.net> Message-ID: <86mszhjrfr.fsf@davidreaver.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org Jonathan Corbet 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