mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Schindler <armin@melware.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isdn divas: fix proc creation
Date: Fri, 6 Jun 2008 08:44:08 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.0.99.0806060842360.7260@k10.melware.de> (raw)
In-Reply-To: <20080606061744.GB4977@martell.zuzino.mipt.ru>

On Fri, 6 Jun 2008, Alexey Dobriyan wrote:
> On Thu, Jun 05, 2008 at 12:25:06PM +0200, Armin Schindler wrote:
>> On Sat, 31 May 2008, Alexey Dobriyan wrote:
>>> 1. creating proc entry and not saving pointer to PDE and checking it
>>>   is not going to work.
>>
>> I don't know where you found this. I have look even in older versions, but
>> the pointer divas_proc_entry is set by proc_create(). The patch to
>> divasproc.c is wrong, it exists from the beginning of the driver.
>> (2.6.25.4 doesn't contain the bug you describe).
>
> Check mainline kernel, namely, 2.6.26-rc5.

Ah, okay. So someone removed the pointer between 2.6.25 and 2.6.26 then.
In that case your patch is correct of course.

Armin

>>> --- a/drivers/isdn/hardware/eicon/divasproc.c
>>> +++ b/drivers/isdn/hardware/eicon/divasproc.c
>>> @@ -125,8 +125,8 @@ static const struct file_operations divas_fops = {
>>>
>>> int create_divas_proc(void)
>>> {
>>> -	proc_create(divas_proc_name, S_IFREG | S_IRUGO, proc_net_eicon,
>>> -		    &divas_fops);
>>> +	divas_proc_entry = proc_create(divas_proc_name, S_IFREG | S_IRUGO,
>>> +					proc_net_eicon, &divas_fops);
>>> 	if (!divas_proc_entry)
>>> 		return (0);
>

      reply	other threads:[~2008-06-06  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 23:34 Alexey Dobriyan
2008-06-05 10:25 ` Armin Schindler
2008-06-06  6:17   ` Alexey Dobriyan
2008-06-06  6:44     ` Armin Schindler [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=alpine.DEB.0.99.0806060842360.7260@k10.melware.de \
    --to=armin@melware.de \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®