to mode 0666 will fail respectively revert to 0664.
Signed-off-by: Nicholas Mc Guire
---
V2: the descriptions were not too helpful as noted by
Greg Kroah-Hartman
so lets see if V2 is any better...
Documentation/filesystems/sysfs.txt | 21 +
1 file changed, 21
0666 will fail.
Signed-off-by: Nicholas Mc Guire
---
Note quite sure if this is the right place to place the note on mode 0666
but it should be somewhere as any attempt to set 0666 will be reverted
to 0664.
Documentation/filesystems/sysfs.txt | 16
1 file changed, 16 insertions
with API conversions or maybe "managed" is
being misunderstood ? So add a note to make the scope of "managed" clear.
Signed-off-by: Nicholas Mc Guire
---
This popped up due to some API checking coccinelle scripts for devm_* that are
under development are triggering far
On Mon, Jan 15, 2018 at 09:28:47PM +0100, Wolfram Sang wrote:
> On Mon, Jan 15, 2018 at 10:24:52PM +0200, Andy Shevchenko wrote:
> > On Mon, Jan 15, 2018 at 2:08 PM, Nicholas Mc Guire wrote:
> > > From: Nicholas Mc Guire
> > >
> > > Currently there are a f
From: Nicholas Mc Guire
Currently there are a few drivers that still set the .owner
in the i2c_driver structure - all of which are reported by
coccinelle (scripts/coccinelle/api/platform_no_drv_owner.cocci)
and there are no cases that set the .onwer and do not call any
of the functions that
On Tue, Jan 10, 2017 at 10:25:29PM +0100, Pavel Machek wrote:
> Hi!
>
> > > "to have zero jitter" at least. I believe it is "does not".
> > >
> > > I don't see how atomic vs. non-atomic context makes difference. There
> > > are sources of jitter that affect atomic context...
> >
> > The relevanc
On Tue, Dec 27, 2016 at 10:56:26PM +0100, Pavel Machek wrote:
> On Tue 2016-12-13 04:58:43, Nicholas Mc Guire wrote:
> > useleep_range() with a delta of 0 makes no sense and only prevents the
> > timer subsystem from optimizing interrupts. As any user of usleep_range()
> > is
On Tue, Dec 13, 2016 at 04:27:32PM -0800, Joe Perches wrote:
> a, On Tue, 2016-12-13 at 09:19 +0000, Nicholas Mc Guire wrote:
> > On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > > useleep_rang
On Tue, Dec 13, 2016 at 01:05:12PM +0100, Julia Lawall wrote:
>
>
> On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
>
> > On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > > useleep_range
On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > useleep_range() with a delta of 0 makes no sense and only prevents the
> > timer subsystem from optimizing interrupts. As any user of usleep_range()
> > is in n
idea.
Signed-off-by: Nicholas Mc Guire
---
V2: trailing whitespaces removed (sent the wrong file before...)
as of 4.9.0 there are about 20 cases of usleep_ranges() that have
min==max and none of them really look like they are necessary, so
it does seem like a relatively common misunderstanding
idea.
Signed-off-by: Nicholas Mc Guire
---
as of 4.9.0 there are about 20 cases of usleep_ranges() that have
min==max and none of them really look like they are necessary, so
it does seem like a relatively common misunderstanding worth
noting in the documentation.
Patch is against 4.9.0
On Tue, Oct 25, 2016 at 12:50:01PM -0700, Brian Norris wrote:
> Hi,
>
> It looks like Nicholas submitted this doc a while back as patch 2/2:
>
> "[PATCH 2/2] doc: detailed documentation for completion"
> http://lkml.iu.edu/hypermail/linux/kernel/1412.2/03676.html
>
> where patch 1/2 got merged a
13 matches
Mail list logo
