From: Johan Hovold <johan@kernel.org>
To: Mathieu OTHACEHE <m.othacehe@gmail.com>
Cc: Johan Hovold <johan@kernel.org>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/4] USB: mxu11x0: fix memory leak on usb_serial private data
Date: Mon, 29 Feb 2016 10:38:50 +0100 [thread overview]
Message-ID: <20160229093850.GA26559@localhost> (raw)
In-Reply-To: <20160228163054.GA6002@gmail.com>
On Sun, Feb 28, 2016 at 05:30:54PM +0100, Mathieu OTHACEHE wrote:
> On Sun, Feb 28, 2016 at 01:20:16PM +0100, Johan Hovold wrote:
> So, I could post a patch serie :
>
> 1. Removing mxu11x0 driver
> 2. Patching ti_usb_3410_5052
> 3. Cleaning up ti_usb_3410_5052 the same as we cleaned-up mxu11x0
Please do. If we could bring ti_usb_3410_5052 to the same state as
mxu11x0 is today that's be great.
> Btw, no response of TI or MOXA about the double opening stuff.
Never mind that for now. Moxa apparently just copied the TI driver and
ran search and replace on the symbol prefixes. I assume they won't have
an answer.
Thanks,
Johan
next prev parent reply other threads:[~2016-02-29 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 18:49 [PATCH v2 0/4] USB: mxu11x0: fixes and follow ups Mathieu OTHACEHE
2016-01-04 18:49 ` [PATCH v2 1/4] USB: mxu11x0: fix memory leak on usb_serial private data Mathieu OTHACEHE
2016-01-25 12:01 ` Johan Hovold
2016-01-30 17:40 ` Mathieu OTHACEHE
2016-02-28 12:20 ` Johan Hovold
2016-02-28 16:30 ` Mathieu OTHACEHE
2016-02-29 9:38 ` Johan Hovold [this message]
2016-01-04 18:49 ` [PATCH v2 2/4] USB: mxu11x0: clean device control commands Mathieu OTHACEHE
2016-01-04 18:49 ` [PATCH v2 3/4] USB: mxu11x0: remove duplicated set_termios call Mathieu OTHACEHE
2016-01-04 18:49 ` [PATCH v2 4/4] USB: mxu11x0: move firmware download and endpoint testing to probe callback Mathieu OTHACEHE
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=20160229093850.GA26559@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.othacehe@gmail.com \
/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