The patch titled
usb/usbtest: comment on why this code "expects" negative and positive errnos
has been removed from the -mm tree. Its filename was
usb-usbtest-comment-on-why-this-code-expects-negative-and-positive-errnos.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: usb/usbtest: comment on why this code "expects" negative and positive errnos
From: Marcin Slusarz <marcin.slusarz@xxxxxxxxx>
Based on comment from David Brownell <david-b@xxxxxxxxxxx>.
Signed-off-by: Marcin Slusarz <marcin.slusarz@xxxxxxxxx>
Cc: David Brownell <david-b@xxxxxxxxxxx>
Cc: Greg KH <greg@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/usb/misc/usbtest.c | 5 +++++
1 file changed, 5 insertions(+)
diff -puN drivers/usb/misc/usbtest.c~usb-usbtest-comment-on-why-this-code-expects-negative-and-positive-errnos drivers/usb/misc/usbtest.c
--- a/drivers/usb/misc/usbtest.c~usb-usbtest-comment-on-why-this-code-expects-negative-and-positive-errnos
+++ a/drivers/usb/misc/usbtest.c
@@ -856,6 +856,11 @@ test_ctrl_queue (struct usbtest_dev *dev
struct urb *u;
struct usb_ctrlrequest req;
struct subcase *reqp;
+
+ /* sign of this variable means:
+ * -: tested code must return this (negative) error code
+ * +: tested code may return this (negative too) error code
+ */
int expected = 0;
/* requests here are mostly expected to succeed on any
_
Patches currently in -mm which might be from marcin.slusarz@xxxxxxxxx are
origin.patch
linux-next.patch
drm-radeon-radeon_enable_vblank-should-return-negative-error.patch
git-jfs.patch
isdn-capi-return-proper-errnos-on-module-init.patch
net-s2io-set_rxd_buffer_pointer-returns-enomem-not-enomem.patch
ntfs-le_add_cpu-conversion.patch
tty_check_change-avoid-taking-tasklist_lock-while-holding-tty-ctrl_lock.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
