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:	Wed, 16 Nov 2011 09:47:07 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [TRIVIAL] usb: gadget: drop "select
 USB_GADGET_S3C_HSOTG_PIO"

On Mon, 2011-11-14 at 11:34 +0100, Paul Bolle wrote:
> On Mon, 2011-11-14 at 10:56 +0100, Jiri Kosina wrote:
> > I hope I have picked up everything what hasn't been picked up by 
> > appropriate maintainers (there are still some things in the queue waiting 
> > for ack, as they might bring dead code into life), please double-check 
> > that.
> 
> Thanks for handling this. I hope to double check everything within a few
> days.

0) All is OK: I've sent you eleven patches in this series. Two were
taken by maintainers (drm and unicore32). Nine are now in trivial
for-next. Two needed approval (powerpc/4xx and unicore32). powerpc/4xx
got acked, and that ack is in your commit and unicore32 got taken by a
maintainer.

1) For future series of this kind (if any): does my approach work for
you? See, I basically have a list of potential problems that I work on
in batches, but one by one. So I'll work on a handful of items on that
list, drop the false positives, send a few to maintainers and send the
rest to you. After that I quickly go do something else, as this is not
the kind of stuff I like to do for hours on end.

2) This means in such a series you'll get batches, a few days apart, of
patches each whatever-it-takes apart. Is that more work on your side?


Paul Bolle

--
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