public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org, device@lanana.org
Subject: Re: devices.txt errors
Date: Thu, 13 Jul 2006 14:04:20 -0700	[thread overview]
Message-ID: <20060713210420.GA4218@kroah.com> (raw)
In-Reply-To: <787b0d920607082349h59ec36f7nc477e3cc9f9b6c77@mail.gmail.com>

On Sun, Jul 09, 2006 at 02:49:19AM -0400, Albert Cahalan wrote:
> Major 216 was ttyUB%d (looks normal), but is now rfcomm%d instead?
> The description claims that the device is a tty, yet it no longer
> has a tty name?

Fun with bluetooth issues.  The ttyUB driver is now gone, and the bluez
code uses it instead.  Take it up with those developers if you have
questions...

thanks,

greg k-h

      parent reply	other threads:[~2006-07-13 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09  6:49 devices.txt errors Albert Cahalan
2006-07-09 16:43 ` Stephen Rothwell
2006-07-09 17:22   ` Albert Cahalan
2006-07-10  1:55     ` Stephen Rothwell
2006-07-13 21:04 ` 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=20060713210420.GA4218@kroah.com \
    --to=greg@kroah.com \
    --cc=acahalan@gmail.com \
    --cc=device@lanana.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