linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth 2014-05-15
Date: Thu, 15 May 2014 10:59:56 -0300	[thread overview]
Message-ID: <20140515135956.GC1966@joana> (raw)
In-Reply-To: <20140515135600.GB1966@joana>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

forgot to sign it..

2014-05-15 Gustavo Padovan <gustavo@padovan.org>:

> Hi John,
> 
> This pull request contains a very important fix for 3.15. Here we fix the
> permissions of a debugfs file that would otherwise allow unauthorized users
> to write content to it.
> 
> Please pull! Thanks.
> 
>         Gustavo
> 
> ---
> The following changes since commit 1fb4e09a7e780b915dbd172592ae7e2a4c071065:
> 
>   Bluetooth: Add support for Lite-on [04ca:3007] (2014-04-25 09:47:16 +0300)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
> 
> for you to fetch changes up to 40b9397a1a61a37917b93e7d57e6f2faf3a086b4:
> 
>   Bluetooth: Fix L2CAP LE debugfs entries permissions (2014-05-14 09:07:07 -0700)
> 
> ----------------------------------------------------------------
> Samuel Ortiz (1):
>       Bluetooth: Fix L2CAP LE debugfs entries permissions
> 
>  net/bluetooth/l2cap_core.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-05-15 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 13:56 pull request: bluetooth 2014-05-15 Gustavo Padovan
2014-05-15 13:59 ` Gustavo Padovan [this message]
2014-05-19 20:34 ` 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=20140515135956.GC1966@joana \
    --to=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).