linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] cpufreq: cpufreq-cpu0: assign cpu_dev correctly to cpu0 device
Date: Wed, 11 Sep 2013 09:55:46 +0100	[thread overview]
Message-ID: <52303012.3060709@arm.com> (raw)
In-Reply-To: <CAKohpokgVqmjNGTUOg61YQyqi1qO-9FaB8dmZqTqq2nQFynOkQ@mail.gmail.com>

On 11/09/13 09:42, Viresh Kumar wrote:
> On 11 September 2013 13:45, Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
>> Noone else seems to complain, but I don't think these =20, =09 etc. codes
>> have been invented on my side and I don't think they belong here. I'm
>> handling enough mails / patches daily to believe, that my mail system
>> isn't the cause of this. Could you please verify and regenerate and
>> resend? Unless I'm mistaken this looks like a corruption on your SMTP
>> side.
> 
> Its on Sudeep's side :) .. Or on ARM's side..
> Don't know why nobody else complained, Atleast people who test these
> patches (Like Shawn), must have applied them from mail.. Don't know
> why they aren't shouting :)
> 
> He mostly send pull requests to Rafael and so this wasn't a issue for
> Rafael :)
> 

Yes looks like its at my end. I will try to fix it. There is alternate
SMTP which should not have this issue, but it was down recently. I
forgot to switch back to it once it was fixed.

For now you can fetch it from:
	git://linux-arm.org/linux-skn.git cpufreq_fixes_v3.12

Regards,
Sudeep

  reply	other threads:[~2013-09-11  8:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 17:59 [PATCH 0/4] cpufreq: fixes for v3.12 Sudeep KarkadaNagesha
2013-09-10 17:59 ` [PATCH 1/4] cpufreq: cpufreq-cpu0: assign cpu_dev correctly to cpu0 device Sudeep KarkadaNagesha
2013-09-11  8:15   ` Guennadi Liakhovetski
2013-09-11  8:42     ` Viresh Kumar
2013-09-11  8:55       ` Sudeep KarkadaNagesha [this message]
2013-09-11  9:22       ` Shawn Guo
2013-09-11 12:47       ` Rafael J. Wysocki
2013-09-11 15:43   ` Guennadi Liakhovetski
2013-09-10 17:59 ` [PATCH 2/4] cpufreq: imx6q-cpufreq: " Sudeep KarkadaNagesha
2013-09-10 17:59 ` [PATCH 3/4] ARM: i.MX: change dev_id to cpu0 while registering cpu clock Sudeep KarkadaNagesha
2013-09-10 17:59 ` [PATCH 4/4] ARM: shmobile: " Sudeep KarkadaNagesha
2013-09-11 16:25   ` Guennadi Liakhovetski
2013-09-10 20:07 ` [PATCH 0/4] cpufreq: fixes for v3.12 Rafael J. Wysocki
2013-09-11  2:23 ` Shawn Guo
2013-09-11 22:58 ` Rafael J. Wysocki
2013-09-12  8:18   ` Sudeep KarkadaNagesha

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=52303012.3060709@arm.com \
    --to=sudeep.karkadanagesha@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).