linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Please pull from 'for-2.6.28' branch
Date: Tue, 21 Oct 2008 11:11:38 +1100	[thread overview]
Message-ID: <1224547898.7654.210.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0810201304160.17086@blarg.am.freescale.net>

On Mon, 2008-10-20 at 13:04 -0500, Kumar Gala wrote:
> Please pull from 'for-2.6.28' branch of
> 
> 	master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git for-2.6.28
> 
> to receive the following updates:

Ok so I'm not too happy. Kumar, you need to be a little bit more careful
with your git tree. Here are a few things that are causing me problems
at the moment and making me not pull this one. Some of them I already
sent separate emails for but let's put it all together:

 - First, please try to keep a consistent merge branch. Even if it ends
up merging separate branches from you internally.

 - Please use git request-pull or at least provide me with the merge
base in the email if it's not my current master or next HEAD, and since
it makes my life a bit harder too, please try to have your tree based on
mine unless you have some conflicts to sort out.

 - Please spend a bit more time cleaning up the cset subjects and
comments. For example:

	"powerpc: remove device_type = "boad_control"

There are a few problems with this one. Not everybody knows what
"device_type" is, it's not obvious that it's a device-tree change, and
you may notice that I've been trying to keep the first character after
the category: uppercase. I would have preferred something like:

	powerpc: Remove device_type = "board_control" properties in .dts files

Another one that doesn't pass my criteria is:

	OF: SPI: specify chip select active high

I don't like caps, and it's not the generally accepted format. It should
be something like:

	of/spi: Provide a way to specify chip select polarity

Nicer heh ?

I almost always rewrite subjects and sometimes fixup descriptions when I
merge patches. Please do so too.

 - Finally, the Kconfig change shouldn't have been in your tree at all,
or at least not without my or paulus ack and prior argeement that it
should be merged that way. No big deal with this obviously correct
patch but where do we put the limit ?

Cheers,
Ben.
   

  parent reply	other threads:[~2008-10-21  0:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 18:04 Please pull from 'for-2.6.28' branch Kumar Gala
2008-10-20 19:17 ` Anton Vorontsov
2008-10-20 19:32   ` Kumar Gala
2008-10-20 20:47     ` Anton Vorontsov
2008-10-21 14:41       ` Anton Vorontsov
2008-10-21 14:49         ` Kumar Gala
2008-10-21 15:35           ` Timur Tabi
2008-10-21 16:22             ` Kumar Gala
2008-10-20 23:29 ` Benjamin Herrenschmidt
2008-10-21  3:37   ` Kumar Gala
2008-10-20 23:37 ` Benjamin Herrenschmidt
2008-10-21  3:38   ` Kumar Gala
2008-10-21  0:11 ` Benjamin Herrenschmidt [this message]
2008-10-21  3:44   ` Benjamin Herrenschmidt
2008-10-21  3:45   ` Kumar Gala
2008-10-21  3:51     ` Benjamin Herrenschmidt
2008-10-21  4:08       ` Kumar Gala

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=1224547898.7654.210.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).