Did you really just broadcast out 1,500 patches?  I appreciate you're
trying to help, but it's not really going to be possible for anybody to
take a serious look at something like this.

Especially since...

On Sat, 21 May 2016 13:40:47 +0200
Andrea Gelmini <[email protected]> wrote:

> Signed-off-by: Andrea Gelmini <[email protected]>
> ---
>  Documentation/filesystems/ramfs-rootfs-initramfs.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/filesystems/ramfs-rootfs-initramfs.txt 
> b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> index b176928..68de194 100644
> --- a/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> +++ b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> @@ -221,7 +221,7 @@ archive into rootfs before trying to run /init.
>  
>  This has the memory efficiency advantages of initramfs (no ramdisk block
>  device) but the separate packaging of initrd (which is nice if you have
> -non-GPL code you'd like to run from initramfs, without conflating it with
> +non-GPL code you'd like to run from initramfs, without conflicting it with

This is not a correct or helpful change.  If anything, what you want is
"combining".

I looked at one of the (many) patches you sent my way at random, and
found this.  That tells me that everything you sent needs to be looked at
closely, which is not something I really have the time and patience to
do.  So I'm going to be dropping the set, sorry.

If you would like to improve the kernel, could I ask you to please:

 - Be careful about your changes and make sure they are correct.

 - Send them out in *small* related groups that a maintainer could 
   rationally hope to be able to deal with.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to