[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080207124203.147ce300.akpm@linux-foundation.org>
Date: Thu, 7 Feb 2008 12:42:03 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jiri Slaby <jirislaby@...il.com>
Cc: stephen.neuendorffer@...inx.com, grant.likely@...retlab.ca,
linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
Kumar Gala <galak@...e.crashing.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Xilinx: hwicap driver comments
On Thu, 07 Feb 2008 21:08:50 +0100
Jiri Slaby <jirislaby@...il.com> wrote:
> first of all, I think that the driver should go through lkml before upstream
> merge or at least be in -mm for a while (I think this used to be a rule some
> time ago), correct me if I'm wrong, but none of it happened.
Never seen it before in my life. Can't find any references to it in any of
the mailing lists. I ended up googling the changelog text for a whopping
three hits and it appears that this change went into the powerpc patch
system (http://patchwork.ozlabs.org/linuxppc/patch?id=16712)
How it got from there into Linux is also a mystery. I see a batch of
powerpc updates just went into mainline but I don't know whose tree was
pulled - I wasn't copied on any pull request and I can't find one on the
kernel mailing list.
Perhaps Paul has just done a stealth merge, but the patch to which you
refer doesn't have his signoff. Very confused.
Guys, can we all play too?
--
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