On Sat, 2016-12-24 at 13:03 +0530, Rahul Krishnan wrote:
> This patch removes unnecessary return statement using spatch tool
[]
> diff --git a/drivers/pci/hotplug/rpadlpar_core.c
> b/drivers/pci/hotplug/rpadlpar_core.c
[]
> @@ -463,8 +463,7 @@ int __init rpadlpar_io_init(void)
> retu
On 2016/12/16 22:43, Lorenzo Pieralisi wrote:
> The acpi_bind_one() error return path can be hit either on physical node
> allocation failure or if the device being configured is already
> associated with an ACPI node and its ACPI companion does not match the
> one acpi_bind_one() is setting it up
Hi Rafael,
Thank you for your comments, when I was demoing your suggestion,
I got a little bit confusions, please see my comments below.
On 2016/12/22 20:57, Rafael J. Wysocki wrote:
> On Thu, Dec 22, 2016 at 6:35 AM, Hanjun Guo wrote:
>> From: Hanjun Guo
>>
>> With the platform msi domain crea
This patch removes unnecessary return statement using spatch tool
Signed-off-by: Rahul Krishnan
---
drivers/pci/hotplug/rpadlpar_core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/pci/hotplug/rpadlpar_core.c
b/drivers/pci/hotplug/rpadlpar_core.c
index dc67f39..
Hi Greg,
2016-12-23 16:20 GMT+09:00 Greg Kroah-Hartman :
> On Fri, Dec 23, 2016 at 12:21:48PM +0900, Masahiro Yamada wrote:
>> Leave the way of zero-out to the compiler's decision; the compiler
>> may know a more optimized way than calling memset().
>
> But no, it doesn't, it will leave "blank" a
Hi Mattew,
On Fri, Dec 23, 2016 at 09:20:03AM -0800, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> This saves 20 bytes on my x86-64 build, mostly due to alignment
> considerations ... I think it actually saves about five bytes of
> instructions. There's really two parts to this commit. Firs
Hi Jiri,
2016-12-23 19:59 GMT+09:00 Jiri Olsa :
> On Fri, Dec 23, 2016 at 01:46:42PM +0900, Masahiro Yamada wrote:
>> The top-level Makefile defines:
>>
>> CPP = $(CC) -E
>
> hum, so that'd work for running from top level, but I guess
> it fails for compiling from other places..? li
On Fri, 23 Dec 2016, Guenter Roeck wrote:
> Hi Julia,
>
> On Fri, Dec 23, 2016 at 04:54:41PM +0100, Julia Lawall wrote:
> [ ... ]
> >
> > // -
> > @ro@
> > declarer name SENSOR_DEVICE_ATTR, SENSOR_DEVICE_ATTR_2;
> > identifi
On Wed, Dec 21, 2016 at 11:18:34PM -0500, Geoff Lansberry wrote:
> From: Jaret Cantu
>
> Repeated polling attempts cause a NULL dereference error to occur.
> This is because the state of the trf7970a is currently reading but
> another request has been made to send a command before it has finished
bna & bfa firmware version 3.2.5.1 was submitted to linux-firmware on
Feb 17 19:10:20 2015 -0500 in 0ab54ff1dc ("linux-firmware: Add QLogic BR
Series Adapter Firmware").
bna was updated to use the newer firmware on Feb 19 16:02:32 2015 -0500 in
3f307c3d70 ("bna: Update the Driver and Firmware Vers
Dear Linux Kernel developers,
The FOSSASIA 2017 Kernel Track would like to welcome all interested
speakers to submit abstracts for presentations. You'll have the
opportunity to share your knowledge and discuss with like-minded
individuals, representing a broad range of industries and
technologies.
Hi Ricardo,
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on next-20161223]
[cannot apply to tip/x86/core v4.9]
[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/linux/commits/Ricardo-Neri
Hi all,
Please do not add any material for v4.11 to your linux-next included
branches until after v4.10-rc1 has been released.
There will be no linux-next releases from me between Dec 25 and Jan 2
inclusive (unless I get really bored with my new toys :-)).
Changes since 20161223:
Non-merge
Hi Joerg,
Ping!
Could you help review this version? Not sure this could catch up to
v4.10 merging.
Thanks
Baoqaun
On 11/25/16 at 01:13pm, Baoquan He wrote:
> This is v7 post.
>
> The principle of the fix is similar to intel iommu. Just defer the assignment
> of device to domain to device drive
Hi Ricardo,
[auto build test WARNING on tip/auto-latest]
[also build test WARNING on next-20161223]
[cannot apply to tip/x86/core v4.9]
[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/linux/commits/Ricardo
On 12/23/2016 12:42 PM, Linus Torvalds wrote:
> On Fri, Dec 23, 2016 at 2:00 AM, Christoph Hellwig wrote:
>>
>> From: Christoph Hellwig
>> Date: Fri, 23 Dec 2016 10:57:06 +0100
>> Subject: virtio_blk: avoid DMA to stack for the sense buffer
>>
>> Most users of BLOCK_PC requests allocate the sense
Hi Ricardo,
[auto build test WARNING on tip/auto-latest]
[also build test WARNING on v4.9 next-20161223]
[cannot apply to tip/x86/core]
[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/linux/commits/Ricardo
On 2016/12/24 9:54, Allen Liu wrote:
> Add ADC driver for the ADC controller found on HiSilicon BVT SOCs, like
> Hi3516CV300, etc.
> The ADC controller is primarily in charge of detecting voltage.
>
> Reviewed-by: Jiancheng Xue
Hi
Sorry. I haven't reviewed this patch. Please remove this line.
On Fri, Dec 23, 2016 at 6:22 PM, Andy Lutomirski wrote:
> There are some pieecs of kernel code that want to compute SHA256
> directly without going through the crypto core. Adjust the exported
> API to decouple it from the crypto core.
>
> I suspect this will very slightly speed up the SHA256 sha
There are some pieecs of kernel code that want to compute SHA256
directly without going through the crypto core. Adjust the exported
API to decouple it from the crypto core.
I suspect this will very slightly speed up the SHA256 shash operations
as well by reducing the amount of indirection involv
BPF digests are intended to be used to avoid reloading programs that
are already loaded. For use cases (CRIU?) where untrusted programs
are involved, intentional hash collisions could cause the wrong BPF
program to execute. Additionally, if BPF digests are ever used
in-kernel to skip verification
This will let other kernel code call into sha256_init(), etc. without
pulling in the core crypto code.
Signed-off-by: Andy Lutomirski
---
crypto/Kconfig | 8
crypto/Makefile | 2 +-
crypto/sha256_generic.c | 4
include/crypto/sha.h| 4
4 files changed, 17
The sha256 helpers can consume a message incrementally, so there's no need
to allocate a buffer to store the whole blob to be hashed.
This may be a slight slowdown for very long messages because gcc can't
inline the sha256_update() calls. For reasonably-sized programs,
however, this should be a c
This makes it easier to add another digest algorithm down the road if
needed. It also serves to force any programs that might have been
written against a kernel that had the old field name to notice the
change and make any necessary changes.
This shouldn't violate any stable API policies, as no r
This makes it easier to add another digest algorithm down the road
if needed. It also serves to force any programs that might have
been written against a kernel that had 'prog_digest' to be updated.
This shouldn't violate any stable API policies, as no released
kernel has ever had 'prog_digest'.
Since there are plenty of uses for the new-in-4.10 BPF digest feature
that would be problematic if malicious users could produce collisions,
the BPF digest should be collision-resistant. SHA-1 is no longer
considered collision-resistant, so switch it to SHA-256.
The actual switchover is trivial.
Hi Elaine,
Am Montag, 19. Dezember 2016, 09:56:13 CET schrieb Elaine Zhang:
> The rk3328's pll and clock are similar with rk3036's,
> it different with pll_mode_mask,there are different
> control registers bit,
> so these should be independent and separate from
> the series of rk3328s.
not sure I
On Fri, Dec 23, 2016 at 5:37 PM, Ricardo Neri
wrote:
> If the User-Mode Instruction Prevention CPU feature is available and
> enabled, a general protection fault will be issued if the instructions
> sgdt, sldt, sidt, str or smsw are executed from user-mode context
> (CPL > 0). If the fault was cau
On Fri, Dec 23, 2016 at 5:37 PM, Ricardo Neri
wrote:
> The feature User-Mode Instruction Prevention present in recent Intel
> processor prevents a group of instructions from being executed with
> CPL > 0. Otherwise, a general protection fault is issued.
>
> Rather than relaying this fault to the u
On Fri, Dec 23, 2016 at 5:37 PM, Ricardo Neri
wrote:
> Section 2.2.1.2 of the Intel 64 and IA-32 Architectures Software
> Developer's Manual volume 2A states that when memory addressing is used
> (i.e., mod part of ModR/M is not 3), a SIB byte is used and the index of
> the SIB byte points to the
On Fri, Dec 23, 2016 at 5:37 PM, Ricardo Neri
wrote:
> Section 2.2.1.2 of the Intel 64 and IA-32 Architectures Software
> Developer's Manual volume 2A states that when memory addressing with no
> explicit displacement (i.e, mod part of ModR/M is 0), a SIB byte is used
> and the base of the SIB byt
Add ADC driver for the ADC controller found on HiSilicon BVT SOCs, like
Hi3516CV300, etc.
The ADC controller is primarily in charge of detecting voltage.
Reviewed-by: Jiancheng Xue
Signed-off-by: Allen Liu
---
.../devicetree/bindings/iio/adc/hibvt-lsadc.txt| 26 ++
drivers/iio/adc/Kconfig
Section 2.2.1.2 of the Intel 64 and IA-32 Architectures Software
Developer's Manual volume 2A states that when memory addressing with no
explicit displacement (i.e, mod part of ModR/M is 0), a SIB byte is used
and the base of the SIB byte points to (R/EBP) (i.e., base = 5), an
explicit displacement
Section 2.2.1.2 of the Intel 64 and IA-32 Architectures Software
Developer's Manual volume 2A states that when memory addressing is used
(i.e., mod part of ModR/M is not 3), a SIB byte is used and the index of
the SIB byte points to the R/ESP (i.e.,index = 4), the index should not be
used in the co
The feature User-Mode Instruction Prevention present in recent Intel
processor prevents a group of instructions from being executed with
CPL > 0. Otherwise, a general protection fault is issued.
Rather than relaying this fault to the user space (in the form of a SIGSEGV
signal), the instructions p
User_mode Instruction Prevention (UMIP) is enabled by setting/clearing a
bit in %cr4.
It makes sense to enable UMIP at some point while booting, before user
spaces come up. Like SMAP and SMEP, is not critical to have it enabled
very early during boot. This is because UMIP is relevant only when the
If the User-Mode Instruction Prevention CPU feature is available and
enabled, a general protection fault will be issued if the instructions
sgdt, sldt, sidt, str or smsw are executed from user-mode context
(CPL > 0). If the fault was caused by any of the instructions protected
by UMIP, fixup_umip_e
This is v2 of my first submission done a while ago[1]. I apologize for the
delay.
User-Mode Instruction Prevention (UMIP) is a security feature present in
new Intel Processors. If enabled, it prevents the execution of certain
instructions if the Current Privilege Level (CPL) is greater than 0. If
User-Mode Instruction Prevention is a security feature present in new
Intel processors that, when set, prevents the execution of a subset of
instructions if such instructions are executed in user mode (CPL > 0).
Attempting to execute such instructions causes a general protection
exception.
The sub
Other kernel submodules can benefit from using the utility functions
defined in mpx.c to obtain the addresses and values of operands contained
in the general purpose registers. An instance of this is the emulation code
used for instructions protected by the Intel User-Mode Instruction
Prevention fe
Hi Grygorii,
On 12/08/2016 05:33 PM, Grygorii Strashko wrote:
> From: "Strashko, Grygorii"
>
> The below call chain generates "scheduling while atomic" backtrace and
> causes system crash when Keystone 2 IRQ chip driver is used with RT-kernel:
>
> gic_handle_irq()
> |-__handle_domain_irq()
>
On Sat, 2016-12-24 at 00:00 +0100, Thomas Preisner wrote:
> diff --git a/drivers/net/ethernet/3com/typhoon.c
> b/drivers/net/ethernet/3com/typhoon.c
> index a0cacbe..9a3ab58 100644
> --- a/drivers/net/ethernet/3com/typhoon.c
> +++ b/drivers/net/ethernet/3com/typhoon.c
> @@ -2404,6 +2404,7 @@ typho
Hannes Frederic Sowa wrote:
> On 24.12.2016 00:39, George Spelvin wrote:
>> We just finished discussing why 8 bytes isn't enough. If you only
>> feed back 8 bytes, an attacker who can do 2^64 computation can find it
>> (by guessing and computing forward to verify the guess) and recover the
>> prev
> From: Benjamin Poirier [mailto:benjamin.poir...@gmail.com] On Behalf Of
> Benjamin Poirier
> Sent: Friday, December 23, 2016 2:01 PM
>
> bna & bfa firmware version 3.2.5.1 was submitted to linux-firmware on Tue
> Feb 17 19:10:20 2015 -0500 in 0ab54ff1dc ("linux-firmware: Add QLogic BR
> Series A
Hi,
On 24.12.2016 00:39, George Spelvin wrote:
> Hannes Frederic Sowa wrote:
>> In general this looks good, but bitbuffer needs to be protected from
>> concurrent access, thus needing at least some atomic instruction and
>> disabling of interrupts for the locking if done outside of
>> get_random_l
On 12/23/2016 11:05 AM, Suman Anna wrote:
> Hi Sarang,
>
>>>
>>> On 12/15/2016 06:03 PM, Sarangdhar Joshi wrote:
The function wkup_m3_rproc_boot_thread waits for asynchronous
firmware loading to complete successfully before calling
rproc_boot(). The same can be achieved by just sett
Hannes Frederic Sowa wrote:
> In general this looks good, but bitbuffer needs to be protected from
> concurrent access, thus needing at least some atomic instruction and
> disabling of interrupts for the locking if done outside of
> get_random_long. Thus I liked your previous approach more where yo
From: Rafael J. Wysocki
If intel_pstate works in the passive mode in which it acts as
a regular cpufreq driver and collaborates with generic cpufreq
governors, the PID parameters are not used, so do not expose
them via debugfs in that case.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/
Hi Julia,
On Fri, Dec 23, 2016 at 04:54:41PM +0100, Julia Lawall wrote:
[ ... ]
>
> // -
> @ro@
> declarer name SENSOR_DEVICE_ATTR, SENSOR_DEVICE_ATTR_2;
> identifier x,show;
> @@
>
> \(SENSOR_DEVICE_ATTR\|SENSOR_DEVICE_ATTR
In a few cases the err-variable is not set to a negative error code if a
function call fails and thus 0 is returned instead.
It may be better to set err to the proper negative error code before
returning.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188841
Reported-by: Pan Bian
Signed-o
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: c280f7736ab26a601932b1ce017a3840dbedcfdc Revert "x86/unwind: Detect
bad stack return address"
There's a number of fixes:
- a round o
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
# HEAD: c9435f35ae64ee162555a82b6a3586b160093957 clocksource/drivers/moxart:
Plug memory and mapping leaks
ARM/MOXA SoC clocksource driv
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: 3705b97505bcbf6440f38119c0e7d6058f585b54 Merge tag
'perf-urgent-for-mingo-20161222' of
git://git.kernel.org/pub/scm/linux/kernel/git
On Wed, Dec 07, 2016 at 05:07:15PM -0800, Linus Torvalds wrote:
> On Wed, Dec 7, 2016 at 4:04 PM, Al Viro wrote:
> >
> > Could you run this just before cutting 4.10-rc1?
>
> Sure. I hope you'll remind me just in case, though.
Doing so... Conversion in question is done by
PATT='^[[:blank:]]*#[
On Fri, 23 Dec 2016, Michal Hocko wrote:
> > We have no way to compact memory for users who are not using
> > MADV_HUGEPAGE,
>
> yes we have. it is defrag=always. If you do not want direct compaction
> and the resulting allocation stalls then you have to rely on kcompactd
> which is something we
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: f357563f958df06cd9ea9e614cdba30578bb08b1 irqchip/st: Mark
st_irq_syscfg_resume() __maybe_unused
A build warning fix with certain .conf
On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote:
>
> Nils, even though this is still highly experimental, could you give it a
> try please?
Yes, no problem! So I kept the very first patch you sent but had to
revert the latest version of the debugging patch (the one in
which you added
During transition to using devm_input_allocate_device()
goto to resource deallocation block was replaced by return
in case of error in iio_device_register().
That is wrong since resources are left undeallocated.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey
Implement operation mode selection using the optional 'mode' devicetree
property (see [1]). The ADC128D818 supports four operation modes differing
in the number and type of input readings (see datasheet, sec. 8.4.1), of
which mode 0 is the default.
We only add handling of the 'mode' property here,
The ADC128D818 offers four different chip operation modes which vary in the
number and measurement types of the available input signals (see datasheet
sec. 8.4.1).
The current version of the driver only supports the default chip operation
mode (mode 0), providing seven analog values and a temperat
Add bindings documentation for the ADC128D818 driver, featuring default I2C
properties along with the optional 'mode' property for chip operation mode
selection (see datasheet, sec. 8.4.1).
Signed-off-by: Alexander Koch
---
.../devicetree/bindings/hwmon/adc128d818.txt | 39
Replace sysfs symbolic file permissions, e.g. 'S_IRUGO', by octal
permissions. This fixes checkpatch.pl warnings.
Signed-off-by: Alexander Koch
---
drivers/hwmon/adc128d818.c | 99 ++
1 file changed, 39 insertions(+), 60 deletions(-)
diff --git a/driv
Add support for operation modes 1-3 of the ADC128D818 (see datasheet sec.
8.4.1). These differ in the number and type of the available input signals,
requiring the driver to selectively hide sysfs nodes according to the
operation mode configured via devicetree.
Signed-off-by: Alexander Koch
---
bna & bfa firmware version 3.2.5.1 was submitted to linux-firmware on Tue
Feb 17 19:10:20 2015 -0500 in 0ab54ff1dc ("linux-firmware: Add QLogic BR
Series Adapter Firmware").
bna was updated to use the newer firmware on Thu, 19 Feb 2015 16:02:32
-0500 in 3f307c3d70 ("bna: Update the Driver and Firm
On Fri, 23 Dec 2016, Peter Zijlstra wrote:
Also, the 'whoops you ran out of RMIDs, please reboot' thing totally and
completely blows.
Well, this is really a hardware limitation. User cannot monitor more events on a
package than # of RMIDs at the *same time*. The 10/14 reuses the RMIDs that
On Fri, Dec 23, 2016 at 7:19 PM, Hannes Frederic Sowa
wrote:
> Factoring out sha3
Per the other thread, you probably don't actually want SHA3, because
it's slow in software. You want SHA2. If you want something faster and
better, then Blake2 is most certainly the way to go. I'll be
submitting som
Matt Fleming writes:
> On Thu, 22 Dec, at 11:23:39AM, Nicolai Stange wrote:
>> So, after memblock is gone, allocations should be done through the "normal"
>> page allocator. Introduce a helper, efi_memmap_alloc() for this. Use
>> it from efi_arch_mem_reserve() and from efi_free_boot_services() as
Hi!
Ok, this should be closer to something working. (But it does not work,
yet).
Pavel
diff --git a/Documentation/devicetree/bindings/media/video-bus-switch.txt
b/Doc
On Thu, Dec 22, 2016 at 07:35:14PM +0100, Sven Schmidt wrote:
> On 12/22/2016 06:29 PM, Greg KH wrote:
> > On Tue, Dec 20, 2016 at 07:53:09PM +0100, Sven Schmidt wrote:
> >>
> >> This patchset is for updating the LZ4 compression module to a version based
> >> on LZ4 v1.7.2 allowing to use the fast
On Fri, Dec 23, 2016 at 11:35:03AM -0800, Shivappa Vikas wrote:
>
> Hello Peterz,
>
> On Fri, 23 Dec 2016, Peter Zijlstra wrote:
>
> >On Fri, Dec 16, 2016 at 03:12:55PM -0800, Vikas Shivappa wrote:
> >>+Continuous monitoring
> >>+-
> >>+A new file cont_monitoring is added to
Hi,
On Fri, 2016-12-23 at 13:26 -0500, George Spelvin wrote:
> (Cc: list trimmed slightly as the topic is wandering a bit.)
>
> Hannes Frederic Sowa wrote:
> > On Thu, 2016-12-22 at 19:07 -0500, George Spelvin wrote:
> > > Adding might_lock() annotations will improve coverage a lot.
> >
> > Migh
On Fri, Dec 23 2016, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> First, the first half of the test: (!nbits || start >= nbits) is
> trivially a subset of the second half, since nbits and start are both
> unsigned.
Yeah, I filed that as a missed optimization bug with gcc a year ago, but
it
On 12/23/2016 11:45 AM, Linus Torvalds wrote:
On Fri, Dec 23, 2016 at 11:40 AM, Guenter Roeck wrote:
FWIW:
Hey, I can generate those myself.
But when they aren't generated by the person who sends the pull
request, they are worthless.
The whole point is that I need to get it with the pull r
Le 23/12/2016 05:54, Zoran Markovic a écrit :
> Add definition of EBI2 clock used by MDM9615 NAND controller.
>
> Cc: Andy Gross
> Cc: David Brown
> Cc: Michael Turquette
> Cc: Stephen Boyd
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Neil Armstrong
> Cc: linux-arm-...@vger.kernel.org
> Cc: l
On Fri, Dec 23, 2016 at 2:00 AM, Christoph Hellwig wrote:
>
> From: Christoph Hellwig
> Date: Fri, 23 Dec 2016 10:57:06 +0100
> Subject: virtio_blk: avoid DMA to stack for the sense buffer
>
> Most users of BLOCK_PC requests allocate the sense buffer on the stack,
> so to avoid DMA to the stack c
Le 23/12/2016 13:52, Heinrich Schuchardt a écrit :
> After reading the fdt u-boot overwrites the reg property of the
> memory node with <0x0 0x0 0x0 0x7800>.
>
> To override this setting we have to use the property
> linux,usable-memory.
>
> If the first 16MB of the 2GB physical memory are us
On Fri, Dec 23, 2016 at 11:40 AM, Guenter Roeck wrote:
>
> FWIW:
Hey, I can generate those myself.
But when they aren't generated by the person who sends the pull
request, they are worthless.
The whole point is that I need to get it with the pull request, so
that I can see that what I get is wh
On Fri, Dec 23, 2016 at 10:22:06AM -0800, Linus Torvalds wrote:
> On Fri, Dec 23, 2016 at 2:07 AM, Wim Van Sebroeck wrote:
> > Hi Linus,
> >
> > Due to time constraints and personal issues Guenter and I decided that this
> > window will be a pull from another location.
> > So please pull from 'wa
Commit-ID: c280f7736ab26a601932b1ce017a3840dbedcfdc
Gitweb: http://git.kernel.org/tip/c280f7736ab26a601932b1ce017a3840dbedcfdc
Author: Josh Poimboeuf
AuthorDate: Thu, 22 Dec 2016 09:02:49 -0600
Committer: Ingo Molnar
CommitDate: Fri, 23 Dec 2016 20:32:30 +0100
Revert "x86/unwind: Detec
On 23-12-2016 1:43, Colin King wrote:
> From: Colin Ian King
>
> Trivial fixes to spelling mistake "Ivalid" to "Invalid" in
> brcmf_err error messages.
Acked-by: Arend van Spriel
> Signed-off-by: Colin Ian King
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 4 ++--
> 1
Hello Peterz,
On Fri, 23 Dec 2016, Peter Zijlstra wrote:
On Fri, Dec 16, 2016 at 03:12:55PM -0800, Vikas Shivappa wrote:
+Continuous monitoring
+-
+A new file cont_monitoring is added to perf_cgroup which helps to enable
+cqm continuous monitoring. Enabling this field woul
Hi Jason,
On 12/23/2016 03:37 PM, Jason Wang wrote:
Since we use EWMA to estimate the size of rx buffer. When rx buffer
size is underestimated, it's usual to have a packet with more than one
buffers. Consider this is not a bug, remove the warning and correct
the comment before XDP linearizing.
Commit-ID: 4fa0d1aa2711a5053fb2422331bdf6bce99b5f87
Gitweb: http://git.kernel.org/tip/4fa0d1aa2711a5053fb2422331bdf6bce99b5f87
Author: Namhyung Kim
AuthorDate: Thu, 22 Dec 2016 15:03:48 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 22 Dec 2016 16:35:46 -0300
perf sched tim
Commit-ID: 9b8087d72086b249ff744cee237ad12cc5e9255d
Gitweb: http://git.kernel.org/tip/9b8087d72086b249ff744cee237ad12cc5e9255d
Author: Namhyung Kim
AuthorDate: Thu, 22 Dec 2016 15:03:48 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 22 Dec 2016 16:35:45 -0300
perf sched tim
Commit-ID: bdd75729e5d279d734e8d3fb41ef4818ac1598ab
Gitweb: http://git.kernel.org/tip/bdd75729e5d279d734e8d3fb41ef4818ac1598ab
Author: Namhyung Kim
AuthorDate: Thu, 22 Dec 2016 15:03:49 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 22 Dec 2016 16:35:46 -0300
perf sched tim
Commit-ID: 0e6758e8231d5905c2e267566e9bd679a68a7b00
Gitweb: http://git.kernel.org/tip/0e6758e8231d5905c2e267566e9bd679a68a7b00
Author: Namhyung Kim
AuthorDate: Thu, 22 Dec 2016 15:03:48 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 22 Dec 2016 16:35:45 -0300
perf sched tim
On 12/23/2016 10:35 AM, Linus Torvalds wrote:
On Thu, Dec 22, 2016 at 10:55 AM, Guenter Roeck wrote:
As mentioned in the tag, this patch series was auto-generated using coccinelle.
I would like to have it applied either now or right after -rc1, at your
preference.
My preference is to not app
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> P.S.: Some of the container test builds now include building samples/bpf/
> with:
>
> $ make O=/tmp/build/linux allmodconfig
> $ make O=/tmp/build/linux headers_install
> $ make O=/tmp/bu
1) We have to be careful to not try and place a checksum after the end
of a rawv6 packet, fix from Dave Jones with help from Hannes Frederic
Sowa.
2) Missing memory barriers in tcp_tasklet_func() lead to crashes, from
Eric Dumazet.
3) Several bug fixes for the new XDP support in virtio_
On 12/19/2016 04:05 PM, Cyrille Pitchen wrote:
> This patch provides an alternative mean to support memory above 16MiB
> (128Mib) by replacing 3byte address op codes by their associated 4byte
> address versions.
>
> Using the dedicated 4byte address op codes doesn't change the internal
> state of
On 12/20/2016 02:54 PM, Geliang Tang wrote:
> Since macros MTDSWAP_ECNT_MIN() and MTDSWAP_ECNT_MAX() have been
> defined in mtdswap.c, use them instead of open-coding.
>
> Signed-off-by: Geliang Tang
Sorry for getting to this so late. The patch is fine, but if you grep
for 'rb_first' in the mtds
Hi all,
Commit 1107d065fdf1 (tpm_tis: Introduce intermediate layer for TPM access)
broke TPM support on ThinkPad X61S (and likely also on other machines which
use TPMs with a static burst count).
It looks like tpm_tis code before this commit had spun on TPM_STS_DATA_AVAIL |
TPM_STS_VALID status b
At the end of function ad7150_write_event_config(), "return 0" seems
improper. It may be better to return the value of ret.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188871
Reported-by: Pan Bian
Signed-off-by: Thomas Preisner
Signed-off-by: Milan Stephan
---
drivers/staging/iio/cd
Hi,
On 23.12.2016 13:42, Pavel Machek wrote:
Hi!
[...]
static int isp_subdev_notifier_bound(struct v4l2_async_notifier *async,
diff --git a/drivers/media/platform/video-bus-switch.c
b/drivers/media/platform/video-bus-switch.c
index 1a5d944..3a2d442 100644
--- a/drivers/media/platform/video-
From: Jason Wang
Date: Fri, 23 Dec 2016 22:37:23 +0800
> Merry Xmas and a Happy New year to all:
>
> This series tries to fixes several issues for virtio-net XDP which
> could be categorized into several parts:
>
> - fix several issues during XDP linearizing
> - allow csumed packet to work for
On Friday, December 23, 2016 5:56 AM, Pankaj Dubey wrote:
>
> From: Niyas Ahmed S T
>
> Currently Exynos PCIe driver is only supported for Exynos5440 SoC.
> This patch does refactoring of Exynos PCIe driver to extend support
> for other Exynos SoC.
>
> Following are the main changes done via th
On Thu, Dec 22, 2016 at 10:55 AM, Guenter Roeck wrote:
>
> As mentioned in the tag, this patch series was auto-generated using
> coccinelle.
> I would like to have it applied either now or right after -rc1, at your
> preference.
My preference is to not apply it at all.
Several of the commit mes
Hi,
On 23-12-16 18:38, Chanwoo Choi wrote:
Hi Hans,
I have two minor comment on below.
But, after fixing it by myself, Applied it on extcon-next branch for v4.11.
Thank you for fixing those up.
Regards,
Hans
2016-12-21 20:20 GMT+09:00 Hans de Goede :
From: David Cohen
Add an extcon d
(Cc: list trimmed slightly as the topic is wandering a bit.)
Hannes Frederic Sowa wrote:
> On Thu, 2016-12-22 at 19:07 -0500, George Spelvin wrote:
>> Adding might_lock() annotations will improve coverage a lot.
>
> Might be hard to find the correct lock we take later down the code
> path, but if
Hello Guys,
I've having some trouble on a new system I'm setting up. I'm getting a kernel
BUG message, seems to be related with the use of Xen (when I boot the system
_without_ Xen, I don't get any crash).
Here is configuration :
- 3x Hard Drives running on RAID 5 Software raid created by mdadm
1 - 100 of 280 matches
Mail list logo
