linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Farhan Ali <alifm@linux.vnet.ibm.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390
Date: Tue, 30 Jan 2018 13:22:38 +0000	[thread overview]
Message-ID: <cb4c884b-9334-325c-0c2d-0f93fae9f1cc@de.ibm.com> (raw)
In-Reply-To: <85ab024b-6af2-8b58-f9e8-7920d132cefb@linux.vnet.ibm.com>

Yes, merging sounds good.
Farhan, can you maybe resend t whole series together with your CONFIG_VT rework?



On 01/26/2018 05:26 PM, Farhan Ali wrote:
> 
> 
> On 01/26/2018 10:06 AM, Geert Uytterhoeven wrote:
>>> Hi Geert,
>>>
>>> I wasn't sure what would be the best ordering since we would never hit the
>>> issue if patch 1 didn't exist. But if the preference is to invert the
>>> ordering of patches, then I will change the ordering.
>> Alternatively, you can combine two patches into a single patch, which
>> moves the dependency from the whole subsystem to the driver that needs
>> it (are there more?).
>>
>> Gr{oetje,eeting}s,
>>
>>                          Geert
> 
> 
> I like the idea of combining both patches into one.
> 
> There are other fbdev drivers that use iomem (found by grepping for "devm_ioremap_resource"):
> 
> CONFIG_FB_S3C (s3c-fb.c)
> 
> CONFIG_FB_CLPS711X (clps711x-fb.c)
> 
> CONFIG_FB_JZ4740 (jz4740_fb.c)
> 
> CONFIG_FB_DA8XX (da8xx-fb.c)
> 
> CONFIG_FB_WM8505 (wm8505fb.c)
> 
> CONFIG_OMAP2_VRFB (omap2/omapfb/vrfb.c)
> 
> CONFIG_FB_OMAP2 (omap2/omapfb/dss/*
> 
> CONFIG_FB_MXS (mxsfb.c)
> 
> CONFIG_PXA3XX_GCU (pxa3xx-gcu.c)
> 
> CONFIG_FB_XILINX (xilinxfb.c)
> 
> 
> All of these are already fenced off by architecture dependencies (which I am assuming enables CONFIG_HAS_IOMEM by default). If we want to be cautious I can add HAS_IOMEM dependency for all of them.
> 
> Thanks
> Farhan


      reply	other threads:[~2018-01-30 13:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 15:47 [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390 Farhan Ali
2018-01-25 15:47 ` [PATCH v1 1/2] Kconfig : Remove HAS_IOMEM dependency for Graphics support Farhan Ali
2018-01-26 12:31   ` Thomas Huth
2018-01-25 15:47 ` [PATCH v1 2/2] fbdev: Kconfig: Add HAS_IOMEM dependency for FB_OPENCORES Farhan Ali
2018-01-26 12:33   ` Thomas Huth
2018-01-26 12:38     ` Tomi Valkeinen
2018-01-26 14:32       ` Farhan Ali
2018-01-26 13:41 ` [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390 Geert Uytterhoeven
2018-01-26 14:35   ` Farhan Ali
2018-01-26 15:06     ` Geert Uytterhoeven
2018-01-26 16:26       ` Farhan Ali
2018-01-30 13:22         ` Christian Borntraeger [this message]

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=cb4c884b-9334-325c-0c2d-0f93fae9f1cc@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=alifm@linux.vnet.ibm.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    --cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).