From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751067AbdEIX2M (ORCPT ); Tue, 9 May 2017 19:28:12 -0400 Received: from mail-qk0-f193.google.com ([209.85.220.193]:32960 "EHLO mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbdEIX2L (ORCPT ); Tue, 9 May 2017 19:28:11 -0400 Subject: Re: [PATCH v2] drm/vc4: Enable selection in Kconfig on any 32-bit BCM platform. To: Eric Anholt , dri-devel@lists.freedesktop.org, bcm-kernel-feedback-list@broadcom.com, Ray Jui , Scott Branden , Jon Mason References: <20170509181539.30278-1-eric@anholt.net> <87efvxtyco.fsf@eliezer.anholt.net> Cc: linux-kernel@vger.kernel.org, mircea.carausu@broadcom.com From: Florian Fainelli Message-ID: Date: Tue, 9 May 2017 16:28:07 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <87efvxtyco.fsf@eliezer.anholt.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/09/2017 04:16 PM, Eric Anholt wrote: > Florian Fainelli writes: > >> On 05/09/2017 11:15 AM, Eric Anholt wrote: >>> With the Cygnus port, we needed to add at least "|| ARCH_BCM_CYGNUS" >>> to let the module get built on a cygnus-only kernel. However, I >>> anticipate having a port for Kona soon, so just present the module on >>> all of BCM. >>> >>> v2: Keep allowing selection with ARCH_BCM2835, since ARCH_BCM doesn't >>> exist on arm64. >> >> Nit: the patch changelog usually goes after the "---" line so it gets >> stripped with git am. Not necessary to resubmit just because of that. > > Behavior on that front differs between subsystems. DRM is one where the > changelog is generally retained. Once the patch lands in git, it's sort of interesting to know its history and the context surrounding this acceptance, but there is already so much context being lost already (like where are all other patches from the same patch series for instance?) that I wonder if we should not add more to it (like links to past iterations and so on). Thanks for explaining how DRM works in that regard, though. -- Florian