devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Daniel Mack <daniel@zonque.org>
Subject: WARNING: SOMEONE RECEIVING THIS HAS BEEN HACKED (was: Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API)
Date: Sat, 15 Oct 2016 22:38:36 +0100	[thread overview]
Message-ID: <20161015213836.GH1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20161015203421.GG1041@n2100.armlinux.org.uk>

Guys,

Looks like gmail's been hacked (or something).  Within 50 minutes of
sending the reply below, I've received at least 10 replies with the
following headers:

In-Reply-To: <20161015203421.GG1041@n2100.armlinux.org.uk>
References: <1476561450-28407-1-git-send-email-robert.jarzmik@free.fr> <20161015203421.GG1041@n2100.armlinux.org.uk>

from various gmail.com addresses, each and every one containing some kind
of spam.  Each reply is from a victim of spam - the replies themselves are
people replying to the spam that they have received.  The quoted message
is allegedly from me, and even includes the line:

 "On 15 Oct 2016, at 21:34, Russell King - ARM Linux <linux@armlinux.org.uk>
 wrote:"

which is the time I sent the original message.

It's either that gmail has been hacked, or one of the mailing lists in
the recipients of this message has been hacked.

On Sat, Oct 15, 2016 at 09:34:21PM +0100, Russell King - ARM Linux wrote:
> On Sat, Oct 15, 2016 at 09:57:26PM +0200, Robert Jarzmik wrote:
> > Hi,
> > 
> > This serie is a preparation to shift the cpufreq of pxa2xx platforms to clocks
> > API.
> > 
> > The first 3 patches are review and merge material :
> >  - patch 1/4 for Viresh and Rafael
> >  - patches 2/4 and 3/4 for me
> > 
> > The 4th on is for review but not merge, as the clock changes must be fully
> > reviewed and go in first as a prequisite
> 
> Have you tested whether this patch set results in functional cpufreq
> support - looking at drivers/clk/pxa, the CPU clock is read-only -
> it can't be used to change the clock rate.  So, I very much doubt this
> has been functionally tested.
> 
> Don't forget that changing the CPU clock rate needs other changes
> (like the memory clock rate) so all that code you're removing in
> patch 4 (which does the actual clock change) needs to go somewhere.
> 
> -- 
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
> according to speedtest.net.
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

      parent reply	other threads:[~2016-10-15 21:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-15 19:57 [PATCH v2 0/4] PXA cpufreq conversion to clock API Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 1/4] cpufreq: pxa: use generic platdev driver for device-tree Robert Jarzmik
     [not found]   ` <1476561450-28407-2-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-18 11:38     ` Viresh Kumar
2016-10-18 15:35       ` Robert Jarzmik
2016-10-19 13:52         ` Viresh Kumar
2016-10-19 20:06           ` Robert Jarzmik
2016-10-20  3:34             ` Viresh Kumar
2016-10-21 15:17               ` Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 2/4] ARM: dts: pxa: add pxa25x cpu operating points Robert Jarzmik
     [not found]   ` <1476561450-28407-3-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-18 11:39     ` Viresh Kumar
2016-10-18 15:30       ` Robert Jarzmik
2016-10-19 13:51         ` Viresh Kumar
2016-10-15 19:57 ` [PATCH v2 3/4] ARM: dts: pxa: add pxa27x " Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 4/4] cpufreq: pxa: convert to clock API Robert Jarzmik
     [not found]   ` <1476561450-28407-5-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-18 11:40     ` Viresh Kumar
2016-10-22 21:37       ` Robert Jarzmik
2016-10-24  3:33         ` Viresh Kumar
     [not found] ` <1476561450-28407-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-10-15 20:34   ` [PATCH v2 0/4] PXA cpufreq conversion " Russell King - ARM Linux
2016-10-15 21:17     ` Robert Jarzmik
2016-10-15 21:38     ` Russell King - ARM Linux [this message]

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=20161015213836.GH1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=daniel@zonque.org \
    --cc=devicetree@vger.kernel.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robert.jarzmik@free.fr \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).