linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-media@vger.kernel.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 8 (docbook/media)
Date: Thu, 09 Jun 2011 16:25:09 -0300	[thread overview]
Message-ID: <4DF11E15.5030907@infradead.org> (raw)
In-Reply-To: <20110608125243.e63a07fc.randy.dunlap@oracle.com>

Hi Randy,

Em 08-06-2011 16:52, Randy Dunlap escreveu:
> 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?

I'll take a look on it. 

FYI, The next build will probably be noisier, as it is now pointing to some 
documentation gaps at the DVB API. Those gaps should take a longer time to fix, 
as we need to discuss upstream about what should be done with those API's,
that seems to be abandoned upstream (only one legacy DVB driver uses them).
However, I was told that some out-of-tree drivers and some drivers under development
are using them.

So, I intend to wait until the next merge window before either dropping those 
legacy API specs (or moving them to a deprecated section) or to merge those
out-of-tree drivers, with the proper documentation updates.

> also, where is the mediaindexdocs target defined?

Thanks for noticing it. We don't need this target anymore. I'll write a patch
removing it.

Cheers,
Mauro.

  reply	other threads:[~2011-06-09 19:25 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 ` linux-next: Tree for June 8 (docbook/media) Randy Dunlap
2011-06-09 19:25   ` Mauro Carvalho Chehab [this message]
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=4DF11E15.5030907@infradead.org \
    --to=mchehab@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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).