Netdev List
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Pull request: bluetooth-2.6 2009-05-05
Date: Tue, 05 May 2009 13:48:59 -0700	[thread overview]
Message-ID: <1241556539.2987.31.camel@localhost.localdomain> (raw)

Hi Dave,

this is kinda embarrassing since I did ack the initial dev_set_name()
change for 2.6.28, but at that point it was not allocating any memory
and so nobody ran into any problems with it. However with 2.6.30 it is
allocating memory with GFP_KERNEL and so we have to move it. The change
is simple and straight forward.

Regards

Marcel


Please pull from

    git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master

This will update the following files:

 net/bluetooth/hci_sysfs.c |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)

through these ChangeSets:

Marcel Holtmann (1):
    Bluetooth: Move dev_set_name() to a context that can sleep




             reply	other threads:[~2009-05-05 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 20:48 Marcel Holtmann [this message]
2009-05-05 20:55 ` Pull request: bluetooth-2.6 2009-05-05 David Miller

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=1241556539.2987.31.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=netdev@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