public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl@eisenstein.dk>
To: linux-serial@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: [PATCH] missing return value from pci_xircom_fn() in drivers/char/serial.c
Date: Sun, 13 May 2001 23:30:46 +0200	[thread overview]
Message-ID: <3AFEFD06.9010500@eisenstein.dk> (raw)


Hi,

I'm using the 2.4.4-ac8 kernel and found that the pci_xircom_fn() 
function in drivers/char/serial.c does not return a value even though it 
is defined as returning int. I took a look at the other initializer 
functions and they all return 0 (zero) on success, so I assumed that the 
correct return value for the pci_xircom_fn() function would also be 0. I 
don't know anything specific about what goes on in serial.c, so I may be 
wrong on this, but I do know that the function should either return some 
value or be declared as returning void, and since declaring it void 
would mess up the way it is used I guess it should return a value.

I have made a patch against 2.4.4-ac8 that makes the change, it is 
below. I guess someone more knowledgeable than me can probably see if 
this is correct. If this is completely bogus, then please just disregard 
this email.


--- linux-2.4.4-ac8/drivers/char/serial.c.orig  Sun May 13 23:13:02 2001
+++ linux-2.4.4-ac8/drivers/char/serial.c       Sun May 13 23:13:24 2001
@@ -4190,6 +4190,7 @@
  {
         __set_current_state(TASK_UNINTERRUPTIBLE);
         schedule_timeout(HZ/10);
+       return(0);
  }

  /*


Best regards,
Jesper Juhl - juhl@eisenstein.dk


             reply	other threads:[~2001-05-13 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-13 21:30 Jesper Juhl [this message]
2001-05-14 21:50 ` [PATCH] missing return value from pci_xircom_fn() in drivers/char/serial.c Bill Nottingham

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=3AFEFD06.9010500@eisenstein.dk \
    --to=juhl@eisenstein.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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