From: Josh Boyer <jwboyer@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
stephen.neuendorffer@xilinx.com, grant.likely@secretlab.ca,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Kumar Gala <galak@gate.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Xilinx: hwicap driver comments
Date: Thu, 7 Feb 2008 15:35:45 -0600 [thread overview]
Message-ID: <20080207153545.14a9c8ed@weaponx> (raw)
In-Reply-To: <20080207124203.147ce300.akpm@linux-foundation.org>
On Thu, 7 Feb 2008 12:42:03 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 07 Feb 2008 21:08:50 +0100
> Jiri Slaby <jirislaby@gmail.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.
Gah, no. Don't blame Paul. It wasn't actually stealth either as it
got posted a few times to the powerpc list.
You can blame me and/or Grant if you'd like. It's a Virtex specific
driver and I didn't see any problem with it going in through the
powerpc tree. I'll/we'll do better next time.
> Guys, can we all play too?
Sure. You could add my tree to -mm if you want. Though I'd really
rather if we all sync up with Paul sooner so you don't have to track 5
or 6 "powerpc" trees.
josh
next prev parent reply other threads:[~2008-02-07 21:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 20:08 Xilinx: hwicap driver comments Jiri Slaby
2008-02-07 20:34 ` Grant Likely
2008-02-07 21:10 ` Stephen Neuendorffer
2008-02-07 20:42 ` Andrew Morton
2008-02-07 20:54 ` Grant Likely
2008-02-07 21:21 ` Andrew Morton
2008-02-07 21:31 ` Grant Likely
2008-02-07 21:35 ` Stephen Neuendorffer
2008-02-07 21:53 ` Andrew Morton
2008-02-07 22:00 ` Stephen Neuendorffer
2008-02-07 21:40 ` Linus Torvalds
2008-02-07 21:25 ` Benjamin Herrenschmidt
2008-02-07 21:35 ` Josh Boyer [this message]
2008-02-07 22:11 ` Andrew Morton
2008-02-07 22:58 ` Josh Boyer
2008-02-07 21:17 ` Benjamin Herrenschmidt
2008-02-07 21:28 ` Jiri Slaby
2008-02-07 21:33 ` Benjamin Herrenschmidt
2008-02-07 21:35 ` Grant Likely
2008-02-07 22:31 ` Stephen Neuendorffer
2008-02-07 22:39 ` Jiri Slaby
2008-02-08 2:17 ` [PATCH] [POWERPC] Xilinx: hwicap driver Stephen Neuendorffer
2008-02-08 9:10 ` Jiri Slaby
2008-02-08 16:49 ` Randy Dunlap
2008-02-08 17:08 ` Xilinx: hwicap driver comments Stephen Neuendorffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080207153545.14a9c8ed@weaponx \
--to=jwboyer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=galak@gate.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=stephen.neuendorffer@xilinx.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox