linux-kernel - Re: Xilinx: hwicap driver comments

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:	Thu, 7 Feb 2008 14:31:21 -0700
From:	"Grant Likely" <grant.likely@...retlab.ca>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	jirislaby@...il.com, stephen.neuendorffer@...inx.com,
	linux-kernel@...r.kernel.org, paulus@...ba.org,
	galak@...e.crashing.org, benh@...nel.crashing.org,
	torvalds@...ux-foundation.org
Subject: Re: Xilinx: hwicap driver comments

On 2/7/08, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Thu, 7 Feb 2008 13:54:06 -0700
> "Grant Likely" <grant.likely@...retlab.ca> wrote:
> >
> > It went through my tree.  Paul pulls from Josh Boyer's tree for
> > powerpc-4xx patches, and Josh pulls from mine for xilinx virtex
> > powerpc 405 patches.
> >
> > My screw up, sorry I broke the rules.  What is the best way to resolve this?
> >
>
> Well I think we'd like to see the patches appear in Paul's tree well before
> the merge window if poss - that way they'll get a little bit of tyre-kicking
> and perhaps review via -mm.  Kamalesh and I (at least) do perform build-
> and runtime testing of powerpc.

Fair enough.  I can do so in the future.

> I would request that Paul copy myself and the main mailing list on pull
> requests.
>
> It seems wrong that the signoff trail for that patch didn't actually
> reflect reality - it should have had both Josh's and Paul's signoffs.  That
> would require that the changelog be altered during git->git transfers which
> I expect is just incompatible with the way git works (as far as I dimly
> understand it).
>
> It never hurts to send a patch to lkml even if you believe it isn't of
> general interest.  People will pass an idle eye across it, and things might
> get picked up, yielding improvements.  Plus more people know about its
> existence.  Probably this is more the case for something which resides
> under drivers/char/ than with something which resides in arch/powerpc/...

ok

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/