linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: federico.vaga@gmail.com (Federico Vaga)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] videobuf2-dma-contig: user can specify GFP flags
Date: Thu, 10 Jan 2013 15:32:37 +0100	[thread overview]
Message-ID: <2134637.remWHy6RQA@harkonnen> (raw)
In-Reply-To: <1357822010-30419-2-git-send-email-federico.vaga@gmail.com>


>  struct vb2_dc_buf {
> @@ -165,7 +166,8 @@ static void *vb2_dc_alloc(void *alloc_ctx, unsigned long
> size) /* align image size to PAGE_SIZE */
>  	size = PAGE_ALIGN(size);
> 
> -	buf->vaddr = dma_alloc_coherent(dev, size, &buf->dma_addr, 
GFP_KERNEL);
> +	buf->vaddr = dma_alloc_coherent(dev, size, &buf->dma_addr,
> +									
GFP_KERNEL | conf->mem_flags);

Unfortunately, I forgot to remove this from Patch v4 series. I did not see it 
while re-reading the first time. I'll send a new patch series (v6). It should 
be:

buf->vaddr = dma_alloc_coherent(dev, size, &buf->dma_addr, conf->mem_flags);


I'm terribly sorry

-- 
Federico Vaga

  reply	other threads:[~2013-01-10 14:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 12:46 [PATCH v5] modify videobuf2-dma-contig and update sta2x11_vip Federico Vaga
2013-01-10 12:46 ` [PATCH v5 1/3] videobuf2-dma-contig: user can specify GFP flags Federico Vaga
2013-01-10 14:32   ` Federico Vaga [this message]
2013-01-10 12:46 ` [PATCH v5 2/3] sta2x11_vip: convert to videobuf2 and control framework Federico Vaga
2013-01-10 12:57   ` Federico Vaga
2013-01-10 14:41     ` Hans Verkuil
2013-01-10 14:58       ` Federico Vaga
2013-01-10 14:01   ` Dan Carpenter
2013-01-10 14:43     ` Federico Vaga
2013-01-10 12:46 ` [PATCH v5 3/3] adv7180: remove {query/g_/s_}ctrl Federico Vaga
2013-01-10 15:22 ` [PATCH v5] modify videobuf2-dma-contig and update sta2x11_vip Federico Vaga
2013-01-10 16:06   ` Mauro Carvalho Chehab

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=2134637.remWHy6RQA@harkonnen \
    --to=federico.vaga@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).