From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: padovan@profusion.mobi, netdev@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: Fix regressions for 3.0
Date: Sun, 17 Jul 2011 12:46:31 -0400 [thread overview]
Message-ID: <20110717164631.GA18545@tuxdriver.com> (raw)
In-Reply-To: <20110716.101518.1007939482226184514.davem@davemloft.net>
On Sat, Jul 16, 2011 at 10:15:18AM -0700, David Miller wrote:
> From: "Gustavo F. Padovan" <padovan@profusion.mobi>
> Date: Sat, 16 Jul 2011 01:30:19 -0300
>
> > From: "Gustavo F. Padovan" <padovan@profusion.mobi>
> >
> > Gustavo F. Padovan (1):
> > Bluetooth: Fix regression in L2CAP connection procedure
> >
> > Ilia Kolomisnky (1):
> > Bluetooth: Fix crash with incoming L2CAP connections
> >
> > net/bluetooth/l2cap_core.c | 9 +++++----
> > 1 files changed, 5 insertions(+), 4 deletions(-)
>
> John I'm going to apply these directly so I can get them to
> Linus in time for 3.0-final.
>
> Thanks Gustavo.
Yup, looks great -- thanks!
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/2] Bluetooth: Fix regressions for 3.0
Date: Sun, 17 Jul 2011 12:46:31 -0400 [thread overview]
Message-ID: <20110717164631.GA18545@tuxdriver.com> (raw)
In-Reply-To: <20110716.101518.1007939482226184514.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Sat, Jul 16, 2011 at 10:15:18AM -0700, David Miller wrote:
> From: "Gustavo F. Padovan" <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
> Date: Sat, 16 Jul 2011 01:30:19 -0300
>
> > From: "Gustavo F. Padovan" <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
> >
> > Gustavo F. Padovan (1):
> > Bluetooth: Fix regression in L2CAP connection procedure
> >
> > Ilia Kolomisnky (1):
> > Bluetooth: Fix crash with incoming L2CAP connections
> >
> > net/bluetooth/l2cap_core.c | 9 +++++----
> > 1 files changed, 5 insertions(+), 4 deletions(-)
>
> John I'm going to apply these directly so I can get them to
> Linus in time for 3.0-final.
>
> Thanks Gustavo.
Yup, looks great -- thanks!
--
John W. Linville Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org might be all we have. Be ready.
next prev parent reply other threads:[~2011-07-17 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 4:30 [PATCH 0/2] Bluetooth: Fix regressions for 3.0 Gustavo F. Padovan
2011-07-16 4:30 ` Gustavo F. Padovan
2011-07-16 4:30 ` [PATCH 1/2] Bluetooth: Fix regression in L2CAP connection procedure Gustavo F. Padovan
2011-07-16 4:30 ` Gustavo F. Padovan
2011-07-16 4:30 ` [PATCH 2/2] Bluetooth: Fix crash with incoming L2CAP connections Gustavo F. Padovan
2011-07-16 17:15 ` [PATCH 0/2] Bluetooth: Fix regressions for 3.0 David Miller
2011-07-16 17:15 ` David Miller
2011-07-17 16:46 ` John W. Linville [this message]
2011-07-17 16:46 ` John W. Linville
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=20110717164631.GA18545@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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.