linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [PATCH v4 0/17] framebuffer: simple conversions to arch_phys_wc_add()
Date: Fri, 29 May 2015 05:48:46 +0000	[thread overview]
Message-ID: <5567FDBE.8010701@ti.com> (raw)
In-Reply-To: <1432859434-17821-1-git-send-email-mcgrof@do-not-panic.com>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]



On 29/05/15 03:30, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
> 
> Tomi,
> 
> Upon integration onto your tree of the series, "[PATCH v3 00/17] framebuffer:
> simple conversions to arch_phys_wc_add()" the 0 day build bot found a
> compilation issue on the gbefb driver. I had test compiled drivers with
> allyesconfig and allmodconfig but failed to test compile against MIPS. This
> driver is enabled *only for MIPS*.  For the life me I could not get a MIPS
> cross compiler even on debian, so what I did to test this was incorporate into
> my private tree a temporary patch [0] which enables this driver to compile on
> x86 and go test compile with that as a temporary patch. The compilation was
> failing since I used the info struct instead of the actual private data
> structure. This fixes that and moves its assignment early.  Sorry about that.
> 
> The rest of the series does not require changes for integration after these
> two patch replacements. Let me know if you'd like me to respin the entire
> series though, but I didn't since I figured its pointless as the patches remain
> intact. For your convenience however I've rebased all these 17 patches onto
> your latest tree on the for-next branch, you can pull the changes with the
> details provided below. This v4 iteration only carries the two patches which
> required updates. The details of the full pull request go below this.

Thanks, I've updated the two patches, and pushed the series to my for-next.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-05-29  5:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  0:30 [PATCH v4 0/17] framebuffer: simple conversions to arch_phys_wc_add() Luis R. Rodriguez
2015-05-29  0:30 ` [PATCH v4 2/17] video: fbdev: gbefb: add missing mtrr_del() calls Luis R. Rodriguez
2015-05-29  0:30 ` [PATCH v4 3/17] video: fbdev: gbefb: use arch_phys_wc_add() and devm_ioremap_wc() Luis R. Rodriguez
2015-05-29  6:41   ` Ingo Molnar
2015-05-30  0:32     ` Luis R. Rodriguez
2015-06-01  8:53       ` Ingo Molnar
2015-06-01 15:57         ` Luis R. Rodriguez
2015-05-29  5:48 ` Tomi Valkeinen [this message]
2015-05-29 21:04   ` [PATCH v4 0/17] framebuffer: simple conversions to arch_phys_wc_add() Luis R. Rodriguez

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=5567FDBE.8010701@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@suse.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).