[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANq1E4T1_0heb+K49-kJYwsqLNusyc-Vc-YsWrP_3gBEVe4C2w@mail.gmail.com>
Date: Thu, 2 Aug 2012 15:45:44 +0200
From: David Herrmann <dh.herrmann@...glemail.com>
To: Shea Levy <shea@...alevy.com>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Gustavo Padovan <gustavo@...ovan.org>,
Johan Hedberg <johan.hedberg@...il.com>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Bluetooth: Add support for Apple MacBook Pro 9,2
Hi Shea
On Thu, Aug 2, 2012 at 3:39 PM, Shea Levy <shea@...alevy.com> wrote:
> Hi David,
>
> On Aug 2, 2012, at 9:32 AM, David Herrmann <dh.herrmann@...glemail.com> wrote:
>
>> Hi Shea
>>
>> On Thu, Aug 2, 2012 at 2:45 PM, <shea@...alevy.com> wrote:
>>> From: Shea Levy <shea@...alevy.com>
>>>
>>>
>>> Signed-off-by: Shea Levy <shea@...alevy.com>
>>
>> Why is this patch missing a commit-message? Please add one.
>
> The commit message was only one line, which git-send-email puts in the subject.
I know that. But I prefer non-empty commit-message bodies. Well, maybe
I am the only one ;)
>> And also
>> include the output of "usb-devices" or the contents of
>> /sys/kernel/debug/usb/devices in this commit-message.
>>
>
> OK. The whole thing or just the relevant bits? Does it matter if I'm booted into the patched kernel or not?
Just copy the output of the relevant parts, that is, the one for your
device. It is used by the maintainer to validate that there was no
copy/paste mistake. It doesn't matter if booted with or without the
patch.
Thanks
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists