[PATCH] net: sunhme: fix spelling mistakes: "ParityErro" -> "ParityError"

From: Colin Ian King trivial fix to spelling mistakes in printk message. Signed-off-by: Colin Ian King --- drivers/net/ethernet/sun/sunhme.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] net: sunhme: fix spelling mistakes: "ParityErro" -> "ParityError"

From: Colin Ian King trivial fix to spelling mistakes in printk message. Signed-off-by: Colin Ian King --- drivers/net/ethernet/sun/sunhme.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/sun/sunhme.c b/drivers/net/ethernet/sun/sunhme.c index

Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349

On Fri, Apr 28, 2017 at 06:03:14PM -0400, Tejun Heo wrote: > On Tue, Apr 18, 2017 at 10:12:16AM +0100, Andre Przywara wrote: > > Yeah, so I stack-dumped on the zero allocations and indeed they are > > called from cleanup functions: > > drivers/pinctrl/pinmux.c:pinmux_generic_free_functions(): > >

Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349

On Fri, Apr 28, 2017 at 06:03:14PM -0400, Tejun Heo wrote: > On Tue, Apr 18, 2017 at 10:12:16AM +0100, Andre Przywara wrote: > > Yeah, so I stack-dumped on the zero allocations and indeed they are > > called from cleanup functions: > > drivers/pinctrl/pinmux.c:pinmux_generic_free_functions(): > >

[PATCH] scsi: megaraid_sas: fix spelling mistakes: "outstanding" -> "outstanding"

From: Colin Ian King trivial fix to spelling mistakes in dev_info and scmd_printk messages. Also join lines on split literal string to clean up checkpatch warning. Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c

[PATCH] scsi: megaraid_sas: fix spelling mistakes: "outstanding" -> "outstanding"

From: Colin Ian King trivial fix to spelling mistakes in dev_info and scmd_printk messages. Also join lines on split literal string to clean up checkpatch warning. Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-

Re: [PATCH v2] x86/mm/kaslr: Use _ASM_MUL macro for multiplication

On 04/26/17 14:29, Greg Hackmann wrote: > On 04/26/2017 02:24 PM, h...@zytor.com wrote: This really feels like a "fix your compiler" issue. >>> >>> We already use the other forms, what's so bad about adding mul too? >>> And if this lets us build under clang, all the better. >>> >>> -Kees >>

Re: [PATCH v2] x86/mm/kaslr: Use _ASM_MUL macro for multiplication

On 04/26/17 14:29, Greg Hackmann wrote: > On 04/26/2017 02:24 PM, h...@zytor.com wrote: This really feels like a "fix your compiler" issue. >>> >>> We already use the other forms, what's so bad about adding mul too? >>> And if this lets us build under clang, all the better. >>> >>> -Kees >>

Re: [PATCH v5] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver

Hey, On Sat, 2017-04-29 at 11:16 -0700, Dmitry Torokhov wrote: > "Say Y here if you wish to connect PSX (PS1/2) pad via SPI > interface." It should say "PlayStation 1/2 joypads". Using "Play Station" is incorrect, PSX is a code name so you could mention it in between brackets. Saying "pads" is

Re: [PATCH v5] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver

Hey, On Sat, 2017-04-29 at 11:16 -0700, Dmitry Torokhov wrote: > "Say Y here if you wish to connect PSX (PS1/2) pad via SPI > interface." It should say "PlayStation 1/2 joypads". Using "Play Station" is incorrect, PSX is a code name so you could mention it in between brackets. Saying "pads" is

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Fri, 28 Apr 2017 15:34:06 +0200, Paolo Bonzini wrote: > > > > On 27/04/2017 02:42, Satoru Takeuchi wrote: > > At Wed, 26 Apr 2017 18:58:27 +0200, > >> On 26/04/2017 13:47, Satoru Takeuchi wrote: > >>> OK, here it is. > >> > >> It looks like the cause is that AMD has removed TBM instructions

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Fri, 28 Apr 2017 15:34:06 +0200, Paolo Bonzini wrote: > > > > On 27/04/2017 02:42, Satoru Takeuchi wrote: > > At Wed, 26 Apr 2017 18:58:27 +0200, > >> On 26/04/2017 13:47, Satoru Takeuchi wrote: > >>> OK, here it is. > >> > >> It looks like the cause is that AMD has removed TBM instructions

Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces

