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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100914021532.9C53E403E6@magilla.sf.frob.com>
Date:	Mon, 13 Sep 2010 19:15:32 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Namhyung Kim <namhyung@...il.com>
Cc:	monstr@...str.eu, Oleg Nesterov <oleg@...hat.com>,
	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 14/24] ptrace: cleanup arch_ptrace() on microblaze

> On Mon, Sep 13, 2010 at 16:14, Michal Simek <monstr@...str.eu> wrote:
> > Hi,
> >
> > just for my info how does it look like this patch series?
> > I mean who should added that patches to mainline?
> >
> 
> Hello,
> 
> I am not sure but I hope Roland will take care of it.

Sorry, I didn't know you had any such expectation.  Oleg and I do not
autonomously maintain any ptrace tree that gets automatically merged or
anything like that.  Our Acked-by's are presumed to help your case and our
objections to hurt it, but you just have to submit patches to linus, akpm,
arch maintainers, or whatever other channels get merged regularly.  We're
not that kind of authoritative ourselves, though we are listed as the
ptrace maintainers.  We have to do the same with our own ptrace patches.


Thanks,
Roland
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