public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Nick Pelly <npelly@google.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: patch: Respect HCI_UART_DEBUG config in hci_ll.c
Date: Sun, 30 Nov 2008 10:04:01 +0100	[thread overview]
Message-ID: <1228035841.9176.9.camel@violet.holtmann.net> (raw)
In-Reply-To: <35c90d960811201824o64e0d814s8cf55ba6ee145517@mail.gmail.com>

Hi Nick,

> Author: Nick Pelly <npelly@google.com>
> Date:   Mon Apr 21 12:18:51 2008 -0700
> 
>     bluetooth: Respect HCI_UART_DEBUG config in hci_ll.c
> 
>     Following the pattern from hci_*.c, turn off BT_DBG messages unless
>     they have been requested via HCI_UART_DEBUG
> 
>     Signed-off-by: Brian Swetland <swetland@google.com>

you have to fix your mail client to _NOT_ send mutli-part crap. Please
follow the proper guidelines for sending kernel patches. Otherwise you
make it complicated for me to apply patches. Especially these no
brainers.

So who wrote this patch? You are Brian. If you wrote the patch like
author indicated, then Brian should do an Acked-by unless he actually
sends the patch to me. In this case you send the patch so it should look
like this:

Signed-off-by: Nick Pelly <npelly@google.com>
Acked-by: Brian Swetland <swetland@google.com>

If you wrote the patch and Brian sent it to me, then he has to do
Signed-off since he is part of the chain. It is all documented in the
kernel source code :)

Regards

Marcel



  reply	other threads:[~2008-11-30  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21  2:24 patch: Respect HCI_UART_DEBUG config in hci_ll.c Nick Pelly
2008-11-30  9:04 ` Marcel Holtmann [this message]
     [not found]   ` <35c90d960811301800o114b9b58pafeae86c09d668e9@mail.gmail.com>
2008-12-01  2:02     ` Nick Pelly

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=1228035841.9176.9.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=npelly@google.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