From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: david@lechnology.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] tinydrm/mipi-dbi: Use dma-safe buffers for all SPI transfers
Date: Tue, 5 Mar 2019 09:32:15 +0200 [thread overview]
Message-ID: <20190305073215.GV9224@smile.fi.intel.com> (raw)
In-Reply-To: <d5e22580-fe6e-e31e-34fb-37020d6eb7a8@tronnes.org>
On Mon, Mar 04, 2019 at 06:51:33PM +0100, Noralf Trønnes wrote:
> Den 04.03.2019 16.10, skrev Andy Shevchenko:
> > On Mon, Mar 04, 2019 at 03:45:56PM +0100, Noralf Trønnes wrote:
> >> Den 22.02.2019 16.58, skrev Andy Shevchenko:
> >>> On Fri, Feb 22, 2019 at 01:43:29PM +0100, Noralf Trønnes wrote:
> > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > I hope to see this in v5.1-rc1.
>
> The patch doesn't apply cleanly on (to be) 5.1 due to this one:
>
> drm/tinydrm: Use struct drm_rect
> https://cgit.freedesktop.org/drm/drm/commit/?id=b051b3459bbae907ef068bcd8b62f73f09ea5016
>
> If it's just a debug warning but no ill effects, it'll show up in 5.2.
> Otherwise I will have to backport it.
For x86 it's just a debug message, since on x86 stack memory is DMA capable.
But in general this should be fixed for any possible scenarios.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-03-05 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 12:43 [PATCH] tinydrm/mipi-dbi: Use dma-safe buffers for all SPI transfers Noralf Trønnes
2019-02-22 15:58 ` Andy Shevchenko
2019-03-04 14:45 ` Noralf Trønnes
2019-03-04 15:10 ` Andy Shevchenko
2019-03-04 17:51 ` Noralf Trønnes
2019-03-05 7:32 ` Andy Shevchenko [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=20190305073215.GV9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=david@lechnology.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=noralf@tronnes.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.