All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Akihiko Odaki <akihiko.odaki@daynix.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, Tushar Dave <tdave@nvidia.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Vidya Sagar <vidyas@nvidia.com>,
	Vikram Sethi <vsethi@nvidia.com>,
	Shanker Donthineni <sdonthineni@nvidia.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Huth <thuth@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Xiongwei Song <xiongwei.song@windriver.com>
Subject: Re: [PATCH] Documentation: Fix config_acs= example
Date: Tue, 14 Jan 2025 09:32:26 +0900	[thread overview]
Message-ID: <20250114003226.GA1810889@rocinante> (raw)
In-Reply-To: <20250113174035.GA408797@bhelgaas>

Hello,

[...]
> Thanks for the patch.  Krzysztof added a bit to the commit log at:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?id=57722057d762
> 
> but I think we should also include the flags template:
> 
>   config_acs =
>                 Format:
>                 <ACS flags>@<pci_dev>[; ...]
> 
> so the commit log includes a hint about what "flag specification"
> means.

I amended the commit log.  Should now include the above for reference.

	Krzysztof

  reply	other threads:[~2025-01-14  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-15  1:36 [PATCH] Documentation: Fix config_acs= example Akihiko Odaki
2025-01-11  5:20 ` Akihiko Odaki
2025-01-13 17:40 ` Bjorn Helgaas
2025-01-14  0:32   ` Krzysztof Wilczyński [this message]
2025-01-15 11:17 ` Krzysztof Wilczyński

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=20250114003226.GA1810889@rocinante \
    --to=kwilczynski@kernel.org \
    --cc=akihiko.odaki@daynix.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=helgaas@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sdonthineni@nvidia.com \
    --cc=tdave@nvidia.com \
    --cc=thuth@redhat.com \
    --cc=vidyas@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=xiongwei.song@windriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.