public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@intel.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, "Wu,
	Fengguang" <fengguang.wu@intel.com>
Subject: Re: Fwd: Re: [linux-next-20120706] x86/mm: incompatible pointer typewarning.
Date: Sat, 07 Jul 2012 11:21:20 +0800	[thread overview]
Message-ID: <4FF7AB30.50405@intel.com> (raw)
In-Reply-To: <201207070943.DBB17689.FOMQJtOFLHOVFS@I-love.SAKURA.ne.jp>

On 07/07/2012 08:43 AM, Tetsuo Handa wrote:

> Alex Shi wrote:
>> Thanks for your report, mm should means mm_struct. no vma. My fault.
>> Could you like try this patch.
> 
> Builds OK. Thank you.


Uh, seems the allnoconfig setting is different on different tree.
I need to tired it other tree no just Linus' tree. :(

> 
>> From 97781231b130e7f7fced12244653ed9b9946c944 Mon Sep 17 00:00:00 2001
>> From: Alex Shi <alex.shi@intel.com>
>> Date: Fri, 6 Jul 2012 20:49:25 +0800
>> Subject: [PATCH] x86/tlb: fix allnoconfig building warning
>>
>> The incompatible parameter of flush_tlb_mm_range cause build warning.
>> Fix it by correct parameter.



-- 
Thanks
    Alex

  reply	other threads:[~2012-07-07  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201207062113.DBE65145.OOLVOHQFFMJFtS@I-love.SAKURA.ne.jp>
     [not found] ` <4FF6F14C.3070104@intel.com>
2012-07-06 14:10   ` Fwd: Re: [linux-next-20120706] x86/mm: incompatible pointer type warning Alex Shi
2012-07-07  0:43     ` Fwd: Re: [linux-next-20120706] x86/mm: incompatible pointer typewarning Tetsuo Handa
2012-07-07  3:21       ` Alex Shi [this message]
2012-07-16  5:36   ` [linux-next-20120706] x86/mm: incompatible pointer type warning Alex Shi

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=4FF7AB30.50405@intel.com \
    --to=alex.shi@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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