From: Al Viro <viro@ZenIV.linux.org.uk>
To: Felipe Balbi <balbi@ti.com>
Cc: Christoph Hellwig <hch@lst.de>,
Maxim Patlasov <MPatlasov@parallels.com>,
Robert Baldyga <r.baldyga@samsung.com>,
Michal Nazarewicz <mina86@mina86.com>,
linux-aio@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] split struct kiocb
Date: Mon, 23 Feb 2015 21:42:13 +0000 [thread overview]
Message-ID: <20150223214213.GJ29656@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20150223212343.GI32701@saruman.tx.rr.com>
On Mon, Feb 23, 2015 at 03:23:43PM -0600, Felipe Balbi wrote:
> > FWIW, I would really like to hear from USB folks concerning those patches
> > (gadgetfs ones, that is). I don't have any way to test them beyond "does
> > it compile" - no hardware that could run Linux and act as USB slave and
> > no idea if there are any sane emulator setups (e.g. qemu doesn't seem to
> > emulate anything drivers/usb/gadget/udc/* stuff would understand).
> >
> > I'm not happy about the idea of having it merged into vfs.git#for-next
> > with zero testing and no comments from the people actually using the
> > drivers in question, _especially_ if it becomes a never-rebase branch
> > used as prereq for other development.
> >
> > Now that the merge window is closed, could USB folks review and comment
> > on the stuff in
> > git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git gadget
> > ?
> >
> > PS: I would prefer to rebase #iov_iter and #gadget to -rc1, actually...
>
> give me a couple days, quite busy myself ;-)
Sure, no problem... BTW, how does one normally test in that area? IOW,
which emulators and/or real hardware that could be found on e.g. ebay can
handle the current kernels?
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2015-02-23 21:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 18:00 [RFC] split struct kiocb Christoph Hellwig
2015-02-23 18:00 ` [PATCH 01/12] new helper: dup_iter() Christoph Hellwig
2015-02-23 18:00 ` [PATCH 02/12] move iov_iter.c from mm/ to lib/ Christoph Hellwig
2015-02-23 18:00 ` [PATCH 03/12] gadget/function/f_fs.c: close leaks Christoph Hellwig
2015-02-23 18:00 ` [PATCH 04/12] gadget/function/f_fs.c: use put iov_iter into io_data Christoph Hellwig
2015-02-23 18:00 ` [PATCH 05/12] gadget/function/f_fs.c: switch to ->{read,write}_iter() Christoph Hellwig
2015-02-23 18:00 ` [PATCH 06/12] gadgetfs: use-after-free in ->aio_read() Christoph Hellwig
2015-03-08 10:07 ` Ming Lei
2015-03-09 15:18 ` Michal Nazarewicz
2015-02-23 18:00 ` [PATCH 07/12] gadget: switch ep_io_operations to ->read_iter/->write_iter Christoph Hellwig
2015-02-23 18:00 ` [PATCH 08/12] fs: remove ki_nbytes Christoph Hellwig
2015-02-23 18:00 ` [PATCH 09/12] fuse: handle synchronous iocbs internally Christoph Hellwig
2015-03-06 2:54 ` Maxim Patlasov
2015-02-23 18:00 ` [PATCH 10/12] fs: don't allow to complete sync iocbs through aio_complete Christoph Hellwig
2015-02-23 18:00 ` [PATCH 11/12] fs: split generic and aio kiocb Christoph Hellwig
2015-02-23 18:00 ` [PATCH 12/12] fs: move struct kiocb to fs.h Christoph Hellwig
2015-02-23 21:20 ` [RFC] split struct kiocb Al Viro
2015-02-23 21:22 ` Christoph Hellwig
2015-02-23 21:39 ` Al Viro
2015-02-24 3:47 ` Al Viro
2015-02-23 21:23 ` Felipe Balbi
2015-02-23 21:42 ` Al Viro [this message]
2015-02-23 21:50 ` Felipe Balbi
2015-02-25 17:13 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2015-01-27 17:55 Christoph Hellwig
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=20150223214213.GJ29656@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=MPatlasov@parallels.com \
--cc=balbi@ti.com \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=r.baldyga@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.