From: Greg KH <gregkh@linuxfoundation.org>
To: Won Kang <wkang77@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
sachin.kamat@linaro.org, yongjun_wei@trendmicro.com.cn,
wonkang@gctsemi.com, joe@perches.com, dan.carpenter@oracle.com
Subject: Re: [PATCH v2] staging: gdm7240: a TTY rewrite according to the latest TTY APIs
Date: Wed, 14 Aug 2013 14:12:00 -0700 [thread overview]
Message-ID: <20130814211200.GA4528@kroah.com> (raw)
In-Reply-To: <1376390761-31545-1-git-send-email-wonkang@gctsemi.com>
On Tue, Aug 13, 2013 at 07:46:01PM +0900, Won Kang wrote:
> Removed the old style reference countings and termios.
> Renamed variables to meaninful ones.
>
> Fixed mis-use of mutex for gdm_table. gdm_table is refered to only
> inside tty_install and port destrcut, and usb callbacks use internal
> reference which was saved during urb submission
>
> Signed-off-by: Won Kang <wonkang@gctsemi.com>
> ---
> v2: fixed mutex bug, added ChangeLog, added missing kfree
> drivers/staging/gdm724x/ChangeLog | 62 ++++++++
Why a changelog? The kernel has a changelog, in the git commit log, if
every individual driver had a separate changelog, the tree would be a
mess, right? It also looks like you included things that are already in
the kernel changelog (patches from me and others), so this is duplicated
effort.
> drivers/staging/gdm724x/gdm_mux.c | 9 +-
> drivers/staging/gdm724x/gdm_mux.h | 14 +-
> drivers/staging/gdm724x/gdm_tty.c | 295 +++++++++++++++++--------------------
> drivers/staging/gdm724x/gdm_tty.h | 36 +++--
> 5 files changed, 237 insertions(+), 179 deletions(-)
> create mode 100644 drivers/staging/gdm724x/ChangeLog
>
> diff --git a/drivers/staging/gdm724x/ChangeLog b/drivers/staging/gdm724x/ChangeLog
> new file mode 100644
> index 0000000..506e60e
> --- /dev/null
> +++ b/drivers/staging/gdm724x/ChangeLog
> @@ -0,0 +1,62 @@
> +2013-08-13 Won Kang <wonkang@gctsemi.com>
> + * Fixed mis-use of mutex for gdm_table. gdm_table is refered to only
> + * inside tty_install and port destrcut, and usb callbacks use internal
> + * reference which was saved during urb submission
> +
> +2013-08-09 Won Kang <wonkang@gctsemi.com>
> + * A rewrite was needed to properly use latest TTY AAPI
> + *
> + * Original TTY codes were written from kernel 2.6.x, doing tty reference
> + * counting within the this driver. This is fixed to use tty core APIs.
> + *
> + * The usage count of tty port is no longer handled by the driver.
> + *
> + * termios members of tty_operations as the ports are virtual and
> + * have no real effect.
> + *
> + * Renamed variables to be more clear as they were confusing due to the
> + * similarities with the tty core structures.
Please send these two patches, not mushed together as one, so I can
apply them that way.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-14 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 8:19 [PATCH] staging: gdm7240: a TTY rewrite according to the latest TTY APIs Won Kang
2013-08-09 10:57 ` Dan Carpenter
2013-08-13 10:46 ` [PATCH v2] " Won Kang
2013-08-14 21:12 ` Greg KH [this message]
2013-08-16 4:13 ` [PATCH 1/2] " Won Kang
2013-08-16 4:13 ` [PATCH 2/2] " Won Kang
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=20130814211200.GA4528@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=wkang77@gmail.com \
--cc=wonkang@gctsemi.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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.