Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755832AbbDIOuu (ORCPT ); Thu, 9 Apr 2015 10:50:50 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:31820 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755813AbbDIOup (ORCPT ); Thu, 9 Apr 2015 10:50:45 -0400 Date: Thu, 9 Apr 2015 17:50:35 +0300 From: Dan Carpenter To: Quentin Lambert Cc: "David S. Miller" , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH 2/2] ide: replace GFP_ATOMIC by GFP_KERNEL Message-ID: <20150409145035.GC16501@mwanda> References: <1428579988-10167-1-git-send-email-lambert.quentin@gmail.com> <1428579988-10167-3-git-send-email-lambert.quentin@gmail.com> <20150409123633.GN10964@mwanda> <55268DCB.3010201@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55268DCB.3010201@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: userv0021.oracle.com [156.151.31.71] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 728 Lines: 19 Sorry, my last email was bad. Splitting patches into logical parts is a bit tricky. Let me try explain better. Every patch should sort of make sense on its own. In the original code it's using GFP_ATOMIC but that's because the original API was bad and we had no choice. In the 1/1 patch we're using GFP_ATOMIC explicitly by choice and it's wrong. In patch 2/2 we fix this problem but we shouldn't introduce bad code even if we fix it in later patches. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/