From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Omnikey Cardman 4000 driver
Date: Mon, 5 Sep 2005 12:44:37 -0700 [thread overview]
Message-ID: <29495f1d05090512447da5bcb5@mail.gmail.com> (raw)
In-Reply-To: <20050906013545.GB16056@rama.de.gnumonks.org>
On 9/5/05, Harald Welte <laforge@gnumonks.org> wrote:
> Hi!
>
> Following-up to the Cardman 4040 driver, I'm now sumitting a driver for
> the Cardman 4000 reader. It is, too, a PCMCIA smartcard reader and the
> predecessor of the 4040.
>
> From a technical point of view, the two devices have nothing in common,
> so there is no possibility of code sharing.
<snip>
> --- /dev/null
> +++ b/drivers/char/pcmcia/cm4000_cs.c
<snip>
> +/* interruptible_pause() */
> +static inline void ipause(unsigned long amount)
> +{
> + current->state = TASK_INTERRUPTIBLE;
> + schedule_timeout(amount);
> +}
> +
> +/* uninterruptible_pause() */
> +static inline void upause(unsigned long amount)
> +{
> + current->state = TASK_UNINTERRUPTIBLE;
> + schedule_timeout(amount);
> +}
It looks like all callers of these functions pass in milliseconds? Any
chance you can get rid of these two and use msleep_interruptible() and
msleep() instead? As long as you are not using these functions around
wait-queues, you are ok (which I think is the case here). If you are
using wait-queues with these sleeps, then please use
schedule_timeout_interruptible() and
schedule_timeout_uninterruptible() from the -mm tree.
Thanks,
Nish
next prev parent reply other threads:[~2005-09-05 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 1:35 [PATCH] Omnikey Cardman 4000 driver Harald Welte
2005-09-05 19:44 ` Nish Aravamudan [this message]
2005-09-07 7:06 ` Harald Welte
2005-09-05 20:29 ` Jesper Juhl
2005-09-05 20:36 ` Jesper Juhl
2005-09-06 6:59 ` Harald Welte
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=29495f1d05090512447da5bcb5@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=laforge@gnumonks.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 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.