Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752246AbbHGKmG (ORCPT ); Fri, 7 Aug 2015 06:42:06 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:33179 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751866AbbHGKmD (ORCPT ); Fri, 7 Aug 2015 06:42:03 -0400 Date: Fri, 7 Aug 2015 16:11:56 +0530 From: Viresh Kumar To: Bartlomiej Zolnierkiewicz Cc: Thomas Abraham , Sylwester Nawrocki , Michael Turquette , Kukjin Kim , Kukjin Kim , Krzysztof Kozlowski , Tomasz Figa , Lukasz Majewski , Heiko Stuebner , Chanwoo Choi , Kevin Hilman , Javier Martinez Canillas , Tobias Jakobi , Anand Moon , linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Javier Martinez Canillas , "Rafael J. Wysocki" Subject: Re: [PATCH v4 1/6] cpufreq: make scaling_boost_freqs sysfs attr available when boost is enabled Message-ID: <20150807104156.GE6939@linux> References: <1438868514-8814-1-git-send-email-b.zolnierkie@samsung.com> <1438868514-8814-2-git-send-email-b.zolnierkie@samsung.com> <20150807034128.GE6325@linux> <5184469.cOpIkgzX4h@amdc1976> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5184469.cOpIkgzX4h@amdc1976> 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 Content-Length: 1376 Lines: 32 On 07-08-15, 12:34, Bartlomiej Zolnierkiewicz wrote: > > I would suggest you sending such patches as reply to the earlier > > threads only, instead of a new chain. This will save your time. > > Please explain it more. This patch needs to be first for cpufreq-dt > switch to be complete. scaling_boost_freqs is available currently > for exynos-cpufreq users when boost is enabled and ideally we would > like it to be available immediately after the switch to cpufreq-dt. I wasn't talking about the ordering of the patches here, but when to send patches. So, you now sent these patches again, but what you could have done is: only send the first patch in reply to the earlier thread. And ask if it looks fine. If yes, resend the whole series properly or keep fixing there only.. That makes things really fast. You don't have to resend the series and people wouldn't stay away from it. I stayed away from this series to find enough available time to see your 6 patches. Had it been just a reply, I would have replied immediately like now. Look at how updated versions in the same mail chain in case of OPP series.. -- viresh -- 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/