Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753223Ab3DLS3N (ORCPT ); Fri, 12 Apr 2013 14:29:13 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:60079 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751406Ab3DLS3L (ORCPT ); Fri, 12 Apr 2013 14:29:11 -0400 Message-ID: <51685272.8010304@wwwdotorg.org> Date: Fri, 12 Apr 2013 12:29:06 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jay Agarwal CC: Prashant Gaikwad , "linux@arm.linux.org.uk" , Krishna Thota , "linux-pci@vger.kernel.org" , Peter De Schrijver , "thierry.reding@avionic-design.de" , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "olof@lixom.net" , Laxman Dewangan , "bhelgaas@google.com" , "mturquette@linaro.org" , Juha Tukkinen , "linux-arm-kernel@lists.infradead.org" , Hiroshi Doyu Subject: Re: [PATCH 1/3] ARM: tegra: pcie: Add tegra3 support References: <1365435688-4179-1-git-send-email-jagarwal@nvidia.com> <51630ABB.1020200@wwwdotorg.org> <51683E00.4020506@wwwdotorg.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2061 Lines: 48 On 04/12/2013 11:06 AM, Jay Agarwal wrote: >> On 04/12/2013 10:43 AM, Jay Agarwal wrote: >>>> On 04/08/2013 09:41 AM, Jay Agarwal wrote: >>>>> Signed-off-by: Jay Agarwal >>>>> >>>>> - Enable pcie root port 2 for cardhu >>>>> - Make private data structure for each SOC >>>>> - Add required tegra3 clocks and regulators >>>>> - Add tegra3 specific code in enable controller >>>>> - Modify clock tree to get clocks based on device >>>>> - Based on git://gitorious.org/thierryreding/linux.git >>>> >>>> A couple more points on this patch: >>>> >>>> * You didn't mention that this series is based on Thierry's >>>> work-in-progress tree, and not something immediately destined for >>>> upstream. As such, only Thierry is expected to actually apply any of these >> patches. >>>> >>> [>] Stephen, I have mentioned it in comment description as Based on >> git://gitorious.org/thierryreding/linux.git, is this not enough? >> >> Well, first off, there are many branches there, and secondly the branch that >> a series is based on doesn't necessarily imply much about what you expect >> people to do with it. >> > I am not clear, What should I mention then? The branch name. Thierry's branch has the following: remotes/gitorious_thierryreding_linux/drm/hdmi-for-3.9 remotes/gitorious_thierryreding_linux/drm/tegra-for-3.9 remotes/gitorious_thierryreding_linux/tegra/drm/for-3.8 remotes/gitorious_thierryreding_linux/tegra/drm/next remotes/gitorious_thierryreding_linux/tegra/next remotes/gitorious_thierryreding_linux/tegra/next-20130122 which of those was it based on? Also, you simply said it was based on that repo. If you intend Thierry to apply the patches to his repo/branch, rather than the usual maintainers of the files you're editing, who you also CC'd, you should specify that. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/