Quoting Eric W. Biederman (ebied...@xmission.com): > > It is pointless and confusing to allow a pid namespace hierarchy and > the user namespace hierarchy to get out of sync. The owner of a child > pid namespace should be the owner of the parent pid namespace or > a descendant of the owner of

Re: [PATCH] userns,pidns: Verify the userns for new pid namespaces

Quoting Eric W. Biederman (ebied...@xmission.com): > > It is pointless and confusing to allow a pid namespace hierarchy and > the user namespace hierarchy to get out of sync. The owner of a child > pid namespace should be the owner of the parent pid namespace or > a descendant of the owner of

Re: [PATCH v2] iov_iter: don't revert iov buffer if csum error

On Sat, Apr 29, 2017 at 05:37:38PM +0800, Ding Tianhong wrote: > Looks good, if so, we don't need the csum_error any more, Acked-by: Al Viro Dave, I could put that through my tree, but I think it would be better off in net.git; either way, it needs to go into mainline

Re: [PATCH v2] iov_iter: don't revert iov buffer if csum error

On Sat, Apr 29, 2017 at 05:37:38PM +0800, Ding Tianhong wrote: > Looks good, if so, we don't need the csum_error any more, Acked-by: Al Viro Dave, I could put that through my tree, but I think it would be better off in net.git; either way, it needs to go into mainline before -final...

[git pull] vfs.git fix (Re: iov_iter_pipe warning.)

On Sat, Apr 29, 2017 at 11:51:40AM -0400, Dave Jones wrote: > > > > Gyah... It's a bloody dumb braino in iov_iter_revert() for > pipe-backed > > > > ones. Sorry, the oneliner below should fix it. > > > > > > 5 hrs in, looking good so far. > > > > Mind your Tested-by on the fix? > >

[git pull] vfs.git fix (Re: iov_iter_pipe warning.)

On Sat, Apr 29, 2017 at 11:51:40AM -0400, Dave Jones wrote: > > > > Gyah... It's a bloody dumb braino in iov_iter_revert() for > pipe-backed > > > > ones. Sorry, the oneliner below should fix it. > > > > > > 5 hrs in, looking good so far. > > > > Mind your Tested-by on the fix? > >

[PATCH v2 resend] Introduce v3 namespaced file capabilities

Root in a non-initial user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any unprivileged user on the host could map his own uid to root in a private namespace, write the xattr, and execute the file with privilege on the host. However

[PATCH v2 resend] Introduce v3 namespaced file capabilities

Root in a non-initial user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any unprivileged user on the host could map his own uid to root in a private namespace, write the xattr, and execute the file with privilege on the host. However

[PATCH] drivers:soc:fsl:qbman:qman.c: unsigned long jiffies value.

unsigned long jiffies value sorry for that. Signed-off-by: Karim Eshapa --- drivers/soc/fsl/qbman/qman.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/soc/fsl/qbman/qman.c b/drivers/soc/fsl/qbman/qman.c index e0df4d1..6e1a44a 100644 ---

[PATCH] drivers:soc:fsl:qbman:qman.c: unsigned long jiffies value.

unsigned long jiffies value sorry for that. Signed-off-by: Karim Eshapa --- drivers/soc/fsl/qbman/qman.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/soc/fsl/qbman/qman.c b/drivers/soc/fsl/qbman/qman.c index e0df4d1..6e1a44a 100644 ---

Re: [PATCH 2/2] iio: adc: Allow setting Shunt Voltage PGA gain and Bus Voltage range

On Mittwoch, 26. April 2017 08:59:47 CEST Jonathan Cameron wrote: > On 26/04/17 07:19, Jonathan Cameron wrote: > > On 17/04/17 23:08, Stefan Bruens wrote: > >> On Freitag, 14. April 2017 17:12:03 CEST Jonathan Cameron wrote: [...] > > > >> 4. Any user of the gain settings had to be made aware of

Re: [PATCH 2/2] iio: adc: Allow setting Shunt Voltage PGA gain and Bus Voltage range

On Mittwoch, 26. April 2017 08:59:47 CEST Jonathan Cameron wrote: > On 26/04/17 07:19, Jonathan Cameron wrote: > > On 17/04/17 23:08, Stefan Bruens wrote: > >> On Freitag, 14. April 2017 17:12:03 CEST Jonathan Cameron wrote: [...] > > > >> 4. Any user of the gain settings had to be made aware of

