From: Andrew Morton <akpm@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: kdrader@us.ibm.com, linux-kernel@vger.kernel.org,
pberger@brimson.com, borchers@steinerpoint.com
Subject: Re: [PATCH][2.6.0-test7] digi_acceleport.c has bogus "address of" operator
Date: Thu, 23 Oct 2003 17:44:33 -0700 [thread overview]
Message-ID: <20031023174433.77770988.akpm@osdl.org> (raw)
In-Reply-To: <20031024000750.GE21734@kroah.com>
Greg KH <greg@kroah.com> wrote:
>
> On Wed, Oct 15, 2003 at 10:48:21PM -0700, Kurtis D. Rader wrote:
> >
> > === diff -rup drivers/usb/serial/digi_acceleport.c.orig drivers/usb/serial/digi_acceleport.c
> > --- drivers/usb/serial/digi_acceleport.c.orig 2003-10-15 22:03:26.000000000 -0700
> > +++ drivers/usb/serial/digi_acceleport.c 2003-10-15 21:10:21.000000000 -0700
>
> This patch does not apply. It looks like the tabs are converted to
> spaces. Can you send it to me again, so that I can apply it?
It was applied. But it added a compile-time warning, which this
fixes:
diff -puN drivers/usb/serial/digi_acceleport.c~digi_acceleport-warning-fix drivers/usb/serial/digi_acceleport.c
--- 25/drivers/usb/serial/digi_acceleport.c~digi_acceleport-warning-fix 2003-10-23 03:21:03.000000000 -0700
+++ 25-akpm/drivers/usb/serial/digi_acceleport.c 2003-10-23 03:21:40.000000000 -0700
@@ -444,7 +444,7 @@ struct digi_port {
/* Local Function Declarations */
static void digi_wakeup_write( struct usb_serial_port *port );
-static void digi_wakeup_write_lock( struct usb_serial_port *port );
+static void digi_wakeup_write_lock(void *);
static int digi_write_oob_command( struct usb_serial_port *port,
unsigned char *buf, int count, int interruptible );
static int digi_write_inb_command( struct usb_serial_port *port,
@@ -608,9 +608,9 @@ static inline long cond_wait_interruptib
* on writes.
*/
-static void digi_wakeup_write_lock( struct usb_serial_port *port )
+static void digi_wakeup_write_lock(void *arg)
{
-
+ struct usb_serial_port *port = arg;
unsigned long flags;
struct digi_port *priv = usb_get_serial_port_data(port);
_
next prev parent reply other threads:[~2003-10-24 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 5:48 Kurtis D. Rader
2003-10-24 0:07 ` Greg KH
2003-10-24 0:44 ` Andrew Morton [this message]
2003-10-24 4:42 ` Kurtis D. Rader
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=20031023174433.77770988.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=borchers@steinerpoint.com \
--cc=greg@kroah.com \
--cc=kdrader@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pberger@brimson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®