Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Nami <nami.li@atheros.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth:  FTP and OPP over L2CAP
Date: Wed, 15 Jun 2011 04:14:38 -0700	[thread overview]
Message-ID: <1308136501.2518.8.camel@aeonflux> (raw)
In-Reply-To: <1308109889-5597-1-git-send-email-nami.li@atheros.com>

Hi Nami,

> From: nami <nami.li@atheros.com>
> 
> 
> Signed-off-by: Nami <nami.li@atheros.com>

the number one thing here is to get your GIT setup done right and follow
our polices like no signed-off-by line for bluez and obexd submissions.

> ---
>  client/main.c       |   26 +++++++----
>  client/session.c    |  119 ++++++++++++++++++++++++++++++++++++++++++++++----
>  client/session.h    |    6 +++
>  gwobex/gw-obex.c    |    6 +-
>  gwobex/gw-obex.h    |    3 +-
>  gwobex/obex-priv.c  |    4 +-
>  gwobex/obex-priv.h  |    2 +-
>  plugins/bluetooth.c |  112 +++++++++++++++++++++++++++++++++++++++++++++---
>  plugins/ftp.c       |    8 +++-
>  plugins/opp.c       |    8 +++-
>  src/obex.c          |   10 +++-
>  src/service.h       |    7 +++
>  test/main.c         |    2 +-
>  13 files changed, 275 insertions(+), 38 deletions(-)

And without even looking at the actual patch, I can tell you right now
here that you should have split this up into logical pieces. For example
gwobex should be it separate patch in the first place. And I assume
others can also be nicely split up.

These "monster" patches are not acceptable.

Regards

Marcel



  reply	other threads:[~2011-06-15 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  3:51 [PATCH 1/2] Bluetooth: FTP and OPP over L2CAP Nami
2011-06-15 11:14 ` Marcel Holtmann [this message]
2011-06-16  3:22   ` Li, Nami

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=1308136501.2518.8.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nami.li@atheros.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