Okay, just got a response from the guy at Creative. He said they'll
try to sort it out this week. Just a heads up. :)
On Wed, Oct 24, 2018 at 12:22 PM Connor McAdams wrote:
>
> Understood. I will see what I can do. I already had them contact
> Takashi, but I will ask if they're willing to give a s
Hi Nishad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.19 next-20181102]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/
On Sat, 3 Nov 2018 at 00:06, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.1 release.
> There are 24 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
Quoting Taniya Das (2018-11-02 20:06:00)
> Hello Stephen,
>
> On 10/18/2018 5:02 AM, Stephen Boyd wrote:
> > Quoting Taniya Das (2018-10-11 04:36:01)
> >> --- a/drivers/cpufreq/Kconfig.arm
> >> +++ b/drivers/cpufreq/Kconfig.arm
> >> @@ -121,6 +121,17 @@ config ARM_QCOM_CPUFREQ_KRYO
> >>
> >>
On Sat, 3 Nov 2018 at 00:08, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.18.17 release.
> There are 150 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.
>
> Res
On Sat, 3 Nov 2018 at 20:34, Greg Kroah-Hartman
wrote:
>
> On Sat, Nov 03, 2018 at 07:31:42AM -0700, Guenter Roeck wrote:
> > On 11/2/18 11:33 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.79 release.
> > > There are 143 patches in this series, all w
Hello Linus,
Here are a few NTB patches for v4.20. Fairly minor changes and bug
fixes. Please consider pulling them.
Thanks,
Jon
---
The following changes since commit 84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d:
Linux 4.19 (2018-10-22 07:37:37 +0100)
are available in the Git repository at:
In push_{rt,dl}_task(), we call pick_next_pushable{_dl}_task() to
pick next_task before the check. If next_task and rq->curr are equal,
which will trigger BUG_ON() in pick_next_pushable{_dl}_task(). See
the following code in pick_next_pushable{_dl}_task().
static struct task_struct *pick_next_pu
On Sat, Nov 03, 2018 at 04:22:59PM -0700, Paul E. McKenney wrote:
> On Fri, Nov 02, 2018 at 10:12:26PM -0700, Joel Fernandes wrote:
> > On Thu, Nov 01, 2018 at 09:13:07AM -0700, Paul E. McKenney wrote:
> > > On Wed, Oct 31, 2018 at 10:00:19PM -0700, Joel Fernandes wrote:
> > > > On Wed, Oct 31, 201
On Sat, Nov 03, 2018 at 08:04:28PM -0700, Andy Lutomirski wrote:
> Trying to use 9pfs causes QEMU to complain:
commit 2cbfdf4df58330f6cb493500387427dae1c5551d
Author: Marc Zyngier
Date: Fri Nov 2 17:16:51 2018 +
iov_iter: Fix 9p virtio breakage
Quoting Bjorn Andersson (2018-11-02 14:45:32)
> With the introduction of commit 3edfb7bd76bd ("gpiolib: Show correct
> direction from the beginning") the gpiolib will attempt to read the
> direction of all pins, which triggers a read from protected register
> regions.
>
> The pins 0 through 3 and
Trying to use 9pfs causes QEMU to complain:
qemu-system-x86_64: virtio: bogus descriptor or out of resources
This happens because 9p was broken by the iov_iter refactoring because
a ! got lost. Put it back. The offending hunk was:
diff --git a/net/9p/trans_virtio.c b/net/9p/trans_virtio.c
Quoting Yixun Lan (2018-10-25 00:29:15)
> yes, I think the documentation need to be fixed
>
> for the final solution, we decide to make 'mmc-clkc' an independent node
> instead of being a sub-node of 'mmc', so both of them may exist in parallel..
>
> the DT part may like this:
>
>
Quoting Jianxin Pan (2018-11-01 09:30:53)
> diff --git a/drivers/clk/meson/clk-phase-delay.c
> b/drivers/clk/meson/clk-phase-delay.c
> new file mode 100644
> index 000..83e74ed
> --- /dev/null
> +++ b/drivers/clk/meson/clk-phase-delay.c
> @@ -0,0 +1,66 @@
> +// SPDX-License-Identifier: (GPL-2.
WARN_ON() already contains an unlikely(), so it's not necessary to use
unlikely.
Signed-off-by: Yangtao Li
---
kernel/cgroup/cgroup.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
index 6aaf5dd5383b..2e5d90dfcb49 100644
---
On Sat, Nov 3, 2018 at 12:55 AM Arnd Bergmann wrote:
>
> On 11/2/18, Masahiro Yamada wrote:
> > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote:
> >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote:
> >
> > How about clang?
> >
> > For clang, -Og might be equivalent to -O1 at t
Quoting Evan Green (2018-10-26 10:35:40)
> (or)
> @@ -150,3 +153,54 @@ Example:
> ...
> ...
> };
> +
> + phy@88eb000 {
> + compatible = "qcom,sdm845-qmp-usb3-uni-phy";
> + reg = <0x88eb000 0x18c>;
> +
WARN_ON() and WARN_ON_ONCE() already contains an unlikely(), so it's not
necessary to use unlikely.
Signed-off-by: Yangtao Li
---
kernel/time/clockevents.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
index
Quoting Alok Chauhan (2018-10-25 09:40:29)
> Re-arrange existing APIs in probe function to
> avoid using goto and remove redundant variables.
>
> Signed-off-by: Alok Chauhan
> ---
Reviewed-by: Stephen Boyd
On Sat, 3 Nov 2018 13:30:21 -0400
Steven Rostedt wrote:
> On Sun, 4 Nov 2018 01:34:30 +0900
> Masami Hiramatsu wrote:
> >
> > > I was thinking of a bitmask that represents the handlers, and use that
> > > to map which handler gets called for which shadow entry for a
> > > particular task.
> >
WARN_ON() already contains an unlikely(), so it's not necessary to use
unlikely.
Signed-off-by: Yangtao Li
---
kernel/trace/trace_functions_graph.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/kernel/trace/trace_functions_graph.c
b/kernel/trace/trace_functions_graph
Quoting Alok Chauhan (2018-10-25 09:40:28)
> fixed the nitpicks.
Agree with Doug, this commit text needs work.
>
> Signed-off-by: Alok Chauhan
> ---
Code is fine though.
Reviewed-by: Stephen Boyd
On Sat, 3 Nov 2018 13:43:16 -0400
Steven Rostedt wrote:
> On Sun, 4 Nov 2018 01:03:34 +0900
> Masami Hiramatsu wrote:
>
> > Introduce symbol_offset data structure for avoiding symbol+offset
> > parsing when updating arguments.
> >
> > For kprobe events, "@symbol+offset" is supported, that req
On Sat, Nov 3, 2018 at 4:52 PM Ingo Molnar wrote:
>
> A memory (under-)allocation fix and a comment fix.
Pulled,
Linus
Hi Nishad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.19 next-20181102]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/
On Sat, Nov 3, 2018 at 4:09 PM Ingo Molnar wrote:
>
> A number of fixes and some late updates:
Pulled,
Linus
On Sat, Nov 3, 2018 at 4:03 PM Ingo Molnar wrote:
>
> These are almost all tooling updates: 'perf top', 'perf trace' and 'perf
> script' fixes and updates, an UAPI header sync with the merge window
> versions, license marker updates, much improved Sparc support from David
> Miller, and a number of
On Sat, Nov 3, 2018 at 3:59 PM Ingo Molnar wrote:
>
> An irqchip driver fix and a memory (over-)allocation fix.
Pulled,
Linus
Commit-ID: ff1cdc94de4d336be45336d70709dfcf3d682514
Gitweb: https://git.kernel.org/tip/ff1cdc94de4d336be45336d70709dfcf3d682514
Author: Muchun Song
AuthorDate: Fri, 26 Oct 2018 21:17:43 +0800
Committer: Ingo Molnar
CommitDate: Sun, 4 Nov 2018 00:59:24 +0100
sched/core: Introduce set_ne
Commit-ID: 3f130a37c442d5c4d66531b240ebe9abfef426b5
Gitweb: https://git.kernel.org/tip/3f130a37c442d5c4d66531b240ebe9abfef426b5
Author: Valentin Schneider
AuthorDate: Wed, 26 Sep 2018 16:12:07 +0100
Committer: Ingo Molnar
CommitDate: Sun, 4 Nov 2018 00:59:23 +0100
sched/fair: Don't inc
Commit-ID: 47b7aee14fd7e453370a5d15dfb11c958ca360f2
Gitweb: https://git.kernel.org/tip/47b7aee14fd7e453370a5d15dfb11c958ca360f2
Author: Valentin Schneider
AuthorDate: Wed, 26 Sep 2018 16:12:06 +0100
Committer: Ingo Molnar
CommitDate: Sun, 4 Nov 2018 00:59:22 +0100
sched/fair: Clean up
Commit-ID: 40fa3780bac2b654edf23f6b13f4e2dd550aea10
Gitweb: https://git.kernel.org/tip/40fa3780bac2b654edf23f6b13f4e2dd550aea10
Author: Valentin Schneider
AuthorDate: Tue, 23 Oct 2018 14:37:31 +0100
Committer: Ingo Molnar
CommitDate: Sun, 4 Nov 2018 00:57:44 +0100
sched/core: Take the
> Subject: Re: [PATCH v3] genirq/matrix: Choose CPU for managed IRQs based
> on how many of them are allocated
>
> On Sat, 3 Nov 2018, Thomas Gleixner wrote:
> > On Fri, 2 Nov 2018, Long Li wrote:
> > > /**
> > > * irq_matrix_assign_system - Assign system wide entry in the matrix
> > > * @m:
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: 993f0b0510dad98b4e6e39506834dab0d13fd539 sched/topology: Fix off by
one bug
A memory (under-)allocation fix and a comment fix.
T
(1) remove type argument from ramoops_get_next_prz
Since we store the type of the prz when we initialize it, we no longer
need to pass it again in ramoops_get_next_prz since we can just use that
to setup the pstore record. So lets remove it from the argument list.
(2) remove max argument from ram
Here are some simple cleanups and fixes for ramoops in pstore. Let me know
what you think, thanks.
Joel Fernandes (Google) (3):
pstore: map pstore types to names
pstore: simplify ramoops_get_next_prz arguments
pstore: donot treat empty buffers as valid
fs/pstore/inode.c | 53 +---
In later patches we will need to map types to names, so create a table
for that which can also be used and reused in different parts of old and
new code. Also use it to save the type in the PRZ which will be useful
in later patches.
Signed-off-by: Joel Fernandes (Google)
---
fs/pstore/inode.c
pstore currently calls persistent_ram_save_old even if a buffer is
empty. While this appears to work, it is does not seem like the right
thing to do and could lead to future bugs so lets avoid that. It also
prevent misleading prints in the logs which claim the buffer is valid.
I got something like
On Fri, Nov 02, 2018 at 10:12:26PM -0700, Joel Fernandes wrote:
> On Thu, Nov 01, 2018 at 09:13:07AM -0700, Paul E. McKenney wrote:
> > On Wed, Oct 31, 2018 at 10:00:19PM -0700, Joel Fernandes wrote:
> > > On Wed, Oct 31, 2018 at 11:17:48AM -0700, Paul E. McKenney wrote:
> > > > On Tue, Oct 30, 201
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 23a12ddee1ce28065b71f14ccc695b5a0c8a64ff Merge branch 'core/urgent'
into x86/urgent, to pick up objtool fix
A number of fixes and some
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 29995d296e3e9ce4f9767963ecbef143ade26c36 Merge tag
'perf-urgent-for-mingo-4.20-20181031' of
git://git.kernel.org/pub/scm/linux/kerne
Linus,
Please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
# HEAD: 3424243e39e8ec138486926949e3668e7553125d irqchip/irq-mvebu-sei: Fix
a NULL vs IS_ERR() bug in probe function
An irqchip driver fix and
This patch adds the IIO_CHAN_INFO_SCALE mask to ad2s90_chan and
implements the relative read behavior at ad2s90_read_raw.
Signed-off-by: Victor Colombo
Signed-off-by: Matheus Tavares
---
drivers/staging/iio/resolver/ad2s90.c | 30 +++
1 file changed, 21 insertions(+), 9
This patch set adds scale info to ad2s90's single channel, improve
error handling in it's functions and fix a possible race condition
issue.
The goal with this patch set is to address the points discussed in the
mailing list in an effort to move ad2s90.c out of staging.
Changes in v3:
- Removed
This patch removes an initial assignment to the variable ret at probe,
that was always overwritten.
Signed-off-by: Matheus Tavares
---
drivers/staging/iio/resolver/ad2s90.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/resolver/ad2s90.c
b/drivers/stagin
Previously, devm_iio_device_register was being called before the
spi_setup call and the spi_device's max_speed_hz and mode assignments.
This could lead to a race condition since the driver was still being
set up after it was already made ready to use. To fix it, this patch
moves the device registra
This patch adds a channel type check at the beginning of the
ad2s90_read_raw function. Since ad2s90 has only one channel, it just
checks if the given channel is the expected one and if not, return
-EINVAL.
Signed-off-by: Matheus Tavares
---
drivers/staging/iio/resolver/ad2s90.c | 3 +++
1 file c
Previously, ad2s90_probe ignored the return code from spi_setup, not
handling its possible failure. This patch makes ad2s90_probe check if
the code is an error code and, if so, do the following:
- Call dev_err with an appropriate error message.
- Return the spi_setup's error code.
Note: The 'retu
Previously, when spi_read returned an error code inside ad2s90_read_raw,
the code was ignored and IIO_VAL_INT was returned. This patch makes the
function return the error code returned by spi_read when it fails.
Signed-off-by: Matheus Tavares
---
drivers/staging/iio/resolver/ad2s90.c | 7 ---
On Sun, Nov 04, 2018 at 08:06:41AM +1100, NeilBrown wrote:
> On Sat, Nov 03 2018, Paul E. McKenney wrote:
>
> > On Sat, Nov 03, 2018 at 07:36:19PM +1100, NeilBrown wrote:
> >> On Fri, Nov 02 2018, Paul E. McKenney wrote:
> >>
> >> > On Fri, Nov 02, 2018 at 08:50:11AM +1100, NeilBrown wrote:
> >>
On Fri, Nov 2, 2018 at 4:16 PM Arnd Bergmann wrote:
> asus_wmi_evaluate_method() is an empty dummy function when CONFIG_ASUS_WMI
> is disabled, or not reachable from a built-in device driver. This leads to
> a theoretical evaluation of an uninitialized variable that the compiler
> complains about,
Randconfig testing revealed a very old bug, with gcc-8:
sound/soc/intel/atom/sst/sst_loader.c: In function 'sst_load_fw':
sound/soc/intel/atom/sst/sst_loader.c:357:5: error: 'fw' may be used
uninitialized in this function [-Werror=maybe-uninitialized]
if (fw == NULL) {
^
sound/soc/intel/at
On Wed, Oct 31, 2018 at 12:58:03AM +0300, Vasily Averin wrote:
> bh was not released after error in ext4_journal_get_write_access()
>
> Fixes ac27a0ec112a ("ext4: initial copy of files from ext3") # 2.6.19
>
> Signed-off-by: Vasily Averin
Thanks, applied. I fixed up the commit description and
On Sat, Nov 03 2018, Paul E. McKenney wrote:
> On Sat, Nov 03, 2018 at 07:36:19PM +1100, NeilBrown wrote:
>> On Fri, Nov 02 2018, Paul E. McKenney wrote:
>>
>> > On Fri, Nov 02, 2018 at 08:50:11AM +1100, NeilBrown wrote:
>> >> On Thu, Nov 01 2018, Paul E. McKenney wrote:
>> >>
>> >> > On Sat, Oc
On Wed, Oct 31, 2018 at 12:57:55AM +0300, Vasily Averin wrote:
> gdb_bh must be released in case of errors before update of s_group_desc
> but it must not be released after update of group descriptors
> because in this case bh can be used later.
>
> Fixes 01f795f9e0d6 ("ext4: add online resizing s
On Wed, Oct 31, 2018 at 12:57:45AM +0300, Vasily Averin wrote:
> Fixes 33afdcc5402d ("ext4: add a function which sets up group blocks ...") #
> 3.3
>
> Signed-off-by: Vasily Averin
Thanks, applied. I adjusted the patch summary:
ext4: add missing brelse() in set_flexbg_block_bitmap()'s err
On Wed, Oct 31, 2018 at 12:57:37AM +0300, Vasily Averin wrote:
> currently bh is set to NULL only during first iteration of for cycle,
> then this pointer is not cleared after end of using.
> Therefore rollback after errors can lead to extra brelse(bh) call,
> decrements bh counter and later trigge
This reverts commit 80463f1b7bf9f822fd3495139bcf3ef254fdca10, because
it breaks the bindeb-pkg build target in the following way:
...
LD [M] sound/soc/rockchip/snd-soc-rk3399-gru-sound.ko
LD [M] sound/soc/rockchip/snd-soc-rockchip-pcm.ko
LD [M] sound/soc/rockchip/snd-soc-rockchip-
On Sat, 3 Nov 2018, Samuel Holland wrote:
> In d8ae72427187, start was changed to point to the character under the
> cursor, instead of the beginning of the cleared area. The offset was
> correctly applied when clearing the backing buffer, but not when
> updating the framebuffer region. Fix this b
On Tue 2018-09-18 22:54:55, Lubomir Rintel wrote:
> The device-tree booted MMP2 needs to enable the timer clock, otherwise
> the it would stop ticking when the boot finishes.
"the it" -> "it"
> It can also use the clock rate from the clk, the non-DT boards need to
> keep using the hardcoded rates
syzbot has found a reproducer for the following crash on:
HEAD commit:25e9471b6a27 Add linux-next specific files for 20181102
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1549cfe540
kernel config: https://syzkaller.appspot.com/x/.config?x=2a22859d8
On Sat, Nov 3, 2018 at 11:45 AM Olof Johansson wrote:
>
> ARM: SoC fixes
Pulled,
Linus
On Tue 2018-09-18 22:54:54, Lubomir Rintel wrote:
> The timer shall enable its clock.
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> ---
> arch/arm/mach-mmp/mmp2-dt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-mmp/mmp2-dt.c b/arch/arm/
On Tue 2018-09-18 22:54:53, Lubomir Rintel wrote:
> The timer needs the timer clock to be enabled, otherwise it stops
> ticking.
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> ---
> arch/arm/boot/dts/mmp2.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot
On Tue 2018-09-18 22:54:52, Lubomir Rintel wrote:
> The timer needs the timer clock to be enabled, otherwise it stops
> ticking.
>
> Signed-off-by: Lubomir Rintel
> Reviewed-by: Rob Herring
Acked-by: Pavel Machek
> ---
> Changes since v1:
> - Made the clock optional, to keep compatibility wi
On Mon 2018-09-17 14:11:24, Lubomir Rintel wrote:
> It makes no sense to remove the device on shutdown. And it break things
> when the hardware crucial for shutdown (such as the embedded controller)
> is attached to the SPI bus.
Again, are you sure?
On some hardware (sharp zaurus, phones) it is g
On Mon 2018-09-17 14:10:41, Lubomir Rintel wrote:
> This allows use of SPI when power management is disables, such as on
> early boot;
disabled
boot.
> See also: commit 31eb74318054 ("PM / runtime: Fix handling of suppliers
> with disabled runtime PM")
>
> Cc: Mark Brown
> Signed-off-by: Lubomi
On Mon 2018-09-17 13:39:46, Lubomir Rintel wrote:
> Marvell keeps their MMP2 datasheet secret, but there are good clues
> that TWSI2 is not on 0xd4025000 on that platform, not does it use
> IRQ 58. In fact, the IRQ 58 on MMP2 seems to be a signal processor:
>
>arch/arm/mach-mmp/irqs.h:#define
On Mon 2018-09-17 13:39:47, Lubomir Rintel wrote:
> I've gotten the base addresses, clocks and interrupts from an rusty and old
> out-of-tree driver. I haven't actually checked against the datasheet, since
> that one is reserved for the Marvell inner circle.
>
> Tested with an accelerometer on TWS
On Mon 2018-09-17 13:23:03, Lubomir Rintel wrote:
> This will be useful for boards that actually use GPIO pins.
>
> Cc: Eric Miao
> Cc: Haojian Zhuang
> Cc: Rob Herring
> Cc: Mark Rutland
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> arch/arm/boot/dts/mmp2.dtsi | 2 +-
> 1 file
On Mon 2018-09-17 13:17:21, Lubomir Rintel wrote:
> Similarly to PXA3xx pinctrl-single can't set pin direction on MMP2 either.
> See also: commit 9dabfdd84bdfa ("gpio: pxa: disable pinctrl calls for
> PXA3xx")
>
> Cc: Robert Jarzmik
> Cc: Linus Walleij
> Signed-off-by: Lubomir Rintel
Acked-by:
Hi Linus,
The following changes since commit 4b42745211af552f170f38a1b97f4a112b5da6b2:
Merge tag 'armsoc-soc' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2018-10-29 15:37:33
-0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/
The numa_slit variable used by node_distance is available to a
module as long as it is linked at compile-time. However, it is
not available to loadable modules. Leading to errors such as:
ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefined!
The error above is caused by the nvme multip
The existing code triggered an invalid warning about 'rq' possibly being
used uninitialized. Instead of doing the silly warning suppression by
initializa it to NULL, refactor the code to bail out early instead.
Warning was:
kernel/sched/psi.c: In function ‘cgroup_move_task’:
kernel/sched/psi.c:63
Tim,
On Tue, 30 Oct 2018, Tim Chen wrote:
> Change the SMT code paths check from using cpu_smt_control to
> cpu_smt_enabled static key. This saves a branching check.
and adds extra size to the kernel for the patching. The only reason why it
would make sense for kvm is that then the EXPORT of cp
On 11/3/18 8:04 AM, Greg Kroah-Hartman wrote:
On Sat, Nov 03, 2018 at 07:31:42AM -0700, Guenter Roeck wrote:
On 11/2/18 11:33 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.79 release.
There are 143 patches in this series, all will be posted as a respons
merged into cifs-2.6.git for-next
On Sat, Nov 3, 2018 at 11:00 AM Colin King wrote:
>
> From: Colin Ian King
>
> Trivial fix to clean up indentation, replace spaces with tab
>
> Signed-off-by: Colin Ian King
> ---
> fs/cifs/cifsencrypt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Tim,
On Tue, 30 Oct 2018, Tim Chen wrote:
> The cpu_smt_enabled static key serves identical purpose as cpu_smt_enabled
That doesn't make any sense.
> to enable SMT specific code.
>
> This patch replaces sched_smt_present in the scheduler with
> cpu_smt_enabled and deprecate sched_smt_present.
Amazon UK are selling a dual-band WiFi adapter for about 11 GBP (approx
15 USD). It contains a RealTek chip, and it comes with a CD with source
for a linux kernel driver which says it is rtl8821ae .
I have a patch to make this work with a 4.19 kernel (Fedora Rawhide a
few days ago).
I believ
Tim,
On Tue, 30 Oct 2018, Tim Chen wrote:
> Extract the logic to show IBPB, STIBP usages in cpu_show_common()
> into helper functions.
>
> Later patches will add other userspace Spectre v2 mitigation modes.
> This patch makes it easy to show IBPB and STIBP
> usage scenario according to the mitiga
Hi Jerome,
Thanks for the review, we really appreciate your time.
I'm very sorry maybe I don't catch all your meaning very well.
Please see my comments below.
On 2018/10/29 3:16, Jerome Brunet wrote:
> On Thu, 2018-10-25 at 22:58 +0200, Martin Blumenstingl wrote:
>> Hi Jerome,
>>
>> On Thu, Oc
On Sat, Nov 3, 2018 at 3:41 AM Catalin Marinas wrote:
>
> arm64 2nd round of updates for 4.20:
Pulled,
Linus
On Sat, Nov 3, 2018 at 12:58 AM Masahiro Yamada
wrote:
>
> Please pull a little more Kbuild updates.
Pulled,
Linus
In d8ae72427187, start was changed to point to the character under the
cursor, instead of the beginning of the cleared area. The offset was
correctly applied when clearing the backing buffer, but not when
updating the framebuffer region. Fix this by having start point once
again to the beginning of
> -Original Message-
> From: Hunter, Adrian
> Sent: Wednesday, October 31, 2018 11:11 AM
> To: Arnaldo Carvalho de Melo
> Cc: Jiri Olsa ; Andi Kleen ; linux-
> ker...@vger.kernel.org; leo@linaro.org; David Miller
> ; Mathieu Poirier
> Subject: [PATCH 2/5] perf tools: Use fallback for
On Sun, 4 Nov 2018 01:03:34 +0900
Masami Hiramatsu wrote:
> Introduce symbol_offset data structure for avoiding symbol+offset
> parsing when updating arguments.
>
> For kprobe events, "@symbol+offset" is supported, that requires
> to be updated when new module is loaded because @symbol address
On 11/3/18 4:59 AM, Priit Laes wrote:
Signed-off-by: Priit Laes
Where is the commit message? The stuff in the cover letter (Patch 0/N) never
makes it to the git repository. You must have a message in each of the
individual patches.
NACK.
Larry
---
drivers/net/wireless/broadcom/b43/Kco
On Fri, Nov 2, 2018 at 5:06 PM Al Viro wrote:
>
> Regression fix for net/9p handling of iov_iter; broken
> by braino when switching to iov_iter_is_kvec() et.al., spotted
> and fixed by Marc.
Pulled,
Linus
On Sat, Nov 03, 2018 at 07:36:19PM +1100, NeilBrown wrote:
> On Fri, Nov 02 2018, Paul E. McKenney wrote:
>
> > On Fri, Nov 02, 2018 at 08:50:11AM +1100, NeilBrown wrote:
> >> On Thu, Nov 01 2018, Paul E. McKenney wrote:
> >>
> >> > On Sat, Oct 27, 2018 at 02:10:10AM +0100, Josh Triplett wrote:
>
From: Eric Biggers
We need to check the return value of match_token() for Opt_err (-1)
before doing anything with it.
Reported-by: syzbot+a22e0dc07567662c5...@syzkaller.appspotmail.com
Fixes: 00d60fd3b932 ("KEYS: Provide keyctls to drive the new key type ops for
asymmetric keys [ver #2]")
Signe
On Sat, 3 Nov 2018 13:04:04 -0300
Matheus Tavares Bernardino wrote:
> On Sun, Oct 28, 2018 at 1:50 PM Jonathan Cameron wrote:
> >
> > On Fri, 26 Oct 2018 23:00:04 -0300
> > Matheus Tavares wrote:
> >
> > > This patch adds the IIO_CHAN_INFO_SCALE mask to ad2s90_chan and
> > > implements the re
WARN_ON() already contains an unlikely(), so it's not necessary to
use WARN_ON(1).
Signed-off-by: Yangtao Li
---
kernel/sched/deadline.c | 4 +---
kernel/sched/rt.c | 4 +---
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
in
On Sat, 3 Nov 2018 12:59:16 -0300
Renato Lui Geh wrote:
> Hi,
>
> >On Thu, 1 Nov 2018 15:02:32 +
> >"Ardelean, Alexandru" wrote:
> >
> >> Good catch.
>
> That was actually Jonathan's catch. :)
>
> >> Acked-by: Alexandru Ardelean
>
> I read up on Acked-by on the kernel docs, as I d
On Sat, 3 Nov 2018 13:06:19 -0300
Renato Lui Geh wrote:
> On Thu, 1 Nov 2018 15:20:55 +
> "Ardelean, Alexandru" wrote:
> >
> > This looks wrong.
> > I admit this was done in the same way in the probe function, but that looks
> > a bit wrong as well.
> >
> > Typically, the return value of `re
On Fri, 2 Nov 2018 15:42:09 +0800
Song Qiang wrote:
> PNI RM3100 is a high resolution, large signal immunity magnetometer,
> composed of 3 single sensors and a processing chip with a MagI2C
> interface.
>
> Following functions are available:
> - Single-shot measurement from
>/sys/bus/iio/d
On Sat, 3 Nov 2018, Thomas Gleixner wrote:
> On Fri, 2 Nov 2018, Long Li wrote:
> > /**
> > * irq_matrix_assign_system - Assign system wide entry in the matrix
> > * @m: Matrix pointer
> > @@ -269,7 +291,7 @@ int irq_matrix_alloc_managed(struct irq_matrix *m,
> > const struct cpum
On Fri, Nov 2, 2018 at 4:36 PM Dave Chinner wrote:
>
> On Fri, Nov 02, 2018 at 09:35:23AM -0700, Linus Torvalds wrote:
> >
> > I don't love the timing of this at the end of the merge window, but pulled,
>
> When would have been a better time? It's too big for a late -rc, and
> it contains stuff th
Remove @space from tpm_transmit() API` in order to completely remove the
bound between low-level transmission functionality and TPM spaces. The
only real dependency existing is the amount of data saved before trying
to send a command to the TPM.
It doesn't really matter if we save always a bit mor
Prepare and commit TPM space before and after calling tpm_transmit()
instead of doing that inside tpm_transmit(). After this change we can
remove TPM_TRANSMIT_NESTED flag from tpm2_prepare_space() and
tpm2_commit_space() and replace it with TPM_TRANSMIT_UNLOCKED.
Signed-off-by: Jarkko Sakkinen
--
Encapsulate tpm_transmit() call pattern to tpm_dev_transmit() because it
is identically used from two places. Use unlocked version of
tpm_transmit() so that we are able to move the calls to
tpm2_prepare_space() and tpm2_commit_space() later on to this new
function.
Signed-off-by: Jarkko Sakkinen
1 - 100 of 166 matches
Mail list logo
