netdev - Re: [patch 1/2] smsc-ircc2: wrap PNP probe code in #ifdef CONFIG

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]

Message-Id: <20080503142603.859b6c86.sfr@canb.auug.org.au>
Date:	Sat, 3 May 2008 14:26:03 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	samuel@...tiz.org, netdev@...r.kernel.org, bjorn.helgaas@...com,
	kamalesh@...ux.vnet.ibm.com
Subject: Re: [patch 1/2] smsc-ircc2: wrap PNP probe code in #ifdef
 CONFIG_PNP

Hi Andrew,

On Fri, 2 May 2008 18:55:11 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Sat, 3 May 2008 11:46:17 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > I put it there directly at the end so that the tee would build for various
> > configs.  I have been carrying it for some time.  I am also carrying a
> > similar patch for nsc-ircc.  I will remove them when someone puts them
> > into some other tree that I am merging.
> 
> argh, that's a process problem.

Yeah, I guessed it might be :-)

> When those patches turn up in linux-next, I will assume that someone merged
> them into a git tree and I will drop them.
> 
> You now own the sole copy.  If you drop them, they are lost.  If you don't
> send them to anyone, you own them forever.
> 
> So..  what to do about this?  I think the only solution is for you to go
> into akpm mode and start desperately trying to entice someone into merging
> the patch.

I can cope with that.  There are some patches I need to have so that
particular trees/configs will build.  It is rare, though.  Normally I
would revert the problematic patch (and push the problem back on the
subsystem/patch owner.  When I grabbed those particular patches, I was
assuming that it would be a short term thing as all the appropriate
people had been notified.

The other turds you will see will be small semi-private fixup patches
that I do myself and send back to the appropriate people until they fix
their tree - these patches rarely last more than a day and are rolled
into the original offending patch or something similar is added to the
offending tree.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped