All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
	David Herrmann <dh.herrmann@gmail.com>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	"linux-bluetooth@vger.kernel.org development"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: hidp: make sure input buffers are big enough
Date: Mon, 17 Feb 2014 08:32:25 -0800	[thread overview]
Message-ID: <37F7D8DE-5861-4452-B2F7-00D5E5F952B0@holtmann.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1402171506450.1192@pobox.suse.cz>

Hi Jiri,

>>>>>>>> just got back to this, finally ... did you have time to work on this at
>>>>>>>> all, or should I just start from scratch?
>>>>>>> 
>>>>>>> Sorry, no. Fosdem is this weekend and I needed to get my code ready
>>>>>>> for that. But I'll finally have time again next week.
>>>>>> 
>>>>>> Okay, thanks. I then guess we should proceed with this bandaid (double
>>>>>> allocation) for 3.14
>>>>> 
>>>>> It would be really nice if we could get the HIDP patch into 3.14-rc2
>>>>> and backported to stable. There have been quite a bunch of reports now
>>>>> and I dislike adding a GFP_ATOMIC allocation in HID core. 
>>>> 
>>>> I agree with David; Gustavo, what is your take on this, please?
>>> 
>>> I leave this up to Gustavo to get this into wireless tree for 3.14-rc2.
>>> 
>>> Acked-by: Marcel Holtmann <marcel@holtmann.org>
>> 
>> Thanks a lot.
>> 
>> Gustavo, what is your take on this please? I can take it through hid.git 
>> in case you don't have anything else queued for -rc2.
> 
> ... ping?
> 
> In case this doesn't get reacted upon by the end of the week, I am 
> inclined to take it through hid.git.

take it through hid.git please.

Regards

Marcel


WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
	David Herrmann <dh.herrmann@gmail.com>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	"linux-bluetooth@vger.kernel.org development"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: hidp: make sure input buffers are big enough
Date: Mon, 17 Feb 2014 08:32:25 -0800	[thread overview]
Message-ID: <37F7D8DE-5861-4452-B2F7-00D5E5F952B0@holtmann.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1402171506450.1192@pobox.suse.cz>

Hi Jiri,

>>>>>>>> just got back to this, finally ... did you have time to work on this at
>>>>>>>> all, or should I just start from scratch?
>>>>>>> 
>>>>>>> Sorry, no. Fosdem is this weekend and I needed to get my code ready
>>>>>>> for that. But I'll finally have time again next week.
>>>>>> 
>>>>>> Okay, thanks. I then guess we should proceed with this bandaid (double
>>>>>> allocation) for 3.14
>>>>> 
>>>>> It would be really nice if we could get the HIDP patch into 3.14-rc2
>>>>> and backported to stable. There have been quite a bunch of reports now
>>>>> and I dislike adding a GFP_ATOMIC allocation in HID core. 
>>>> 
>>>> I agree with David; Gustavo, what is your take on this, please?
>>> 
>>> I leave this up to Gustavo to get this into wireless tree for 3.14-rc2.
>>> 
>>> Acked-by: Marcel Holtmann <marcel@holtmann.org>
>> 
>> Thanks a lot.
>> 
>> Gustavo, what is your take on this please? I can take it through hid.git 
>> in case you don't have anything else queued for -rc2.
> 
> ... ping?
> 
> In case this doesn't get reacted upon by the end of the week, I am 
> inclined to take it through hid.git.

take it through hid.git please.

Regards

Marcel


  reply	other threads:[~2014-02-17 16:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 11:09 [PATCH] Bluetooth: hidp: make sure input buffers are big enough David Herrmann
2013-12-19 11:09 ` David Herrmann
2013-12-20 13:36 ` Marcel Holtmann
2013-12-27 12:35   ` David Herrmann
2014-01-07 12:11     ` Jiri Kosina
2014-01-07 16:34       ` David Herrmann
2014-01-07 17:13         ` Jiri Kosina
2014-01-28 20:53           ` Jiri Kosina
2014-01-29  8:36             ` David Herrmann
2014-02-03 10:08               ` Jiri Kosina
2014-02-03 11:27                 ` David Herrmann
2014-02-04 13:46                   ` Jiri Kosina
2014-02-04 13:46                     ` Jiri Kosina
2014-02-04 16:39                     ` Marcel Holtmann
2014-02-05 15:49                       ` Jiri Kosina
2014-02-05 15:49                         ` Jiri Kosina
2014-02-17 14:07                         ` Jiri Kosina
2014-02-17 14:07                           ` Jiri Kosina
2014-02-17 16:32                           ` Marcel Holtmann [this message]
2014-02-17 16:32                             ` Marcel Holtmann
2014-02-17 20:21                             ` Jiri Kosina
2014-02-17 20:21                               ` Jiri Kosina

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=37F7D8DE-5861-4452-B2F7-00D5E5F952B0@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=dh.herrmann@gmail.com \
    --cc=gustavo@padovan.org \
    --cc=jkosina@suse.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-input@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 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.