All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Marek Michalkiewicz <marekm@amelek.gda.pl>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [patch] 2.4.2 Advantech WDT driver
Date: Sat, 03 Mar 2001 13:53:03 -0500	[thread overview]
Message-ID: <3AA13D8F.404DC635@mandrakesoft.com> (raw)
In-Reply-To: <E14ZCEl-0001xd-00@mm.amelek.gda.pl>

Marek Michalkiewicz wrote:
> 
> > Why is lock_kernel necessary?
> 
> Well, it is there in 2.4.2 acquirewdt.c (which this driver is based on -
> really only minimal changes, the hardware is only slightly different).
> I can remove it if you tell me it's really not necessary.

Sounds like it got caught in an audit and is necessary, I didn't look
closely...


> > > +       spin_lock_init(&advwdt_lock);
> > > +       misc_register(&advwdt_miscdev);
> >
> > check return code for error
> 
> Again, acquirewdt.c doesn't do it with the misc_register, request_region
> and register_reboot_notifier calls.  (Should it?  Cc: Alan Cox)

Yes, the return codes should be checked.  :)

-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie

      reply	other threads:[~2001-03-03 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28 17:21 [patch] 2.4.2 Advantech WDT driver Marek Michalkiewicz
2001-02-28 17:37 ` Jeff Garzik
2001-03-03 13:38   ` Marek Michalkiewicz
2001-03-03 18:53     ` Jeff Garzik [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=3AA13D8F.404DC635@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marekm@amelek.gda.pl \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.