All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] soc_camera: cleanup control device on async_unbind
Date: Sat, 09 Jan 2016 13:16:07 +0000	[thread overview]
Message-ID: <20160109131607.GA1520@katana> (raw)
In-Reply-To: <Pine.LNX.4.64.1601091226440.15612@axis700.grange>

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]


> Thanks for the patch! From looking at it, I agree, that this looks like a 
> fix, and I even would recommend it for stable, but - at least for that I'd 
> like this patch to actually be tested! At least if someone could try to 
> use the camera after such a unbind / bind cycle. Would you be able to test 
> this? Until then I'll just push this for the forthcoming 4.5.

I'll try to get it tested.

Thanks,

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] soc_camera: cleanup control device on async_unbind
Date: Sat, 9 Jan 2016 14:16:07 +0100	[thread overview]
Message-ID: <20160109131607.GA1520@katana> (raw)
In-Reply-To: <Pine.LNX.4.64.1601091226440.15612@axis700.grange>

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]


> Thanks for the patch! From looking at it, I agree, that this looks like a 
> fix, and I even would recommend it for stable, but - at least for that I'd 
> like this patch to actually be tested! At least if someone could try to 
> use the camera after such a unbind / bind cycle. Would you be able to test 
> this? Until then I'll just push this for the forthcoming 4.5.

I'll try to get it tested.

Thanks,

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-09 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 12:48 [PATCH] soc_camera: cleanup control device on async_unbind Wolfram Sang
2016-01-04 12:48 ` Wolfram Sang
2016-01-09 11:29 ` Guennadi Liakhovetski
2016-01-09 11:29   ` Guennadi Liakhovetski
2016-01-09 13:16   ` Wolfram Sang [this message]
2016-01-09 13:16     ` Wolfram Sang
2016-01-09 13:19   ` Wolfram Sang
2016-01-09 13:19     ` Wolfram Sang
2016-02-07 13:23 ` Niklas Söderlund
2016-02-07 13:23   ` Niklas Söderlund
2016-02-07 22:08   ` Wolfram Sang
2016-02-07 22:08     ` Wolfram Sang

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=20160109131607.GA1520@katana \
    --to=wsa@the-dreams.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mchehab@osg.samsung.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.