From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, linux-doc@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Ahmed S. Darwish" <darwi@linutronix.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] PCI/MSI: api: Use bullet lists in kernel-doc comments
Date: Tue, 22 Nov 2022 10:44:18 +0700 [thread overview]
Message-ID: <Y3xFkgq5rdUxB52A@debian.me> (raw)
In-Reply-To: <20221121123402.GA100653@bhelgaas>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Mon, Nov 21, 2022 at 06:34:02AM -0600, Bjorn Helgaas wrote:
> Hi Bagas,
>
> If you have opportunity, please update the subject line to remove
> "api: " to match previous history:
>
> PCI/MSI: Correct 'can_mask' test in msi_add_msi_desc()
> PCI/MSI: Remove bogus warning in pci_irq_get_affinity()
> PCI/MSI: Prevent UAF in error path
> PCI/MSI: Unbreak pci_irq_get_affinity()
> PCI/MSI: Use msi_on_each_desc()
> PCI/MSI: Let core code free MSI descriptors
> PCI/MSI: Use msi_add_msi_desc()
> PCI/MSI: Protect MSI operations
> PCI/MSI: Simplify pci_irq_get_affinity()
> ...
OK, thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-22 3:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 7:41 linux-next: build warnings after merge of the tip tree Stephen Rothwell
2022-11-21 10:12 ` [PATCH] PCI/MSI: api: Use bullet lists in kernel-doc comments Bagas Sanjaya
2022-11-21 12:34 ` Bjorn Helgaas
2022-11-22 3:44 ` Bagas Sanjaya [this message]
2022-11-21 13:27 ` Ahmed S. Darwish
2022-11-22 3:43 ` Bagas Sanjaya
2022-11-22 5:56 ` Ahmed S. Darwish
2022-11-22 8:11 ` Bagas Sanjaya
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=Y3xFkgq5rdUxB52A@debian.me \
--to=bagasdotme@gmail.com \
--cc=bhelgaas@google.com \
--cc=darwi@linutronix.de \
--cc=helgaas@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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.