public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/3] drm: arm-hdlcd: add explictit DRM dependency
Date: Mon, 11 Jan 2016 13:18:55 +0100	[thread overview]
Message-ID: <10589993.Lxk3kTHnpj@wuerfel> (raw)
In-Reply-To: <20160111111255.GE13633@e106497-lin.cambridge.arm.com>

On Monday 11 January 2016 11:12:56 Liviu Dudau wrote:
> On Mon, Jan 04, 2016 at 09:39:46AM +0100, Arnd Bergmann wrote:
> > On Monday 04 January 2016 09:24:16 Thierry Reding wrote:
> > > 
> > > Ugh... wouldn't it be much simpler to get rid of DRM_ARM? It seems like
> > > a completely superfluous option to me. I don't think we've ever had the
> > > equivalent of "vendor" Kconfig options in DRM, and I don't see why we'd
> > > need to start now. If ARM was going to add another driver it can simply
> > > have a separate Kconfig entry. There should be no need to select the
> > > vendor option first.
> > 
> > Fine with me too. I vaguely remembered having seen some discussion about
> > this, so I decided to do a minimal fix, but I agree that would be more
> > in line with the other drivers.
> > 
> >       Arnd
> > 
> 
> Arnd,
> 
> I'm OK with the whole series of Kconfig clean-up/fixes and I offer my appologies
> for adding noise with my patchset. Please let me know how do you prefer to handle
> them. I'm OK with merging your changes into my series before sending the pull
> request to David Airlie.

Please merge them into your tree if you have some other changes to send to him.

I just realized that these are in your own git tree at the moment, not
in drm-next. I guess that means you will rebase the whole series after -rc1 and
submit it into linux-4.6, right?

If so, just fold my fixes into your patches when you rebase.

	Arnd

  reply	other threads:[~2016-01-11 12:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01 14:09 [PATCH] drm: arm-hdlcd: remove DMA_CMA select Arnd Bergmann
2016-01-01 14:38 ` [PATCH 2/3] drm: arm-hdlcd: remove COMMON_CLK_SCPI select Arnd Bergmann
2016-01-04  8:26   ` Thierry Reding
2016-01-01 14:39 ` [PATCH 3/3] drm: arm-hdlcd: fix build warnings for !CONFIG_PM Arnd Bergmann
2016-01-04  8:24   ` Thierry Reding
2016-01-01 22:04 ` [PATCH 4/3] drm: arm-hdlcd: add explictit DRM dependency Arnd Bergmann
2016-01-04  8:24   ` Thierry Reding
2016-01-04  8:39     ` Arnd Bergmann
2016-01-11 11:12       ` Liviu Dudau
2016-01-11 12:18         ` Arnd Bergmann [this message]
2016-01-11 12:26           ` Liviu Dudau
2016-01-11 13:49             ` Arnd Bergmann
2016-01-11 14:14               ` Liviu Dudau
2016-01-04  8:27 ` [PATCH] drm: arm-hdlcd: remove DMA_CMA select Thierry Reding
2016-01-11 10:37 ` Liviu Dudau

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=10589993.Lxk3kTHnpj@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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