From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754318AbYKYEYS (ORCPT ); Mon, 24 Nov 2008 23:24:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753217AbYKYEYJ (ORCPT ); Mon, 24 Nov 2008 23:24:09 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:46491 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753205AbYKYEYI (ORCPT ); Mon, 24 Nov 2008 23:24:08 -0500 From: KOSAKI Motohiro To: LKML , linux-mm , Andrew Morton Subject: mm: various sparse warning fix Cc: kosaki.motohiro@jp.fujitsu.com Message-Id: <20081125131942.26CD.KOSAKI.MOTOHIRO@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.42 [ja] Date: Tue, 25 Nov 2008 13:24:00 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi This patch series doesn't have any functional change. and I think it is not so serious. However, many developer often check sparse warnings because it is required from Documentation/SubmitChecklist. Therefore, too many warnings can decrease development efficiency. and, all patch independent each other.