From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sekhar Nori <nsekhar@ti.com>
Cc: rjw@sisk.pl, arvind.chauhan@arm.com, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, arnd.bergmann@linaro.org,
linux@arm.linux.org.uk,
davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH 3/9] cpufreq: davinci: move cpufreq driver to drivers/cpufreq
Date: Wed, 27 Mar 2013 16:07:50 +0530 [thread overview]
Message-ID: <CAKohpom9KLu0L_Ehkmd7sVd6KnhH0AsOV0jHF+CCZhwBLs671Q@mail.gmail.com> (raw)
In-Reply-To: <5152CADA.4020502@ti.com>
On 27 March 2013 16:02, Sekhar Nori <nsekhar@ti.com> wrote:
> Too bad. But something needs to be done about it since we all like to
> apply patches received in email ;). I have seen reports of people
> configuring gmail to know their @company.com address as another e-mail
> address they own and then using gmail SMTP to send patches (git config).
> You should try that.
I don't use ARM's email id for sending mails and linaro id uses gmail servers
only for sending mails..
The problem is, when i am in office, i can' use google servers to send mails
and whatever mail i send from within ARM, they are broken.
I can use linaro servers from outside office without any issues and it is never
broken.
>> And for this reason only i push my patches in my public repo all the
>> time, mentioned in cover-letter.
>>
>> http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/cpufreq-move-drivers
>
> Okay but you never copied me on the cover letter so I only saw this one
> patch. I will pull your tree and test now.
This series was affecting lots of people and so every patch had a number of
people added as cc. I didn't wanted to add everybody in cc of complete
patchset.
BUT, i have another idea now. The way i used to add people in cc for specific
patches (by editing the patch), i will do the same for cover-letter
too next time.
And so all people will receive relevant patches + cover letter.
--
viresh
next prev parent reply other threads:[~2013-03-27 10:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:11 [PATCH 0/9] ARM: CPUFreq: Move drivers arch/arm/ -> drivers/cpufreq Viresh Kumar
2013-03-25 10:11 ` [PATCH 1/9] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-03-25 10:11 ` [PATCH 2/9] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-03-25 10:11 ` [PATCH 3/9] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-03-27 10:17 ` Sekhar Nori
2013-03-27 10:21 ` Viresh Kumar
2013-03-27 10:32 ` Sekhar Nori
2013-03-27 10:37 ` Viresh Kumar [this message]
2013-03-27 10:56 ` Sekhar Nori
2013-03-25 10:11 ` [PATCH 4/9] cpufreq: imx: " Viresh Kumar
2013-03-27 15:22 ` Markus Pargmann
2013-03-27 15:23 ` Viresh Kumar
2013-03-25 10:11 ` [PATCH 5/9] cpufreq: integrator: " Viresh Kumar
2013-03-31 3:51 ` Viresh Kumar
2013-04-04 8:32 ` Viresh Kumar
2013-04-04 11:40 ` Linus Walleij
2013-03-25 10:11 ` [PATCH 6/9] cpufreq: pxa3xx: " Viresh Kumar
2013-03-31 3:52 ` Viresh Kumar
2013-03-31 5:24 ` Eric Miao
2013-03-31 6:45 ` Viresh Kumar
2013-03-31 11:34 ` Eric Miao
2013-03-25 10:11 ` [PATCH 7/9] cpufreq: pxa2xx: " Viresh Kumar
2013-03-25 10:11 ` [PATCH 8/9] cpufreq: s3c24xx: " Viresh Kumar
2013-03-31 3:53 ` Viresh Kumar
2013-04-03 9:27 ` Viresh Kumar
2013-03-25 10:11 ` [PATCH 9/9] cpufreq: sa11x0: " Viresh Kumar
2013-03-31 3:54 ` Viresh Kumar
2013-03-25 10:33 ` [PATCH 0/9] ARM: CPUFreq: Move drivers arch/arm/ -> drivers/cpufreq Viresh Kumar
2013-03-25 16:49 ` Stephen Warren
2013-04-04 9:38 ` Arnd Bergmann
2013-04-04 9:39 ` Viresh Kumar
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=CAKohpom9KLu0L_Ehkmd7sVd6KnhH0AsOV0jHF+CCZhwBLs671Q@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arnd.bergmann@linaro.org \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
/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).