From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: jirislaby@gmail.com, stephen.neuendorffer@xilinx.com,
linux-kernel@vger.kernel.org, paulus@samba.org,
galak@gate.crashing.org, benh@kernel.crashing.org,
torvalds@linux-foundation.org
Subject: Re: Xilinx: hwicap driver comments
Date: Thu, 7 Feb 2008 14:31:21 -0700 [thread overview]
Message-ID: <fa686aa40802071331l16b40bacm4a7ca01a7219f1fb@mail.gmail.com> (raw)
In-Reply-To: <20080207132106.ec5ebf1d.akpm@linux-foundation.org>
On 2/7/08, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 7 Feb 2008 13:54:06 -0700
> "Grant Likely" <grant.likely@secretlab.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.
next prev parent reply other threads:[~2008-02-07 21:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 20:08 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 [this message]
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
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=fa686aa40802071331l16b40bacm4a7ca01a7219f1fb@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=galak@gate.crashing.org \
--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
all inboxes | Powered by JetHome®