On Wed, 2016-02-17 at 21:51 -0200, Mauro Carvalho Chehab wrote:
> […]
>
> We have 2 types of documentation for the Kernel part of the
> subsystem,
> Both using DocBook:
> - The uAPI documentation:
> https://linuxtv.org/downloads/v4l-dvb-apis
> - The kAPI documentation:
> https://linuxt
Em Thu, 18 Feb 2016 08:17:00 +
Russel Winder escreveu:
> On Wed, 2016-02-17 at 21:51 -0200, Mauro Carvalho Chehab wrote:
> > […]
> >
> > We have 2 types of documentation for the Kernel part of the
> > subsystem,
> > Both using DocBook:
> > - The uAPI documentation:
> > https://linuxtv.or
Em Thu, 18 Feb 2016 06:31:14 -0200
Mauro Carvalho Chehab escreveu:
> Em Thu, 18 Feb 2016 08:17:00 +
> Russel Winder escreveu:
>
> > On Wed, 2016-02-17 at 21:51 -0200, Mauro Carvalho Chehab wrote:
> > > […]
> > >
> > > We have 2 types of documentation for the Kernel part of the
> > > subs
On Thu, 18 Feb 2016, Daniel Vetter wrote:
> On Wed, Feb 17, 2016 at 11:14 PM, Jonathan Corbet wrote:
>> On Sun, 14 Feb 2016 13:27:04 +0100
>> Daniel Vetter wrote:
>>
>>> One concern/open I have for pro/cons are the hyperlinks from kerneldoc
>>> comments. Currently we have the postproc hack, iirc
On Thu, Feb 18, 2016 at 10:11 AM, Jani Nikula wrote:
> On Thu, 18 Feb 2016, Daniel Vetter wrote:
>> On Wed, Feb 17, 2016 at 11:14 PM, Jonathan Corbet wrote:
>>> On Sun, 14 Feb 2016 13:27:04 +0100
>>> Daniel Vetter wrote:
>>>
One concern/open I have for pro/cons are the hyperlinks from kern
Em Thu, 18 Feb 2016 07:10:14 -0200
Mauro Carvalho Chehab escreveu:
> Em Thu, 18 Feb 2016 06:31:14 -0200
> Mauro Carvalho Chehab escreveu:
>
> > Em Thu, 18 Feb 2016 08:17:00 +
> > Russel Winder escreveu:
> >
> > > On Wed, 2016-02-17 at 21:51 -0200, Mauro Carvalho Chehab wrote:
> > >
On Thu, 18 Feb 2016, Russel Winder wrote:
> On Wed, 2016-02-17 at 21:51 -0200, Mauro Carvalho Chehab wrote:
>> […]
>>
>> We have 2 types of documentation for the Kernel part of the
>> subsystem,
>> Both using DocBook:
>> - The uAPI documentation:
>> https://linuxtv.org/downloads/v4l-dvb-apis
On Thu, 18 Feb 2016, Mauro Carvalho Chehab wrote:
> Are there any tools that would convert from DocBook to ASCIIDoc?
I used pandoc when I tested the asciidoc pipeline. Something along the
lines of this for filtering docbook in stdin to asciidoc in stdout:
pandoc --atx-headers -f docbook -t ascii
Em Thu, 18 Feb 2016 11:37:41 +0200
Jani Nikula escreveu:
> On Thu, 18 Feb 2016, Mauro Carvalho Chehab wrote:
> > Are there any tools that would convert from DocBook to ASCIIDoc?
>
> I used pandoc when I tested the asciidoc pipeline. Something along the
> lines of this for filtering docbook in
On Thu, 18 Feb 2016, Hans Verkuil wrote:
> I looked at ReStructuredText and it looks like it will be a pain to convert
> the media DocBook code to that, and the main reason is the poor table support.
> The syntax for that looks very painful and the media DocBook is full of
> tables.
The table su
Em Thu, 18 Feb 2016 10:24:04 +0100
Daniel Vetter escreveu:
> On Thu, Feb 18, 2016 at 10:11 AM, Jani Nikula wrote:
> > On Thu, 18 Feb 2016, Daniel Vetter wrote:
> >> On Wed, Feb 17, 2016 at 11:14 PM, Jonathan Corbet wrote:
> >>> On Sun, 14 Feb 2016 13:27:04 +0100
> >>> Daniel Vetter wrote:
On Thu, 2016-02-18 at 08:58 +0100, Ingo Molnar wrote:
> So why not simply do the patch below? Very few people use boot
> parameters, and the
> complexity does not seem to be worth it.
>
> Furthermore I think an IMR range in itself is safe enough - it's not
> like such
> register state is going t
On 02/18/16 11:19, Jani Nikula wrote:
> On Thu, 18 Feb 2016, Hans Verkuil wrote:
>> I looked at ReStructuredText and it looks like it will be a pain to convert
>> the media DocBook code to that, and the main reason is the poor table
>> support.
>> The syntax for that looks very painful and the me
This is David and Carol Martin, We both won £33million lottery, we just
commenced a Charity Donation by giving out 1,500,000.00 GBP to five (5)
individuals; we listed you as a recipient of our cash donation of 1,500,000
GBP. get back to us for more with is email: davidcar...@yahoo.com.hk
http:/
On Thu, 18 Feb 2016, Mauro Carvalho Chehab wrote:
> For simple documents like the one produced by kernel-doc, I guess
> all markup languages would work equally.
>
> The problem is for complex documents like the media kAPI one, where
> the document was written to produce a book. So, it uses some co
Em Thu, 18 Feb 2016 13:23:37 +0200
Jani Nikula escreveu:
> On Thu, 18 Feb 2016, Mauro Carvalho Chehab wrote:
> > For simple documents like the one produced by kernel-doc, I guess
> > all markup languages would work equally.
> >
> > The problem is for complex documents like the media kAPI one, wh
On 02/18/16 13:04, Mauro Carvalho Chehab wrote:
> Em Thu, 18 Feb 2016 13:23:37 +0200
> Jani Nikula escreveu:
>
>> On Thu, 18 Feb 2016, Mauro Carvalho Chehab wrote:
>>> For simple documents like the one produced by kernel-doc, I guess
>>> all markup languages would work equally.
>>>
>>> The probl
Em Thu, 18 Feb 2016 13:07:03 +0100
Hans Verkuil escreveu:
> On 02/18/16 13:04, Mauro Carvalho Chehab wrote:
> > Em Thu, 18 Feb 2016 13:23:37 +0200
> > Jani Nikula escreveu:
> >
> >> On Thu, 18 Feb 2016, Mauro Carvalho Chehab
> >> wrote:
> >>> For simple documents like the one produced by
On Thu, 18 Feb 2016 10:24:04 +0100
Daniel Vetter wrote:
> > Worth noting is that, AFAICT, in all of the proposals, including the
> > original where kernel-doc produces docbook, this autoreferencing only
> > works within parts processed by kernel-doc. Not in the template
> > documents themselves.
On Thu, 18 Feb 2016 10:44:34 -0200
Mauro Carvalho Chehab wrote:
> > > It is workable, but I guess nested tables produced a better
> > > result.
> > >
> > > I did myself a test with nested tables with asciidoc too:
> > >
> > > https://mchehab.fedorapeople.org/media-kabi-docs-test/pandoc_asciidoc/
On Thu, Feb 18, 2016 at 2:01 PM, Jonathan Corbet wrote:
> On Thu, 18 Feb 2016 10:24:04 +0100
> Daniel Vetter wrote:
>
>> > Worth noting is that, AFAICT, in all of the proposals, including the
>> > original where kernel-doc produces docbook, this autoreferencing only
>> > works within parts proces
On 2016-02-17 23:30, Stewart Smith wrote:
Steven Royer writes:
On 2016-02-17 16:31, Greg Kroah-Hartman wrote:
On Wed, Feb 17, 2016 at 03:18:26PM -0600, Steven Royer wrote:
On 2016-02-16 16:18, Greg Kroah-Hartman wrote:
>On Tue, Feb 16, 2016 at 02:43:13PM -0600, Steven Royer wrote:
>>From: Ste
* Bryan O'Donoghue wrote:
> On Thu, 2016-02-18 at 08:58 +0100, Ingo Molnar wrote:
> > So why not simply do the patch below? Very few people use boot
> > parameters, and the
> > complexity does not seem to be worth it.
> >
> > Furthermore I think an IMR range in itself is safe enough - it's not
On Mon, 2016-02-08 at 10:41 -0500, João Paulo Rechi Vita wrote:
> This creates a new LED trigger to be used by platform drivers as a
> default trigger for airplane-mode indicator LEDs.
>
> By default this trigger will fire when RFKILL_OP_CHANGE_ALL is called
> for all types (RFKILL_TYPE_ALL), sett
Hi,
Sorry for the delay reviewing this.
On Mon, 2016-02-08 at 10:41 -0500, João Paulo Rechi Vita wrote:
> Provide an interface for the airplane-mode indicator be controlled
> from
> userspace. User has to first acquire the control through
> RFKILL_OP_AIRPLANE_MODE_ACQUIRE and keep the fd open f
On Thu, 2016-02-18 at 19:53 +0100, Ingo Molnar wrote:
> * Bryan O'Donoghue wrote:
>
> > On Thu, 2016-02-18 at 08:58 +0100, Ingo Molnar wrote:
> > > So why not simply do the patch below? Very few people use boot
> > > parameters, and the
> > > complexity does not seem to be worth it.
> > >
> > >
26 matches
Mail list logo
