From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759523Ab1IIRMd (ORCPT ); Fri, 9 Sep 2011 13:12:33 -0400 Received: from mail-yw0-f46.google.com ([209.85.213.46]:60276 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759407Ab1IIRMc (ORCPT ); Fri, 9 Sep 2011 13:12:32 -0400 Date: Fri, 9 Sep 2011 10:11:58 -0700 From: Dan Carpenter To: Nitin Gupta Cc: Harvey Harrison , Jerome Marchand , linux-kernel , Pekka Enberg , Linux Driver Project , Robert Jennings Subject: Re: [PATCH 1/5] Fix sparse warnings Message-ID: <20110909171158.GH17041@mwanda> References: <1315445357-14338-1-git-send-email-ngupta@vflare.org> <1315445357-14338-2-git-send-email-ngupta@vflare.org> <4E687A33.1080401@redhat.com> <4E68DBA5.6010307@vflare.org> <4E6A4641.9090606@vflare.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E6A4641.9090606@vflare.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Just resend the whole patch. When you're applying patches from mutt normally you have a macro set up to automatically run git-am. Under your system maintainers have to manually fix your patch and it breaks the work flow. regards, dan carpenter