Nathan Scott <[email protected]> wrote: > > Any chance that could be renamed to something thats a bit clearer, > maybe generic_file_non_aio_read and generic_file_non_aio_write? I guess that logically, we should avoid the double-negative and use generic_file_sio_*. I dunno if we want to be that logical though ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH 0/3] VFS changes to collapse AIO and vectored IO into single (set of) fileops.
- From: Badari Pulavarty <[email protected]>
- [PATCH 0/3] VFS changes to collapse AIO and vectored IO into single (set of) fileops.
- From: Badari Pulavarty <[email protected]>
- [PATCH 0/4] VFS fileop cleanups by collapsing AIO and vector IO
- From: Badari Pulavarty <[email protected]>
- [PATCH 0/4] VFS fileop cleanups by collapsing AIO and vector IO
- From: Badari Pulavarty <[email protected]>
- [PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups
- From: Badari Pulavarty <[email protected]>
- Re: [PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups
- From: Nathan Scott <[email protected]>
- [PATCH 0/3] VFS changes to collapse AIO and vectored IO into single (set of) fileops.
- Prev by Date: Re: [PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups
- Next by Date: Re: [PATCH] jffs2: memory leak in jffs2_scan_medium()
- Previous by thread: Re: [PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups
- Next by thread: Re: [PATCH 4/4] Streamline generic_file_* interfaces and filemap cleanups
- Index(es):
 |