linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <davidb@codeaurora.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Greg KH <greg@kroah.com>, Russell King <rmk@arm.linux.org.uk>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Stepan Moskovchenko <stepanm@codeaurora.org>
Subject: Re: linux-next: manual merge of the msm tree with the arm tree
Date: Wed, 02 Feb 2011 14:59:16 -0800	[thread overview]
Message-ID: <8yaipx259h7.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1102021557530.8212@xanadu.home> (Nicolas Pitre's message of "Wed, 02 Feb 2011 16:47:12 -0500 (EST)")

On Wed, Feb 02 2011, Nicolas Pitre wrote:

> The actual problem here is that some people, notably the msm folks, are 
> bypassing the maintainer hierarchy and going straight to Linus for their 
> pull requests instead of asking RMK to pull.  We once debated this at 
> some point and it was agreed that completely independent SOC specific 
> code with no dependencies on the common ARM code _could_ go straight to 
> Linus directly if they crave for it.

I also have no real problem sending pull requests to RMK instead of
Linus, as long as it isn't a pain.  Linus gives clear directions as to
how his tree works, and when he expects what kinds of pull requests.
Weird web-based patch tracking systems are a pain.  Pull requests from
git with a fairly easy way to know when they've been pulled are not.

I also find that http://ftp.arm.linux.org.uk/ is frequently
inaccessable, and usually slow.

As it stands, so far, it's been a lot less work for me to send directly
to Linus, and resolve the issues that come up when they do.

David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  parent reply	other threads:[~2011-02-02 22:59 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31  2:14 linux-next: manual merge of the msm tree with the arm tree Stephen Rothwell
2011-02-02 18:29 ` David Brown
2011-02-02 19:43   ` Greg KH
2011-02-02 20:00     ` Russell King
2011-02-02 20:32       ` Greg KH
2011-02-02 20:44         ` Russell King
2011-02-02 21:47           ` Nicolas Pitre
2011-02-02 22:46             ` David Brown
2011-02-02 22:59             ` David Brown [this message]
2011-02-03  0:15               ` Nicolas Pitre
2011-02-04 17:17             ` Daniel Walker
2011-02-04 17:42               ` Russell King
2011-02-04 18:02                 ` David Brown
2011-02-04 18:10                 ` Daniel Walker
2011-02-04 19:40               ` Nicolas Pitre
2011-02-04 20:38                 ` David Brown
  -- strict thread matches above, loose matches on Subject: below --
2013-07-31  6:08 Stephen Rothwell
2011-01-31  2:14 Stephen Rothwell
2010-10-17 23:35 Stephen Rothwell
2010-10-18  0:02 ` Stephen Rothwell
2010-10-18  8:15   ` Russell King
2010-10-18 17:26     ` Daniel Walker
2010-10-18 18:20       ` Russell King
2010-10-18 18:46         ` Daniel Walker
2010-10-18 19:29           ` Nicolas Pitre
2010-10-18 20:12             ` Daniel Walker
2010-10-18 20:19               ` Arnd Bergmann
2010-10-18 20:37                 ` Daniel Walker
2010-10-18 20:48                   ` Arnd Bergmann
2010-10-18 21:05                     ` Daniel Walker
2010-10-18 21:17                       ` Nicolas Pitre
2010-10-18 21:35                         ` Daniel Walker
2010-10-18 21:11                   ` Nicolas Pitre
2010-10-18 20:58               ` Russell King
2010-10-18 21:29                 ` Daniel Walker
2010-10-18 21:58                   ` Russell King
2010-10-18 22:27                     ` Daniel Walker
2010-10-18 22:35                       ` Nicolas Pitre
2010-10-18 22:53                         ` Joe Perches
2010-10-19 13:18                           ` Arnd Bergmann
2010-10-19 17:03                             ` Daniel Walker
2010-10-19 17:18                               ` Nicolas Pitre
2010-10-19 18:42                                 ` Daniel Walker
2010-10-19 18:53                                   ` Russell King
2010-10-19 19:24                                     ` Daniel Walker
2010-10-19 18:34                               ` Russell King
2010-10-19 18:49                                 ` Daniel Walker
2010-10-18 23:09                         ` Daniel Walker
2010-10-18 23:32                           ` Nicolas Pitre
2010-10-18 23:45                             ` Daniel Walker
2010-10-19  2:47                               ` Nicolas Pitre
2010-10-19 16:55                                 ` Daniel Walker
2010-10-18 20:19             ` Daniel Walker
2010-10-18 20:57               ` Nicolas Pitre
2010-05-04  1:07 Stephen Rothwell
2010-05-04 16:42 ` Daniel Walker
2010-05-04 21:26   ` Stephen Rothwell

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=8yaipx259h7.fsf@huya.qualcomm.com \
    --to=davidb@codeaurora.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=rmk@arm.linux.org.uk \
    --cc=sfr@canb.auug.org.au \
    --cc=stepanm@codeaurora.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).