On Wed, 2018-08-15 at 09:48 +0800, houlong wei wrote:
> On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> > This patch adds the device node of the GCE hardware for CMDQ module.
> > [...]
Hello Matthias,
Sorry to disturb you. Are you availabe to review this patch and give
your comment? Tha
2018-09-07 8:37 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> If there is no System.map file for "make modules_install",
> scripts/depmod.sh will silently exit with success, having done
> nothing. Since this is an unexpected situation, change it to
> report a Warning for the missing file. Th
On Wed, 2018-08-15 at 09:46 +0800, houlong wei wrote:
> On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
> >[...]
Hello Matthias,
Sorry to disturb you. Could you please review this patch and give
your comment? Tha
On 8 September 2018 at 02:39, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.4.155 release.
> There are 47 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
On 8 September 2018 at 02:39, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.9.126 release.
> There are 63 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
On 8 September 2018 at 02:38, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.14.69 release.
> There are 89 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
On 8 September 2018 at 02:37, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.18.7 release.
> There are 145 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
On Sat, Sep 08, 2018 at 04:28:09PM +0200, Arnd Bergmann wrote:
> The SNDCTL_* and SOUND_* commands are the old OSS user interface.
>
> I checked all the sound ioctl commands listed in fs/compat_ioctl.c
> to see if we still need the translation handlers. Here is what I
> found:
>
> - sound/oss/ is
On Sat, Sep 08, 2018 at 04:28:12PM +0200, Arnd Bergmann wrote:
> These are all handled by the random driver, so instead of listing
> each ioctl, we can just use the same function to deal with both
> native and compat commands.
Umm... I don't think it's right -
> .unlocked_ioctl = random_io
On 09/05/2018 10:01 AM, Linus Torvalds wrote:
On Wed, Sep 5, 2018 at 8:34 AM Guenter Roeck wrote:
On 09/05/2018 02:01 AM, Greg Kroah-Hartman wrote:
---
[ 9990.754641] watchdog: BUG: soft lockup - CPU#5 stuck for 22s!
[kworker/5:1:155]
[ 9990.762601] RIP: 0010:smp_call_function_many+0x208/0x2
Greg,
On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman
wrote:
>
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Jann Horn
>
> commit 5820f140edef111a9ea2ef414ab2428b8cb805b1 upstream.
>
> The old code would hold the userns_state_mut
On Tue, Aug 28, 2018 at 6:53 AM, Patrick Bellasi
wrote:
> In order to properly support hierarchical resources control, the cgroup
> delegation model requires that attribute writes from a child group never
> fail but still are (potentially) constrained based on parent's assigned
> resources. This r
On Thu, Aug 30, 2018 at 01:20:05PM +0800, Anson Huang wrote:
> Update i.MX6ULL iomux header according to latest reference
> manual Rev.1, 11/2017.
>
> Signed-off-by: Anson Huang
Applied, thanks.
On Thu, Sep 06, 2018 at 11:15:17AM +0100, Mark Brown wrote:
> On Mon, Aug 27, 2018 at 09:48:16AM +0800, Shawn Guo wrote:
>
> > Can you ACK on those two regulator patches, so that I can queue this
> > series up on IMX tree?
>
> I was expecting to get a pull request with the precursor patches in it
syzbot has found a reproducer for the following crash on:
HEAD commit:d7b686ebf704 Merge branch 'i2c/for-current' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=148ac14940
kernel config: https://syzkaller.appspot.com/x/.config?x=8f5987
Hi,
On Fri, Aug 3, 2018 at 10:53 AM, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add ZynqMP firmware IOCTL API to control and configure
> devices like PLLs, SD, Gem, etc.
>
> Signed-off-by: Rajan Vaja
> Signed-off-by: Jolly Shah
This patch worries me somewhat. It's a transparent pass-through ioc
Hi,
I noticed the below when I was reviewing the code for merge into
arm-soc. Would you mind following up with an incremental patch? I
don't think we need to ask Michal to respin for this:
On Fri, Aug 3, 2018 at 10:53 AM, Jolly Shah wrote:
> From: Rajan Vaja
>
> Add debugfs file to query platfo
Hi Patrick!
On Tue, Aug 28, 2018 at 6:53 AM, Patrick Bellasi
wrote:
> Utilization clamping requires each CPU to know which clamp values are
> assigned to tasks that are currently RUNNABLE on that CPU.
> Multiple tasks can be assigned the same clamp value and tasks with
> different clamp values ca
Currently, "disable_clkrun" yenta_socket module parameter is only
implemented for TI CardBus bridges.
Add also an implementation for Ricoh bridges that have the necessary
setting documented in publicly available datasheets.
Tested on a RL5C476II with a Sunrich C-160 CardBus NIC that doesn't work
c
Commit 9c695203a7dd ("compiler-gcc.h: gcc-4.5 needs noclone
and noinline on __naked functions") added noinline and noclone
as a workaround for a gcc 4.5 bug, which was resolved in 4.6.0.
Since now the minimum gcc supported version is 4.6,
we can clean it up.
See https://gcc.gnu.org/bugzilla/show_
Cc: Rasmus Villemoes
Cc: Luc Van Oostenryck
Cc: Eli Friedman
Cc: Christopher Li
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Masahiro Yamada
Cc: Joe Perches
Cc: Dominique Martinet
Cc: Linus Torvalds
Cc: linux-spa...@vger.kernel.org
R
Different definitions of __must_be_array:
* gcc: disabled for __CHECKER__
* clang: same definition as gcc's, but without __CHECKER__
* intel: the comment claims __builtin_types_compatible_p()
is unsupported; but icc seems to support it since 13.0.1
(released in 2012). See https://g
Sparse knows about a few more attributes now, so we can remove
the __CHECKER__ conditions from them (which, in turn, allow us
to move some of them later on to compiler_attributes.h).
* assume_aligned: since sparse's commit ffc860b ("sparse:
ignore __assume_aligned__ attribute"), included in
Attributes const and always_inline have tests around them
which are unneeded, since they are supported by gcc >= 4.6,
clang >= 3 and icc >= 13. https://godbolt.org/z/DFPq37
In the case of gnu_inline, we do not need to test for
__GNUC_STDC_INLINE__ because, regardless of the current
inlining behavi
Instead of using version checks per-compiler to define (or not)
each attribute, use __has_attribute to test for them, following
the cleanup started with commit 815f0ddb346c
("include/linux/compiler*.h: make compiler-*.h mutually exclusive"),
which is supported on gcc >= 5, clang >= 2.9 and icc >= 1
The Compiler Attributes series is an effort to disentangle
the include/linux/compiler*.h headers and bring them up to date.
The main idea behind the series is to use feature checking macros
(i.e. __has_attribute) instead of compiler version checks (e.g. GCC_VERSION),
which are compiler-agnostic (s
Cc: Rasmus Villemoes
Cc: Luc Van Oostenryck
Cc: Eli Friedman
Cc: Christopher Li
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Masahiro Yamada
Cc: Joe Perches
Cc: Dominique Martinet
Cc: Nick Desaulniers
Cc: Linus Torvalds
Cc: linux-sp
Cc: Eli Friedman
Cc: Christopher Li
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Masahiro Yamada
Cc: Joe Perches
Cc: Dominique Martinet
Cc: Nick Desaulniers
Cc: Linus Torvalds
Signed-off-by: Miguel Ojeda
---
MAINTAINERS | 5 +
1
The attribute syntax optionally allows to surround attribute names
with "__" in order to avoid collisions with macros of the same name
(see https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html).
This homogenizes all attributes to use the syntax with underscores.
While there are currently only
__optimize and __deprecate_for_modules are unused in
the whole kernel tree. Simply drop them.
Cc: Rasmus Villemoes
Cc: Luc Van Oostenryck
Cc: Eli Friedman
Cc: Christopher Li
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Masahiro Yamada
Cc: Jonathan Corbet
Cc: Rasmus Villemoes
Cc: Luc Van Oostenryck
Cc: Eli Friedman
Cc: Christopher Li
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Masahiro Yamada
Cc: Joe Perches
Cc: Dominique Martinet
Cc: Nick Desaulniers
Cc: Linus T
Cc: Rasmus Villemoes
Cc: Luc Van Oostenryck
Cc: Eli Friedman
Cc: Christopher Li
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Geert Uytterhoeven
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Cc: Masahiro Yamada
Cc: Joe Perches
Cc: Dominique Martinet
Cc: Linus Torvalds
Cc: linux-spa...@vger.kernel.org
S
The naked attribute is supported by at least gcc >= 4.6 (for ARM,
which is the only current user), gcc >= 8 (for x86), clang >= 3.1
and icc >= 13. See https://godbolt.org/z/350Dyc
Therefore, move it out of compiler-gcc.h so that the definition
is shared by all compilers.
Cc: Rasmus Villemoes
Cc:
On 09/07/2018 02:07 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.18.7 release.
There are 145 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 09/07/2018 02:08 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.69 release.
There are 89 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.126 release.
There are 63 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.155 release.
There are 47 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Sat, Sep 08, 2018 at 09:10:46AM -0700, Randy Dunlap wrote:
> On 09/08/2018 08:54 AM, Matthew Wilcox wrote:
> > On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
> >> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> >>> I'd rather use KB and MB suffixes or at leas
Hi Jerome,
Thank you for the patch.
On 09/06/2018 03:59 PM, Jerome Brunet wrote:
> When probing, if we fail to get the pwm due to probe deferal, we shouldn't
> print an error message. Just be silent in this case.
>
> Signed-off-by: Jerome Brunet
> ---
> drivers/leds/leds-pwm.c | 5 +++--
> 1 f
On Thu, Sep 06, 2018 at 10:15:12PM +, Tyler Hicks wrote:
> On 2018-09-06 09:28:55, Tycho Andersen wrote:
> > /**
> > * struct seccomp_filter - container for seccomp BPF programs
> > *
> > @@ -66,6 +114,30 @@ struct seccomp_filter {
> > bool log;
> > struct seccomp_filter *prev;
> >
Debugging a specific driver or subsystem can be a lot easier
if we can trace events specific to that driver or subsystem.
This type of filtering can be achieved using existing
dynamic debug library which provides a way to filter based
on files, functions and modules.
Using this, provide an additio
The new asm-generic/io-instrumented.h will keep arch code
clean and separate from instrumented version which traces
io register accesses. This instrumented header can later
be included in arm as well for tracing io register accesses.
Suggested-by: Will Deacon
Signed-off-by: Sai Prakash Ranjan
--
Currently pstore has function trace support which can be
used to get the function call chain with limited data.
Event tracing has extra data which is useful to debug wide
variety of issues and is heavily used across the kernel.
Adding this support to pstore can be very helpful to debug
different s
Generic IO read/write i.e., __raw_{read,write}{b,l,w,q} are
typically used to read/write from/to memory mapped registers,
which can cause hangs or some undefined behaviour if access
unclocked. Tracing these register accesses can be very helpful
to debug such issues during initial development stages
Add an optional property called event-size to reserve
log buffer for trace events.
Signed-off-by: Sai Prakash Ranjan
---
.../devicetree/bindings/reserved-memory/ramoops.txt| 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/reserve
Add the kernel command line tp_pstore option that will have
tracepoints go to persistent ram buffer as well as to the
trace buffer for further debugging. This is similar to tp_printk
cmdline option of ftrace.
Pstore support for event tracing is already added and we enable
logging to pstore only if
Hi,
This patch series adds Event tracing support to pstore and is continuation
to the RFC patch introduced to add a new tracing facility for register
accesses called Register Trace Buffer(RTB). Since we decided to not introduce
a separate framework to trace register accesses and use existing frame
Hi Bjorn,
On 09/08/2018 07:02 AM, Bjorn Andersson wrote:
> On Tue 04 Sep 04:01 PDT 2018, Baolin Wang wrote:
>
>> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
>> b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
> [..]
>> +What: /sys/class/leds//h
Hi Vincent,
On 07/09/18 08:40, Vincent Guittot wrote:
> When CPUs have different capacity because of RT/DL tasks or
> micro-architecture or max frequency differences, there are situation where
> the imbalance is not correctly set to migrate waiting task on the idle CPU.
>
This is essentially alw
Dan,
On 09/07/2018 03:52 PM, Dan Murphy wrote:
[...]
>>
>>> And I think Jacek pointed out that the bindings references in this bindings
>>> don't even exist.
>>>
>>> I am thinking we need to deprecate this MFD driver and consolidate these
>>> drivers
>>> in the LED directory as we indicated befor
On 09/06/2018 09:16 AM, Keerthy wrote:
>
>
> On Wednesday 05 September 2018 04:07 PM, Linus Walleij wrote:
>> On Mon, Sep 3, 2018 at 7:40 AM Keerthy wrote:
>>> On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote:
Use dev_name to get a unique label and use -1 for a base to get o
On non-SMP configs, when only one of CONFIG_{PARAVIRT,IRQ_TIME}_ACCOUNTING
is defined, we are declaring a variable (irq_delta or steal) which
is not used:
kernel/sched/core.c: In function ‘update_rq_clock_task’:
kernel/sched/core.c:139:17: warning: unused variable ‘irq_delta’
[-Wunused-va
Hello,
whlie using this path i got another stall - which i never saw under
kernel 4.4. Here is the trace:
[305111.932698] INFO: task ksmtuned:1399 blocked for more than 120 seconds.
[305111.933612] Tainted: G 4.12.0+105-ph #1
[305111.934456] "echo 0 > /proc/sys/kernel/hung_
On Sun, 2 Sep 2018 15:29:23 +0200
Tomasz Duszynski wrote:
> Relying on CONFIG_PM_SLEEP to set PM ops is not necessary
> since core will handle everything internally. One have to only make sure
> that functions that can go unused are marked with __maybe_unused.
>
> Signed-off-by: Tomasz Duszynsk
From: Dou Liyang
Linux has spread out the non managed interrupt across the possible
target CPUs to avoid vector space exhaustion.
But, the same situation may happen on the managed interrupts.
Spread managed interrupt on allocation as well.
Note: also change the return value for the empty searc
From: Dou Liyang
Linux finds the CPU which has the lowest vector allocation count to spread
out the non managed interrupt across the possible target CPUs.
This common CPU finding code will also be used in managed case,
So Split it out into a helper for preparation.
Signed-off-by: Dou Liyang
-
On Sat, 08 Sep 2018 19:00:34 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 8. September 2018 um 18:21 geschrieben:
> >
> >
> > On Sat, 08 Sep 2018 15:18:10 +0200,
> > Stefan Wahren wrote:
> > >
> > > Hi Takashi,
> > >
> > > > Takashi Iwai hat am 4. September 2018 um 17:58
>
Hi Linus,
The following changes since commit a72b44a871c218e2a0580e68affa1d3528c0587a:
Merge tag 'omap-for-v4.19/fixes-v2-signed' of
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
(2018-09-01 18:22:19 -0700)
are available in the git repository at:
git://git.ker
Hi,
> Takashi Iwai hat am 8. September 2018 um 18:21 geschrieben:
>
>
> On Sat, 08 Sep 2018 15:18:10 +0200,
> Stefan Wahren wrote:
> >
> > Hi Takashi,
> >
> > > Takashi Iwai hat am 4. September 2018 um 17:58
> > > geschrieben:
> > >
> > >
> > > Hi,
> > >
> > > since I had an opportunity
On 09/08/2018 06:43 AM, Masanari Iida wrote:
> This patch fixes some spelling typos found in printk messages.
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> drivers/dma/ep93xx_dma.c | 6 +++---
> drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c
On Sat, 08 Sep 2018 15:18:10 +0200,
Stefan Wahren wrote:
>
> Hi Takashi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > Hi,
> >
> > since I had an opportunity to play with RPi3B+ recently, I took a look
> > at the existing bcm2835-audio driver code and was amuse
On Sat, 08 Sep 2018 15:25:14 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > Only a few of them are really needed.
> >
> > Signed-off-by: Takashi Iwai
> > ---
> > .../vc04_services/bcm2835-audio/bcm2835-ctl.c | 15 ---
On Sat, 08 Sep 2018 15:40:41 +0200,
Stefan Wahren wrote:
>
> Hi,
>
> > Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
> >
> >
> > The chip->audio_mutex is used basically for protecting the opened
> > stream assignment, and the prepare callback is irrelevant with it.
> >
> > Signe
On 09/08/2018 08:54 AM, Matthew Wilcox wrote:
> On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
>> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
>>> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
- {"kmalloc-1024", 1024},
On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> > On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > > -
This report contains "getblk(): executed=9 bh_count=0 bh_state=0" lines.
Thus,
#syz dup: INFO: task hung in generic_file_write_iter
Hello,
syzbot found the following crash on:
HEAD commit:b50694381cfc Merge branch 'stable/for-linus-4.17' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166708d780
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
da
Marcel Holtmann wrote:
> so I have reviewed and tested this code. In addition, we have test cases for
> it in ELL (embedded linux library).
I wonder if there's any practical way to add a test for this to the keyutils
test suite. I'm guessing it's quite tricky, given the extra bits you need to
e
Tony Lindgren wrote:
> > > Looks like next-20180906 now has a regression where mounting
> > > root won't work with commit fd0002870b45 ("vfs: Implement a
> > > filesystem superblock creation/configuration context").
> >
> > Am I right in thinking you're not using any of the LSMs?
>
> Assuming L
On Fri, Sep 7, 2018 at 9:57 PM, Kees Cook wrote:
> On Fri, Sep 7, 2018 at 9:17 AM, Tetsuo Handa
> wrote:
>> On 2018/09/08 0:29, syzbot wrote:
>>> syzbot has found a reproducer for the following crash on:
>>>
>>> HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
>>> git
Hi,
Please Cc the watchdog maintainers. Else, I have very few comments.
On 07/09/2018 09:17:43-0600, Jeremy Gebben wrote:
> The abx804 and abx805 chips have support for a simple watchdog
> function that can trigger an external reset.
>
> Signed-off-by: Jeremy Gebben
> ---
> drivers/rtc/Kconfig
The /proc/pci/ implementation already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 23c0406d8b30..28ebff2d1799 10
The /dev/rawX implementation already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 4
1 file changed, 4 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index 28ebff2d1799..e755802cd887 1006
Commit aa98aa31987a ("md: move compat_ioctl handling into md.c")
already removed the COMPATIBLE_IOCTL() table entries and added
a complete implementation, but a few lines got left behind and
should also be removed here.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 5 -
1 file changed
The joystick driver already handles these just fine, so
the entries in the table are not needed any more.
Signed-off-by: Arnd Bergmann
---
fs/compat_ioctl.c | 8
1 file changed, 8 deletions(-)
diff --git a/fs/compat_ioctl.c b/fs/compat_ioctl.c
index eb29188d1dbb..23c0406d8b30 100644
--
On Tue, 4 Sep 2018 17:13:14 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol.
> This patch adds the documentation of device tree bindings for adxl372
> I2C.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
> Documentation/devicetr
These are all handled by the random driver, so instead of listing
each ioctl, we can just use the same function to deal with both
native and compat commands.
Signed-off-by: Arnd Bergmann
---
drivers/char/random.c | 1 +
fs/compat_ioctl.c | 7 ---
2 files changed, 1 insertion(+), 7 deleti
Since commit 07d106d0a33d ("vfs: fix up ENOIOCTLCMD error handling"),
we don't warn about unhandled compat-ioctl command code any more, but
just return the same error that a native file descriptor returns when
there is no handler.
This means the IGNORE_IOCTL() annotations are completely useless an
The SNDCTL_* and SOUND_* commands are the old OSS user interface.
I checked all the sound ioctl commands listed in fs/compat_ioctl.c
to see if we still need the translation handlers. Here is what I
found:
- sound/oss/ is (almost) gone from the kernel, this is what actually
needed all the transl
On Tue, 4 Sep 2018 17:12:32 +0300
Stefan Popa wrote:
> The adxl372 is designed to communicate in either SPI or I2C protocol. It
> autodetects the format being used, requiring no configuration control to
> select the format.
>
> Signed-off-by: Stefan Popa
Applied.
Thanks,
Jonathan
> ---
> MAI
The KD* family of ioctls is implemented in two drivers:
drivers/tty/vt and drivers/s390/char/tty3270.c. Both of them
have compat handlers for all their ioctl commands, so translation
in fs/compat_ioctl.c is never used.
Commit fb07a5f857ac ("compat_ioctl: remove all VT ioctl handling")
removed the
On Tue, 4 Sep 2018 17:11:31 +0300
Stefan Popa wrote:
> This patch restructures the existing adxl372 driver by adding a module for
> SPI and a header file, while the baseline module deals with the chip-logic.
>
> This is a necessary step, as this driver should support in the future
> a similar de
The two drivers implementing these both gained proper compat_ioctl()
handlers a long time ago with commits bb6c8d8fa9b5 ("HID: hiddev:
Add 32bit ioctl compatibilty") and ae5e49c79c05 ("HID: hidraw: add
compatibility ioctl() for 32-bit applications."), so the lists in
fs/compat_ioctl.c are no longer
On Sat, 8 Sep 2018 17:59:13 +0530
Himanshu Jha wrote:
> On Sat, Sep 08, 2018 at 06:57:36PM +0800, zhong jiang wrote:
> > The iterator in for_each_set_bit is never null, therefore, remove
> > the redundant conditional judgment.
> >
> > Signed-off-by: zhong jiang
> > ---
> > drivers/iio/humidity
On 2018/09/08 22:57, Johannes Weiner wrote:
> On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
>> Due to commit d75da004c708c9fc ("oom: improve oom disable handling") and
>> commit 3100dab2aa09dc6e ("mm: memcontrol: print proper OOM header when
>> no eligible victim left"), all
>>
>>
On Thu, 6 Sep 2018 14:22:06 -0700
Matthias Kaehlcke wrote:
> On Thu, Sep 06, 2018 at 02:10:43PM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke
> > wrote:
> > > Add a channel node for the die temperature to the ADC.
> > >
> > > Signed-off-by: Mat
On Thu, 6 Sep 2018 14:04:52 -0700
Matthias Kaehlcke wrote:
> The documentation of Qualcomm's SPMI PMIC voltage ADC claims that the
> 'reg' property consists of two values, the SPMI address and the length
> of the controller's registers. However the SPMI bus to which it is added
> specifies "#siz
On Tue, 04 Sep 2018 20:23:57 +0100
Afonso Bordado wrote:
> On Fri, 2018-08-31 at 17:35 +0200, Tomasz Duszynski wrote:
> > On Thu, Aug 30, 2018 at 10:18:22PM +0100, Afonso Bordado wrote:
> > > FXAS21002C is a 3 axis gyroscope with integrated temperature sensor
Just a quick hint to make my life
On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> On Thu, Sep 06, 2018 at 03:48:49PM -0700, a...@linux-foundation.org wrote:
> > - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> > - {"kmalloc-4096", 4096}, {"kmalloc-8192", 8192
On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
remove the unnecessary condition.
Signed-off-by: zhong jiang
---
drivers/infiniband/hw/usnic/usnic_debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/infiniband/hw/usnic/usnic_debugfs.c
b/drivers
On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote:
> On 2018/08/22 1:04, Johannes Weiner wrote:
> > When the memcg OOM killer runs out of killable tasks, it currently
> > prints a WARN with no further OOM context. This has caused some user
> > confusion.
> >
> > Warnings indicate a kern
I, Mikhail Fridman have selected you specifically as one of my
beneficiaries for my Charitable Donation,
Check the link below for confirmation:
https://www.rt.com/business/343781-mikhail-fridman-will-charity/
I await your earliest response.
Best Regards,
Mikhail Fridman.
---
On Thu, 6 Sep 2018 15:19:29 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks a lot for the review. Please see my response inline.
Hi Manish,
Just one thing to think about. (and I'm not that great about this
myself :) Please look to crop out irrelevant text. It saves
time when people are
This patch fixes some spelling typos found in printk messages.
Signed-off-by: Masanari Iida
---
drivers/dma/ep93xx_dma.c | 6 +++---
drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c | 2 +-
drivers/gpu/drm/drm_kms_helper_common.c| 2 +-
drivers/gpu/drm/sel
On Thu, 6 Sep 2018 13:27:34 +
Manish Narani wrote:
> Hi Jonathan,
>
> Thanks for the review!
>
> > -Original Message-
> > From: Jonathan Cameron [mailto:ji...@kernel.org]
> > Sent: Sunday, September 2, 2018 11:45 PM
> > To: Manish Narani
> > Cc: knaac...@gmx.de; l...@metafoo.de; pm
debugfs_remove_recursive has taken IS_ERR_OR_NULL into account. So just
remove the condition check before debugfs_remove_recursive.
Signed-off-by: zhong jiang
---
drivers/md/bcache/debug.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/debug.c b/drivers/m
Hi,
> Takashi Iwai hat am 4. September 2018 um 17:58 geschrieben:
>
>
> The chip->audio_mutex is used basically for protecting the opened
> stream assignment, and the prepare callback is irrelevant with it.
>
> Signed-off-by: Takashi Iwai
> ---
> drivers/staging/vc04_services/bcm2835-audio/b
On 2018/08/22 1:04, Johannes Weiner wrote:
> When the memcg OOM killer runs out of killable tasks, it currently
> prints a WARN with no further OOM context. This has caused some user
> confusion.
>
> Warnings indicate a kernel problem. In a reported case, however, the
> situation was triggered by
1 - 100 of 175 matches
Mail list logo
