From: Gianluca Anzolin <gianluca@sottospazio.it>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
peter@hurleysoftware.com,
"linux-bluetooth@vger.kernel.org development"
<linux-bluetooth@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
jslaby@suse.cz, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] Regression fixes for rfcomm/tty.c
Date: Mon, 6 Jan 2014 18:42:34 +0100 [thread overview]
Message-ID: <20140106174234.GA23339@sottospazio.it> (raw)
In-Reply-To: <D4D6DA93-0C44-4F35-AD45-9EDE4775B052@holtmann.org>
On Mon, Jan 06, 2014 at 09:35:18AM -0800, Marcel Holtmann wrote:
> Hi Gianluca,
>
> I applied both patches to bluetooth-next to expose them wider testing. I like to have them go through bluetooth-next first before we push them back into -stable.
>
> Regards
>
> Marcel
>
Thank you for the reply, however there is another regression and the fix would
make the second patch unnecessary.
Would it be better if I resend a second iteration of patches? There would be 4
patches, two fixes and two which move code around.
next prev parent reply other threads:[~2014-01-06 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 16:30 [PATCH 0/2] Regression fixes for rfcomm/tty.c Gianluca Anzolin
2014-01-04 16:30 ` [PATCH 1/2] rfcomm: release the port when the last user closes the tty Gianluca Anzolin
2014-01-04 16:30 ` [PATCH 2/2] rfcomm: move the device under its parent if already connected Gianluca Anzolin
2014-01-06 17:35 ` [PATCH 0/2] Regression fixes for rfcomm/tty.c Marcel Holtmann
2014-01-06 17:42 ` Gianluca Anzolin [this message]
2014-01-06 18:19 ` Marcel Holtmann
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=20140106174234.GA23339@sottospazio.it \
--to=gianluca@sottospazio.it \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@padovan.org \
--cc=jslaby@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=peter@hurleysoftware.com \
--cc=stable@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