All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org,
	Xavier Bestel <xavier.bestel@free.fr>,
	Jason Dravet <dravet@hotmail.com>
Subject: Re: wrong number of serial port detected
Date: Sat, 7 Jan 2006 16:46:39 +0000	[thread overview]
Message-ID: <20060107164639.GG31384@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051208030916.GC14569@redhat.com>

On Wed, Dec 07, 2005 at 10:09:16PM -0500, Dave Jones wrote:
> Make the number of UARTs registered configurable.
> Also add a nr_uarts module option to the 8250 code
> to override this, up to a maximum of CONFIG_SERIAL_8250_NR_UARTS
> 
> This should appease people who complain about a proliferation
> of /dev/ttyS & /sysfs nodes whilst at the same time allowing
> a single kernel image to support the rarer occasions of
> lots of devices.
> 
> Signed-off-by: Dave Jones <davej@redhat.com>

Any chance of an updated patch please?  It doesn't appear to be
healthy:

patching file drivers/serial/8250.c
Hunk #1 succeeded at 54 (offset 1 line).
Hunk #2 succeeded at 2119 (offset 70 lines).
Hunk #3 succeeded at 2069 (offset 1 line).
Hunk #4 succeeded at 2160 (offset 70 lines).
Hunk #5 succeeded at 2194 (offset 3 lines).
Hunk #6 succeeded at 2297 with fuzz 2 (offset 70 lines).
Hunk #7 succeeded at 2352 with fuzz 1 (offset 1 line).
misordered hunks! output would be garbled
Hunk #8 FAILED at 2421.
Hunk #9 succeeded at 2381 with fuzz 2 (offset -3 lines).
Hunk #10 succeeded at 2492 (offset 69 lines).
Hunk #11 succeeded at 2429 (offset -3 lines).
Hunk #12 succeeded at 2510 (offset 69 lines).
Hunk #13 succeeded at 2523 (offset -3 lines).
Hunk #14 succeeded at 2659 (offset 69 lines).
1 out of 14 hunks FAILED -- saving rejects to file drivers/serial/8250.c.rej
patching file drivers/serial/Kconfig
patching file Documentation/kernel-parameters.txt

Thanks.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-01-07 16:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 15:44 wrong number of serial port detected Jason Dravet
2005-12-07 15:50 ` Russell King
2005-12-07 19:59   ` Jason Dravet
2005-12-07 21:15     ` Russell King
2005-12-07 21:28       ` Xavier Bestel
2005-12-07 21:31         ` Russell King
2005-12-07 21:38           ` Russell King
2005-12-07 23:03             ` Dave Jones
2005-12-07 23:46               ` Russell King
2005-12-08  0:50                 ` Dave Jones
2005-12-08  3:09                   ` Dave Jones
2006-01-07 16:46                     ` Russell King [this message]
2006-01-07 21:05                       ` Dave Jones
2006-01-08  1:23                         ` Jason Dravet
2006-01-08  9:08                           ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2005-12-08  3:02 Jason Dravet
2005-12-08 10:54 ` Russell King
2005-12-09 14:37   ` Jason Dravet
2005-12-09 17:27     ` Russell King
2005-12-09 19:54     ` Bjorn Helgaas
2005-12-10  1:46       ` Jason Dravet
2005-12-10 10:35       ` Russell King
2005-12-10 14:24         ` Jason Dravet
2005-12-10 15:46           ` Russell King
2005-12-10 17:56             ` Jason Dravet

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=20060107164639.GG31384@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=dravet@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /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.