| 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
| ||
|
Date: Wed, 16 Sep 2009 00:13:25 -0400 From: Mike Frysinger <vapier.adi@...il.com> To: Daniel Walker <dwalker@...o99.com> Cc: linux-kernel@...r.kernel.org, uclinux-dist-devel@...ckfin.uclinux.org Subject: Re: [PATCH 00/72] Blackfin updates for 2.6.32 On Tue, Sep 15, 2009 at 23:59, Daniel Walker wrote: > On Tue, 2009-09-15 at 23:21 -0400, Mike Frysinger wrote: >> On Tue, Sep 15, 2009 at 23:06, Daniel Walker wrote: >> > On Tue, 2009-09-15 at 22:56 -0400, Mike Frysinger wrote: >> >> On Mon, Sep 14, 2009 at 18:36, Daniel Walker wrote: >> >> > If you ultimately don't correct these changes, I'd ask that in the >> >> > future you submit pull requests for the blackfin architecture instead of >> >> > sending individual patches .. >> >> >> >> you havent been following anything related to how Blackfin (or any >> >> arch?) patches are merged. this patch series is for review only from >> >> my tree. no one is picking these up because they've already been >> >> picked up. >> > >> > Picked up by Linus? You know this isn't the "blackfin" list right? You >> > don't seem to care too about review your getting from _this_ list. So >> > why in the world are you sending your patches (all 72 of them!) here .. >> >> Linus doesnt pick up random patches, he does pull requests. Blackfin >> patches already get reviewed on the Blackfin list (during original >> commit and later merge). i post all the patches for sanity checking >> things we may have missed (it happens). any sane mailer makes it >> trivial to delete/ignore a single thread, and for anyone reading LKML, >> not using a sane mailer is a poor excuse. i'm open to review of real >> issues with the code (locking / leaks / design problems / etc...). >> forcing a respin of patches for a minor style difference is noise. > > I read all of LKML, sane mailer or not _your_ patches are noise .. You > have your own mailing list. You have no good reason to post that many > patches here, and it's more than likely no one is reviewing them (except > me, and your ignoring my valid comments) .. If you have specific patches > that have questionable "locking, leaks, or design problems" that's > welcome, but not what your doing.. if i thought something had questionable code, i'd of fixed it myself, or specifically asked someone. if the larger lkml community would prefer to not see the patch series for review, i have no program refraining, but i havent seen a negative response so far. i have seen some random fixes which were certainly nice. -mike -- 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