linux-kernel - Re: [patch 19/26] mount options: fix jfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Jan 2008 13:57:13 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
Cc:	miklos@...redi.hu, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 19/26] mount options: fix jfs

> On Thu, 24 Jan 2008 15:15:01 -0600 Dave Kleikamp <shaggy@...ux.vnet.ibm.com> wrote:
> On Thu, 2008-01-24 at 20:34 +0100, Miklos Szeredi wrote:
> > plain text document attachment (jfs_opts.patch)
> > From: Miklos Szeredi <mszeredi@...e.cz>
> > 
> > Add iocharset= and errors= options to /proc/mounts for jfs
> > filesystems.
> > 
> > Signed-off-by: Miklos Szeredi <mszeredi@...e.cz>
> 
> Acked-by: Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
> 
> Andrew,
> Would you like me to add this to the jfs git tree, or would you like to
> handle these patches as a set?
> 

My usual algorithm here is to

1: queue all the patches and send the ones which have a maintainer to
   that maintainer until he merges it.

2: If the patches have a dependency upon (say) a VFS patch then I'll
   merge the VFS patch and will then goto 1.

I don't think this particular patch has a VFS depencency so sure, merge
away.  You'll probably see that I merged it anyway, but I'll drop it again
when I see it turn up in your tree (I used to resync with the git trees
at least daily, but I now do this far less frequently because it is such
torture because everyone is paddling in everyone else's puddle).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/