Re: [PATCH v8 05/10] media: venus: adding core part and helper functions

On Fri 28 Apr 15:02 PDT 2017, Jordan Crouse wrote: > On Fri, Apr 28, 2017 at 12:13:52PM +0300, Stanimir Varbanov wrote: > > +int venus_boot(struct device *parent, struct device *fw_dev) > > +{ > > + const struct firmware *mdt; > > + phys_addr_t mem_phys; > > + ssize_t fw_size; > > +

Re: [PATCH v8 05/10] media: venus: adding core part and helper functions

On Fri 28 Apr 15:02 PDT 2017, Jordan Crouse wrote: > On Fri, Apr 28, 2017 at 12:13:52PM +0300, Stanimir Varbanov wrote: > > +int venus_boot(struct device *parent, struct device *fw_dev) > > +{ > > + const struct firmware *mdt; > > + phys_addr_t mem_phys; > > + ssize_t fw_size; > > +

net/core/rtnetlink.c:1234:1: internal compiler error: output_operand: unrecognized address

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0060e79a1f5231940ef38e6621745c0c808065cb commit: 9af15c38254d81c9991eba89335ca7c537d7f2c3 device: Implement a bus agnostic dev_num_vf routine date: 3 months ago config: cris-artpec_3_defconfig (attached

net/core/rtnetlink.c:1234:1: internal compiler error: output_operand: unrecognized address

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0060e79a1f5231940ef38e6621745c0c808065cb commit: 9af15c38254d81c9991eba89335ca7c537d7f2c3 device: Implement a bus agnostic dev_num_vf routine date: 3 months ago config: cris-artpec_3_defconfig (attached

Re: [RFC 1/3] dt-binding: soc: qcom: Add binding for RFSA

On Fri 28 Apr 10:42 PDT 2017, Rob Herring wrote: > On Sat, Apr 22, 2017 at 10:35:17AM -0700, Bjorn Andersson wrote: > > This adds the binding for describing shared memory buffers for > > implementing the remote filesystem protocol. > > > > Signed-off-by: Bjorn Andersson

Re: [RFC 1/3] dt-binding: soc: qcom: Add binding for RFSA

On Fri 28 Apr 10:42 PDT 2017, Rob Herring wrote: > On Sat, Apr 22, 2017 at 10:35:17AM -0700, Bjorn Andersson wrote: > > This adds the binding for describing shared memory buffers for > > implementing the remote filesystem protocol. > > > > Signed-off-by: Bjorn Andersson > > --- > > > > My

Re: [PATCH v1] LSM: Enable multiple calls to security_add_hooks() for the same LSM

On 4/29/2017 12:02 PM, Mickaël Salaün wrote: > Check if the registering LSM already registered hooks just before. This > enable to split hook declarations into multiple files without > registering multiple time the same LSM name, starting from commit > d69dece5f5b6 ("LSM: Add

Re: [PATCH v1] LSM: Enable multiple calls to security_add_hooks() for the same LSM

On 4/29/2017 12:02 PM, Mickaël Salaün wrote: > Check if the registering LSM already registered hooks just before. This > enable to split hook declarations into multiple files without > registering multiple time the same LSM name, starting from commit > d69dece5f5b6 ("LSM: Add

Re: [patch 0/6] staging: speakup: migrate synths to use TTY-based comms

Hi, Forgot to add intro. Following is what I wanted to say: This patchset migrates all external synths from using raw serial i/o to using tty-based comms. The synths not migrated are internal ones - plugged directly into motherboard, communicating over ISA etc. It's important to note that these

Re: [patch 0/6] staging: speakup: migrate synths to use TTY-based comms

Hi, Forgot to add intro. Following is what I wanted to say: This patchset migrates all external synths from using raw serial i/o to using tty-based comms. The synths not migrated are internal ones - plugged directly into motherboard, communicating over ISA etc. It's important to note that these

[patch 5/6] staging: speakup: add send_xchar, tiocmset and input functionality for tty

This patch adds further TTY-based functionality, specifically implementation of send_xchar and tiocmset methods, and input. send_xchar and tiocmset methods simply delegate to corresponding TTY operations. For input, it implements the receive_buf2 callback in tty_ldisc_ops of speakup's ldisc. If a

[patch 5/6] staging: speakup: add send_xchar, tiocmset and input functionality for tty

This patch adds further TTY-based functionality, specifically implementation of send_xchar and tiocmset methods, and input. send_xchar and tiocmset methods simply delegate to corresponding TTY operations. For input, it implements the receive_buf2 callback in tty_ldisc_ops of speakup's ldisc. If a

[patch 6/6] staging: speakup: migrate apollo, ltlk, audptr, decext, dectlk and spkout

This patch simply uses the changes introduced in previous patches and migrates apollo, ltlk, audptr, decext, spkout and dectlk. Migrations are straightforward function pointer updates. Signed-off by: Okash Khawaja Reviewed-by: Samuel Thibault

[patch 6/6] staging: speakup: migrate apollo, ltlk, audptr, decext, dectlk and spkout

This patch simply uses the changes introduced in previous patches and migrates apollo, ltlk, audptr, decext, spkout and dectlk. Migrations are straightforward function pointer updates. Signed-off by: Okash Khawaja Reviewed-by: Samuel Thibault Index:

[patch 4/6] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio

This changes the above five synths to TTY-based comms. They were chosen as a first pass because their serial comms are straightforward, i.e. they don't use serial input and don't do internal port knocking. Signed-off-by: Okash Khawaja Reviewed-by: Samuel Thibault

[patch 1/6] staging: speakup: make input functionality swappable

This moves functions which take input from external synth, into struct spk_io_ops. The calling code then uses serial implementation of those methods through spk_io_ops. That way we can add a parallel TTY-based implementation and simply replace serial with TTY. That is what the next patch in this

[patch 3/6] staging: speakup: add tty-based comms functions

This adds spk_ttyio.c file. It contains a set of functions which implement those methods in spk_synth struct which relate to sending bytes out using serial comms. Implementations in this file perform the same function but using TTY subsystem instead. Currently synths access serial ports, directly

[patch 2/6] tty: export tty_open_by_driver

This applies on top of the changes already in staging-next branch which allow kernel access to TTY dev. Signe-doff-by: Okash Khawaja Reviewed-by: Samuel Thibault Index: linux-staging/drivers/tty/tty_io.c

[patch 2/6] tty: export tty_open_by_driver

This applies on top of the changes already in staging-next branch which allow kernel access to TTY dev. Signe-doff-by: Okash Khawaja Reviewed-by: Samuel Thibault Index: linux-staging/drivers/tty/tty_io.c === ---

[patch 4/6] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio

This changes the above five synths to TTY-based comms. They were chosen as a first pass because their serial comms are straightforward, i.e. they don't use serial input and don't do internal port knocking. Signed-off-by: Okash Khawaja Reviewed-by: Samuel Thibault Index:

[patch 1/6] staging: speakup: make input functionality swappable

This moves functions which take input from external synth, into struct spk_io_ops. The calling code then uses serial implementation of those methods through spk_io_ops. That way we can add a parallel TTY-based implementation and simply replace serial with TTY. That is what the next patch in this

[patch 3/6] staging: speakup: add tty-based comms functions

This adds spk_ttyio.c file. It contains a set of functions which implement those methods in spk_synth struct which relate to sending bytes out using serial comms. Implementations in this file perform the same function but using TTY subsystem instead. Currently synths access serial ports, directly

[patch 0/6] staging: speakup: migrate synths to use TTY-based comms

[patch 0/6] staging: speakup: migrate synths to use TTY-based comms

[PATCH] drivers:soc:fsl:qbman:qman.c: Sleep instead of stuck hacking jiffies.

Convert the jiffies into usecs then use it with usleep_range such that instead of stuck doing nothing until action happens, sleep with range improves responsiveness and power usage and avoid hacking jiffies. it's used for approximate time. You can check /kernel/time/timer.c. Signed-off-by: Karim

[PATCH] drivers:soc:fsl:qbman:qman.c: Sleep instead of stuck hacking jiffies.

Convert the jiffies into usecs then use it with usleep_range such that instead of stuck doing nothing until action happens, sleep with range improves responsiveness and power usage and avoid hacking jiffies. it's used for approximate time. You can check /kernel/time/timer.c. Signed-off-by: Karim

[PATCH] m501fb: don't return zero on failure path in sm501fb_start()

If fbmem iomemory mapping failed, sm501fb_start() breaks off initialization, deallocates resources, but returns zero. As a result, double deallocation can happen in sm501fb_stop(). Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov

[PATCH] m501fb: don't return zero on failure path in sm501fb_start()

If fbmem iomemory mapping failed, sm501fb_start() breaks off initialization, deallocates resources, but returns zero. As a result, double deallocation can happen in sm501fb_stop(). Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov ---

[PATCH] userns,pidns: Verify the userns for new pid namespaces

It is pointless and confusing to allow a pid namespace hierarchy and the user namespace hierarchy to get out of sync. The owner of a child pid namespace should be the owner of the parent pid namespace or a descendant of the owner of the parent pid namespace. Otherwise it is possible to

[PATCH] userns,pidns: Verify the userns for new pid namespaces

It is pointless and confusing to allow a pid namespace hierarchy and the user namespace hierarchy to get out of sync. The owner of a child pid namespace should be the owner of the parent pid namespace or a descendant of the owner of the parent pid namespace. Otherwise it is possible to

Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy

Kirill Tkhai writes: > On 27.04.2017 19:07, Eric W. Biederman wrote: >> Kirill Tkhai writes: >> >>> On 27.04.2017 18:15, Eric W. Biederman wrote: Kirill Tkhai writes: > On implementing of nested pid namespaces

Re: [PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy

Kirill Tkhai writes: > On 27.04.2017 19:07, Eric W. Biederman wrote: >> Kirill Tkhai writes: >> >>> On 27.04.2017 18:15, Eric W. Biederman wrote: Kirill Tkhai writes: > On implementing of nested pid namespaces support in CRIU > (checkpoint-restore in userspace tool) we run

[PATCH V2] staging: atomisp: Add __printf validation and fix fallout

__printf validation adds format and argument validation. Fix the various broken format/argument mismatches. Signed-off-by: Joe Perches --- v2: bah, now without unrelated changes to other staging files... I'm not at all sure all the modifications are appropriate. Some maybe

[PATCH V2] staging: atomisp: Add __printf validation and fix fallout

__printf validation adds format and argument validation. Fix the various broken format/argument mismatches. Signed-off-by: Joe Perches --- v2: bah, now without unrelated changes to other staging files... I'm not at all sure all the modifications are appropriate. Some maybe should use the

[PATCH] staging: atomisp: Add __printf validation and fix fallout

__printf validation adds format and argument validation. Fix the various broken format/argument mismatches. Signed-off-by: Joe Perches --- I'm not at all sure all the modifications are appropriate. Some maybe should use the original format types like %x instead of %p with

[PATCH] staging: atomisp: Add __printf validation and fix fallout

__printf validation adds format and argument validation. Fix the various broken format/argument mismatches. Signed-off-by: Joe Perches --- I'm not at all sure all the modifications are appropriate. Some maybe should use the original format types like %x instead of %p with *pointer instead of

[PATCH v1] LSM: Enable multiple calls to security_add_hooks() for the same LSM

Check if the registering LSM already registered hooks just before. This enable to split hook declarations into multiple files without registering multiple time the same LSM name, starting from commit d69dece5f5b6 ("LSM: Add /sys/kernel/security/lsm"). Signed-off-by: Mickaël Salaün

[PATCH v1] LSM: Enable multiple calls to security_add_hooks() for the same LSM

Check if the registering LSM already registered hooks just before. This enable to split hook declarations into multiple files without registering multiple time the same LSM name, starting from commit d69dece5f5b6 ("LSM: Add /sys/kernel/security/lsm"). Signed-off-by: Mickaël Salaün Cc: Casey

Cash Grant Donation!!

Dear Beloved, You were chosen to receive my Cash Grant Donation of £2,000,000 GBP. Do contact me for details. Regards, Mrs. Anita Eric Rubenstein

Cash Grant Donation!!

Dear Beloved, You were chosen to receive my Cash Grant Donation of £2,000,000 GBP. Do contact me for details. Regards, Mrs. Anita Eric Rubenstein

Re: [PATCH v2] Introduce v3 namespaced file capabilities

"Serge E. Hallyn" writes: [snip] > A patch to linux-test-project adding a new set of tests for this > functionality is in the nsfscaps branch at github.com/hallyn/ltp > > Changelog: >Nov 02 2016: fix invalid check at refuse_fcap_overwrite() >Nov 07 2016: convert rootid

Re: [PATCH v2] Introduce v3 namespaced file capabilities

"Serge E. Hallyn" writes: [snip] > A patch to linux-test-project adding a new set of tests for this > functionality is in the nsfscaps branch at github.com/hallyn/ltp > > Changelog: >Nov 02 2016: fix invalid check at refuse_fcap_overwrite() >Nov 07 2016: convert rootid from and to fs

Re: [patch] timer: Fix timers_update_migration(), and call it in tmigr_init()

On Sat, 2017-04-29 at 11:06 -0700, Paul E. McKenney wrote: > If someone will either repost a fresh series or point me at exactly > the set of patches to use, I will run it through rcutorture again. Patchlet is against x86-tip/master.today. -Mike

Re: [patch] timer: Fix timers_update_migration(), and call it in tmigr_init()

On Sat, 2017-04-29 at 11:06 -0700, Paul E. McKenney wrote: > If someone will either repost a fresh series or point me at exactly > the set of patches to use, I will run it through rcutorture again. Patchlet is against x86-tip/master.today. -Mike

Re: [PATCH v5] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver

Hi, On Sat, Apr 29, 2017 at 06:40:53PM +0900, Tomohiro Yoshidomi wrote: > PSX pads can be connected directly to the SPI bus. > > Signed-off-by: Tomohiro Yoshidomi Thank you very much for making requested changes and your patience. I think we just need a few finishing

Re: [PATCH v5] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver

Hi, On Sat, Apr 29, 2017 at 06:40:53PM +0900, Tomohiro Yoshidomi wrote: > PSX pads can be connected directly to the SPI bus. > > Signed-off-by: Tomohiro Yoshidomi Thank you very much for making requested changes and your patience. I think we just need a few finishing touches and we can commit

Re: [PATCH v3] ia64: fix module loading for gcc-5.4

On Sat, 8 Apr 2017 20:53:18 +0100 Sergei Trofimovich wrote: > Starting from gcc-5.4+ gcc generates MLX > instructions in more cases to refer local > symbols: > https://gcc.gnu.org/PR60465 > > That caused ia64 module loader to choke > on such instructions: > fuse:

Re: [PATCH v3] ia64: fix module loading for gcc-5.4

On Sat, 8 Apr 2017 20:53:18 +0100 Sergei Trofimovich wrote: > Starting from gcc-5.4+ gcc generates MLX > instructions in more cases to refer local > symbols: > https://gcc.gnu.org/PR60465 > > That caused ia64 module loader to choke > on such instructions: > fuse: invalid slot number 1

Re: [PATCH 3/3] staging: rtl8192u: Convert u4bAcParam back to little-endian after construction

Hi Tuomo, [auto build test WARNING on staging/staging-testing] [also build test WARNING on next-20170428] [cannot apply to v4.11-rc8] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 3/3] staging: rtl8192u: Convert u4bAcParam back to little-endian after construction

Hi Tuomo, [auto build test WARNING on staging/staging-testing] [also build test WARNING on next-20170428] [cannot apply to v4.11-rc8] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [patch] timer: Fix timers_update_migration(), and call it in tmigr_init()

On Sat, Apr 29, 2017 at 06:06:40PM +0200, Mike Galbraith wrote: > Note: there is more. With this applied, my desktop box will no longer > reproduce when booted to init 3 with nowatchdog on the command line. > My 8 socket DL980 OTOH still will, though it takes longer, and is > seemingly no

Re: [patch] timer: Fix timers_update_migration(), and call it in tmigr_init()

On Sat, Apr 29, 2017 at 06:06:40PM +0200, Mike Galbraith wrote: > Note: there is more. With this applied, my desktop box will no longer > reproduce when booted to init 3 with nowatchdog on the command line. > My 8 socket DL980 OTOH still will, though it takes longer, and is > seemingly no

Re: [PATCH] crypto: stm32 - fix building as a module

On Thu, Apr 27, 2017 at 01:07:07PM +0200, Arnd Bergmann wrote: > The names in the MODULE_DEVICE_TABLE and the actual array don't match: > > drivers/crypto/stm32/stm32_crc32.c:309:21: error: 'sti_dt_ids' undeclared > here (not in a function); did you mean 'stm32_dt_ids'? > > This changes the

[PATCH] staging/ks7010: Fix type assignment for struct hostif_hdr

Sparse spits out a warnings about __le16 and unsigned short assignment. Change the type of size and event members of struct hostif_hdr to __le16 and correct conversion to the proper cpu type. Signed-off-by: Cezary Gapinski --- drivers/staging/ks7010/ks7010_sdio.c | 10

Re: [PATCH] crypto: stm32 - fix building as a module

On Thu, Apr 27, 2017 at 01:07:07PM +0200, Arnd Bergmann wrote: > The names in the MODULE_DEVICE_TABLE and the actual array don't match: > > drivers/crypto/stm32/stm32_crc32.c:309:21: error: 'sti_dt_ids' undeclared > here (not in a function); did you mean 'stm32_dt_ids'? > > This changes the

[PATCH] staging/ks7010: Fix type assignment for struct hostif_hdr

Sparse spits out a warnings about __le16 and unsigned short assignment. Change the type of size and event members of struct hostif_hdr to __le16 and correct conversion to the proper cpu type. Signed-off-by: Cezary Gapinski --- drivers/staging/ks7010/ks7010_sdio.c | 10 ++

Re: [PATCH 1/1] staging: comedi: use __func__ instead of hardcoded function name

On Sat, 2017-04-29 at 22:17 +0530, Dhiru Kholia wrote: > This coding style issue was found by checkpatch.pl script. Using > __func__ instead of hardcoded function name should help in future > refactoring of this code. > > Signed-off-by: Dhiru Kholia > --- >

Re: [PATCH 1/1] staging: comedi: use __func__ instead of hardcoded function name

On Sat, 2017-04-29 at 22:17 +0530, Dhiru Kholia wrote: > This coding style issue was found by checkpatch.pl script. Using > __func__ instead of hardcoded function name should help in future > refactoring of this code. > > Signed-off-by: Dhiru Kholia > --- >

Re: [PATCH] staging: fsl-mc/dpio: add cpu <--> LE conversion for dpaa2_fd

On 4/29/2017 7:32 PM, Stuart Yoder wrote: > On Fri, Apr 28, 2017 at 9:38 AM, Horia Geantă wrote: >> >> While dpaa2_fd.simple structure fields are marked __leXX, >> corresponding cpu_to_leXX / leXX_to_cpu conversions are missing. >> >> While here, fix dpaa2_fd_{get,set}_bpid

Re: [PATCH] staging: fsl-mc/dpio: add cpu <--> LE conversion for dpaa2_fd

On 4/29/2017 7:32 PM, Stuart Yoder wrote: > On Fri, Apr 28, 2017 at 9:38 AM, Horia Geantă wrote: >> >> While dpaa2_fd.simple structure fields are marked __leXX, >> corresponding cpu_to_leXX / leXX_to_cpu conversions are missing. >> >> While here, fix dpaa2_fd_{get,set}_bpid such that BMT, IVP

[PATCH] checkpatch: Improve the embedded function name test for patch contexts

The current test works only for a single patch context as it is done in the foreach ($rawlines) loop that precedes the loop where the actual $context_function variable is used. ' Move the set of $context_function into the foreach (@lines) loop where it is useful for each patch context.

[PATCH] checkpatch: Improve the embedded function name test for patch contexts

The current test works only for a single patch context as it is done in the foreach ($rawlines) loop that precedes the loop where the actual $context_function variable is used. ' Move the set of $context_function into the foreach (@lines) loop where it is useful for each patch context.

[PATCH 1/1] staging: comedi: use __func__ instead of hardcoded function name

This coding style issue was found by checkpatch.pl script. Using __func__ instead of hardcoded function name should help in future refactoring of this code. Signed-off-by: Dhiru Kholia --- drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +- 1 file changed, 1

[PATCH 1/1] staging: comedi: use __func__ instead of hardcoded function name

This coding style issue was found by checkpatch.pl script. Using __func__ instead of hardcoded function name should help in future refactoring of this code. Signed-off-by: Dhiru Kholia --- drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH] w1: w1-gpio: Fix double-free of platform_data

Hi Alexey 25.03.2017, 20:08, "Alexey Ignatov" : > struct w1_gpio_platform_data was allocated using devres when using > device tree. Then it was assigned to dev.platform_data, which leaded > to double free on device removal by devres and by direct > kfree(platform_data) in

Re: [PATCH] w1: w1-gpio: Fix double-free of platform_data

Hi Alexey 25.03.2017, 20:08, "Alexey Ignatov" : > struct w1_gpio_platform_data was allocated using devres when using > device tree. Then it was assigned to dev.platform_data, which leaded > to double free on device removal by devres and by direct > kfree(platform_data) in platform_device_release)

Re: [PATCH 2/2] Add driver for MAX17211/MAX17215 fuel gauge

Hi, Please make sure you Cc the relevant people / mailing lists. You can use ./scripts/get_maintainer.pl to find out who should receive the patches. On Sat, Apr 29, 2017 at 05:34:29PM +0300, Alex A. Mihaylov wrote: > Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge > monitor

Re: [PATCH 2/2] Add driver for MAX17211/MAX17215 fuel gauge

Hi, Please make sure you Cc the relevant people / mailing lists. You can use ./scripts/get_maintainer.pl to find out who should receive the patches. On Sat, Apr 29, 2017 at 05:34:29PM +0300, Alex A. Mihaylov wrote: > Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge > monitor

Re: [PATCH] staging: fsl-mc/dpio: add cpu <--> LE conversion for dpaa2_fd

On Fri, Apr 28, 2017 at 9:38 AM, Horia Geantă wrote: > > While dpaa2_fd.simple structure fields are marked __leXX, > corresponding cpu_to_leXX / leXX_to_cpu conversions are missing. > > While here, fix dpaa2_fd_{get,set}_bpid such that BMT, IVP bits > sharing the 16-bit

Re: [PATCH] staging: fsl-mc/dpio: add cpu <--> LE conversion for dpaa2_fd

On Fri, Apr 28, 2017 at 9:38 AM, Horia Geantă wrote: > > While dpaa2_fd.simple structure fields are marked __leXX, > corresponding cpu_to_leXX / leXX_to_cpu conversions are missing. > > While here, fix dpaa2_fd_{get,set}_bpid such that BMT, IVP bits > sharing the 16-bit field with BPID are not

[patch] timer: Fix timers_update_migration(), and call it in tmigr_init()

Note: there is more. With this applied, my desktop box will no longer reproduce when booted to init 3 with nowatchdog on the command line. My 8 socket DL980 OTOH still will, though it takes longer, and is seemingly no longer interested in following up with a permanent RCU stall after the tsc

[patch] timer: Fix timers_update_migration(), and call it in tmigr_init()

Note: there is more. With this applied, my desktop box will no longer reproduce when booted to init 3 with nowatchdog on the command line. My 8 socket DL980 OTOH still will, though it takes longer, and is seemingly no longer interested in following up with a permanent RCU stall after the tsc

Re: [PATCH 1/2] Add support for OneWire (W1) devices family 0x26 (MAX17211/MAX17215)

Hi, On Sat, Apr 29, 2017 at 05:34:28PM +0300, Alex A. Mihaylov wrote: > Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge > monitor with M5 Fuel Gauge algorithm > > Slave device provide software layer for access to internal registers > MAX17211/MAX17215 chip. Please convert

Re: [PATCH 1/2] Add support for OneWire (W1) devices family 0x26 (MAX17211/MAX17215)

Hi, On Sat, Apr 29, 2017 at 05:34:28PM +0300, Alex A. Mihaylov wrote: > Maxim Semiconductor MAX17211/MAX17215 single/multi-cell fuel gauge > monitor with M5 Fuel Gauge algorithm > > Slave device provide software layer for access to internal registers > MAX17211/MAX17215 chip. Please convert

Re: iov_iter_pipe warning.

On Sat, Apr 29, 2017 at 03:47:36AM +0100, Al Viro wrote: > On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote: > > On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote: > > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400,

Re: iov_iter_pipe warning.

On Sat, Apr 29, 2017 at 03:47:36AM +0100, Al Viro wrote: > On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote: > > On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote: > > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400,

<    1   2   3   4   >