netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Chen <wangchen@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 02/15] [ATM]: Use proc_create() to setup ->proc_fops first
Date: Fri, 29 Feb 2008 13:23:45 +0800	[thread overview]
Message-ID: <47C796E1.7030203@cn.fujitsu.com> (raw)
In-Reply-To: <20080228.135611.252555298.davem@davemloft.net>

David Miller said the following on 2008-2-29 5:56:
> From: Wang Chen <wangchen@cn.fujitsu.com>
> Date: Thu, 28 Feb 2008 18:55:23 +0800
> 
>> Use proc_create() to make sure that ->proc_fops be setup before gluing
>> PDE to main tree.
>>
>> Signed-off-by: Wang Chen <wangchen@cn.fujitsu.com>
> 
> Applied, thanks.
> 
> Some of those paths could definitely use some error
> handling.
> 

Thanks Dave, I will make patch for error handling later.


      reply	other threads:[~2008-02-29  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 10:55 [PATCH 02/15] [ATM]: Use proc_create() to setup ->proc_fops first Wang Chen
2008-02-28 21:56 ` David Miller
2008-02-29  5:23   ` Wang Chen [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=47C796E1.7030203@cn.fujitsu.com \
    --to=wangchen@cn.fujitsu.com \
    --cc=davem@davemloft.net \
    --cc=netdev@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).