* [PATCH] PCI: acpiphp: Fixed coding style of open braces and comments
@ 2021-03-07 23:54 chakravarthikulkarni
0 siblings, 0 replies; only message in thread
From: chakravarthikulkarni @ 2021-03-07 23:54 UTC (permalink / raw)
Cc: chakravarthikulkarni2021, Rafael J. Wysocki, Len Brown,
Bjorn Helgaas, linux-acpi, linux-pci, linux-kernel
Fixed WARNING and ERROR message provided by ./checkpatch.pl scripts.
Signed-off-by: chakravarthi kulkarni <chakravarthikulkarni2021@gmail.com>
---
drivers/pci/hotplug/acpiphp.h | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/pci/hotplug/acpiphp.h b/drivers/pci/hotplug/acpiphp.h
index a74b274a8c45..e0964600a78f 100644
--- a/drivers/pci/hotplug/acpiphp.h
+++ b/drivers/pci/hotplug/acpiphp.h
@@ -80,8 +80,8 @@ struct acpiphp_bridge {
struct acpiphp_slot {
struct list_head node;
struct pci_bus *bus;
- struct list_head funcs; /* one slot may have different
- objects (i.e. for each function) */
+ struct list_head funcs; /* one slot may have different */
+ /* objects (i.e. for each function) */
struct slot *slot;
u8 device; /* pci device# */
@@ -148,8 +148,7 @@ static inline struct acpiphp_root_context *to_acpiphp_root_context(struct acpi_h
* ACPI has no generic method of setting/getting attention status
* this allows for device specific driver registration
*/
-struct acpiphp_attention_info
-{
+struct acpiphp_attention_info {
int (*set_attn)(struct hotplug_slot *slot, u8 status);
int (*get_attn)(struct hotplug_slot *slot, u8 *status);
struct module *owner;
--
2.17.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2021-03-07 23:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-07 23:54 [PATCH] PCI: acpiphp: Fixed coding style of open braces and comments chakravarthikulkarni
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).