qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Vijaya Kumar K <vijayak@caviumnetworks.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
	suresh knv <knv.suresh2009@gmail.com>,
	Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>,
	Suresh <ksuresh@caviumnetworks.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Will Deacon <Will.Deacon@arm.com>
Subject: Re: [Qemu-devel] [RFC PATCH v2 2/3] utils: Add cpuinfo helper to fetch /proc/cpuinfo
Date: Wed, 13 Apr 2016 10:59:02 +0100	[thread overview]
Message-ID: <570E1866.9010201@arm.com> (raw)
In-Reply-To: <CALicx6u-LOA2gAc2f33a=VY0duHhtiHSZ=2+269daeE3YZ1xiA@mail.gmail.com>

On 13/04/16 10:54, Vijay Kilari wrote:
> On Mon, Apr 11, 2016 at 3:07 PM, Suzuki K Poulose
> <Suzuki.Poulose@arm.com> wrote:
>> On 11/04/16 07:52, Vijay Kilari wrote:

>
> Hi Suzuki,
>
>   The last 5 patches are not compiling on v4.4. Looks like your patch
> series is not merged completely. Can you please
> rebase your patches and let me know.
>

Could you please give the tree below a try ?

git://linux-arm.org/linux-skp.git cpu-ftr/v3-4.3-rc4

Cheers
Suzuki

  reply	other threads:[~2016-04-13  9:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  9:58 [Qemu-devel] [RFC PATCH v2 0/3] ARM64: Live migration optimization vijayak
2016-04-07  9:58 ` [Qemu-devel] [RFC PATCH v2 1/3] target-arm: Use Neon for zero checking vijayak
2016-04-07 10:30   ` Paolo Bonzini
2016-04-07 10:44     ` Peter Maydell
2016-04-07 10:44   ` Peter Maydell
2016-04-09 22:45   ` Richard Henderson
2016-04-11 10:40     ` Peter Maydell
2016-04-07  9:58 ` [Qemu-devel] [RFC PATCH v2 2/3] utils: Add cpuinfo helper to fetch /proc/cpuinfo vijayak
2016-04-07 10:11   ` Peter Maydell
2016-04-07 10:56     ` Vijay Kilari
2016-04-07 11:45       ` Peter Maydell
2016-04-08  6:21         ` Vijay Kilari
2016-04-08  9:43           ` Peter Maydell
2016-04-11  6:52             ` Vijay Kilari
2016-04-11  9:37               ` Suzuki K Poulose
2016-04-13  9:54                 ` Vijay Kilari
2016-04-13  9:59                   ` Suzuki K Poulose [this message]
2016-05-09  3:30                     ` Vijay Kilari
2016-05-09 10:59                       ` Suzuki K Poulose
2016-05-09 11:21                         ` Peter Maydell
2016-05-09 13:44                           ` Catalin Marinas
2016-05-10 10:24                             ` Will Deacon
2016-05-10 13:06                               ` Catalin Marinas

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=570E1866.9010201@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=Vijaya.Kumar@caviumnetworks.com \
    --cc=Will.Deacon@arm.com \
    --cc=knv.suresh2009@gmail.com \
    --cc=ksuresh@caviumnetworks.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vijay.kilari@gmail.com \
    --cc=vijayak@caviumnetworks.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).