linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alfred E. Heggestad" <aeh@db.org>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: dtor@mail.ru, linux-input@vger.kernel.org
Subject: Re: [PATCH] Driver for VoIP CM109 Chipset
Date: Thu, 07 Feb 2008 19:39:20 +0100	[thread overview]
Message-ID: <47AB5058.6090507@db.org> (raw)
In-Reply-To: <200802052223.26399.carlos@strangeworlds.co.uk>

Carlos Corbacho wrote:
> Two minor nitpicks.
> 

Hi Carlos,

thanks for your feedback. I just updated the patch, and submitted a new
version..


/alfred

> On Tuesday 05 February 2008 21:39:30 Alfred E. Heggestad wrote:
>> +/*
>> + * drivers/input/misc/cm109.c
> 
> Don't put the filename in the source file - this is now generally frowned 
> upon. Instead, replace that with a title/ short description for the driver.
> 
> e.g. Move this line up instead to the top, rather than burying it under the 
> copyright notice:
> 
> Driver for the VoIP USB phones with CM109 chipsets.
> 
>> + * History:
>> + *   20080205 alfredh	Upgrade to 2.6.24
>> + *   20070829 alfredh	Added keymap for Genius G-talk (thanks Shaun)
>> + *   20070826 alfredh	2.6.22.5, added to blacklist in hid-quirks.c
>> + *   20070626 alfredh	2.6.22-rc6, linux-input peer review
>> + *   20070616 alfredh	Adapt for kernel 2.6.22-rc4
>> + *   20070615 alfredh	Change GFP_KERNEL -> GFP_ATOMIC
>> + *   20070610 alfredh	Buzzer through input SND_TONE/SND_BELL
>> + *   20070227 alfredh	Draft version with keyboard scan and buzzer
> 
> ChangeLog's/ history should go in the commit message, not the code. It's the 
> job of the revision control system to maintain the history of the code, not 
> the codes job.
> 
> -Carlos

      reply	other threads:[~2008-02-07 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 21:39 [PATCH] Driver for VoIP CM109 Chipset Alfred E. Heggestad
2008-02-05 22:23 ` Carlos Corbacho
2008-02-07 18:39   ` Alfred E. Heggestad [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=47AB5058.6090507@db.org \
    --to=aeh@db.org \
    --cc=carlos@strangeworlds.co.uk \
    --cc=dtor@mail.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).