From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-media@vger.kernel.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: linux-next: Tree for June 8 (docbook/media)
Date: Wed, 8 Jun 2011 12:52:43 -0700 [thread overview]
Message-ID: <20110608125243.e63a07fc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110608161046.4ad95776.sfr@canb.auug.org.au>
On Wed, 8 Jun 2011 16:10:46 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20110607:
Hi Mauro,
The DocBook/media/Makefile seems to be causing too much noise:
ls: cannot access linux-next-20110608/Documentation/DocBook/media/*/*.gif: No such file or directory
ls: cannot access linux-next-20110608/Documentation/DocBook/media/*/*.png: No such file or directory
Maybe the cleanmediadocs target could be made silent?
also, where is the mediaindexdocs target defined?
thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-06-08 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 6:10 linux-next: Tree for June 8 Stephen Rothwell
2011-06-08 19:52 ` Randy Dunlap [this message]
2011-06-09 19:25 ` linux-next: Tree for June 8 (docbook/media) Mauro Carvalho Chehab
2011-06-09 19:43 ` Mauro Carvalho Chehab
2011-06-09 20:32 ` Randy Dunlap
2011-06-09 23:32 ` Mauro Carvalho Chehab
2011-06-09 23:37 ` Randy Dunlap
2011-06-10 12:47 ` Mauro Carvalho Chehab
2011-06-10 15:04 ` Randy Dunlap
2011-06-10 15:19 ` Mauro Carvalho Chehab
2011-06-10 16:04 ` Randy Dunlap
2011-06-11 4:42 ` Stephen Rothwell
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=20110608125243.e63a07fc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).