From: Marcel Holtmann <marcel@holtmann.org>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 1/3] Add support for command line arguments on hid2hci tool
Date: Sat, 16 May 2009 06:35:51 -0700 [thread overview]
Message-ID: <1242480951.3446.33.camel@localhost.localdomain> (raw)
In-Reply-To: <4A0DE78B.8080503@dell.com>
Hi Mario,
> > please restrict the commit message to 70-72 chars per line.
> >
> > And please do the following changes:
> >
> > s/radiomode/mode/ since it is not about the radio part here.
> >
> > s/hidproxy/csr/ if you wanna expose this then call it what it is.
> >
> > And go over the coding style once more since there are some cases where
> > it breaks.
> >
> > Also please split Makefile/rules changes from the actual code changes. I
> > want two patches here. One that fixes the code and another one that
> > takes care of the udev integration.
> >
> > Other than that, looks pretty good.
> >
> Thanks for the feedback. I've hopefully addressed all of your
> concerns. If you still have problems with coding style, can you please
> point them out specifically? The attached patch is the code portion of
> the split up patch. Again it's attached so my mail server doesn't
> mangle it.
patch has been applied. However I was serious about the 70-72 chars
width of the commit message. Had to manually fix that.
Also it is Bluetooth and not bluetooth when writing about it. That is a
trademark issue :)
Regards
Marcel
prev parent reply other threads:[~2009-05-16 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 19:40 [PATCH 1/3] Add support for command line arguments on hid2hci tool Mario Limonciello
2009-05-15 20:11 ` Marcel Holtmann
2009-05-15 22:07 ` Mario Limonciello
2009-05-16 13:35 ` Marcel Holtmann [this message]
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=1242480951.3446.33.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mario_limonciello@dell.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