public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Philipp Stanner <pstanner@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the pci tree
Date: Tue, 2 Jul 2024 05:15:32 +0900	[thread overview]
Message-ID: <20240701201532.GA272504@rocinante> (raw)
In-Reply-To: <20240701193748.GA13881@bhelgaas>

Hello,

[...]
> > After merging the pci tree, today's linux-next build (htmldocs) produced
> > this warning:
> > 
> > Documentation/driver-api/pci/pci:10: drivers/pci/devres.c:556: WARNING: Inline emphasis start-string without end-string.
> > 
> > Introduced by commit
> > 
> >   06fa2e1e9116 ("PCI: Deprecate pcim_iomap_table(), pcim_iomap_regions_request_all()")
> 
> I fixed by changing * to \* here:
> 
>   * void __iomem \*mappy = pcim_iomap(pdev, bar, length);

I wonder if the following hack would work too:

  void __iomem * mappy = pcim_iomap(pdev, bar, length);

Separate the asterisks from the name, so that the parser will no longer try
to make "mappy" bold.

Also, "mappy"... Philipp, this is so amazingly cringe. :)

    Krzysztof

  reply	other threads:[~2024-07-01 20:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  9:24 linux-next: build warning after merge of the pci tree Stephen Rothwell
2024-07-01 19:37 ` Bjorn Helgaas
2024-07-01 20:15   ` Krzysztof Wilczyński [this message]
2024-07-02  6:59     ` Philipp Stanner
  -- strict thread matches above, loose matches on Subject: below --
2025-07-18 12:41 Stephen Rothwell
2025-05-21 10:26 Stephen Rothwell
2025-05-21 12:10 ` Krzysztof Wilczyński
2025-03-03  7:26 Stephen Rothwell
2025-03-03  7:50 ` Krzysztof Wilczyński
2025-03-03  9:46   ` Krzysztof Wilczyński
2020-09-09  2:38 Stephen Rothwell
2020-09-15  3:43 ` Stephen Rothwell
2020-09-09  2:37 Stephen Rothwell
2020-09-09 16:06 ` Rob Herring
2020-09-15  3:47   ` Stephen Rothwell
2020-09-15 10:53     ` Lorenzo Pieralisi
2020-09-15 17:22       ` Bjorn Helgaas
2020-09-02  1:07 Stephen Rothwell
2020-09-02 12:33 ` Bjorn Helgaas
2020-09-02 14:13   ` Vaibhav Gupta
2020-08-05  1:32 Stephen Rothwell
2020-08-05  2:29 ` Bjorn Helgaas
2016-06-23  1:51 Stephen Rothwell
2016-06-23 16:48 ` Bjorn Helgaas
2016-06-24  8:07   ` Johannes Thumshirn
2013-09-03 23:55 Stephen Rothwell
2013-09-03 23:59 ` Bjorn Helgaas
2012-12-10  9:03 Stephen Rothwell
2012-12-10 21:25 ` Bjorn Helgaas
2012-12-10 23:21   ` Bjorn Helgaas
2012-05-01  6:08 Stephen Rothwell
2012-05-01  7:35 ` Yinghai Lu

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=20240701201532.GA272504@rocinante \
    --to=kw@linux.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=pstanner@redhat.com \
    --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