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] [day] [month] [year] [list]
Date:	Thu, 8 Sep 2011 20:02:11 +0200
From:	Janusz Krzysztofik <jkrzyszt@....icnet.pl>
To:	"Russell King - ARM Linux" <linux@....linux.org.uk>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3.1-rc1] ARM: entry: fix wrong parameter used in do_thumb_abort

On Wed, 7 Sep 2011 at 19:58:47 Janusz Krzysztofik wrote:
> On Wed, 7 Sep 2011 at 13:47:40 Russell King - ARM Linux wrote:
> > On Wed, Sep 07, 2011 at 01:10:08PM +0200, Janusz Krzysztofik wrote:
> > > Any special requirements as to the process of submitting bug
> > > fixes against arch/arm common bits?
> > 
> > It needs to go into the patch system for merging so that it doesn't
> > get buried and forgotten - as already demonstrated.
> 
> Still not sure: am I suppposed to do something for the patch to go to
> the patch system? Or do you take care of this?

OK, instead of waiting for your answer, I've found an interface to your 
patch system myself and submitted the patch.

Next time, for how long after posting a patch to the linux-arm-kernel 
lists should I wait for comments before I can submit it to the patch 
system even if there are no signs of the patch being reviewed? IOW, can 
I assume you accept a patch if you don't comment it for a certain period 
of time?

Thanks,
Janusz
--
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