From: Christian Brauner <brauner@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Christian Brauner <brauner@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libfs: fix table format warning
Date: Tue, 4 Jul 2023 09:47:51 +0200 [thread overview]
Message-ID: <20230704-yacht-pfeffer-567bbd67d7f7@brauner> (raw)
In-Reply-To: <20230704044643.8622-1-rdunlap@infradead.org>
On Mon, 03 Jul 2023 21:46:43 -0700, Randy Dunlap wrote:
> Drop the unnecessary colon to make the table formatting correct.
> The colons are not needed and this file uses them sometimes and
> doesn't at other times. Generally they are not preferred in
> documentation tables IMO.
>
> Also extend the table line widths to match the table text.
>
> [...]
I've folded this fix into Chuck's series. Thanks!
---
Applied to the vfs.readdir branch of the vfs/vfs.git tree.
Patches in the vfs.readdir branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.readdir
[1/1] libfs: Add directory operations for stable offsets
https://git.kernel.org/vfs/vfs/c/2b1732fc0a7c
prev parent reply other threads:[~2023-07-04 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 4:46 [PATCH] libfs: fix table format warning Randy Dunlap
2023-07-04 7:47 ` Christian Brauner [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=20230704-yacht-pfeffer-567bbd67d7f7@brauner \
--to=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).