Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754752Ab3IYR6f (ORCPT ); Wed, 25 Sep 2013 13:58:35 -0400 Received: from mail-pa0-f45.google.com ([209.85.220.45]:59889 "EHLO mail-pa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754667Ab3IYR6b (ORCPT ); Wed, 25 Sep 2013 13:58:31 -0400 Date: Wed, 25 Sep 2013 10:58:27 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Dave Jones , Andrew Morton , KOSAKI Motohiro , Chen Gang , Rik van Riel , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch] mm, mempolicy: make mpol_to_str robust and always succeed In-Reply-To: <20130925032530.GA4771@redhat.com> Message-ID: References: <5215639D.1080202@asianux.com> <5227CF48.5080700@asianux.com> <20130925031127.GA4210@redhat.com> <20130925032530.GA4771@redhat.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 993 Lines: 28 On Tue, 24 Sep 2013, Dave Jones wrote: > > /* fall through */ > > > > for all of them would be pretty annoying. > > agreed, but with that example, it seems pretty obvious (to me at least) > that the lack of break's is intentional. Where it gets trickier to > make quick judgment calls is cases like the one I mentioned above, > where there are only a few cases, and there's real code involved in > some but not all cases. > I fully agree and have code in the oom killer that has the "fall through" comment if there's code in between the case statements, but I think things like case MPOL_BIND: case MPOL_INTERLEAVE: ... is quite easy to read. I don't feel strongly at all, though, so I'll just leave it to Andrew's preference. -- 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/