On 05/05/2014 01:36 PM, Tejun Heo wrote:
On Mon, May 05, 2014 at 03:30:34PM -0400, Devin Heitmueller wrote:
On Mon, May 5, 2014 at 3:26 PM, Tejun Heo wrote:
As such, please consider the patches nacked and try to find someone
who can shepherd the code. Mauro, can you help out here?
We
On Mon, May 5, 2014 at 3:36 PM, Tejun Heo wrote:
> On Mon, May 05, 2014 at 03:30:34PM -0400, Devin Heitmueller wrote:
>> On Mon, May 5, 2014 at 3:26 PM, Tejun Heo wrote:
>> > As such, please consider the patches nacked and try to find someone
>> > who can shepherd the code. Mauro, can you help
On Mon, May 05, 2014 at 03:30:34PM -0400, Devin Heitmueller wrote:
> On Mon, May 5, 2014 at 3:26 PM, Tejun Heo wrote:
> > As such, please consider the patches nacked and try to find someone
> > who can shepherd the code. Mauro, can you help out here?
>
> We actually discussed this proposal at
Hi Tejun,
On Mon, May 5, 2014 at 3:26 PM, Tejun Heo wrote:
> As such, please consider the patches nacked and try to find someone
> who can shepherd the code. Mauro, can you help out here?
We actually discussed this proposal at length at the media summit last
week. The patches are being pulled
Hello, Shuah.
On Mon, May 05, 2014 at 01:16:46PM -0600, Shuah Khan wrote:
> You are right that there is a need for an owner field to indicate who
> has the token. Since the path is very long, I didn't want to use just
> the mutex and keep it tied up for long periods of time. That is the
> reason
Hi Tejun,
On 05/01/2014 08:53 AM, Tejun Heo wrote:
+ if (!mutex_trylock(_ptr->lock))
+ return -EBUSY;
How is this lock supposed to be used? Have you tested it with lockdep
enabled? Does it ever get released by a task which is different from
the one which locked it? If
Hi Tejun,
On 05/01/2014 08:53 AM, Tejun Heo wrote:
+ if (!mutex_trylock(tkn_ptr-lock))
+ return -EBUSY;
How is this lock supposed to be used? Have you tested it with lockdep
enabled? Does it ever get released by a task which is different from
the one which locked it?
Hello, Shuah.
On Mon, May 05, 2014 at 01:16:46PM -0600, Shuah Khan wrote:
You are right that there is a need for an owner field to indicate who
has the token. Since the path is very long, I didn't want to use just
the mutex and keep it tied up for long periods of time. That is the
reason why
Hi Tejun,
On Mon, May 5, 2014 at 3:26 PM, Tejun Heo t...@kernel.org wrote:
As such, please consider the patches nacked and try to find someone
who can shepherd the code. Mauro, can you help out here?
We actually discussed this proposal at length at the media summit last
week. The patches are
On Mon, May 05, 2014 at 03:30:34PM -0400, Devin Heitmueller wrote:
On Mon, May 5, 2014 at 3:26 PM, Tejun Heo t...@kernel.org wrote:
As such, please consider the patches nacked and try to find someone
who can shepherd the code. Mauro, can you help out here?
We actually discussed this
On Mon, May 5, 2014 at 3:36 PM, Tejun Heo t...@kernel.org wrote:
On Mon, May 05, 2014 at 03:30:34PM -0400, Devin Heitmueller wrote:
On Mon, May 5, 2014 at 3:26 PM, Tejun Heo t...@kernel.org wrote:
As such, please consider the patches nacked and try to find someone
who can shepherd the code.
On 05/05/2014 01:36 PM, Tejun Heo wrote:
On Mon, May 05, 2014 at 03:30:34PM -0400, Devin Heitmueller wrote:
On Mon, May 5, 2014 at 3:26 PM, Tejun Heo t...@kernel.org wrote:
As such, please consider the patches nacked and try to find someone
who can shepherd the code. Mauro, can you help out
Hello,
On Tue, Apr 29, 2014 at 01:49:23PM -0600, Shuah Khan wrote:
> +/* creates a token devres and marks it available */
> +int devm_token_create(struct device *dev, const char *id)
> +{
> + struct token_devres *tkn;
> + size_t tkn_size;
> +
> + tkn_size = sizeof(struct token_devres)
Hello,
On Tue, Apr 29, 2014 at 01:49:23PM -0600, Shuah Khan wrote:
+/* creates a token devres and marks it available */
+int devm_token_create(struct device *dev, const char *id)
+{
+ struct token_devres *tkn;
+ size_t tkn_size;
+
+ tkn_size = sizeof(struct token_devres) +
Media devices often have hardware resources that are shared
across several functions. These devices appear as a group of
independent devices. Each device implements a function which
could be shared by one or more functions supported by the same
device. For example, tuner is shared by analog and
Media devices often have hardware resources that are shared
across several functions. These devices appear as a group of
independent devices. Each device implements a function which
could be shared by one or more functions supported by the same
device. For example, tuner is shared by analog and
16 matches
Mail list logo
