All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>
Cc: Linux I2C <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: i2c: cdev lock_kernel() pushdown
Date: Tue, 15 Jul 2008 17:41:55 +0200	[thread overview]
Message-ID: <20080715174155.2d52e6f6@hyperion.delvare> (raw)

Hi Jonathan,

I am looking at this patch of yours:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3db633ee352bfe20d4a2b0c3c8a46ce31a6c7149

I believe that no locking is needed in i2cdev_open(). Do you have any
reason to think it does? If not, can I simply revert this patch?

Thanks,
-- 
Jean Delvare

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

             reply	other threads:[~2008-07-15 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 15:41 Jean Delvare [this message]
     [not found] ` <20080715174155.2d52e6f6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-15 16:14   ` i2c: cdev lock_kernel() pushdown Jonathan Corbet
     [not found]     ` <20080715101406.6b4517e3-vw3g6Xz/EtPk1uMJSBkQmQ@public.gmane.org>
2008-07-15 16:35       ` Jean Delvare
     [not found]         ` <20080715183552.7e1b797a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-15 16:52           ` Jonathan Corbet
2008-07-15 17:01           ` Jon Smirl
     [not found]             ` <9e4733910807151001r88ed121o4f13546e1d3d93ff-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-15 17:33               ` Ben Dooks
2008-07-15 17:45               ` Jean Delvare
     [not found]                 ` <20080715194550.79dbb226-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-15 18:58                   ` Jon Smirl

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=20080715174155.2d52e6f6@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=corbet-T1hC0tSOHrs@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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.