From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>,
dri-devel@lists.freedesktop.org,
bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>
Cc: linux-kernel@vger.kernel.org, mircea.carausu@broadcom.com
Subject: Re: [PATCH v2] drm/vc4: Enable selection in Kconfig on any 32-bit BCM platform.
Date: Tue, 09 May 2017 16:16:39 -0700 [thread overview]
Message-ID: <87efvxtyco.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <a72f1029-cff5-aacf-9c40-039117a77e67@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Florian Fainelli <f.fainelli@gmail.com> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-09 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 18:15 Eric Anholt
2017-05-09 18:27 ` Scott Branden
2017-05-09 23:08 ` Florian Fainelli
2017-05-09 23:16 ` Eric Anholt [this message]
2017-05-09 23:28 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efvxtyco.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=f.fainelli@gmail.com \
--cc=jonmason@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mircea.carausu@broadcom.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®