public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: liyu <liyu@ccoss.com.cn>
To: Arnd Bergmann <arnd.bergmann@de.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Subject: Re: [PATCH 2/2] usbhid: HID device simple driver interface
Date: Thu, 27 Jul 2006 09:17:56 +0800	[thread overview]
Message-ID: <44C81444.9090706@ccoss.com.cn> (raw)
In-Reply-To: <200607270154.14021.arnd.bergmann@de.ibm.com>

    Well, That change from macro to inline function is more bettter idea.

    Regarding the Documentation/newwhere, I also have such plan to
complete it, but need some time.
We will have it.

    Regarding list_* marco, I really apologize, they wrote when I
implemented matched_lock/simple_lock
as spin lock. As I found this design have some restrictions, I replace
spin lock with semaphore, but leave these macro in header. I will clear
them.

    For Patch splitting, I can not find more words in Documentation/,
however, It seem Arnd are right.
The next version of this patch will join core patch and header patch.

    Last, I had tried again and again, but mail client still replace TAB
with spaces, I think I should replace it with another.
   
    Thanks a lot.

Arnd Bergmann wrote:
> On Wednesday 26 July 2006 18:10, Josef Sipek wrote:
>   
>> You should use (hid) instead of hid. Because of how the pre-processor works.
>>
>>     
>
> Or, even better, use an inline function instead of a macro whereever
> possible.
>
> One more thing, the description for patch 1 can probably be refined
> a bit more and put into Documentation/somewhere as a new file.
>
> Regarding the split of the patch, it's usually a bad idea to 
> put the header file into a separate patch from its users.
> E.g. if someone during debugging tries to revert patch 2 but not
> patch 1, he ends up with a broken build.
>
> 	Arnd <><
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>
>   


      reply	other threads:[~2006-07-27  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 10:41 [PATCH 2/2] usbhid: HID device simple driver interface liyu
2006-07-26 16:10 ` Josef Sipek
2006-07-26 23:54   ` Arnd Bergmann
2006-07-27  1:17     ` liyu [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=44C81444.9090706@ccoss.com.cn \
    --to=liyu@ccoss.com.cn \
    --cc=arnd.bergmann@de.ibm.com \
    --cc=jsipek@fsl.cs.sunysb.edu \
    --cc=linux-kernel@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