Re: [PATCH v8] fs: imgdafs: Add IMG DAFS filesystem for metag

[James Hogan]

Hi Al,

On 09/05/13 16:14, James Hogan wrote:
> Add the IMG Debug Adapter File System (DAFS) for metag, which uses
> SWITCH operations to communicate with a file server on a host computer
> via a JTAG debug adapter.
> 
> Signed-off-by: James Hogan <james.hogan@xxxxxxxxxx>
> Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>

Is this patch acceptable for v3.11?

Thanks
James

> ---
> v8:
>   * enabled building as a module (commit e605ff8 merged during v3.10
>     merge window exports the necessary symbols)
> 
> v7:
>   * use explicit sized types in da_stat and da_finddata (Al Viro)
>   * move IMGDAFS_SUPER_MAGIC to <linux/magic.h> (Al Viro)
>   * use fmode_t instead of int in a couple of places (Al Viro)
>   * removed "will unlock" comment (Al Viro)
>   * use kmalloc and init hi->mode explicitly (Al Viro)
>   * kmalloc instead of using dynamic array for path (Al Viro)
>   * use file_inode() helper in dafs_readdir (Al Viro)
> 
> v6:
>   * use file_inode() helper introduced in v3.9-rc1
>   * remove dafs_iops as it only contained directory methods
>   * add MODULE_ALIAS_FS()
> 
> v5:
>   * removed arch/metag changes (the arch/metag patchset it was
>     previously part of is now mainline with those changes)
> 
> v4:
>   * clean up fscall similarly to chancall in tty/metag_da
> 
> v2:
>   * fixed fserrno problem (Al Viro)
>   * renamed to imgdafs
> 
>  fs/Kconfig                 |   1 +
>  fs/Makefile                |   1 +
>  fs/imgdafs/Kconfig         |   6 +
>  fs/imgdafs/Makefile        |   7 +
>  fs/imgdafs/imgdafs.h       |  82 +++++
>  fs/imgdafs/inode.c         | 842 +++++++++++++++++++++++++++++++++++++++++++++
>  include/uapi/linux/magic.h |   1 +
>  7 files changed, 940 insertions(+)
>  create mode 100644 fs/imgdafs/Kconfig
>  create mode 100644 fs/imgdafs/Makefile
>  create mode 100644 fs/imgdafs/imgdafs.h
>  create mode 100644 fs/imgdafs/inode.c

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/