linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "tip-bot2 for Alex Shi" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alex Shi <alex.shi@linux.alibaba.com>,
	Borislav Petkov <bp@suse.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cleanups] x86/PCI: Make a kernel-doc comment a normal one
Date: Fri, 27 Nov 2020 13:06:27 -0000	[thread overview]
Message-ID: <160648238740.3364.16081084412087294713.tip-bot2@tip-bot2> (raw)
In-Reply-To: <1605257895-5536-5-git-send-email-alex.shi@linux.alibaba.com>

The following commit has been merged into the x86/cleanups branch of tip:

Commit-ID:     638920a66a17c8e1f4415cbab0d49dc4a344c2a7
Gitweb:        https://git.kernel.org/tip/638920a66a17c8e1f4415cbab0d49dc4a344c2a7
Author:        Alex Shi <alex.shi@linux.alibaba.com>
AuthorDate:    Fri, 13 Nov 2020 16:58:14 +08:00
Committer:     Borislav Petkov <bp@suse.de>
CommitterDate: Fri, 27 Nov 2020 13:43:09 +01:00

x86/PCI: Make a kernel-doc comment a normal one

The comment is using kernel-doc markup but that comment isn't a
kernel-doc comment so make it a normal one to avoid:

  arch/x86/pci/i386.c:373: warning: Function parameter or member \
	  'pcibios_assign_resources' not described in 'fs_initcall'

 [ bp: Massage and fixup comment while at it. ]

Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/1605257895-5536-5-git-send-email-alex.shi@linux.alibaba.com
---
 arch/x86/pci/i386.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/x86/pci/i386.c b/arch/x86/pci/i386.c
index fa855bb..f2f4a5d 100644
--- a/arch/x86/pci/i386.c
+++ b/arch/x86/pci/i386.c
@@ -366,9 +366,9 @@ static int __init pcibios_assign_resources(void)
 	return 0;
 }
 
-/**
- * called in fs_initcall (one below subsys_initcall),
- * give a chance for motherboard reserve resources
+/*
+ * This is an fs_initcall (one below subsys_initcall) in order to reserve
+ * resources properly.
  */
 fs_initcall(pcibios_assign_resources);
 

  reply	other threads:[~2020-11-27 13:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  8:58 [PATCH] PM / suspend: fix kernel-doc markup Alex Shi
2020-11-13  8:58 ` [PATCH] locking/rtmutex: add missed " Alex Shi
2021-01-12 13:28   ` Will Deacon
2021-01-27 19:31   ` [tip: locking/core] locking/rtmutex: Add missing " tip-bot2 for Alex Shi
2021-01-28 12:21   ` tip-bot2 for Alex Shi
2020-11-13  8:58 ` [PATCH] locking/rtmutex: remove useless parameter for rt_mutex_proxy_unlock Alex Shi
2021-01-12 13:31   ` Will Deacon
2020-11-13  8:58 ` [PATCH] configfs: fix kernel-doc markup issue Alex Shi
2020-11-14  9:26   ` Christoph Hellwig
2020-11-13  8:58 ` [PATCH] x86/PCI: fix a comments issue Alex Shi
2020-11-27 13:06   ` tip-bot2 for Alex Shi [this message]
2020-11-13  8:58 ` [PATCH] PKCS#7: drop function from kernel-doc pkcs7_validate_trust_one Alex Shi
2020-11-23 17:26 ` [PATCH] PM / suspend: fix kernel-doc markup Rafael J. Wysocki

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=160648238740.3364.16081084412087294713.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=alex.shi@linux.alibaba.com \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=x86@kernel.org \
    /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).