public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
Cc: linux-kernel@vger.kernel.org, bryder@sgi.com,
	kuba@mareimbrium.org, ftdi-usb-sio-devel@lists.sourceforge.net,
	edwin@harddisk-recovery.nl
Subject: Re: Bug when using custom baud rates....
Date: Thu, 20 Jan 2005 16:03:42 -0800	[thread overview]
Message-ID: <20050121000342.GA14469@kroah.com> (raw)
In-Reply-To: <20050120152256.GA3614@bitwizard.nl>

On Thu, Jan 20, 2005 at 04:22:56PM +0100, Rogier Wolff wrote:
> On Thu, Jan 20, 2005 at 07:08:58AM -0800, Greg KH wrote:
> > On Thu, Jan 20, 2005 at 03:54:22PM +0100, Rogier Wolff wrote:
> > > Hi,
> > > 
> > > When using custom baud rates, the code does: 
> > > 
> > > 
> > >        if ((new_serial.baud_base != priv->baud_base) ||
> > >             (new_serial.baud_base < 9600))
> > >                 return -EINVAL;
> > > 
> > > Which translates to english as: 
> > > 
> > > 	If you changed the baud-base, OR the new one is
> > > 	invalid, return invalid. 
> > > 
> > > but it should be:
> > > 
> > > 	If you changed the baud-base, OR the new one is
> > > 	invalid, return invalid. 
> > 
> > You mean AND, not OR here, right?  :)
> 
> :-) Sorry. Too noisy here. 
> 
> > > Patch attached. 
> > 
> > Have a 2.6 patch?
> 
> Patch told me: 
>    patching file drivers/usb/serial/ftdi_sio.c
>    Hunk #1 succeeded at 1137 (offset 156 lines).
> 
> but the resulting patch is attached. 

Applied, thanks.

greg k-h

      reply	other threads:[~2005-01-21  0:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 14:54 Bug when using custom baud rates Rogier Wolff
     [not found] ` <20050120150857.GH13036@kroah.com>
2005-01-20 15:22   ` Rogier Wolff
2005-01-21  0:03     ` Greg KH [this message]

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=20050121000342.GA14469@kroah.com \
    --to=greg@kroah.com \
    --cc=R.E.Wolff@harddisk-recovery.nl \
    --cc=bryder@sgi.com \
    --cc=edwin@harddisk-recovery.nl \
    --cc=ftdi-usb-sio-devel@lists.sourceforge.net \
    --cc=kuba@mareimbrium.org \
    --cc=linux-kernel@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