From: Gustavo Padovan <gustavo@padovan.org>
To: Gianluca Anzolin <gianluca@sottospazio.it>
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Fix tty refcounting in rfcomm/tty.c
Date: Wed, 10 Jul 2013 17:55:41 +0100 [thread overview]
Message-ID: <20130710165541.GE2952@joana> (raw)
In-Reply-To: <20130710162418.GA16548@debian.seek.priv>
Hi Gianluca,
* Gianluca Anzolin <gianluca@sottospazio.it> [2013-07-10 18:24:18 +0200]:
> Hello,
>
> On Wed, Jul 10, 2013 at 04:46:23PM +0100, Gustavo Padovan wrote:
> > Hi Gianluca,
> >
> > haven't looked into detail into these patches, but to get rfcomm patches
> > upstream you would first need the tty maintainer to accept this patch you are
> > mentioning since our side would depend on it. It seems to be a regression
> > caused by aa27a094e2c and your patch seems to be the right fix.
>
> Thank you for pointing that out. These patches were also sent to Marcel Holtman
> who seems to be the maintainer by looking at the source and by using the script
> get_maintainers.pl and I'm waiting for a reply.
>
> The source mentions also Maxim Krasnyansky, I didn't include him since the
> maintainers script didn't return his name anymore. Should I send the patches
> also to him?
No, just keep sending the bluetooth patches here. Once you get the drivers/tty
patch applied we can go ahead with the bluetooth ones. It helps if you also
use git formatted patches.
Gustavo
next prev parent reply other threads:[~2013-07-10 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 17:05 [PATCH 1/2] Fix tty refcounting in rfcomm/tty.c Gianluca Anzolin
2013-07-10 8:17 ` Dean Jenkins
2013-07-10 8:39 ` Mathias Hasselmann
2013-07-10 11:24 ` Gianluca Anzolin
2013-07-10 9:37 ` Gianluca Anzolin
2013-07-10 10:43 ` Gianluca Anzolin
2013-07-10 15:46 ` Gustavo Padovan
2013-07-10 16:24 ` Gianluca Anzolin
2013-07-10 16:55 ` Gustavo Padovan [this message]
2013-07-10 17:01 ` Gianluca Anzolin
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=20130710165541.GE2952@joana \
--to=gustavo@padovan.org \
--cc=gianluca@sottospazio.it \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).