From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ming Lei <tom.leiming@gmail.com>
Subject: Re: linux-next: build warning after merge of the usb tree
Date: Mon, 17 May 2010 11:01:15 -0700 [thread overview]
Message-ID: <20100517180115.GB16419@kroah.com> (raw)
In-Reply-To: <20100517160958.b5208a24.sfr@canb.auug.org.au>
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
next prev parent reply other threads:[~2010-05-17 18:20 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 6:09 linux-next: build warning after merge of the usb tree Stephen Rothwell
2010-05-17 18:01 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-17 6:16 Stephen Rothwell
2010-05-17 18:01 ` Greg KH
2010-11-17 2:14 Stephen Rothwell
2010-11-17 4:20 ` Greg KH
2012-11-02 4:08 Stephen Rothwell
2012-11-02 9:07 ` Felipe Balbi
2012-11-02 9:07 ` Felipe Balbi
2012-11-02 14:18 ` Alan Stern
2012-11-02 14:18 ` Alan Stern
2013-12-10 3:59 Stephen Rothwell
2017-11-02 4:06 Stephen Rothwell
2018-09-11 2:47 Stephen Rothwell
2018-09-11 8:12 ` Greg KH
2020-01-06 3:41 Stephen Rothwell
2020-01-06 7:58 ` Krzysztof Kozlowski
2020-01-06 9:30 ` Greg KH
2020-11-20 5:15 Stephen Rothwell
2020-11-20 6:38 ` Prashant Malani
2021-01-06 2:12 Stephen Rothwell
2021-01-13 22:48 ` Stephen Rothwell
2021-01-14 8:51 ` Greg KH
2021-02-03 5:13 Stephen Rothwell
2021-02-03 7:04 ` Benson Leung
2021-03-03 6:05 Stephen Rothwell
2021-03-10 2:49 Stephen Rothwell
2021-04-21 6:07 ` Stephen Rothwell
2021-04-21 6:22 ` Greg KH
2021-04-26 12:37 Stephen Rothwell
2021-04-26 12:53 ` Greg KH
2021-04-26 21:12 ` Thinh Nguyen
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-06-01 8:30 Stephen Rothwell
2021-06-01 17:39 ` Rajat Jain
2021-06-04 13:37 ` Greg KH
2021-07-13 21:03 ` Rajat Jain
2021-07-08 2:22 ` Stephen Rothwell
2021-07-08 8:10 ` Greg KH
2022-01-06 15:48 Stephen Rothwell
2022-01-06 16:10 ` Greg KH
2022-01-07 10:02 ` Pavel Hofman
2022-01-07 10:35 ` Greg KH
2022-07-19 9:43 Stephen Rothwell
2022-07-19 10:25 ` Maxim Devaev
2022-07-19 11:24 ` Greg KH
2022-07-23 7:14 ` Maxim Devaev
2022-07-23 7:26 ` Greg KH
2022-07-23 7:44 ` Maxim Devaev
2023-01-23 4:24 Stephen Rothwell
2023-01-23 14:42 ` Greg KH
2023-01-25 17:01 ` Jó Ágila Bitsch
2023-02-06 3:50 Stephen Rothwell
2023-02-06 7:29 ` Greg KH
2023-02-06 7:45 ` Dan Scally
2023-02-06 9:22 ` Greg KH
2023-02-06 12:30 ` Bagas Sanjaya
2024-01-08 5:02 Stephen Rothwell
2024-01-08 7:54 ` Greg KH
2024-01-25 0:35 ` Stephen Rothwell
2024-01-25 5:53 ` Krishna Kurapati PSSNV
2024-01-25 15:53 ` Greg KH
2024-09-05 8:40 Stephen Rothwell
2024-11-18 8:40 Stephen Rothwell
2025-01-20 7:22 Stephen Rothwell
2025-01-20 8:18 ` Greg KH
2025-01-21 1:36 ` Thinh Nguyen
2025-05-23 5:09 Stephen Rothwell
2025-05-23 12:50 ` Greg KH
2025-07-11 8:28 Stephen Rothwell
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=20100517180115.GB16419@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tom.leiming@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.