linux-kernel - [PATCH] usb 'print_schedule_frame' defined but not used warning fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Oct 2006 21:04:08 +0100
From:	Mariusz Kozlowski <m.kozlowski@...land.pl>
To:	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: [PATCH] usb 'print_schedule_frame' defined but not used warning fix

Hello,

	This is a simple fix for this warning:

drivers/usb/host/ehci-sched.c:270: warning: 'print_schedule_frame' defined but 
not used

The print_budget_frame() is not used anywhere in the kernel tree and serves 
debugging purposes only. This patch is against 2.6.19-rc3-mm1.

Regards,

	Mariusz Kozlowski

Signed-off-by: Mariusz Kozlowski <m.kozlowski@...land.pl>
---

--- linux-2.6.19-rc3-orig/drivers/usb/host/ehci-sched.c 2006-10-30 
20:20:30.000000000 +0100
+++ linux-2.6.19-rc3/drivers/usb/host/ehci-sched.c      2006-10-30 
20:39:08.000000000 +0100
@@ -206,6 +206,7 @@ periodic_next_shadow (union ehci_shadow 
 /* the following are merely frame-structure dumpers to aid in
    debugging.  Be careful of their use; they will introduce extreme
    latencies in what is [essentially] realtime code. */
+#if 0
 static void print_budget_frame (struct ehci_hcd *ehci, int frame,
                                struct ehci_shadow_budget *insert,
                                void *owner)
@@ -255,6 +256,7 @@ static void print_budget_frame (struct e
        }
        printk("\n");
 }
+#endif
 
 static void print_budget (struct ehci_hcd *ehci,
                          struct ehci_shadow_budget *insert,
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/