From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, monstr@monstr.eu,
Andrew Bresticker <abrestic@chromium.org>,
David Box <david.e.box@linux.intel.com>,
Kamal Dasu <kdasu.kdev@gmail.com>,
Joachim Eastwood <manabian@gmail.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
linux-i2c@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Neelesh Gupta <neelegup@linux.vnet.ibm.com>,
Subhendu Sekhar Behera <sbehera@broadcom.com>
Subject: Re: [PATCH] i2c: Enable Cadence driver for ARM64
Date: Tue, 27 Oct 2015 07:14:42 +0900 [thread overview]
Message-ID: <562EA5D2.5030503@osg.samsung.com> (raw)
In-Reply-To: <20151026164559.GP597@x1>
Hello Lee,
On 10/27/2015 01:45 AM, Lee Jones wrote:
> On Tue, 27 Oct 2015, Javier Martinez Canillas wrote:
>
>> Hello,
>>
>> On 10/27/2015 12:00 AM, Lee Jones wrote:
>>> On Mon, 26 Oct 2015, Wolfram Sang wrote:
>>>> On Mon, Oct 26, 2015 at 02:32:36PM +0000, Lee Jones wrote:
>>>>> Regarding your address list -- it's too big. Most of your addressees
>>>>> don't care about this patch. Please be more selective when sending
>>>>> patches to people, most of us have enough (relevant) mail as it is.
>>>>
>>>> Probably more effective than to write every user of get_maintainer.pl:
>>>> Patch it to not use git history by default and win the fight ;)
>>>
>>
>> Agreed, coincidentally I was telling people today that get_maintainers.pl
>> only provides a suggestion and that it should not be followed blindly.
>>
>>> Geert wrote to Joe today. Let's see if he can improve things.
>>>
>>
>> What about something like the following patch until Joe writes a more
>> smarter git fallback version?
>>
>> From d6dc34810d24f33afb3c158d519966c1b6167a2f Mon Sep 17 00:00:00 2001
>> From: Javier Martinez Canillas <javier@osg.samsung.com>
>> Date: Mon, 26 Oct 2015 23:46:52 +0900
>> Subject: [RFC PATCH] get_maintainer: Don't fallback to git by default
>>
>> The get_maintainer.pl script could be used to get a list of people that
>> has to be in the copy list when posting patches for a given file but it
>> defaults to git fallback so the list returned isn't really relevant and
>> submitters are posting patches to random developers that just happened
>> to touch that file in the past.
>>
>> Disable git fallback so get_maintainer.pl only returns the information
>> that is in MAINTAINERS by default.
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>> ---
>> scripts/get_maintainer.pl | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Works for me. Although you should have used get_maintainer.pl and
> CC'ed Joe. ;)
>
hehe, yes. I first wanted to share with Wolfram and you to see if
that is what you were thinking about and that is why I didn't add
Joe and marked the patch as RFC.
I posted it as a proper patch now and also added a Suggested-by
tag from Wolfram.
> I never did this before -- it was both odd and fun:
>
> $ ./scripts/get_maintainer.pl -f scripts/get_maintainer.pl
> Joe Perches <joe@perches.com> (maintainer:GET_MAINTAINER SCRIPT)
>
Fun indeed.
[0]: https://patchwork.kernel.org/patch/7492371/
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-10-26 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 14:09 [PATCH] i2c: Enable Cadence driver for ARM64 Michal Simek
2015-10-26 14:32 ` Lee Jones
2015-10-26 14:43 ` Michal Simek
2015-10-26 15:00 ` Lee Jones
2015-10-26 14:44 ` Wolfram Sang
2015-10-26 15:00 ` Lee Jones
2015-10-26 15:06 ` Javier Martinez Canillas
2015-10-26 16:45 ` Lee Jones
2015-10-26 22:14 ` Javier Martinez Canillas [this message]
2015-10-26 14:50 ` Wolfram Sang
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=562EA5D2.5030503@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=abrestic@chromium.org \
--cc=david.e.box@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=kdasu.kdev@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=neelegup@linux.vnet.ibm.com \
--cc=sbehera@broadcom.com \
--cc=wsa@the-dreams.de \
--cc=zhangfei.gao@linaro.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