From: Kyungmin Park <kyungmin.park@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media <linux-media@vger.kernel.org>,
Tomasz Stanislawski <t.stanislaws@samsung.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: linux-next: Tree for Nov 27 (media/v4l2-core/videobuf2-dma-contig.c)
Date: Wed, 28 Nov 2012 09:52:19 +0900 [thread overview]
Message-ID: <CAH9JG2WfpNttdthgZEAM+W5T8rrZwOULSBGaSB8XdVDVMhC1FA@mail.gmail.com> (raw)
In-Reply-To: <20121128081514.84c71b8eb965a7d11cb1ff07@canb.auug.org.au>
Hi,
It's fixed already and you will check it at Nov 28 tree
http://www.spinics.net/lists/linux-media/msg56830.html
Thank you,
Kyungmin Park
On 11/28/12, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> [Just adding some cc's]
>
> On Tue, 27 Nov 2012 10:32:15 -0800 Randy Dunlap <rdunlap@infradead.org>
> wrote:
>>
>> On 11/26/2012 10:25 PM, Stephen Rothwell wrote:
>>
>> > Hi all,
>> >
>> > Changes since 20121126:
>> >
>>
>>
>> on i386:
>>
>> drivers/media/v4l2-core/videobuf2-dma-contig.c:743:16: error:
>> 'vb2_dc_get_dmabuf' undeclared here (not in a function)
>>
>>
>> Full randconfig file is attached.
>>
>> --
>> ~Randy
>
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
prev parent reply other threads:[~2012-11-28 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 6:25 linux-next: Tree for Nov 27 Stephen Rothwell
2012-11-27 16:43 ` linux-next: Tree for Nov 27 (file notify) Randy Dunlap
2012-11-27 21:09 ` Eric Paris
2012-11-27 21:09 ` Stephen Rothwell
2012-11-27 18:32 ` linux-next: Tree for Nov 27 (media/v4l2-core/videobuf2-dma-contig.c) Randy Dunlap
2012-11-27 21:15 ` Stephen Rothwell
2012-11-28 0:52 ` Kyungmin Park [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=CAH9JG2WfpNttdthgZEAM+W5T8rrZwOULSBGaSB8XdVDVMhC1FA@mail.gmail.com \
--to=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=t.stanislaws@samsung.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).