All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jean Delvare <jdelvare@suse.de>, Greg KH <gregkh@linuxfoundation.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@linaro.org>
Subject: Re: [PATCH 2/2] i2c-dev: Don't block the adapter from unregistering
Date: Mon, 18 Jul 2016 13:20:05 -0700	[thread overview]
Message-ID: <20160718202005.GA18283@ubuntu> (raw)
In-Reply-To: <20160711215058.GA7808@kroah.com>

On 11-07-16, 14:50, Greg KH wrote:
> Ideally, yes, userspace will have closed that device node.  But again,
> hardware isn't kind and sometimes decides to be yanked out by users
> before they tell the kernel about it.  We handle this for almost all
> other device subsystems, i2c is one of the last to be fixed up in this
> manner.  Sorry it's taken us well over a decade to get here :)
> 
> hope that explains things better,

@Jean: Ping :)

-- 
viresh

  reply	other threads:[~2016-07-18 20:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  2:57 [PATCH 0/2] i2c-dev: Don't let userspace block adapter Viresh Kumar
2016-07-06  2:57 ` [PATCH 1/2] i2c-dev: don't get i2c adapter via i2c_dev Viresh Kumar
2016-07-06 17:04   ` Jean Delvare
2016-07-06 17:07     ` Viresh Kumar
2016-07-07 13:16   ` Jean Delvare
2016-07-07 15:35     ` Viresh Kumar
2016-07-08  1:31   ` Wolfram Sang
2016-07-06  2:57 ` [PATCH 2/2] i2c-dev: Don't block the adapter from unregistering Viresh Kumar
2016-07-06  4:32   ` kbuild test robot
2016-07-06  4:32     ` kbuild test robot
2016-07-06  6:55   ` Wolfram Sang
2016-07-06 13:50     ` Viresh Kumar
2016-07-06 17:12     ` Jean Delvare
2016-07-06 20:55       ` Viresh Kumar
2016-07-11 12:22         ` Jean Delvare
2016-07-11 21:50           ` Greg KH
2016-07-18 20:20             ` Viresh Kumar [this message]
2016-07-25  9:39             ` Jean Delvare
2016-07-25 22:31               ` Viresh Kumar
2016-07-26  7:41                 ` Jean Delvare
2016-07-26 15:18                   ` Dmitry Torokhov
2016-07-06  8:22   ` Peter Rosin
2016-07-06  8:22     ` Peter Rosin
2016-07-06 14:33     ` Viresh Kumar
2016-07-06 14:43       ` Lars-Peter Clausen
2016-07-06 15:04         ` Peter Rosin
2016-07-06 15:04           ` Peter Rosin
2016-07-06 15:37           ` Viresh Kumar
2016-07-06 15:35         ` Viresh Kumar
2016-07-06 14:41 ` [PATCH 0/2] i2c-dev: Don't let userspace block adapter Lars-Peter Clausen
2016-07-06 15:34   ` Viresh Kumar

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=20160718202005.GA18283@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=elder@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.de \
    --cc=johan@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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.