At 02/16/2017 09:06 PM, Hanjun Guo wrote:
On 2017/2/16 18:38, Dou Liyang wrote:
In ACPI spec, we can declare processors using both Processor and
Device operator. But now, we just handle the mapping of processors
which are declared by Processor operator.
It misses the processors declared by De
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/powerpc/kernel/asm-offsets.c
between commit:
454656155110 ("powerpc/asm: Use OFFSET macro in asm-offsets.c")
from the powerpc tree and commit:
8c8b73c4811f ("sched/cputime, powerpc: Prepare accounting structure for
On 02/16/2017 at 08:22 PM, Borislav Petkov wrote:
> On Thu, Feb 16, 2017 at 07:52:09PM +0800, Xunlei Pang wrote:
>> then mce will be broadcast to the other cpus which are still running
>> in the first kernel(i.e. looping in crash_nmi_callback).
> Simple: the crash code should really mark CP
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/Kconfig.debug
between commit:
ad21fc4faa2a ("arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to
be common")
from the kspp tree and commit:
3ad38ceb2769 ("x86/mm: Remove CONFIG_DEBUG_NX_TEST")
from t
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
include/linux/kref.h
between commit:
56e3d1cd05cc ("kref: prefer atomic_inc_not_zero to atomic_add_unless")
from the drm tree and commit:
10383aea2f44 ("kref: Implement 'struct kref' using refcount_t")
from the tip tre
Use rcuidle console tracepoint because, apparently, it may be issued
from an idle CPU:
[2.581939] hw-breakpoint: Failed to enable monitor mode on CPU 0.
[2.591613] hw-breakpoint: CPU 0 failed to disable vector catch
[2.597686]
[2.597717] ===
[2.59771
On Mon, 13 Feb 2017 14:20:20 -0300
Arnaldo Carvalho de Melo wrote:
> Cc: Adrian Hunter
> Cc: David Ahern
> Cc: Jiri Olsa
> Cc: Namhyung Kim
> Cc: Wang Nan
> Link: http://lkml.kernel.org/n/tip-b5wyjocel55gorl2jq2cb...@git.kernel.org
> Signed-off-by: Arnaldo Carv
James Bottomley writes:
> On Thu, 2017-02-16 at 11:42 -0500, Vivek Goyal wrote:
>> On Thu, Feb 16, 2017 at 07:51:58AM -0800, James Bottomley wrote:
>>
>> [..]
>> > > Two levels of checks will simplify this a bit. Top level inode
>> > > will belong to the user namespace of caller and checks shou
Hi, Hugh,
Hugh Dickins writes:
> On Thu, 16 Feb 2017, Tim Chen wrote:
>>
>> > I do not understand your zest for putting wrappers around every little
>> > thing, making it all harder to follow than it need be. Here's the patch
>> > I've been running with (but you have a leak somewhere, and I do
This helps us compartmentalize all last required opmode work
and declutter the async firmware callback.
Signed-off-by: Luis R. Rodriguez
---
drivers/net/wireless/intel/iwlwifi/iwl-drv.c | 33 +++-
1 file changed, 18 insertions(+), 15 deletions(-)
diff --git a/drivers/net
Although these are iwlwifi patches, there are some core module, async,
firmware questions I'd appreciate a bit more review from folks on -- tx!
Firmware folks / async folks / module folks:
I started to look to generalize the way the iwlwifi driver uses the
firmware API to request for firmware thr
This lets us offload and share all the final opmode related work
necessary for either an opmode driver or new device. This has the most
impact for opmode drivers as this now offloads opmode start for each
device onto the workqueue.
Signed-off-by: Luis R. Rodriguez
---
drivers/net/wireless/intel/
The firmware async callback and the opmode registration share
some functionality -- to start the drv's opmode. Move this work
into a helper which is shared. This should help us share fixes
should these diverging code paths change.
Signed-off-by: Luis R. Rodriguez
---
drivers/net/wireless/intel/i
The return value of request_module() being 0 does not mean that the
driver which was requested has loaded. To properly check that the driver
was loaded each driver can use internal mechanisms to vet the driver is
now present. The helper try_then_request_module() was added to help with
this, allowin
The firmware async callback handles the device's opmode start
call, but optionally also allows opmode registration to take
care of its opmode start. If the firmware callback handles it
its error path in case of opmode start failure has a few pieces
of code missing from the opmode registration. The
On Fri, 17 Feb 2017 10:59:32 +0900
Sergey Senozhatsky wrote:
file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 7180088cbb23..34da86e73d00 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -1563,7 +1563,7
On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote:
> +static const struct dentry_operations shiftfs_dentry_ops = {
> + .d_release = shiftfs_d_release,
> + .d_real = shiftfs_d_real,
> +};
In other words, those dentries are *never* revalidated. Nevermind that
und
Hi, Arnaldo :)
Regarding perf annotate:
1) Problem : wrong line numbers on perf-annotate (both stdio and TUI)
2) Problem : wrong sum of overhead(percent) matching source lines
3) Suggestion : new option showing only source code per function
with overhead info (to be more readable
"Huang, Ying" writes:
> Hi, Hugh,
>
> Hugh Dickins writes:
>
>> On Thu, 16 Feb 2017, Tim Chen wrote:
>>>
>>> > I do not understand your zest for putting wrappers around every little
>>> > thing, making it all harder to follow than it need be. Here's the patch
>>> > I've been running with (but
On Tue, Feb 14, 2017 at 5:00 PM, Cyril Bur wrote:
> diff --git a/drivers/misc/aspeed-lpc-ctrl.c b/drivers/misc/aspeed-lpc-ctrl.c
> new file mode 100644
> index ..9b51548e9d81
> --- /dev/null
> +++ b/drivers/misc/aspeed-lpc-ctrl.c
> +static long aspeed_lpc_ctrl_ioctl(struct file *file,
Hi Linus,
Just two last minute fixes, one for DP MST oopses and one for a radeon
regression.
Dave.
The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc:
Linux 4.10-rc8 (2017-02-12 13:03:20 -0800)
are available in the git repository at:
git://people.freedesktop.org/~
From: Charles
Pegasus series is a RAID support product by using Thunderbolt technology.
The newest product, Pegasus 3(P3) is support Thunderbolt 3 technology with
another chip.
1.Change driver version.
2.Add P3 VID, DID and define it's device address.
3.P3 use msi interrupt, so stex_request_irq
From: Charles
1.Add reboot notifier and register it in stex_probe for all supported device.
2.For all supported device in restart flow, we get a callback from notifier and
set S6flag for stex_shutdown & stex_hba_stop to send restart command to FW.
Signed-off-by: Charles.Chiou
Signed-off-by: Pa
On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote:
> > Hi James,
> >
> > Should it be "return d_splice_alias()" so that if we find an alias it
> > is returned back to caller and passed in dentry can be freed. Though
> > I don't know in what cases alias can be found. And if alias i
On Fri, Feb 10, 2017 at 02:42:00AM +0200, Andy Shevchenko wrote:
> On Fri, Feb 10, 2017 at 2:16 AM, Jonathan Woithe wrote:
> > On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote:
>
> > In summary, I see no issues with this patch series which provides a much
> > needed clean up of th
On Thu, Feb 16, 2017 at 06:57:08PM -0800, Darren Hart wrote:
> On Fri, Feb 10, 2017 at 02:42:00AM +0200, Andy Shevchenko wrote:
> > On Fri, Feb 10, 2017 at 2:16 AM, Jonathan Woithe wrote:
> > > On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote:
> >
> > > In summary, I see no issues
The analog joystick driver spits a warning at us:
drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer
not defined for this architecture.
PPC has get_cycles() so use that.
Signed-off-by: Michael Ellerman
---
drivers/input/joystick/analog.c | 2 +-
1 file changed, 1 insert
On Fri, Feb 17, 2017 at 5:16 AM, Rask Ingemann Lambertsen
wrote:
> In summary: I'll propose a new property "extended-address" or so to the
> existing "x-powers,axp806" compatible, because the axp808 does seem to have
> the register at 0xff after all, it just needs a value of 0 instead of the 16
>
In sun4i_layers_init we are allocating an array of pointers to struct
sun4i_layer:
layers = devm_kcalloc(drm->dev, ARRAY_SIZE(sun4i_backend_planes),
sizeof(**layers), GFP_KERNEL);
The element size should be the size of an individual element of the
array. Chan
drm_mode_config_cleanup is the complement of drm_mode_config_init, which
is called in the bind function of sun4i_drv. drm_mode_config_cleanup
should be put in the unbind function to match.
Signed-off-by: Chen-Yu Tsai
---
drivers/gpu/drm/sun4i/sun4i_drv.c | 1 +
drivers/gpu/drm/sun4i/sun4
Hi Maxime,
This is the first bunch of fixes for the sun4i drm driver. This is part
of the cleanup I am doing towards making the driver support multiple
display pipelines.
Patch 1 moves the drm_mode_config_cleanup call from sun4i_framebuffer_free
to be called directly in sun4i_drv_unbind. This is
drm_vblank_init can fail due to insufficient memory. Ignoring the error
and proceeding may cause the kernel to dereference an invalid pointer
when vblank is enabled.
Signed-off-by: Chen-Yu Tsai
---
drivers/gpu/drm/sun4i/sun4i_drv.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff
sun4i_crtc_init can fail for a number of reasons. Instead of returning
a NULL pointer when it fails, pass back the encountered error using
ERR_PTR.
Signed-off-by: Chen-Yu Tsai
---
drivers/gpu/drm/sun4i/sun4i_crtc.c | 4 ++--
drivers/gpu/drm/sun4i/sun4i_drv.c | 4 ++--
2 files changed, 4 inserti
sun4i_layers_init allocates an array to store pointers to newly created
layers returned by sun4i_layer_init_one(), but fails to actually store
them. But it actually returns the empty array to unsuspecting users.
Save the pointers in the array, so that they may be used later.
Signed-off-by: Chen-Y
The assignment found in the main loop in sun4i_layers_init:
struct sun4i_layer *layer = layers[i];
is useless as it gets overwritten by the next line:
layer = sun4i_layer_init_one(drm, plane);
Drop the assignment.
Signed-off-by: Chen-Yu Tsai
---
drivers/gpu/drm/sun4i/sun4i_la
The master bind function calls numerous drm functions which initialize
underlying structures. It also tries to bind the various components
of the display pipeline, some of which may add additional drm objects.
This patch adds proper cleanup functions in the error path of the
master bind function.
Hi Frederic,
[auto build test ERROR on tip/timers/core]
[cannot apply to v4.10-rc8 next-20170216]
[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/Frederic-Weisbecker/nohz-Fix-possible-missing
The 6390 family of Marvell chips uses 5 bits to describe the ToPort and
FromPort values of PortVec in the ATU Move operation, while older
switches use 0xf.
Add an atu_move_port_mask member in the info structure to describe that.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/chip.c
Because there are several variant of the VTU operations and because
checking for the presence of an STU is not enough, add new ops to the
info structure to describe the VTU operations that a chip supports.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/chip.c | 54 +
This series adds support to 88E6390 for the ATU (MAC address databases)
and VTU (VLAN databases), as well as providing a cleaner API for both.
The 6390 family of Marvell switch chip handles the ATU Move operation
differently and has a different usage of the VTU Data registers.
Vivien Didelot (6):
In order to manage server systems, there is typically another processor
known as a BMC (Baseboard Management Controller) which is responsible
for powering the server and other various elements, sometimes fans,
often the system flash.
The Aspeed BMC family which is what is used on OpenPOWER machine
Move the Global (1) ATU related code in its own file, and export the
necessary primitives.
Use that opportunity to provide a cleaner API for the ATU, by renaming a
few underscore prefixed functions, and members of the
mv88e6xxx_atu_entry structures.
Signed-off-by: Vivien Didelot
---
drivers/net
Move the Global (1) VTU related code to its own file.
Use this opportunity to provide a cleaner API for the VTU, by renaming a
few underscore prefixed functions, split the data member of the
mv88e6xxx_vtu_entry structure into membership (for 802.1q) and port
state (for 802.1s) members, and add a m
Add a mv88e6xxx_port_mask() helper to get the bitmask of ports in a
switch chip, that will be used in several features.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/mv88e6xxx.h | 5 +
drivers/net/dsa/mv88e6xxx/port.c | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
The 6390 family of chips use only 2 of the 3 VTU Data registers to pack
the MemberTag and PortState VLAN data. This means that they must be
written or read before or after each VTU/STU operations.
Implement this variant to add support for VTU with such chips.
Signed-off-by: Vivien Didelot
---
d
We already have counters for sent/recv packets and sent/recv bytes.
Doing a batched update to reduce the number of
u64_stats_update_begin/end().
Take care not to bother with stats update when called
speculatively.
Cc: Willem de Bruijn
Signed-off-by: Jason Wang
Signed-off-by: Michael S. Tsirkin
On Tue, Feb 14, 2017 at 07:46:12PM +0530, Ritesh Raj Sarraf wrote:
> Lenovo Yoga (many variants: Yoga, Yoga2 Pro, Yoga2 13, Yoga3 Pro, Yoga 3
> 14 etc) has multiple modles that are a hybrid laptop, working in laptop
> mode as well as tablet mode.
>
> Currently, there is no easy interface to determ
On Mon, Feb 13, 2017 at 07:37:00PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/platform/x86/Kconfig:config INTEL_TURBO_MAX_3
> drivers/platform/x86/Kconfig: bool "Intel Turbo Boost Max Technology 3.0
> enumeration driver"
>
> ...mea
On Fri, Feb 17, 2017 at 1:58 PM, Cyril Bur wrote:
> In order to manage server systems, there is typically another processor
> known as a BMC (Baseboard Management Controller) which is responsible
> for powering the server and other various elements, sometimes fans,
> often the system flash.
>
> Th
On Fri, Feb 17, 2017 at 10:59:32AM +0900, Sergey Senozhatsky wrote:
> Use rcuidle console tracepoint because, apparently, it may be issued
> from an idle CPU:
>
> [2.581939] hw-breakpoint: Failed to enable monitor mode on CPU 0.
> [2.591613] hw-breakpoint: CPU 0 failed to disable vector ca
On Thu, Jan 19, 2017 at 07:50:29PM -0800, Dan Williams wrote:
> The direct-I/O write path for a pmem device must ensure that data is flushed
> to a power-fail safe zone when the operation is complete. However, other
> dax capable block devices, like brd, do not have this requirement.
> Introduce a
On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote:
> On Thu, Feb 16, 2017 at 06:57:08PM -0800, Darren Hart wrote:
> > On Fri, Feb 10, 2017 at 02:42:00AM +0200, Andy Shevchenko wrote:
> > > On Fri, Feb 10, 2017 at 2:16 AM, Jonathan Woithe
> > > wrote:
> > > > On Wed, Feb 08, 2017 at
On Thu, Feb 16, 2017 at 7:52 PM, Ross Zwisler
wrote:
> On Thu, Jan 19, 2017 at 07:50:29PM -0800, Dan Williams wrote:
>> The direct-I/O write path for a pmem device must ensure that data is flushed
>> to a power-fail safe zone when the operation is complete. However, other
>> dax capable block devi
The comment about ring buffer's organization is outdated and the code sits
elsewhere, remove the comment.
Cc: Steven Rostedt
Signed-off-by: Joel Fernandes
---
kernel/trace/trace.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/kernel/trace/trace.c b/kernel/tra
On Fri, Feb 17, 2017 at 09:25:27AM +0800, Ming Lei wrote:
> Hi Shaohua,
>
> On Fri, Feb 17, 2017 at 6:16 AM, Shaohua Li wrote:
> > On Thu, Feb 16, 2017 at 07:45:30PM +0800, Ming Lei wrote:
> >> In MD's resync I/O path, there are lots of direct access to bio's
> >> bvec table. This patchset kills
On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote:
> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote:
> > Do you want me to continue to use Acked-by, or should I switch to
> > Reviewed-by?
>
> These tags do have different meanings, and have come up at Kernel Summit the
>
On Thu, Feb 16, 2017 at 11:08 AM, wrote:
> On Thu, Feb 16, 2017 at 10:52:19AM -0500, Soheil Hassas Yeganeh wrote:
>> On Thu, Feb 16, 2017 at 10:50 AM, Soheil Hassas Yeganeh
>> wrote:
>> > Thank you Vito for the report.
>> >
>> > The patch you cited actually resolves a similar backward compatibil
Hi Arnd,
On 17/02/17 02:28, Arnd Bergmann wrote:
> On Thursday, February 16, 2017 9:50:39 PM CET Chris Packham wrote:
>> The DFX server on the 98dx3236 and compatible SoCs has an ID register
>> that provides revision information that the PCI based ID register
>> doesn't have. Use this if it's avail
Hello Linus,
Here are a few last minute NTB bug fixes for v4.10. They are fairly
critical, and would appreicate them getting pulled in (though I
understand this is extremely late in the cycle).
Thanks,
Jon
The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc:
Linux 4.
On Wed, Feb 15, 2017 at 10:41:40PM +, Ben Hutchings wrote:
> 3.16.40-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Dave Chinner
>
> commit 541d48f05fa1c19a4a968d38df685529e728a20a upstream.
>
> oss.sgi.com is going away, move contact
When booting a VM in libvirt/KVM attached to a local bridge and KASAN
enabled on 4.9.10, we see a stream of KASAN warnings about off-slab
access [1].
Let me know if you'd like more debug.
Thanks,
Daniel
-- [1]
[ 473.579567] BUG: KASAN: slab-out-of-bounds in
ip_route_me_harder+0xbd5/0xf20 at
Hi all,
Today's linux-next merge of the akpm-current tree got conflicts in:
arch/cris/include/asm/Kbuild
arch/m32r/include/asm/Kbuild
arch/parisc/include/asm/Kbuild
arch/score/include/asm/Kbuild
between commit:
b672592f0221 ("sched/cputime: Remove generic asm headers")
from the tip t
Oleg Nesterov writes:
> de_thread() waits for other threads with ->cred_guard_mutex held and this
> is really bad because the time is not bounded, debugger can delay the exit
> and this lock has a lot of users (mostly abusers imo) in fs/proc and more.
> And this leads to deadlock if debugger trie
commit bb98e72adaf9d19719aba35f802d4836f5d5176c
Author: Hans de Goede
Date: Fri Dec 2 15:29:04 2016 +0100
drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from
vlv_init_display_clock_gating
On my Cherrytrail CUBE iwork8 Air tablet PIPE-A would get stuck on loading
i915 at boo
Hi all,
Today's linux-next merge of the akpm-current tree got conflicts in:
arch/x86/Kconfig.debug
arch/x86/kernel/Makefile
between commits:
ad21fc4faa2a ("arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to
be common")
3ad38ceb2769 ("x86/mm: Remove CONFIG_DEBUG_NX_TEST")
fro
On 17-02-15 01:08 AM, Jason Wang wrote:
> We set queues before reset which will cause a crash[1]. This is
> because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
> number to do the correct detection. So fix this by:
>
> - set queues after reset, to keep the old vi->curr_queue_pairs.
On 02/16/17 15:27, Daniel Kiper wrote:
>
> That is obvious. Do you think that Multiboot/Multiboot2 protocols are
> substantially suboptimal?
>
Yes. They push a lot of things into the bootloader for no good reason,
thus tying the kernel's hands and making the whole boot process more
fragile.
It
Nitpick: Are you sure this patch is necessary having #3 on top of it ?
On 16/02/2017 08:08, Peter Huewe wrote:
Abort the transfer with ETIMEDOUT when the TPM signals more than
TPM_RETRY wait states. Continuing with the transfer in this state
will only lead to arbitrary failures in other parts of
v2:
-Split fixes into separate patches
Olav Haugan (2):
staging: speakup: (coding style) Simplify comparisons to NULL
staging: speakup: (coding style) Limit line to 80 chars
drivers/staging/speakup/synth.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
--
Qual
Fix checkpatch check notices by simplifying comparisons to NULL.
Signed-off-by: Olav Haugan
---
drivers/staging/speakup/synth.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c
index a61c02ba06d
That's is correct, this is a mistake on my side and never saw it :-(.
I guess it was possibly leading to "waste" at least 1 wait state on some
TPMs.
Wouldn't it be better to merge that with #1 and update the comment
consequently?
On 16/02/2017 08:08, Peter Huewe wrote:
Wait states are sig
Are you sure it is not better to introduce this delay directly in the
rpi spi driver ?
Other than that i don't see any issue with it.
On 16/02/2017 08:09, Peter Huewe wrote:
Testing the implementation with a Raspberry Pi 2 showed that under some
circumstances its SPI master erroneously releas
On 2017年02月17日 12:53, John Fastabend wrote:
On 17-02-15 01:08 AM, Jason Wang wrote:
We set queues before reset which will cause a crash[1]. This is
because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
number to do the correct detection. So fix this by:
- set queues after reset
Fix checkpatch warning about line being over 80 characters.
Signed-off-by: Olav Haugan
---
drivers/staging/speakup/synth.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c
index b57315110e67..8340748ae9cb 10
I am not sure i understand here, are you considering there could be
burstcount > 64 with "TCG" TPM ?
Or is this because of TIS vs PTP differences ?
To be honest, this is a little behind me now :-)
On 16/02/2017 08:08, Peter Huewe wrote:
Limiting transfers to MAX_SPI_FRAMESIZE was not expecte
On Fri, Feb 17, 2017 at 02:47:56PM +1030, Jonathan Woithe wrote:
> On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote:
> > On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote:
> > > Do you want me to continue to use Acked-by, or should I switch to
> > > Reviewed-by?
> >
> > Th
Hi Frederic,
[auto build test ERROR on tip/timers/core]
[cannot apply to v4.10-rc8 next-20170216]
[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/Frederic-Weisbecker/nohz-Fix-possible-missing
On Fri, 2017-02-17 at 12:36 +0800, Daniel J Blueman wrote:
> When booting a VM in libvirt/KVM attached to a local bridge and KASAN
> enabled on 4.9.10, we see a stream of KASAN warnings about off-slab
> access [1].
>
> Let me know if you'd like more debug.
Could you try the following patch ?
Tha
On 09-02-17, 09:11, Viresh Kumar wrote:
> The first 5 patches update the PM domain and QoS frameworks to support
> that and the last one presents the front end interface to it.
@Kevin and Ulf,
Is there something wrong with this series? Its been 7 weeks since this
series is getting posted and I ha
On 23 January 2017 at 19:57, Felipe Balbi wrote:
>
> Hi,
>
> Alan Stern writes:
>> On Mon, 16 Jan 2017, Felipe Balbi wrote:
>>
>>> > The gadget driver never calls usb_ep_queue in order to receive the next
>>> > SETUP packet; the UDC driver takes care of SETUP handling
>>> > automatically.
>>>
>>>
Hi Johannes,
On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote:
> On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote:
> > @@ -1419,11 +1419,18 @@ static int try_to_unmap_one(struct page *page,
> > struct vm_area_struct *vma,
> > VM_BUG_ON_PAGE(!PageSwapCa
Hi Shaohua,
On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote:
> On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote:
> > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote:
> > > @@ -1419,11 +1419,18 @@ static int try_to_unmap_one(struct page *page,
> > > struct vm_a
Hi all,
Changes since 20170216:
The powerpc tree gained a conflict against Linus' tree.
The tip tree gained conflicts against the drm, kspp, openrisc and
powerpc trees.
The akpm-current tree gained conflicts against the kspp and tip trees.
I dropped 3 patches from the akpm tree that turn
From: Sean Wang
This patch adds documentation for devicetree bindings
for LED support on MT6323 PMIC
Signed-off-by: Sean Wang
---
.../devicetree/bindings/leds/leds-mt6323.txt | 60 ++
1 file changed, 60 insertions(+)
create mode 100644 Documentation/devicetree/bindin
From: Sean Wang
This patch adds documentation for devicetree bindings
for LED support as the subnode of MT6323 PMIC
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/mfd/mt6397.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/mt6397
From: Sean Wang
MT7623 SoC uses MT6323 PMIC as the default power supply
which has LED function insides. The patchset introduces
the LED support for MT6323 with on, off and hardware
dimmed and blinked and it should work on other similar
SoCs if also using MT6323.
Changes since v1:
- fixed typo in
Pan Xinhui writes:
> diff --git a/arch/powerpc/xmon/xmon.c b/arch/powerpc/xmon/xmon.c
> index 9c0e17c..f6e5c3d 100644
> --- a/arch/powerpc/xmon/xmon.c
> +++ b/arch/powerpc/xmon/xmon.c
> @@ -76,6 +76,7 @@ static int xmon_gate;
> #endif /* CONFIG_SMP */
>
> static unsigned long in_xmon __read
From: Sean Wang
MT6323 PMIC is a multi-function device that includes
LED function. It allows attaching up to 4 LEDs which
can either be on, off or dimmed and/or blinked with
the controller.
Signed-off-by: Sean Wang
---
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
dri
From: Sean Wang
Add compatible string as "mt6323-led" that will make
the OF core spawn child devices for the LED subnode
of that MT6323 MFD device.
Signed-off-by: Sean Wang
---
drivers/mfd/mt6397-core.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/mfd/mt6397-core.c b/drivers
Here, dss_init_ports is not handling return error form
dpi_init_port and sdi_init_port. Now dss_init_ports is returning
always 0. And it's making below code as a dead code.
static int dss_bind(struct device *dev)
{
.
.
r = dss_init_ports(pdev); //dss_init_ports will return always 0
if (r)/
On one system during power off slot, find card get power on right away.
# echo 0 > /sys/bus/pci/slots/1/power
pci_hotplug: power_write_file: power = 0
pciehp :16:00.0:pcie004: pciehp_get_power_status: SLOTCTRL a8 value read
11f1
pciehp :16:00.0:pcie004: pciehp_unconfigure_device: domai
On 17/01/2017 11:20, Marc Zyngier wrote:
> Most ITS commands do operate on a collection object, and require
> a SYNC command to be performed on that collection in order to
> guarantee the execution of the first command.
>
> With GICv4 ITS, another set of commands perform similar operations
> on
On 17/01/2017 11:20, Marc Zyngier wrote:
> Allow the pending state of an LPI to be set or cleared via
> irq_set_irqchip_state.
>
> Signed-off-by: Marc Zyngier
Reviewed-by: Eric Auger
Eric
> ---
> drivers/irqchip/irq-gic-v3-its.c | 78
>
> 1 file ch
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> The VCPU tables can be quite sparse as well, and it makes sense
> to use indirect tables as well if possible.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3-its.c | 20 +---
> 1 file changed, 13 insertions(+
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> Move the LPI property table allocation into its own function, as
> this is going to be required for those associated with VMs in
> the future.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3-its.c | 28 ++-
On Fri, 2017-02-17 at 14:28 +1100, Cyril Bur wrote:
> In order to manage server systems, there is typically another
> processor
> known as a BMC (Baseboard Management Controller) which is responsible
> for powering the server and other various elements, sometimes fans,
> often the system flash.
.
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/ia64
Prior to this patch, there was 1 use of pr_warning and
1 use of pr_warn in arch/ia64
Signed-off-by: Joe Perches
---
arch/ia64/kernel/setup.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
dif
To enable eventual removal of pr_warning.
This makes pr_warn use consistent for arch/arm
Prior to this patch, there were 2 uses of pr_warning and
405 uses of pr_warn in arch/arm
Signed-off-by: Joe Perches
---
arch/arm/mach-ep93xx/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
To enable eventual removal of pr_warning
This makes pr_warn use consistent for arch/arm64
Prior to this patch, there were 7 uses of pr_warning and
27 uses of pr_warn in arch/arm64
Signed-off-by: Joe Perches
---
arch/arm64/include/asm/syscall.h | 8
arch/arm64/kernel/hw_breakpoint.c |
To enable eventual removal of pr_warning
This makes pr_warn use consistent for drivers/isdn
Prior to this patch, there were 20 uses of pr_warning and
3 uses of pr_warn in drivers/isdn
Signed-off-by: Joe Perches
---
drivers/isdn/gigaset/interface.c| 2 +-
drivers/isdn/hardware/mISDN/av
701 - 800 of 854 matches
Mail list logo
