From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-media@vger.kernel.org, Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org, security@kernel.org,
pmatouse@redhat.com, agk@redhat.com, jbottomley@parallels.com,
mchristi@redhat.com, msnitzer@redhat.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: Broken ioctl error returns (was Re: [PATCH 2/3] block: fail SCSI passthrough ioctls on partition devices)
Date: Sat, 07 Jan 2012 00:07:31 -0200 [thread overview]
Message-ID: <4F07A8E3.7010105@redhat.com> (raw)
In-Reply-To: <4F05F57A.2070007@infradead.org>
On 05-01-2012 17:09, Mauro Carvalho Chehab wrote:
> On 05-01-2012 15:47, Linus Torvalds wrote:
>> Can you test the patch with some media capture apps (preferably with
>> the obvious fix for the problem that Paulo already pointed out -
>> although that won't actually matter until some block driver starts
>> using ENOIOCTLCMD there, so even the unfixed patch should mostly work
>> for testing)?
>
> Sure. I'm currently traveling, so I have just my "first aids kit" of devices
> but they should be enough for testing it. I'll return you as soon as I finish
> compiling the kernel on this slow 4 years-old notebook and run some
> tests with the usual applications.
I did a quick test today: didn't notice any regressions with the usual
applications.
Regards,
Mauro
next prev parent reply other threads:[~2012-01-07 2:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 17:02 Broken ioctl error returns (was Re: [PATCH 2/3] block: fail SCSI passthrough ioctls on partition devices) Linus Torvalds
2012-01-05 17:26 ` Paolo Bonzini
2012-01-05 17:38 ` Linus Torvalds
2012-01-05 17:30 ` Linus Torvalds
2012-01-05 17:37 ` Mauro Carvalho Chehab
2012-01-05 17:47 ` Linus Torvalds
2012-01-05 19:09 ` Mauro Carvalho Chehab
2012-01-07 2:07 ` Mauro Carvalho Chehab [this message]
2012-01-06 16:19 ` Arnd Bergmann
2012-01-06 17:04 ` Linus Torvalds
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=4F07A8E3.7010105@redhat.com \
--to=mchehab@redhat.com \
--cc=agk@redhat.com \
--cc=hch@lst.de \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=msnitzer@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pmatouse@redhat.com \
--cc=security@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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.