public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: k.kozlowski@samsung•com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 00/44] dma-mapping: Use unsigned long for dma_attrs
Date: Tue, 12 Jul 2016 14:19:07 +0200	[thread overview]
Message-ID: <5784E03B.6060000@samsung.com> (raw)
In-Reply-To: <20160712121625.GP23520@phenom.ffwll.local>

On 07/12/2016 02:16 PM, Daniel Vetter wrote:
> On Thu, Jun 30, 2016 at 10:23:39AM +0200, Krzysztof Kozlowski wrote:
>> Hi,
>>
>>
>> This is fifth approach for replacing struct dma_attrs with unsigned
>> long.
>>
>> The main patch (1/44) doing the change is split into many subpatches
>> for easier review (2-42).  They should be squashed together when
>> applying.
> 
> For all the drm driver patches:
> 
> Acked-by: Daniel Vetter <daniel.vetter@ffwll•ch>
> 
> Should I pull these in through drm-misc, or do you prefer to merge them
> through a special topic branch (with everything else) instead on your own?
> -Daniel

Thanks. I saw today that Andrew Morton applied the patchset so I think
he will handle it.

Best regards,
Krzysztof

      reply	other threads:[~2016-07-12 12:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30  8:23 [PATCH v5 00/44] dma-mapping: Use unsigned long for dma_attrs Krzysztof Kozlowski
     [not found] ` <1467275171-6298-1-git-send-email-k.kozlowski@samsung.com>
2016-06-30  8:25   ` [PATCH v5 04/44] ARM: " Krzysztof Kozlowski
2016-06-30  8:25   ` [PATCH v5 05/44] arm64: " Krzysztof Kozlowski
2016-06-30  8:25   ` [PATCH v5 11/44] drm/exynos: " Krzysztof Kozlowski
2016-06-30  8:25   ` [PATCH v5 12/44] drm/mediatek: " Krzysztof Kozlowski
2016-06-30  8:25   ` [PATCH v5 15/44] drm/rockship: " Krzysztof Kozlowski
2016-06-30  8:26   ` [PATCH v5 43/44] dma-mapping: Remove dma_get_attr Krzysztof Kozlowski
2016-07-12 12:16 ` [PATCH v5 00/44] dma-mapping: Use unsigned long for dma_attrs Daniel Vetter
2016-07-12 12:19   ` Krzysztof Kozlowski [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=5784E03B.6060000@samsung.com \
    --to=k.kozlowski@samsung$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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