From: Greg KH <greg@kroah.com>
To: Abhijit Lamsoge <abhijitelinux@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Serial Core crash in tty_open
Date: Wed, 28 May 2014 07:36:50 -0700 [thread overview]
Message-ID: <20140528143650.GC24698@kroah.com> (raw)
In-Reply-To: <CAKnSG-bhcO6x309aiE2nwgBjXU=0u=3dXH-GgKQvjK=6S-q1JA@mail.gmail.com>
On Wed, May 28, 2014 at 02:25:06PM +0530, Abhijit Lamsoge wrote:
> Hi All,
> I had written a char/serial driver for Kernel 3.0 to 3.1 in old times
> and it used to work absolutely fine.
> Now I need this driver for some bluetooth, virtual mount-point for
> data transfer to and fro to mobile,
> for kernel version 3.8 onwards, however, there is a big crash, when I
> do any data transfer on the uart_port created by this driver.
Lots of things have changed in the serial / tty layer since 3.0 days.
Why not post your code to be merged into the kernel tree so that this
doesn't happen in the future when apis change again?
greg k-h
prev parent reply other threads:[~2014-05-28 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 8:55 Serial Core crash in tty_open Abhijit Lamsoge
2014-05-28 9:04 ` Abhijit Lamsoge
2014-05-28 14:37 ` Greg KH
2014-05-29 9:39 ` Abhijit Lamsoge
2014-05-28 14:36 ` 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=20140528143650.GC24698@kroah.com \
--to=greg@kroah.com \
--cc=abhijitelinux@gmail.com \
--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 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.