Hi
In Documentation/rapidio/sysfs.txt, there is a description of the sysfs
interface which could be moved to Documentation/ABI (as a bus interface under
testing).
Would such a change be useful?
The ABI documentation format looks like the following:
What: (the full sysfs path of the attribute)
D
Hi
In Documentation/infiniband/sysfs.txt, there is a description of the infiniband
sysfs interface and there also exists
Documentation/ABI/testing/sysfs-class-infiniband which is out of date.
Would it be useful to move out the interface completely from
Documentation/infiniband/sysfs.txt to the AB
On Mon, Jan 08, 2018 at 11:58:12AM +0300, Ozgur wrote:
>
>
> 08.01.2018, 11:38, "Aishwarya Pant" :
> > Hi
>
> Hello,
>
> > In Documentation/rapidio/sysfs.txt, there is a description of the sysfs
> > interface which could be moved to Documentation/ABI (as a bus interface
> > under
> > testing).
08.01.2018, 11:38, "Aishwarya Pant" :
> Hi
Hello,
> In Documentation/rapidio/sysfs.txt, there is a description of the sysfs
> interface which could be moved to Documentation/ABI (as a bus interface under
> testing).
>
> Would such a change be useful?
>
> The ABI documentation format looks like
08.01.2018, 12:03, "Aishwarya Pant" :
> On Mon, Jan 08, 2018 at 11:58:12AM +0300, Ozgur wrote:
>> 08.01.2018, 11:38, "Aishwarya Pant" :
>> > Hi
>>
>> Hello,
>>
>> > In Documentation/rapidio/sysfs.txt, there is a description of the sysfs
>> > interface which could be moved to Documentation/AB
On Sat, Dec 30, 2017 at 11:53:06PM +0100, Luca Ceresoli wrote:
> The bullet list documenting the 'struct dma_device' fields has several
> nesting errors, making it render improperly. It also has incoherent
> formatting: some fields have a description in the same bullet, some in
> a sub-bullet.
App
Hello,
On Thu, Jan 04, 2018 at 10:57:00PM +0100, Maciej S. Szmigiero wrote:
> Currently, cgroups v2 documentation contains only a generic remark that
> "How resource consumption in the root cgroup is governed is up to each
> controller", which isn't really telling users much, who need to dig in th
[Sorry everyone for the late response, I went away on vacation and pushed this
off until I returned.]
On 12/13/2017 07:45 AM, Lorenzo Pieralisi wrote:
> [+Mark, Graeme]
>
> In $SUBJECT, s/avialable/available
>
> On Mon, Dec 11, 2017 at 10:50:58AM -0500, Prarit Bhargava wrote:
>> Other architectu
Hi Mauro,
Thanks for this patch series, nice to see this moving forward.
Some comments below (note the wrong queue_setup code in particular since that
relates to my comment about the '[PATCH v3] media: videobuf2-core: don't go out
of the buffer range' patch).
On 12/21/2017 05:18 PM, Mauro Carval
A quick follow-up:
On 01/08/2018 02:54 PM, Hans Verkuil wrote:
>> +/*
>> + * Videobuf operations
>> + */
>> +int dvb_vb2_init(struct dvb_vb2_ctx *ctx, const char *name, int nonblocking)
>> +{
>> +struct vb2_queue *q = &ctx->vb_q;
>> +int ret;
>> +
>> +memset(ctx, 0, sizeof(struct dvb_v
Em Mon, 8 Jan 2018 14:54:51 +0100
Hans Verkuil escreveu:
> Hi Mauro,
>
> Thanks for this patch series, nice to see this moving forward.
>
> Some comments below (note the wrong queue_setup code in particular since that
> relates to my comment about the '[PATCH v3] media: videobuf2-core: don't go
Em Mon, 8 Jan 2018 15:26:50 +0100
Hans Verkuil escreveu:
> A quick follow-up:
>
> On 01/08/2018 02:54 PM, Hans Verkuil wrote:
> >> +/*
> >> + * Videobuf operations
> >> + */
> >> +int dvb_vb2_init(struct dvb_vb2_ctx *ctx, const char *name, int
> >> nonblocking)
> >> +{
> >> + struct vb2_queue
The cross-release lockdep functionality has been removed in
e966eaeeb623f0997 ("locking/lockdep: Remove the cross-release locking
checks"), leaving the kernel parameter docs behind. The code handling
the parameter does not exist so this is a plain documentation change.
Signed-off-by: David Sterba
Hello,
On 08.01.2018 13:15, Tejun Heo wrote:
> Hello,
>
> On Thu, Jan 04, 2018 at 10:57:00PM +0100, Maciej S. Szmigiero wrote:
>> Currently, cgroups v2 documentation contains only a generic remark that
>> "How resource consumption in the root cgroup is governed is up to each
>> controller", which
On Sat, 6 Jan 2018 12:20:13 -0800
Matthew Wilcox wrote:
> I've been thinking about all the kernel-doc we have that's completely
> unincorporated. I've also been thinking about core-api/kernel-api.rst
> which to my mind is completely unreadable in its current form -- look at
> https://www.kernel.
On Mon, 08 Jan 2018 10:39:14 +1100
NeilBrown wrote:
> > There is value in using the c:func syntax, as it will generate
> > cross-references to the kerneldoc comments for those functions. In this
> > case, it would appear that these comments exist, but nobody has pulled
> > them into the docs yet
On 1/2/2018 8:46 AM, Rob Herring wrote:
On Wed, Dec 27, 2017 at 09:27:21AM -0700, Karthikeyan Ramasubramanian wrote:
Add device tree binding support for the QCOM GENI SE driver.
Signed-off-by: Karthikeyan Ramasubramanian
---
.../devicetree/bindings/soc/qcom/qcom,geni-se.txt | 15 ++
On 1/2/2018 8:47 AM, Rob Herring wrote:
On Wed, Dec 27, 2017 at 09:27:21AM -0700, Karthikeyan Ramasubramanian wrote:
Add device tree binding support for the QCOM GENI SE driver.
Also, "dt-bindings: ..." is the preferred subject prefix. Same for the
rest of the series.
I will update the subj
On 1/2/2018 8:51 AM, Rob Herring wrote:
On Wed, Dec 27, 2017 at 09:27:23AM -0700, Karthikeyan Ramasubramanian wrote:
Add device tree binding support for I2C Controller in GENI based
QUP Wrapper.
Signed-off-by: Sagar Dharia
Signed-off-by: Karthikeyan Ramasubramanian
---
.../devicetree/bind
Hello,
I personally am happy with the more organized Documentation/ tree. But
as everyone knows, there's still a bit of breakage. Not the most fun
to fix. However, it seems some tools could help ease this process /
prevent future breakage. I listed a couple below. If either seem worth
pursuing, I'
20 matches
Mail list logo
