Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* linux-next: build warning after merge of the usb tree
@ 2010-11-17  2:14 Stephen Rothwell
  2010-11-17  4:20 ` Greg KH
       [not found] ` <20101116215906.GA2869@kroah.com>
  0 siblings, 2 replies; 39+ messages in thread
From: Stephen Rothwell @ 2010-11-17  2:14 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-next, linux-kernel, Michal Nazarewicz


[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Hi Greg,

After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:

In file included from drivers/usb/gadget/g_ffs.c:64:
drivers/usb/gadget/f_fs.c:30:1: warning: "pr_fmt" redefined
In file included from include/linux/kernel.h:20,
                 from arch/x86/include/asm/percpu.h:44,
                 from arch/x86/include/asm/current.h:5,
                 from arch/x86/include/asm/processor.h:15,
                 from include/linux/prefetch.h:14,
                 from include/linux/list.h:7,
                 from include/linux/module.h:9,
                 from drivers/usb/gadget/g_ffs.c:22:
include/linux/printk.h:161:1: warning: this is the location of the previous definition

Introduced by commit d8df0b611c66db3b7afd0678213979209616681a ("usb:
gadget: f_fs: remove custom printk() wrappers").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2010-11-17  2:14 linux-next: build warning after merge of the usb tree Stephen Rothwell
@ 2010-11-17  4:20 ` Greg KH
       [not found] ` <20101116215906.GA2869@kroah.com>
  1 sibling, 0 replies; 39+ messages in thread
From: Greg KH @ 2010-11-17  4:20 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Michal Nazarewicz

On Wed, Nov 17, 2010 at 01:14:27PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> In file included from drivers/usb/gadget/g_ffs.c:64:
> drivers/usb/gadget/f_fs.c:30:1: warning: "pr_fmt" redefined
> In file included from include/linux/kernel.h:20,
>                  from arch/x86/include/asm/percpu.h:44,
>                  from arch/x86/include/asm/current.h:5,
>                  from arch/x86/include/asm/processor.h:15,
>                  from include/linux/prefetch.h:14,
>                  from include/linux/list.h:7,
>                  from include/linux/module.h:9,
>                  from drivers/usb/gadget/g_ffs.c:22:
> include/linux/printk.h:161:1: warning: this is the location of the previous definition
> 
> Introduced by commit d8df0b611c66db3b7afd0678213979209616681a ("usb:
> gadget: f_fs: remove custom printk() wrappers").

Thanks, I told Michal about this, he should be sending me a patch for it
soon.

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* [PATCH] usb: gadget: g_fs: Fix compilation warning
       [not found] ` <20101116215906.GA2869@kroah.com>
@ 2010-11-17 16:09   ` Michal Nazarewicz
       [not found]     ` <0c1bd123752a7adc7f034ef81d155903da115081.1290007778.git.mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
  0 siblings, 1 reply; 39+ messages in thread
From: Michal Nazarewicz @ 2010-11-17 16:09 UTC (permalink / raw)
  To: Greg KH
  Cc: Stephen Rothwell, linux-usb, linux-next, linux-kernel, Michal Nazarewicz

This commit fixes warning in f_fs.c introduced by "usb:
gadget: f_fs: remove custom printk() wrappers":

In file included from drivers/usb/gadget/g_ffs.c:64:
drivers/usb/gadget/f_fs.c:30:1: warning: "pr_fmt" redefined

Signed-off-by: Michal Nazarewicz <mina86@mina86.com>
---
 drivers/usb/gadget/f_fs.c  |   78 +++++++++++++++++++++----------------------
 drivers/usb/gadget/g_ffs.c |    2 +
 2 files changed, 40 insertions(+), 40 deletions(-)

> On Fri, Nov 12, 2010 at 02:29:29PM +0100, Michal Nazarewicz wrote:
>> diff --git a/drivers/usb/gadget/f_fs.c b/drivers/usb/gadget/f_fs.c
>> @@ -27,6 +27,8 @@
>>  /* #define DEBUG */
>>  /* #define VERBOSE_DEBUG */
>>  
>> +#define pr_fmt(fmt) "f_fs: " fmt "\n"

Greg KH <greg@kroah.com> writes:
> Hm, this causes a compiler warning.  Care to fix this up with a
> follow-up patch as this isn't the way to do this...

Sorry about that.  Fix included.

diff --git a/drivers/usb/gadget/f_fs.c b/drivers/usb/gadget/f_fs.c
index 5950c4b..255969c 100644
--- a/drivers/usb/gadget/f_fs.c
+++ b/drivers/usb/gadget/f_fs.c
@@ -27,8 +27,6 @@
 /* #define DEBUG */
 /* #define VERBOSE_DEBUG */
 
-#define pr_fmt(fmt) "f_fs: " fmt "\n"
-
 #include <linux/blkdev.h>
 #include <linux/pagemap.h>
 #include <asm/unaligned.h>
@@ -46,13 +44,13 @@
 #ifdef VERBOSE_DEBUG
 #  define pr_vdebug pr_debug
 #  define ffs_dump_mem(prefix, ptr, len) \
-	print_hex_dump_bytes("f_fs" prefix ": ", DUMP_PREFIX_NONE, ptr, len)
+	print_hex_dump_bytes(pr_fmt(prefix ": "), DUMP_PREFIX_NONE, ptr, len)
 #else
 #  define pr_vdebug(...)                 do { } while (0)
 #  define ffs_dump_mem(prefix, ptr, len) do { } while (0)
 #endif /* VERBOSE_DEBUG */
 
-#define ENTER()    pr_vdebug("%s()", __func__)
+#define ENTER()    pr_vdebug("%s()\n", __func__)
 
 
 /* The data structure and setup file ****************************************/
@@ -390,12 +388,12 @@ static int __ffs_ep0_queue_wait(struct ffs_data *ffs, char *data, size_t len)
 static int __ffs_ep0_stall(struct ffs_data *ffs)
 {
 	if (ffs->ev.can_stall) {
-		pr_vdebug("ep0 stall");
+		pr_vdebug("ep0 stall\n");
 		usb_ep_set_halt(ffs->gadget->ep0);
 		ffs->setup_state = FFS_NO_SETUP;
 		return -EL2HLT;
 	} else {
-		pr_debug("bogus ep0 stall!");
+		pr_debug("bogus ep0 stall!\n");
 		return -ESRCH;
 	}
 }
@@ -436,7 +434,7 @@ static ssize_t ffs_ep0_write(struct file *file, const char __user *buf,
 
 		/* Handle data */
 		if (ffs->state == FFS_READ_DESCRIPTORS) {
-			pr_info("read descriptors");
+			pr_info("read descriptors\n");
 			ret = __ffs_data_got_descs(ffs, data, len);
 			if (unlikely(ret < 0))
 				break;
@@ -444,7 +442,7 @@ static ssize_t ffs_ep0_write(struct file *file, const char __user *buf,
 			ffs->state = FFS_READ_STRINGS;
 			ret = len;
 		} else {
-			pr_info("read strings");
+			pr_info("read strings\n");
 			ret = __ffs_data_got_strings(ffs, data, len);
 			if (unlikely(ret < 0))
 				break;
@@ -1110,7 +1108,7 @@ static int ffs_fs_parse_opts(struct ffs_sb_fill_data *data, char *opts)
 		/* Value limit */
 		eq = strchr(opts, '=');
 		if (unlikely(!eq)) {
-			pr_err("'=' missing in %s", opts);
+			pr_err("'=' missing in %s\n", opts);
 			return -EINVAL;
 		}
 		*eq = 0;
@@ -1118,7 +1116,7 @@ static int ffs_fs_parse_opts(struct ffs_sb_fill_data *data, char *opts)
 		/* Parse value */
 		value = simple_strtoul(eq + 1, &end, 0);
 		if (unlikely(*end != ',' && *end != 0)) {
-			pr_err("%s: invalid value: %s", opts, eq + 1);
+			pr_err("%s: invalid value: %s\n", opts, eq + 1);
 			return -EINVAL;
 		}
 
@@ -1153,7 +1151,7 @@ static int ffs_fs_parse_opts(struct ffs_sb_fill_data *data, char *opts)
 
 		default:
 invalid:
-			pr_err("%s: invalid option", opts);
+			pr_err("%s: invalid option\n", opts);
 			return -EINVAL;
 		}
 
@@ -1227,9 +1225,9 @@ static int functionfs_init(void)
 
 	ret = register_filesystem(&ffs_fs_type);
 	if (likely(!ret))
-		pr_info("file system registered");
+		pr_info("file system registered\n");
 	else
-		pr_err("failed registering file system (%d)", ret);
+		pr_err("failed registering file system (%d)\n", ret);
 
 	return ret;
 }
@@ -1238,7 +1236,7 @@ static void functionfs_cleanup(void)
 {
 	ENTER();
 
-	pr_info("unloading");
+	pr_info("unloading\n");
 	unregister_filesystem(&ffs_fs_type);
 }
 
@@ -1268,7 +1266,7 @@ static void ffs_data_put(struct ffs_data *ffs)
 	ENTER();
 
 	if (unlikely(atomic_dec_and_test(&ffs->ref))) {
-		pr_info("%s(): freeing", __func__);
+		pr_info("%s(): freeing\n", __func__);
 		ffs_data_clear(ffs);
 		BUG_ON(mutex_is_locked(&ffs->mutex) ||
 		       spin_is_locked(&ffs->ev.waitq.lock) ||
@@ -1588,14 +1586,14 @@ static int __must_check ffs_do_desc(char *data, unsigned len,
 
 	/* At least two bytes are required: length and type */
 	if (len < 2) {
-		pr_vdebug("descriptor too short");
+		pr_vdebug("descriptor too short\n");
 		return -EINVAL;
 	}
 
 	/* If we have at least as many bytes as the descriptor takes? */
 	length = _ds->bLength;
 	if (len < length) {
-		pr_vdebug("descriptor longer then available data");
+		pr_vdebug("descriptor longer then available data\n");
 		return -EINVAL;
 	}
 
@@ -1603,14 +1601,14 @@ static int __must_check ffs_do_desc(char *data, unsigned len,
 #define __entity_check_STRING(val)     (val)
 #define __entity_check_ENDPOINT(val)   ((val) & USB_ENDPOINT_NUMBER_MASK)
 #define __entity(type, val) do {					\
-		pr_vdebug("entity " #type "(%02x)", (val));		\
+		pr_vdebug("entity " #type "(%02x)\n", (val));		\
 		if (unlikely(!__entity_check_ ##type(val))) {		\
-			pr_vdebug("invalid entity's value");		\
+			pr_vdebug("invalid entity's value\n");		\
 			return -EINVAL;					\
 		}							\
 		ret = entity(FFS_ ##type, &val, _ds, priv);		\
 		if (unlikely(ret < 0)) {				\
-			pr_debug("entity " #type "(%02x); ret = %d",	\
+			pr_debug("entity " #type "(%02x); ret = %d\n",	\
 				 (val), ret);				\
 			return ret;					\
 		}							\
@@ -1623,13 +1621,13 @@ static int __must_check ffs_do_desc(char *data, unsigned len,
 	case USB_DT_STRING:
 	case USB_DT_DEVICE_QUALIFIER:
 		/* function can't have any of those */
-		pr_vdebug("descriptor reserved for gadget: %d",
+		pr_vdebug("descriptor reserved for gadget: %d\n",
 		      _ds->bDescriptorType);
 		return -EINVAL;
 
 	case USB_DT_INTERFACE: {
 		struct usb_interface_descriptor *ds = (void *)_ds;
-		pr_vdebug("interface descriptor");
+		pr_vdebug("interface descriptor\n");
 		if (length != sizeof *ds)
 			goto inv_length;
 
@@ -1641,7 +1639,7 @@ static int __must_check ffs_do_desc(char *data, unsigned len,
 
 	case USB_DT_ENDPOINT: {
 		struct usb_endpoint_descriptor *ds = (void *)_ds;
-		pr_vdebug("endpoint descriptor");
+		pr_vdebug("endpoint descriptor\n");
 		if (length != USB_DT_ENDPOINT_SIZE &&
 		    length != USB_DT_ENDPOINT_AUDIO_SIZE)
 			goto inv_length;
@@ -1656,7 +1654,7 @@ static int __must_check ffs_do_desc(char *data, unsigned len,
 
 	case USB_DT_INTERFACE_ASSOCIATION: {
 		struct usb_interface_assoc_descriptor *ds = (void *)_ds;
-		pr_vdebug("interface association descriptor");
+		pr_vdebug("interface association descriptor\n");
 		if (length != sizeof *ds)
 			goto inv_length;
 		if (ds->iFunction)
@@ -1670,16 +1668,16 @@ static int __must_check ffs_do_desc(char *data, unsigned len,
 	case USB_DT_SECURITY:
 	case USB_DT_CS_RADIO_CONTROL:
 		/* TODO */
-		pr_vdebug("unimplemented descriptor: %d", _ds->bDescriptorType);
+		pr_vdebug("unimplemented descriptor: %d\n", _ds->bDescriptorType);
 		return -EINVAL;
 
 	default:
 		/* We should never be here */
-		pr_vdebug("unknown descriptor: %d", _ds->bDescriptorType);
+		pr_vdebug("unknown descriptor: %d\n", _ds->bDescriptorType);
 		return -EINVAL;
 
 inv_length:
-		pr_vdebug("invalid length: %d (descriptor %d)",
+		pr_vdebug("invalid length: %d (descriptor %d)\n",
 			  _ds->bLength, _ds->bDescriptorType);
 		return -EINVAL;
 	}
@@ -1710,7 +1708,7 @@ static int __must_check ffs_do_descs(unsigned count, char *data, unsigned len,
 		/* Record "descriptor" entity */
 		ret = entity(FFS_DESCRIPTOR, (u8 *)num, (void *)data, priv);
 		if (unlikely(ret < 0)) {
-			pr_debug("entity DESCRIPTOR(%02lx); ret = %d",
+			pr_debug("entity DESCRIPTOR(%02lx); ret = %d\n",
 				 num, ret);
 			return ret;
 		}
@@ -1720,7 +1718,7 @@ static int __must_check ffs_do_descs(unsigned count, char *data, unsigned len,
 
 		ret = ffs_do_desc(data, len, entity, priv);
 		if (unlikely(ret < 0)) {
-			pr_debug("%s returns %d", __func__, ret);
+			pr_debug("%s returns %d\n", __func__, ret);
 			return ret;
 		}
 
@@ -2013,11 +2011,11 @@ static void __ffs_event_add(struct ffs_data *ffs,
 			if ((*ev == rem_type1 || *ev == rem_type2) == neg)
 				*out++ = *ev;
 			else
-				pr_vdebug("purging event %d", *ev);
+				pr_vdebug("purging event %d\n", *ev);
 		ffs->ev.count = out - ffs->ev.types;
 	}
 
-	pr_vdebug("adding event %d", type);
+	pr_vdebug("adding event %d\n", type);
 	ffs->ev.types[ffs->ev.count++] = type;
 	wake_up_locked(&ffs->ev.waitq);
 }
@@ -2064,7 +2062,7 @@ static int __ffs_func_bind_do_descs(enum ffs_entity_type type, u8 *valuep,
 	ffs_ep = func->eps + idx;
 
 	if (unlikely(ffs_ep->descs[isHS])) {
-		pr_vdebug("two %sspeed descriptors for EP %d",
+		pr_vdebug("two %sspeed descriptors for EP %d\n",
 			  isHS ? "high" : "full",
 			  ds->bEndpointAddress & USB_ENDPOINT_NUMBER_MASK);
 		return -EINVAL;
@@ -2080,7 +2078,7 @@ static int __ffs_func_bind_do_descs(enum ffs_entity_type type, u8 *valuep,
 		struct usb_request *req;
 		struct usb_ep *ep;
 
-		pr_vdebug("autoconfig");
+		pr_vdebug("autoconfig\n");
 		ep = usb_ep_autoconfig(func->gadget, ds);
 		if (unlikely(!ep))
 			return -ENOTSUPP;
@@ -2150,7 +2148,7 @@ static int __ffs_func_bind_do_nums(enum ffs_entity_type type, u8 *valuep,
 		break;
 	}
 
-	pr_vdebug("%02x -> %02x", *valuep, newValue);
+	pr_vdebug("%02x -> %02x\n", *valuep, newValue);
 	*valuep = newValue;
 	return 0;
 }
@@ -2315,11 +2313,11 @@ static int ffs_func_setup(struct usb_function *f,
 
 	ENTER();
 
-	pr_vdebug("creq->bRequestType = %02x", creq->bRequestType);
-	pr_vdebug("creq->bRequest     = %02x", creq->bRequest);
-	pr_vdebug("creq->wValue       = %04x", le16_to_cpu(creq->wValue));
-	pr_vdebug("creq->wIndex       = %04x", le16_to_cpu(creq->wIndex));
-	pr_vdebug("creq->wLength      = %04x", le16_to_cpu(creq->wLength));
+	pr_vdebug("creq->bRequestType = %02x\n", creq->bRequestType);
+	pr_vdebug("creq->bRequest     = %02x\n", creq->bRequest);
+	pr_vdebug("creq->wValue       = %04x\n", le16_to_cpu(creq->wValue));
+	pr_vdebug("creq->wIndex       = %04x\n", le16_to_cpu(creq->wIndex));
+	pr_vdebug("creq->wLength      = %04x\n", le16_to_cpu(creq->wLength));
 
 	/*
 	 * Most requests directed to interface go through here
@@ -2419,7 +2417,7 @@ static char *ffs_prepare_buffer(const char * __user buf, size_t len)
 		return ERR_PTR(-EFAULT);
 	}
 
-	pr_vdebug("Buffer from user space:");
+	pr_vdebug("Buffer from user space:\n");
 	ffs_dump_mem("", data, len);
 
 	return data;
diff --git a/drivers/usb/gadget/g_ffs.c b/drivers/usb/gadget/g_ffs.c
index 3dc1989..ebf6970 100644
--- a/drivers/usb/gadget/g_ffs.c
+++ b/drivers/usb/gadget/g_ffs.c
@@ -19,6 +19,8 @@
  * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
  */
 
+#define pr_fmt(fmt) "g_ffs: " fmt
+
 #include <linux/module.h>
 #include <linux/utsname.h>
 
-- 
1.7.1

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: [PATCH] usb: gadget: g_fs: Fix compilation warning
       [not found]     ` <0c1bd123752a7adc7f034ef81d155903da115081.1290007778.git.mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
@ 2010-11-17 21:25       ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2010-11-17 21:25 UTC (permalink / raw)
  To: Michal Nazarewicz
  Cc: Stephen Rothwell, linux-usb-u79uwXL29TY76Z2rM5mHXA,
	linux-next-u79uwXL29TY76Z2rM5mHXA,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA

On Wed, Nov 17, 2010 at 05:09:47PM +0100, Michal Nazarewicz wrote:
> This commit fixes warning in f_fs.c introduced by "usb:
> gadget: f_fs: remove custom printk() wrappers":
> 
> In file included from drivers/usb/gadget/g_ffs.c:64:
> drivers/usb/gadget/f_fs.c:30:1: warning: "pr_fmt" redefined
> 
> Signed-off-by: Michal Nazarewicz <mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>

Now queued up, thanks.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-06-01 17:39 ` Rajat Jain
@ 2021-06-04 13:37   ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2021-06-04 13:37 UTC (permalink / raw)
  To: Rajat Jain
  Cc: Stephen Rothwell, Linux Kernel Mailing List, Linux Next Mailing List

On Tue, Jun 01, 2021 at 10:39:42AM -0700, Rajat Jain wrote:
> Hello,
> 
> 
> On Tue, Jun 1, 2021 at 1:30 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > After merging the usb tree, today's linux-next build (htmldocs) produced
> > this warning:
> >
> > Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Unexpected indentation.
> > Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Block quote ends without a blank line; unexpected unindent.
> 
> I'd be happy to send a patch to fix this, but I didn't really
> understand what needs to be done.
> 
> Here is the relevant documentation update in the patch:
> 
> +What:          /sys/devices/.../removable
> +Date:          May 2021
> +Contact:       Rajat Jain <rajatxjain@gmail.com>
> +Description:
> +               Information about whether a given device can be removed from the
> +               platform by the user. This is determined by its subsystem in a
> +               bus / platform-specific way. This attribute is only present for
> +               devices that can support determining such information:
> +
> +               "removable": device can be removed from the platform by the user
> +               "fixed":     device is fixed to the platform / cannot be removed
> +                            by the user.
> +               "unknown":   The information is unavailable / cannot be deduced.
> +
> +               Currently this is only supported by USB (which infers the
> +               information from a combination of hub descriptor bits and
> +               platform-specific data such as ACPI).
> 
> I'd be happy to send a patch if you can point me what needs to be done
> (or let Stephen / Greg / some one else do it if it is easier to just
> do it instead of guiding me).

I do not know what the "right" thing to do here is, sorry.  Maybe one of
the kerneldoc people know?

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-06-01  8:30 linux-next: build warning after merge of the usb tree Stephen Rothwell
@ 2021-06-01 17:39 ` Rajat Jain
  2021-06-04 13:37   ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Rajat Jain @ 2021-06-01 17:39 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, Linux Kernel Mailing List, Linux Next Mailing List

Hello,


On Tue, Jun 1, 2021 at 1:30 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Unexpected indentation.
> Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Block quote ends without a blank line; unexpected unindent.

I'd be happy to send a patch to fix this, but I didn't really
understand what needs to be done.

Here is the relevant documentation update in the patch:

+What:          /sys/devices/.../removable
+Date:          May 2021
+Contact:       Rajat Jain <rajatxjain@gmail.com>
+Description:
+               Information about whether a given device can be removed from the
+               platform by the user. This is determined by its subsystem in a
+               bus / platform-specific way. This attribute is only present for
+               devices that can support determining such information:
+
+               "removable": device can be removed from the platform by the user
+               "fixed":     device is fixed to the platform / cannot be removed
+                            by the user.
+               "unknown":   The information is unavailable / cannot be deduced.
+
+               Currently this is only supported by USB (which infers the
+               information from a combination of hub descriptor bits and
+               platform-specific data such as ACPI).

I'd be happy to send a patch if you can point me what needs to be done
(or let Stephen / Greg / some one else do it if it is easier to just
do it instead of guiding me).

Thanks,

Rajat

>
> Introduced by commit
>
>   70f400d4d957 ("driver core: Move the "removable" attribute from USB to core")
>
> --
> Cheers,
> Stephen Rothwell

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-06-01  8:30 Stephen Rothwell
  2021-06-01 17:39 ` Rajat Jain
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-06-01  8:30 UTC (permalink / raw)
  To: Greg KH; +Cc: Rajat Jain, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 453 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htmldocs) produced
this warning:

Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Block quote ends without a blank line; unexpected unindent.

Introduced by commit

  70f400d4d957 ("driver core: Move the "removable" attribute from USB to core")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-05-21  0:40   ` Stephen Rothwell
@ 2021-05-21  1:28     ` Fabio Estevam
  0 siblings, 0 replies; 39+ messages in thread
From: Fabio Estevam @ 2021-05-21  1:28 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, Linux Kernel Mailing List, Linux Next Mailing List

Hi Stephen,

On Thu, May 20, 2021 at 9:40 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> I am still seeing this warning.

I will submit a fix for this warning.

Thanks

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-04-26 12:53 ` Greg KH
@ 2021-05-21  0:40   ` Stephen Rothwell
  2021-05-21  1:28     ` Fabio Estevam
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-05-21  0:40 UTC (permalink / raw)
  To: Greg KH; +Cc: Fabio Estevam, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

Hi all,

On Mon, 26 Apr 2021 14:53:15 +0200 Greg KH <greg@kroah.com> wrote:
>
> On Mon, Apr 26, 2021 at 10:44:13PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the usb tree, today's linux-next build (htlmdocs) produced
> > this warning:
> > 
> > Documentation/driver-api/usb/writing_usb_driver.rst:129: WARNING: undefined label: usb_header
> > 
> > Presumably introduced by commit
> > 
> >   caa93d9bd2d7 ("usb: Fix up movement of USB core kerneldoc location")  
> 
> Ugh, we'll get this right yet, there's been updates posted, I'll pick
> them up after 5.13-rc1 is out.

I am still seeing this warning.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-04-26 12:53 ` Greg KH
@ 2021-04-26 21:12   ` Thinh Nguyen
  0 siblings, 0 replies; 39+ messages in thread
From: Thinh Nguyen @ 2021-04-26 21:12 UTC (permalink / raw)
  To: Greg KH, Stephen Rothwell, Thinh Nguyen
  Cc: Linux Kernel Mailing List, Linux Next Mailing List

Greg KH wrote:
> On Mon, Apr 26, 2021 at 10:37:33PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the usb tree, today's linux-next build (htmldocs) produced
>> this warning:
>>
>> drivers/usb/dwc3/core.h:865: warning: Function parameter or member 'hwparams9' not described in 'dwc3_hwparams'
>>
>> Introduced by commit
>>
>>   16710380d3aa ("usb: dwc3: Capture new capability register GHWPARAMS9")
> 
> Thinh, can you submit a fix for this?
> 

My mistake. Just submitted it.

Thanks,
Thinh

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-04-26 12:37 Stephen Rothwell
@ 2021-04-26 12:53 ` Greg KH
  2021-04-26 21:12   ` Thinh Nguyen
  0 siblings, 1 reply; 39+ messages in thread
From: Greg KH @ 2021-04-26 12:53 UTC (permalink / raw)
  To: Stephen Rothwell, Thinh Nguyen
  Cc: Linux Kernel Mailing List, Linux Next Mailing List

On Mon, Apr 26, 2021 at 10:37:33PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> drivers/usb/dwc3/core.h:865: warning: Function parameter or member 'hwparams9' not described in 'dwc3_hwparams'
> 
> Introduced by commit
> 
>   16710380d3aa ("usb: dwc3: Capture new capability register GHWPARAMS9")

Thinh, can you submit a fix for this?

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-04-26 12:44 Stephen Rothwell
@ 2021-04-26 12:53 ` Greg KH
  2021-05-21  0:40   ` Stephen Rothwell
  0 siblings, 1 reply; 39+ messages in thread
From: Greg KH @ 2021-04-26 12:53 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Fabio Estevam, Linux Kernel Mailing List, Linux Next Mailing List

On Mon, Apr 26, 2021 at 10:44:13PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the usb tree, today's linux-next build (htlmdocs) produced
> this warning:
> 
> Documentation/driver-api/usb/writing_usb_driver.rst:129: WARNING: undefined label: usb_header
> 
> Presumably introduced by commit
> 
>   caa93d9bd2d7 ("usb: Fix up movement of USB core kerneldoc location")

Ugh, we'll get this right yet, there's been updates posted, I'll pick
them up after 5.13-rc1 is out.

thanks!

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-04-26 12:44 Stephen Rothwell
  2021-04-26 12:53 ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-04-26 12:44 UTC (permalink / raw)
  To: Greg KH; +Cc: Fabio Estevam, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 340 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htlmdocs) produced
this warning:

Documentation/driver-api/usb/writing_usb_driver.rst:129: WARNING: undefined label: usb_header

Presumably introduced by commit

  caa93d9bd2d7 ("usb: Fix up movement of USB core kerneldoc location")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-04-26 12:37 Stephen Rothwell
  2021-04-26 12:53 ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-04-26 12:37 UTC (permalink / raw)
  To: Greg KH; +Cc: Thinh Nguyen, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 349 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htmldocs) produced
this warning:

drivers/usb/dwc3/core.h:865: warning: Function parameter or member 'hwparams9' not described in 'dwc3_hwparams'

Introduced by commit

  16710380d3aa ("usb: dwc3: Capture new capability register GHWPARAMS9")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-04-21  6:07 ` Stephen Rothwell
@ 2021-04-21  6:22   ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2021-04-21  6:22 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Chunfeng Yun, Linux Kernel Mailing List, Linux Next Mailing List

On Wed, Apr 21, 2021 at 04:07:25PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Wed, 10 Mar 2021 13:49:16 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > 
> > After merging the usb tree, today's linux-next build (htmldocs) produced
> > this warning:
> > 
> > include/linux/usb/ch9.h:1: warning: no structured comments found
> > 
> > Introduced by commit
> > 
> >   855b35ea96c4 ("usb: common: move function's kerneldoc next to its definition")
> 
> I am still seeing thus warning (as of next-20210420).

Ick, sorry, will go dig...

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-03-10  2:49 Stephen Rothwell
@ 2021-04-21  6:07 ` Stephen Rothwell
  2021-04-21  6:22   ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-04-21  6:07 UTC (permalink / raw)
  To: Greg KH; +Cc: Chunfeng Yun, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

Hi all,

On Wed, 10 Mar 2021 13:49:16 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> include/linux/usb/ch9.h:1: warning: no structured comments found
> 
> Introduced by commit
> 
>   855b35ea96c4 ("usb: common: move function's kerneldoc next to its definition")

I am still seeing thus warning (as of next-20210420).

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-03-10  2:49 Stephen Rothwell
  2021-04-21  6:07 ` Stephen Rothwell
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-03-10  2:49 UTC (permalink / raw)
  To: Greg KH; +Cc: Chunfeng Yun, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htmldocs) produced
this warning:

include/linux/usb/ch9.h:1: warning: no structured comments found

Introduced by commit

  855b35ea96c4 ("usb: common: move function's kerneldoc next to its definition")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-03-03  6:05 Stephen Rothwell
  0 siblings, 0 replies; 39+ messages in thread
From: Stephen Rothwell @ 2021-03-03  6:05 UTC (permalink / raw)
  To: Greg KH; +Cc: Ray Chi, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 335 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htmldocs) produced
this warning:

drivers/usb/dwc3/core.h:1273: warning: Function parameter or member 'usb_psy' not described in 'dwc3'

Introduced by commit

  59fa3def35de ("usb: dwc3: add a power supply for current control")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-02-03  5:13 Stephen Rothwell
@ 2021-02-03  7:04 ` Benson Leung
  0 siblings, 0 replies; 39+ messages in thread
From: Benson Leung @ 2021-02-03  7:04 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, Benson Leung, Linux Kernel Mailing List,
	Linux Next Mailing List, kyletso


[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

Hi,

On Wed, Feb 03, 2021 at 04:13:00PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the usb tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/usb/typec/class.c: In function 'typec_partner_set_pd_revision':
> drivers/usb/typec/class.c:763:6: warning: unused variable 'ret' [-Wunused-variable]
>   763 |  int ret;
>       |      ^~~
> 
> Introduced by commit
> 
>   29b01295a829 ("usb: typec: Add typec_partner_set_pd_revision")
> 

Will be fixed by https://lore.kernel.org/r/20210202095512.761214-1-kyletso@google.com,
already in Greg's usb-testing.

Thanks Kyle for the quick fix yesterday.

Benson

-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-02-03  5:13 Stephen Rothwell
  2021-02-03  7:04 ` Benson Leung
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-02-03  5:13 UTC (permalink / raw)
  To: Greg KH; +Cc: Benson Leung, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/usb/typec/class.c: In function 'typec_partner_set_pd_revision':
drivers/usb/typec/class.c:763:6: warning: unused variable 'ret' [-Wunused-variable]
  763 |  int ret;
      |      ^~~

Introduced by commit

  29b01295a829 ("usb: typec: Add typec_partner_set_pd_revision")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-01-13 22:48 ` Stephen Rothwell
@ 2021-01-14  8:51   ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2021-01-14  8:51 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Wesley Cheng, Linux Kernel Mailing List, Linux Next Mailing List

On Thu, Jan 14, 2021 at 09:48:56AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> On Wed, 6 Jan 2021 13:12:25 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the usb tree, today's linux-next build (htmldocs) produced
> > this warning:
> > 
> > drivers/usb/dwc3/core.h:1259: warning: Function parameter or member 'gadget_max_speed' not described in 'dwc3'
> > 
> > Introduced by commit
> > 
> >   7c9a2598463a ("usb: dwc3: gadget: Preserve UDC max speed setting")
> 
> I am still getting this warning.

Looks like Mauro just sent me a patch for this, will queue it up now,
thanks.

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2021-01-06  2:12 Stephen Rothwell
@ 2021-01-13 22:48 ` Stephen Rothwell
  2021-01-14  8:51   ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-01-13 22:48 UTC (permalink / raw)
  To: Greg KH; +Cc: Wesley Cheng, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

Hi all,

On Wed, 6 Jan 2021 13:12:25 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> drivers/usb/dwc3/core.h:1259: warning: Function parameter or member 'gadget_max_speed' not described in 'dwc3'
> 
> Introduced by commit
> 
>   7c9a2598463a ("usb: dwc3: gadget: Preserve UDC max speed setting")

I am still getting this warning.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2021-01-06  2:12 Stephen Rothwell
  2021-01-13 22:48 ` Stephen Rothwell
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2021-01-06  2:12 UTC (permalink / raw)
  To: Greg KH; +Cc: Wesley Cheng, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htmldocs) produced
this warning:

drivers/usb/dwc3/core.h:1259: warning: Function parameter or member 'gadget_max_speed' not described in 'dwc3'

Introduced by commit

  7c9a2598463a ("usb: dwc3: gadget: Preserve UDC max speed setting")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2020-11-20  5:15 Stephen Rothwell
@ 2020-11-20  6:38 ` Prashant Malani
  0 siblings, 0 replies; 39+ messages in thread
From: Prashant Malani @ 2020-11-20  6:38 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, Linux Kernel Mailing List, Linux Next Mailing List

Hi Stephen,

On Fri, Nov 20, 2020 at 04:15:06PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the usb tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
> 
> Introduced by commit
> 
>   a0ccdc4a77a1 ("usb: typec: Add number of altmodes partner attr")


Thank you for the email, and my apologies about the warning. I've sent a
patch the mailing lists which should hopefully fix this [1].

Please let me know if there is further action required from my side.

Best regards,

[1]:
https://lore.kernel.org/linux-usb/20201120063523.4159877-1-pmalani@chromium.org/
> 
> -- 
> Cheers,
> Stephen Rothwell



^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2020-11-20  5:15 Stephen Rothwell
  2020-11-20  6:38 ` Prashant Malani
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2020-11-20  5:15 UTC (permalink / raw)
  To: Greg KH
  Cc: Prashant Malani, Linux Kernel Mailing List, Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (htmldocs) produced
this warning:

drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'
drivers/usb/typec/class.c:632: warning: Excess function parameter 'num_alt_modes' description in 'typec_partner_set_num_altmodes'

Introduced by commit

  a0ccdc4a77a1 ("usb: typec: Add number of altmodes partner attr")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2020-01-06  7:58 ` Krzysztof Kozlowski
@ 2020-01-06  9:30   ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2020-01-06  9:30 UTC (permalink / raw)
  To: Krzysztof Kozlowski
  Cc: Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Kishon Vijay Abraham I, Chunfeng Yun,
	Matthias Brugger, Maxime Ripard

On Mon, Jan 06, 2020 at 08:58:58AM +0100, Krzysztof Kozlowski wrote:
> On Mon, Jan 06, 2020 at 02:41:22PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> > 
> > WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
> >   Depends on [n]: ARCH_DAVINCI_DA8XX
> >   Selected by [m]:
> >   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> > 
> > WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
> >   Depends on [n]: ARCH_DAVINCI_DA8XX
> >   Selected by [m]:
> >   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> > 
> > WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
> >   Depends on [n]: ARCH_DAVINCI_DA8XX
> >   Selected by [m]:
> >   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> > 
> > Introduced by commit
> > 
> >   88eaaecc4446 ("usb: host: Enable compile testing for some of drivers")
> 
> +Cc,
> 
> Hi Stephen,
> 
> Thanks for the report.  I already sent a patch for it for the phy:
> https://lore.kernel.org/lkml/20200103164710.4829-2-krzk@kernel.org/

I'll go queue this up through my usb tree as it is annoying for my
builds as well :(

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2020-01-06  3:41 Stephen Rothwell
@ 2020-01-06  7:58 ` Krzysztof Kozlowski
  2020-01-06  9:30   ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Krzysztof Kozlowski @ 2020-01-06  7:58 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, Linux Next Mailing List, Linux Kernel Mailing List,
	Kishon Vijay Abraham I, Chunfeng Yun, Matthias Brugger,
	Maxime Ripard

On Mon, Jan 06, 2020 at 02:41:22PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
>   Depends on [n]: ARCH_DAVINCI_DA8XX
>   Selected by [m]:
>   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> 
> WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
>   Depends on [n]: ARCH_DAVINCI_DA8XX
>   Selected by [m]:
>   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> 
> WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
>   Depends on [n]: ARCH_DAVINCI_DA8XX
>   Selected by [m]:
>   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> 
> Introduced by commit
> 
>   88eaaecc4446 ("usb: host: Enable compile testing for some of drivers")

+Cc,

Hi Stephen,

Thanks for the report.  I already sent a patch for it for the phy:
https://lore.kernel.org/lkml/20200103164710.4829-2-krzk@kernel.org/

Best regards,
Krzysztof

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2020-01-06  3:41 Stephen Rothwell
  2020-01-06  7:58 ` Krzysztof Kozlowski
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2020-01-06  3:41 UTC (permalink / raw)
  To: Greg KH
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Krzysztof Kozlowski


[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

Hi all,

After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:

WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
  Depends on [n]: ARCH_DAVINCI_DA8XX
  Selected by [m]:
  - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]

WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
  Depends on [n]: ARCH_DAVINCI_DA8XX
  Selected by [m]:
  - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]

WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
  Depends on [n]: ARCH_DAVINCI_DA8XX
  Selected by [m]:
  - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]

Introduced by commit

  88eaaecc4446 ("usb: host: Enable compile testing for some of drivers")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2018-09-11  2:47 Stephen Rothwell
@ 2018-09-11  8:12 ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2018-09-11  8:12 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Sebastian Andrzej Siewior

On Tue, Sep 11, 2018 at 12:47:43PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/usb/core/hcd.c: In function '__usb_hcd_giveback_urb':
> drivers/usb/core/hcd.c:1741:16: warning: unused variable 'flags' [-Wunused-variable]
>   unsigned long flags;
>                 ^~~~~
> 
> Introduced by commit
> 
>   ed194d136769 ("usb: core: remove local_irq_save() around ->complete() handler")

Ugh, sorry I missed this :(

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2018-09-11  2:47 Stephen Rothwell
  2018-09-11  8:12 ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2018-09-11  2:47 UTC (permalink / raw)
  To: Greg KH
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Sebastian Andrzej Siewior


[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

Hi Greg,

After merging the usb tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/usb/core/hcd.c: In function '__usb_hcd_giveback_urb':
drivers/usb/core/hcd.c:1741:16: warning: unused variable 'flags' [-Wunused-variable]
  unsigned long flags;
                ^~~~~

Introduced by commit

  ed194d136769 ("usb: core: remove local_irq_save() around ->complete() handler")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2017-11-02  4:06 Stephen Rothwell
  0 siblings, 0 replies; 39+ messages in thread
From: Stephen Rothwell @ 2017-11-02  4:06 UTC (permalink / raw)
  To: Greg KH; +Cc: Linux-Next Mailing List, Linux Kernel Mailing List

Hi Greg,

After merging the usb tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

arch/arm/boot/dts/stih410-b2120.dtb: Warning (gpios_property): hdmi,hpd-gpio property size (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000
arch/arm/boot/dts/stih407-b2120.dtb: Warning (gpios_property): hdmi,hpd-gpio property size (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000
arch/arm/boot/dts/stih410-b2260.dtb: Warning (gpios_property): hdmi,hpd-gpio property size (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000
arch/arm/boot/dts/mt2701-evb.dtb: Warning (resets_property): Missing property '#reset-cells' in node /syscon@1b000000 or bad phandle (referred from /ethernet@1b100000:resets[0])
arch/arm/boot/dts/mt7623n-rfb-nand.dtb: Warning (resets_property): Missing property '#reset-cells' in node /syscon@1b000000 or bad phandle (referred from /ethernet@1b100000:resets[0])
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dtb: Warning (resets_property): Missing property '#reset-cells' in node /syscon@1b000000 or bad phandle (referred from /ethernet@1b100000:resets[0])

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2013-12-10  3:59 Stephen Rothwell
  0 siblings, 0 replies; 39+ messages in thread
From: Stephen Rothwell @ 2013-12-10  3:59 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-next, linux-kernel, Ming Lei


[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Hi Greg,

After merging the usb tree, today's linux-next build (sparc64 defconfig)
produced this warning:

drivers/usb/storage/protocol.c: In function 'usb_stor_access_xfer_buf':
drivers/usb/storage/protocol.c:155:22: warning: comparison of distinct pointer types lacks a cast [enabled by default]

Introduced by commit e5fc70d5ccc3 ("USB: storage: use sg_miter_* APIs to
access scsi buffer").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2012-11-02  9:07 ` Felipe Balbi
@ 2012-11-02 14:18   ` Alan Stern
  0 siblings, 0 replies; 39+ messages in thread
From: Alan Stern @ 2012-11-02 14:18 UTC (permalink / raw)
  To: Felipe Balbi
  Cc: Stephen Rothwell, Greg KH, linux-next, linux-kernel, Alexander Shishkin

On Fri, 2 Nov 2012, Felipe Balbi wrote:

> Hi,
> 
> On Fri, Nov 02, 2012 at 03:08:28PM +1100, Stephen Rothwell wrote:
> > Hi Greg,
> > 
> > After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> > 
> > WARNING: drivers/usb/host/ehci-hcd: 'ehci_init_driver' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> > WARNING: drivers/usb/host/ehci-hcd: 'ehci_resume' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> > WARNING: drivers/usb/host/ehci-hcd: 'ehci_suspend' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> > WARNING: drivers/usb/host/ehci-hcd: 'ehci_setup' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> > 
> > Introduced by commit 3e0232039967 ("USB: EHCI: prepare to make ehci-hcd a
> > library module").
> 
> Alex, why on earth is chipidea exporting symbols it doesn't own ?

That's at least partly my fault.  ehci-hcd.c now exports four symbols 
that it didn't before.  Since the ChipIdea driver does

	#include "../host/ehci-hcd.c"

it now exports them too, unintentionally.  A quick band-aid fix would 
be to protect those functions with

	#ifndef CHIPIDEA_EHCI

but the real fix is the patch I posted yesterday -- assuming it works 
right.  If we don't hear back from Alex soon, I will post the band-aid 
fix as a temporary stop-gap.

Alan Stern

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2012-11-02  4:08 Stephen Rothwell
@ 2012-11-02  9:07 ` Felipe Balbi
  2012-11-02 14:18   ` Alan Stern
  0 siblings, 1 reply; 39+ messages in thread
From: Felipe Balbi @ 2012-11-02  9:07 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, linux-next, linux-kernel, Alan Stern, Felipe Balbi,
	Alexander Shishkin


[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Hi,

On Fri, Nov 02, 2012 at 03:08:28PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> WARNING: drivers/usb/host/ehci-hcd: 'ehci_init_driver' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> WARNING: drivers/usb/host/ehci-hcd: 'ehci_resume' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> WARNING: drivers/usb/host/ehci-hcd: 'ehci_suspend' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> WARNING: drivers/usb/host/ehci-hcd: 'ehci_setup' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
> 
> Introduced by commit 3e0232039967 ("USB: EHCI: prepare to make ehci-hcd a
> library module").

Alex, why on earth is chipidea exporting symbols it doesn't own ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2012-11-02  4:08 Stephen Rothwell
  2012-11-02  9:07 ` Felipe Balbi
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2012-11-02  4:08 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-next, linux-kernel, Alan Stern, Felipe Balbi


[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

Hi Greg,

After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:

WARNING: drivers/usb/host/ehci-hcd: 'ehci_init_driver' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
WARNING: drivers/usb/host/ehci-hcd: 'ehci_resume' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
WARNING: drivers/usb/host/ehci-hcd: 'ehci_suspend' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko
WARNING: drivers/usb/host/ehci-hcd: 'ehci_setup' exported twice. Previous export was in drivers/usb/chipidea/ci_hdrc.ko

Introduced by commit 3e0232039967 ("USB: EHCI: prepare to make ehci-hcd a
library module").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2010-05-17  6:09 Stephen Rothwell
@ 2010-05-17 18:01 ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2010-05-17 18:01 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Ming Lei

On Mon, May 17, 2010 at 04:09:58PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (powerpc
> ppc44x_defconfig) produced this warning:
> 
> drivers/usb/core/usb.c:596: warning: 'match_device' defined but not used
> 
> Introduced by commit c8a3789b05e2ed43d8fd98934edbf66587cd3f96 ("USB:
> remove usb_find_device") which removed the last user of this function.

Thanks, Ming just sent me a patch to resolve this, I'll go apply it now.

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* Re: linux-next: build warning after merge of the usb tree
  2010-05-17  6:16 Stephen Rothwell
@ 2010-05-17 18:01 ` Greg KH
  0 siblings, 0 replies; 39+ messages in thread
From: Greg KH @ 2010-05-17 18:01 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel, John Youn, Sarah Sharp

On Mon, May 17, 2010 at 04:16:03PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (powerpc allyesconfig)
> produced this warning:
> 
> drivers/usb/host/xhci-ring.c: In function 'prepare_ring':
> drivers/usb/host/xhci-ring.c:1729: warning: unused variable 'addr'
> 
> Introduced by commit a2fbb0e4784f6d1b3be0779918e84dd3c0c73f04 ("USB:
> xhci: Transfer ring link TRB activation change").

Thanks, I'll go fix this up.

greg k-h

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2010-05-17  6:16 Stephen Rothwell
  2010-05-17 18:01 ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2010-05-17  6:16 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-next, linux-kernel, John Youn, Sarah Sharp


[-- Attachment #1: Type: text/plain, Size: 474 bytes --]

Hi Greg,

After merging the usb tree, today's linux-next build (powerpc allyesconfig)
produced this warning:

drivers/usb/host/xhci-ring.c: In function 'prepare_ring':
drivers/usb/host/xhci-ring.c:1729: warning: unused variable 'addr'

Introduced by commit a2fbb0e4784f6d1b3be0779918e84dd3c0c73f04 ("USB:
xhci: Transfer ring link TRB activation change").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

* linux-next: build warning after merge of the usb tree
@ 2010-05-17  6:09 Stephen Rothwell
  2010-05-17 18:01 ` Greg KH
  0 siblings, 1 reply; 39+ messages in thread
From: Stephen Rothwell @ 2010-05-17  6:09 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-next, linux-kernel, Ming Lei


[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

Hi Greg,

After merging the usb tree, today's linux-next build (powerpc
ppc44x_defconfig) produced this warning:

drivers/usb/core/usb.c:596: warning: 'match_device' defined but not used

Introduced by commit c8a3789b05e2ed43d8fd98934edbf66587cd3f96 ("USB:
remove usb_find_device") which removed the last user of this function.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 39+ messages in thread

end of thread, back to index

Thread overview: 39+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-17  2:14 linux-next: build warning after merge of the usb tree Stephen Rothwell
2010-11-17  4:20 ` Greg KH
     [not found] ` <20101116215906.GA2869@kroah.com>
2010-11-17 16:09   ` [PATCH] usb: gadget: g_fs: Fix compilation warning Michal Nazarewicz
     [not found]     ` <0c1bd123752a7adc7f034ef81d155903da115081.1290007778.git.mina86-deATy8a+UHjQT0dZR+AlfA@public.gmane.org>
2010-11-17 21:25       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2021-06-01  8:30 linux-next: build warning after merge of the usb tree Stephen Rothwell
2021-06-01 17:39 ` Rajat Jain
2021-06-04 13:37   ` Greg KH
2021-04-26 12:44 Stephen Rothwell
2021-04-26 12:53 ` Greg KH
2021-05-21  0:40   ` Stephen Rothwell
2021-05-21  1:28     ` Fabio Estevam
2021-04-26 12:37 Stephen Rothwell
2021-04-26 12:53 ` Greg KH
2021-04-26 21:12   ` Thinh Nguyen
2021-03-10  2:49 Stephen Rothwell
2021-04-21  6:07 ` Stephen Rothwell
2021-04-21  6:22   ` Greg KH
2021-03-03  6:05 Stephen Rothwell
2021-02-03  5:13 Stephen Rothwell
2021-02-03  7:04 ` Benson Leung
2021-01-06  2:12 Stephen Rothwell
2021-01-13 22:48 ` Stephen Rothwell
2021-01-14  8:51   ` Greg KH
2020-11-20  5:15 Stephen Rothwell
2020-11-20  6:38 ` Prashant Malani
2020-01-06  3:41 Stephen Rothwell
2020-01-06  7:58 ` Krzysztof Kozlowski
2020-01-06  9:30   ` Greg KH
2018-09-11  2:47 Stephen Rothwell
2018-09-11  8:12 ` Greg KH
2017-11-02  4:06 Stephen Rothwell
2013-12-10  3:59 Stephen Rothwell
2012-11-02  4:08 Stephen Rothwell
2012-11-02  9:07 ` Felipe Balbi
2012-11-02 14:18   ` Alan Stern
2010-05-17  6:16 Stephen Rothwell
2010-05-17 18:01 ` Greg KH
2010-05-17  6:09 Stephen Rothwell
2010-05-17 18:01 ` Greg KH

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git