From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Bill Pemberton <wfp5p@virginia.edu>
Subject: Re: linux-next: build failure after merge of the input tree
Date: Wed, 18 Aug 2010 22:19:20 -0700 [thread overview]
Message-ID: <20100819051919.GA5832@core.coreip.homeip.net> (raw)
In-Reply-To: <20100819113545.ee9d52ec.sfr@canb.auug.org.au>
Hi Stephen,
On Thu, Aug 19, 2010 at 11:35:45AM +1000, Stephen Rothwell wrote:
> Hi Dmitry,
>
> After merging the input tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/usb/serial/ssu100.c:599: warning: passing argument 1 of 'usb_serial_handle_sysrq_char' from incompatible pointer type
> include/linux/usb/serial.h:345: note: expected 'struct usb_serial_port *' but argument is of type 'struct tty_struct *'
> drivers/usb/serial/ssu100.c:599: warning: passing argument 2 of 'usb_serial_handle_sysrq_char' makes integer from pointer without a cast
> include/linux/usb/serial.h:345: note: expected 'unsigned int' but argument is of type 'struct usb_serial_port *'
> drivers/usb/serial/ssu100.c:599: error: too many arguments to function 'usb_serial_handle_sysrq_char'
>
> Caused by commit 0c870dc9828fee03abd60b441f9025a1b4e3d3e6 ("USB: drop tty
> argument from usb_serial_handle_sysrq_char()") interacting with
> 52af954599396e5945a895035525c703f2761b20 ("USB: add USB serial ssu100
> driver") from Linus' tree.
>
> I have used the input tree from next-20100818 for today.
I updated the patch in question to include this new driver as well,
thank you for letting me know.
--
Dmitry
next prev parent reply other threads:[~2010-08-19 5:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 1:35 linux-next: build failure after merge of the input tree Stephen Rothwell
2010-08-19 5:19 ` Dmitry Torokhov [this message]
2012-01-24 3:25 Stephen Rothwell
2012-01-24 6:59 ` Dmitry Torokhov
2012-01-24 23:16 ` John Stultz
2012-10-05 1:47 Stephen Rothwell
2012-10-05 6:12 ` Dmitry Torokhov
2015-07-24 1:49 Stephen Rothwell
2015-07-24 2:33 ` Dmitry Torokhov
2015-10-16 2:19 Stephen Rothwell
2015-10-16 7:37 ` Hans de Goede
2015-10-17 16:39 ` Dmitry Torokhov
2020-03-25 7:16 Stephen Rothwell
2020-03-31 21:06 ` Stephen Rothwell
2022-04-27 0:48 Stephen Rothwell
2022-04-27 6:53 ` Fabien Parent
2022-04-27 7:35 ` Lee Jones
2022-04-27 7:41 ` Fabien Parent
2022-05-02 2:17 ` Stephen Rothwell
2022-05-06 0:25 ` Dmitry Torokhov
2022-05-31 10:13 ` Fabien Parent
2022-08-01 21:44 broonie
2022-08-04 12:33 ` Mark Brown
2022-08-04 23:36 ` Jiri Kosina
2022-08-17 0:00 Stephen Rothwell
2022-08-17 0:07 ` Stephen Rothwell
2022-08-17 4:43 ` Uwe Kleine-König
2022-10-24 23:00 Stephen Rothwell
2022-10-25 5:02 ` Dmitry Torokhov
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=20100819051919.GA5832@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wfp5p@virginia.edu \
/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 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).