Fix the following build error:
CC drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm.o
drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm.c:52:2:
error: excess elements in array initializer [-Werror]
"i", /* ion */
^~~
drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm.c:52:2:
note:
Use kvmalloc() and kvfree() instead of open-coding.
Signed-off-by: Geliang Tang
---
drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c
On Thu, 2017-03-23 at 11:21 +, Lee Jones wrote:
> On Thu, 16 Mar 2017, Andy Shevchenko wrote:
>
> > There is a potential flaw if cell has id > 0 and is going to be
> > registered with PLATFORM_DEVID_NONE.
> >
> > Ignore if PLATFORM_DEVID_NONE is supplied.
>
> This is a substantial change to
Since the vmalloc code has been removed from write_pmsg() in the commit
"5bf6d1b pstore/pmsg: drop bounce buffer", remove the unused header
vmalloc.h.
Signed-off-by: Geliang Tang
---
fs/pstore/pmsg.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/pstore/pmsg.c b/fs/pstore/pmsg.c
index
Use setup_timer() instead of init_timer() to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/isdn/divert/isdn_divert.c | 9 +++--
drivers/isdn/hardware/eicon/divasi.c| 5 ++---
drivers/isdn/hardware/mISDN/hfcmulti.c | 10 --
Use sg_phys() instead of open-coding it.
Signed-off-by: Geliang Tang
---
drivers/iommu/intel-iommu.c | 2 +-
drivers/iommu/iommu.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index d412a31..9d09a9e 100644
Use sg_virt() instead of open-coding it.
Signed-off-by: Geliang Tang
---
drivers/crypto/ixp4xx_crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/ixp4xx_crypto.c b/drivers/crypto/ixp4xx_crypto.c
index 7868765..771dd26 100644
---
Use sg_virt() instead of open-coding it.
Signed-off-by: Geliang Tang
---
drivers/scsi/qla2xxx/qla_isr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c
index 3203367..9610d85 100644
---
Use sg_phys() instead of open-coding it.
Signed-off-by: Geliang Tang
---
arch/microblaze/kernel/dma.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/microblaze/kernel/dma.c b/arch/microblaze/kernel/dma.c
index 12e093a..e45ada8 100644
---
On Tue, Mar 21, 2017 at 12:40:24PM +0530, Pranay Kr. Srivastava wrote:
> speakup_allocate used GFP_ATOMIC for allocations
> even while during initialization due to it's use
> in notifier call.
>
> Pass GFP_ flags as well to speakup_allocate depending
> on the context it is called in.
>
>
On Wed, Mar 22, 2017 at 10:56:02AM -0700, Ankur Arora wrote:
> >It is ok to do upload_pm_data() with delay i.e. after some other
> >resume actions are done and possibly xen-acpi-processor is in
> >running state ?
> The state uploaded is ACPI P and C state from struct acpi_processor
> which AFAICS
On 23.03.2017 13:33, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following report while running syzkaller fuzzer on
> 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected
> kmalloc failure, most likely it's the root cause.
>
>
> FAULT_INJECTION: forcing a failure.
> name
On Tue, Mar 21, 2017 at 05:12:26PM +0530, Arushi Singhal wrote:
> This patch fixes the checkpatch.pl warning "multiple assignments
> should be avoided."
>
> Signed-off-by: Arushi Singhal
> ---
> drivers/staging/speakup/main.c | 18 --
> 1 file changed, 12 insertions(+), 6
On Tue, Mar 21, 2017 at 05:12:29PM +0530, Arushi Singhal wrote:
> This patch fixes the checkpatch.pl warning "multiple assignments
> should be avoided."
>
> Signed-off-by: Arushi Singhal
> ---
> drivers/staging/speakup/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff
On Tue, Mar 21, 2017 at 05:12:33PM +0530, Arushi Singhal wrote:
> Fixed coding style for null comparisons in speakup driver to be more
> consistant with the rest of the kernel coding style.
> Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'.
>
> Signed-off-by: Arushi Singhal
> ---
>
On Tue, Mar 21, 2017 at 05:12:35PM +0530, Arushi Singhal wrote:
> This patch fixes the warnings reported by checkpatch.pl
> for please use a blank line after function/struct/union/enum
> declarations.
That's not what this patch does at all!
Please be more careful.
greg k-h
Assign the correct dev pointer to struct ocotp_priv during probe. This
is needed to display dev_* messages correctly. Furthermore harmonize
the usage of dev (instead of >dev) in the probe function.
Signed-off-by: Richard Leitner
---
drivers/nvmem/imx-ocotp.c | 4 +++-
1 file changed, 3
On Thu, Mar 23, 2017 at 02:20:53PM +0530, Pushkar Jambhlekar wrote:
> Current implementation manually traces function using 'dev_dbg'. This way is
> not needed because of ftrace, making these calls redundant.
Always wrap your changelog lines properly.
Also, someone else sent this same patch in
Hi!
> > Plus I have played with v4l-utils, and managed to implement autofocus
> > and autoexposure -- it was easier than expected. I believe you
> > mentioned you had some patches to automatically initialize the
> > pipeline. Do you and can I have them?
>
> It was an early prototype and it
On 23.03.2017 03:27, Kees Cook wrote:
This is a modified revert of commit 65fe935dd238 ("x86/KASLR, x86/power:
Remove x86 hibernation restrictions"), since it appears that 32-bit
hibernation still can't support KASLR. 64-bit is fine. Since people have
been running with KASLR by default on 32-bit
On Thu, Mar 23, 2017 at 08:38:20AM +0100, Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > On Wed, Mar 22, 2017 at 08:46:16AM +0100, Ingo Molnar wrote:
> > >
> > > * Jiri Slaby wrote:
> > >
> > > > On 03/22/2017, 08:25 AM, Ingo Molnar wrote:
> > > > >
> > > > > * Pavel Machek wrote:
>
Hello,
The following program triggers WARNING in ata_qc_issue:
https://gist.githubusercontent.com/dvyukov/3503afce181b7d48dabb421e10e70b00/raw/d049bd2128a8b1089497beb6104ba48c5550b4a8/gistfile1.txt
[ cut here ]
WARNING: CPU: 3 PID: 2956 at drivers/ata/libata-core.c:5317
DT properties specifying physical properties should contain appropriate
suffices indicating the units of measurement.
Hence amend the HD44780 DT bindings to add "chars" suffixes to the
"display-height" and "display-width" properties, and update the driver
to parse them.
Fixes: dd9502a9e9156dd8
Hi,
This mail is regarding the DT overlay support in the Linux
kernel
I am able to make the device-tree overlay work out of box by
using my own dtc complier (I mean I used the dtc compiler
Available here
On Thu, Mar 23, 2017 at 04:06:59PM +0300, Andrey Ryabinin wrote:
> On 03/23/2017 03:41 PM, Mark Rutland wrote:
> > Rather than trying to pick an arbitrarily large number, how about we use
> > separate flags to determine whether we're in multi-shot mode, and
> > whether a (oneshot) report has been
On Thu, Mar 23, 2017 at 9:49 AM, Dmitry Vyukov wrote:
> On Wed, Mar 22, 2017 at 10:27 PM, Arnd Bergmann wrote:
>> On Wed, Mar 22, 2017 at 12:27 PM, Arnd Bergmann wrote:
>>> On Wed, Mar 22, 2017 at 12:10 PM, Dmitry Vyukov wrote:
Arnd reported that the new code leads to compilation failures
On Thu, Mar 23, 2017 at 03:08:38PM +0800, Zhengyi Shen wrote:
> Fix endian sparse warnings of incorrect type in assignment.
> This patch changes type to the appropriate endian specific versions.
>
>
> Signed-off-by: Zhengyi Shen
> ---
> drivers/staging/fbtft/fbtft-io.c | 2 +-
> 1 file
On Wed, Mar 22, 2017 at 01:33:39PM +1100, Eddie Youseph wrote:
> Fixed checkpatch WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
>
> Signed-off-by: Eddie Youseph
> ---
> Changes in v2:
> - Added changelog
Did you actually build this change?
Please do so...
thanks,
greg k-h
On Thu, Mar 23, 2017 at 09:12:39PM +0800, Geliang Tang wrote:
> Use kvmalloc() and kvfree() instead of open-coding.
These functions are not in Linus's tree, so I can't apply this patch
without breaking things :(
thanks,
greg k-h
On Thu, Mar 23, 2017 at 11:10 AM, Uwe Kleine-König
wrote:
> So you exchanged many obvious and easy to fix problems with a few hard
> ones. I don't agree that's a good idea, but you seem to be willing to
> try it. Good luck.
I think instead of going to sarcastic remarks you can say you NACK the
Fix checkpatch issues: "CHECK: Alignment should match open parenthesis".
Signed-off-by: Arushi Singhal
---
changes in v2
- change the commit message.
drivers/staging/speakup/speakup_apollo.c | 2 +-
drivers/staging/speakup/speakup_decext.c | 4 ++--
2 files changed, 3 insertions(+), 3
On Thu, Mar 23, 2017 at 1:34 PM, Uwe Kleine-König
wrote:
> Maybe we can make gpiod_get_optional look like this:
>
> if (!dev->of_node && isnt_a_acpi_device(dev) && !IS_ENABLED(GPIOLIB))
> return NULL;
> else
> return -ENOSYS;
>
> I don't know how
35.830111] Modules linked in: lzo zram(-) zsmalloc mousedev nls_iso8859_1
nls_cp437 vfat fat psmouse serio_raw atkbd libps2 coretemp hwmon iwlmvm
crc32c_intel i2c_i801 r8169 iwlwifi lpc_ich mii mfd_core ie31200_edac edac_core
thermal i8042 serio wmi evdev acpi_cpufreq sd_mod
[ 2935.830127] CPU:
On Tue, 21 Mar 2017, Julia Cartwright wrote:
> The asic3 mfd driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because the
On Thu, Mar 23, 2017 at 1:22 PM, Colin King wrote:
> From: Colin Ian King
>
> info is being checked to see if it is a null pointer, however, vpgu is
> dereferencing info before this check, leading to a potential null
> pointer dereference. If info is null, then the error message being
> printed
On Thu, Mar 23, 2017 at 12:30:18AM -0700, l...@pengaru.com wrote:
> On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote:
> > On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote:
> > > Hello list,
> > >
> > > After approximately one day day of running 4.11.0-rc3 with
Two different set_mac functions exists but stmmac_dwmac4_set_mac() is
only used for enabling and never for disabling.
So on dwmac4, the MAC RX/TX is never disabled.
This patch add a generic function pointer set_mac() to stmmac_ops and
replace all call to stmmac_set_mac/stmmac_dwmac4_set_mac by a
On Tue, 21 Mar 2017, Julia Cartwright wrote:
> The t7l66xb mfd driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because the
On Tue, 21 Mar 2017, Julia Cartwright wrote:
> The tc6393xb mfd driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because the
Dmitry Vyukov wrote:
> On Thu, Mar 23, 2017 at 2:06 PM, Dmitry Vyukov wrote:
> > Hello,
> >
> > I've got the following report while running syzkaller fuzzer on
> > 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected
> > kmalloc failure in inode_alloc_security, most likely it's
It should be staging: speakup:, not staging:speakup:
On Thu, 23 Mar 2017, Arushi Singhal wrote:
> Fix checkpatch issues: "CHECK: Alignment should match open parenthesis".
It would really be better to say what the patch does, not just say what
error message you have fixed.
julia
>
Hi,
On Wed, Mar 22, 2017 at 01:53:19PM +, Wojciech Ziemba wrote:
> [...]
>
> >> and a number of knobs for controlling the charging process
> > missing sysfs ABI documentation. Most of them are probably either
> > not needed, or should become standard POWER_SUPPLY_PROP_ properties.
>
> Well,
On 23/03/17 14:37, Jan Beulich wrote:
On 23.03.17 at 13:52, wrote:
>> Connecting to the backend isn't working reliably in xen-fbfront: in
>> case XenbusStateInitWait of the backend has been missed the backend
>> transition to XenbusStateConnected will trigger the connected state
>> only
On Wednesday 22 March 2017 11:50 PM, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> This patchset adds Palmchip BK3710 IDE controller driver to
> libata and switches ARM/DaVinci to use it (instead of the old
> IDE driver).
>
> Sekhar, please check that it still works after changes, thanks.
Did some
On Thu, Mar 23, 2017 at 10:40:22AM +0100, Peter Zijlstra wrote:
> On Wed, Mar 22, 2017 at 10:58:04PM -0400, Dave Jones wrote:
> > Not seen this one before..
> >
> > Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>
> That's a write fault reaching no_context() afaict.
>
> > CPU: 1 PID: 24420
>>> On 23.03.17 at 13:52, wrote:
> Connecting to the backend isn't working reliably in xen-fbfront: in
> case XenbusStateInitWait of the backend has been missed the backend
> transition to XenbusStateConnected will trigger the connected state
> only without doing the actions required when the
Hi,
On 17-03-17 19:22, Andy Shevchenko wrote:
On Fri, 2017-03-17 at 10:55 +0100, Hans de Goede wrote:
The Intel Cherry Trail Whiskey Cove PMIC has a builtin SMBUS
controller
for talking to an external PMIC. Add a driver for this.
Looking to all this mess we have with PMICs, perhaps some file
On Thu, 23 Mar 2017 18:21:23 +0900
Byungchul Park wrote:
> On Thu, Mar 23, 2017 at 11:12:49AM +0900, Byungchul Park wrote:
> > It would be better to avoid pushing tasks to other cpu within
> > a SD_PREFER_SIBLING domain, instead, get more chances to check other
> > siblings.
>
> +cc
On Thu, Mar 23, 2017 at 12:01:30PM +, Daniel Stone wrote:
> Hi Michel,
>
> On 23 March 2017 at 08:53, Michel Dänzer wrote:
> > Otherwise this can also prevent modesets e.g. for switching VTs, when
> > multiple monitors with different native resolutions are connected.
> >
> > The depths must
Correct patch for the typo.
Sorry for I sent first patch w/o commit log and second patch with incorrect fix.
Thanks!
Fix the typo "alloted" -> "allotted" in comment.
Signed-off-by: Shile Zhang
---
drivers/char/hangcheck-timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
with: x86_64_defconfig
Patch is against 4.11-rc3 (localversion-next is next-20170323)
kernel/sched/completion.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/kernel/sched/completion.c b/kernel/sched/completion.c
index 53f9558..ef92b15 100644
--- a/kernel/sched/completion.c
On Thu, Mar 23, 2017 at 12:40 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> On Fri, Mar 10, 2017 at 7:34 AM, David Windsor wrote:
>> > v3: rebase against latest Linus tree; re-add include/linux/refcount.h
>> > missing from v2 series
>> >
>> > Signed-off-by: David Windsor
>>
>>
> - if (!cpu_has_vmx_vpid())
> + if (!cpu_has_vmx_vpid() || !cpu_has_vmx_invvpid() ||
> + !(cpu_has_vmx_invvpid_single() || cpu_has_vmx_invvpid_global()))
I still don't like this way of indentation, but looks like I am the only
one complaining :)
So I think this patch is
On Thu, 23 Mar 2017 19:36:51 +0900
Byungchul Park wrote:
> On Thu, Mar 23, 2017 at 10:44:45AM +0100, Peter Zijlstra wrote:
> > On Thu, Mar 23, 2017 at 11:12:49AM +0900, Byungchul Park wrote:
> > > It would be better to avoid pushing tasks to other cpu within
> > > a SD_PREFER_SIBLING domain,
On 2017-03-23 09:06, Sean Wang wrote:
> Hi Andrew,
>
> The purpose for the regmap table registered is to
>
> provide a way which helps us to look up a specific
>
> register on the switch through regmap-debugfs.
>
>
> And not all ranges of register is defined
>
> so I only include the
Hello,
I've got the following WARNING while running syzkaller on
093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected
kmalloc failure, most likely it's the root cause.
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 3 PID:
Hello,
The following program triggers WARNING in percpu_ref_kill_and_confirm:
https://gist.githubusercontent.com/dvyukov/bcfcef3d6b24b9fd841b88ee20c14d4b/raw/a54aeeb09ad1e0659b0ed87ef5efc4480ab2536f/gistfile1.txt
[ cut here ]
WARNING: CPU: 3 PID: 19987 at
On 03/23/2017 08:53 AM, Juergen Gross wrote:
> Today xen-fbfront supports specifying the display size via module
> parameters only. Add support for specifying the size via Xenstore in
> order to enable doing this easily via the domain's Xen configuration.
>
> Add an error message in case the
Hello,
I've got the following crash while running syzkaller on
093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected
kmalloc failure, most likely it's the root cause.
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 1 PID: 4874
On 03/23/2017 08:52 AM, Juergen Gross wrote:
> Connecting to the backend isn't working reliably in xen-fbfront: in
> case XenbusStateInitWait of the backend has been missed the backend
> transition to XenbusStateConnected will trigger the connected state
> only without doing the actions required
Arnd Bergmann writes:
> gcc points out that we are converting a 16-bit integer into a 32-bit
> little-endian type and assigning that to 16-bit little-endian
> will end up with a zero:
>
> drivers/scsi/qedf/drv_fcoe_fw_funcs.c: In function
> 'init_initiator_rw_fcoe_task':
>
On 23/03/17 13:05, Mason wrote:
> I think this version is ready for review.
> It has all the required bits and pieces.
> I still have a few questions, embedded as comments in the code.
> (Missing are ancillary changes to Kconfig, Makefile)
May I suggest that if you think that a patch is ready for
Hi Stephen,
On Fri, Feb 24, 2017 at 05:39:08PM -0800, Stephen Boyd wrote:
> Quoting James Morse (2017-02-20 03:10:10)
> > On 17/02/17 15:53, Stephen Boyd wrote:
> > > Quoting James Morse (2017-02-17 03:00:39)
> > >> On 17/02/17 01:19, Stephen Boyd wrote:
> > >>> diff --git a/arch/arm64/mm/fault.c
On Thu, Mar 23, 2017 at 01:13:50PM +0800, Jason Wang wrote:
>
>
> On 2017年03月23日 08:30, Laura Abbott wrote:
>> Hi,
>>
>> Fedora has received multiple reports of crashes when running
>> 4.11 as a guest
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1430297
>>
On Sun, Mar 5, 2017 at 8:18 PM, Al Viro wrote:
> On Sun, Mar 05, 2017 at 06:33:18PM +0100, Dmitry Vyukov wrote:
>
>> Added more debug output.
>>
>> name_to_handle_at(r4, &(0x7f003000-0x6)="2e2f62757300",
>> &(0x7f003000-0xd)={0xc, 0x0, "cd21"}, &(0x7f002000)=0x0,
>> 0x1000)
>>
>>
On Thu, Mar 23, 2017 at 3:59 AM, valmiki wrote:
> On 3/20/2017 3:15 AM, Arnd Bergmann wrote:
>>
>> On Sun, Mar 19, 2017 at 3:14 PM, valmiki wrote:
>>>
>>> Hi,
>>>
>>> When ranges property is being parsed using
>>> of_pci_get_host_bridge_resources,
>>> the pci address is being used for
>>>
On 23/03/17 15:09, Felix Fietkau wrote:
On 2017-03-23 09:06, Sean Wang wrote:
Hi Andrew,
The purpose for the regmap table registered is to
provide a way which helps us to look up a specific
register on the switch through regmap-debugfs.
And not all ranges of register is defined
so I
From: Michael Hennerich
This patch adds support for the Analog Devices / Linear Technology
LTC4306 and LTC4305 4/2 Channel I2C Bus Multiplexer/Switches.
The LTC4306 optionally provides two general purpose input/output pins
(GPIOs) that can be configured as logic inputs, opendrain outputs or
Hi Geert,
thanks for detailed review
On Wed, Mar 22, 2017 at 11:26:58AM +0100, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> On Mon, Mar 20, 2017 at 5:14 PM, Jacopo Mondi
> wrote:
> > Add combined gpio and pin controller driver for Renesas RZ/A1
> > r7s72100 SoC.
> >
> > Signed-off-by: Jacopo
>>> On 23.03.17 at 14:56, wrote:
> On 23/03/17 14:37, Jan Beulich wrote:
> On 23.03.17 at 13:52, wrote:
>>> Connecting to the backend isn't working reliably in xen-fbfront: in
>>> case XenbusStateInitWait of the backend has been missed the backend
>>> transition to XenbusStateConnected will
Hello.
I know this means of communication may not be morally right to you as a person
but I also have had a great thought about it and I have come to this conclusion
which I am about to share with you.
INTRODUCTION:I am the Credit Manager U. B. A Bank of Burkina Faso Ouagadougou
and in one way
On Tue, Mar 21, 2017 at 07:50:04AM -0700, Andrey Smirnov wrote:
> Add code allowing for control of various power domains managed by GPCv2
> IP block found in i.MX7 series of SoCs. Power domains covered by this
> patch are:
>
> - PCIE PHY
> - MIPI PHY
> - USB HSIC PHY
> - USB
From: David Woodhouse
Signed-off-by: David Woodhouse
---
Actually it turns out this is fairly trivial for x86 too; it just looked
more interesting at first glance. But pgprot_writecombine() and
pgprot_device() will both do the right thing here, and allowing WC
conditionally based on
Christian,
- Are we going to support resizing BAR when kernel
modesetting is not enabled and we are running in console
under VBIOS control (VESA/VGA)?
- Should we restore PCI configuration if amdgpu
will be unloaded?
- In function amdgpu_resize_bar0():
If resizing for "max" size failed
On Tue, 21 Mar 2017, Sebastian Reichel wrote:
> CPCAP can sense if IRQ is currently set or not. This
> functionality is required for a few subdevices, such
> as the power button and usb phy modules.
>
> Acked-by: Tony Lindgren
> Signed-off-by: Sebastian Reichel
> ---
> Changes since PATCHv2:
>
Add support for interrupt controller unit.
Use cpu_wait instead of endless loop in cpu_halt.
Make coding style changes and documentation additions to platform
configuration options.
Signed-off-by: Amit Kama
arch/mips/Kconfig | 29
On 2017-03-23 15:25, John Crispin wrote:
>
>
> On 23/03/17 15:09, Felix Fietkau wrote:
>> On 2017-03-23 09:06, Sean Wang wrote:
>>> Hi Andrew,
>>>
>>> The purpose for the regmap table registered is to
>>>
>>> provide a way which helps us to look up a specific
>>>
>>> register on the switch
Hi Punit,
On 01/02/17 21:38, Tyler Baicar wrote:
> From: "Jonathan (Zhixiong) Zhang"
>
> If ACPI_APEI and MEMORY_FAILURE is configured, select
> ACPI_APEI_MEMORY_FAILURE. This enables memory failure recovery
> when such memory failure is reported through ACPI APEI. APEI
> (ACPI Platform Error
On Thu, 23 Mar 2017, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following report while running syzkaller fuzzer on
> 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Not the preceding injected
> kmalloc failure, most likely it's the root cause.
I find this bug report puzzling. Maybe I don't
From: "Steven Rostedt (VMware)"
When ftrace_regs_caller was created, it was designed to preserve flags as
much as possible as it needed to act just like a breakpoint triggered on the
same location. But the design is over complicated as it treated all
operations as modifying flags. But push, mov
From: "Steven Rostedt (VMware)"
The function hook ftrace_caller does not create its own stack frame, and
this causes the ftrace stack trace to miss the first function when doing
stack traces.
# echo schedule:stacktrace > /sys/kernel/tracing/set_ftrace_filter
Before:
-0 [002] .N..
No caller currently checks the return value of
kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on
freeing their device. A stale reference will remain in the io_bus,
getting at least used again, when the iobus gets teared down on
kvm_destroy_vm() - leading to use after free
From: "Steven Rostedt (VMware)"
The function tracing hook code for ftrace is not an entry point from
userspace and does not belong in the entry_*.S files. It has already been
moved out of entry_64.S. This moves it out of entry_32.S into its own
ftrace_32.S file.
Also updated the comment in
On Tue, Mar 21, 2017 at 07:50:03AM -0700, Andrey Smirnov wrote:
> Add DT bindings for power domain driver for GPCv2 IP block found in
> i.MX7 SoCs.
>
> Cc: yurov...@gmail.com
> Cc: Lucas Stach
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Fabio Estevam
> Cc: Dong Aisheng
> Cc:
From: "Steven Rostedt (VMware)"
x86_64 has had fentry support for some time. I did not add support to x86_32
as I was unsure if it will be used much in the future. It is still very much
used, and there's issues with function graph tracing with gcc playing around
with the mcount frames, causing
Hi Dong,
Am Freitag, den 24.03.2017, 14:24 +0800 schrieb Dong Aisheng:
[...]
> > +static struct platform_driver imx7_pgc_domain_driver = {
> > + .driver = {
> > + .name = "imx7-pgc",
> > + },
> > + .probe= imx7_pgc_domain_probe,
> > + .remove = imx7_pgc_domain_remove,
> >
[
Ingo, Thomas or H.Peter,
I believe this is all set to go now. I updated those patches that Linus
commented on and I don't believe there are any more issues. I ran this
through several tests (although some of my tests are failing due to
bugs introduced by others in 4.11-rc2). You can take
From: "Steven Rostedt (VMware)"
Currently ftrace_32.S and ftrace_64.S are compiled even when
CONFIG_FUNCTION_TRACER is not set. This means there's an unnecessary #ifdef
to protect the code. Instead of using preprocessor directives, only compile
those files when FUNCTION_TRACER is defined.
Link:
From: "Steven Rostedt (VMware)"
With the advent of -mfentry that uses the new "fentry" hook over mcount, the
mcount name is obsolete. Having the code file that ftrace hooks into called
"mcount*.S" is rather misleading. Rename it to ftrace_64.S
Signed-off-by: Steven Rostedt (VMware)
---
ws the board to boot again. I have not had
chance to dig into this any further yet, but can unless you have some
thoughts.
Cheers
Jon
[0]
https://nvtb.github.io//linux-next/test_next-20170323/20170323021534/boot/tegra210-smaug/tegra210-smaug/defconfig_log.txt
--
nvpublic
On Thu, Mar 23, 2017 at 3:34 PM, Alan Stern wrote:
> On Thu, 23 Mar 2017, Dmitry Vyukov wrote:
>
>> Hello,
>>
>> I've got the following report while running syzkaller fuzzer on
>> 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Not the preceding injected
>> kmalloc failure, most likely it's the root
Hi Thomas,
Thank you very much for looking at this patchset. Comments below:
On 03/23/2017 06:56 AM, Thomas Gleixner wrote:
On Wed, 22 Mar 2017, Pasha Tatashin wrote:
Yes, I am certain it is 0 or near 0 on reset on this machine. Because, I
Emphasis on "this machine'
It's not guaranteed
--
I apologize if this email violates your privacy. It is important and
urgent.
One Mr Edgar Davies who won huge amount in our recent draw is seriously
ill has few weeks to live so his wife and only daughter became so
devastated and they told us that they were not interested in the money
On 23.03.2017 12:28, Peter Meerwald-Stadler wrote:
On Thu, 23 Mar 2017, michael.henner...@analog.com wrote:
From: Michael Hennerich
comments below
Hi Peter,
Thanks for the review -
comments inline.
Signed-off-by: Michael Hennerich
---
.../devicetree/bindings/iio/adc/ltc2497.txt
On Tue, 14 Mar 2017 00:53:55 +0100
Christian Lamparter wrote:
> On Monday, March 13, 2017 10:05:11 PM CET Alban wrote:
> > Currently SoC platforms use a firmware request to get the EEPROM data.
> > This is mostly a hack and rely on using a user-helper scripts which is
> > deprecated. A nicer
On Thu, Mar 23, 2017 at 02:41:53PM +0100, Linus Walleij wrote:
> On Thu, Mar 23, 2017 at 1:34 PM, Uwe Kleine-König
> wrote:
>
> > Maybe we can make gpiod_get_optional look like this:
> >
> > if (!dev->of_node && isnt_a_acpi_device(dev) &&
> > !IS_ENABLED(GPIOLIB))
> >
Hi Leonard,
On Wed, Mar 22, 2017 at 04:27:37PM +0200, Leonard Crestez wrote:
> The imx6sl-evk board has a LAN8720A ethernet phy supported by SMSC_PHY.
> Add this driver to the default imx config since the device is present on
> one of the evaluation boards.
Upstream currently no evaluation board
Will be sending a revised version splitting the irqchip related code to a
different patch and using a generic platform code...
-Original Message-
From: Amit Kama IL
Sent: Wednesday, March 22, 2017 7:38 AM
To: 'r...@linux-mips.org'
Cc: 'devicet...@vger.kernel.org' ;
* Sebastian Reichel [170322 18:02]:
> Hi,
>
> On Wed, Mar 22, 2017 at 08:57:16AM -0700, Tony Lindgren wrote:
> > * Pavel Machek [170322 02:29]:
> > > On Wed 2017-03-22 01:09:11, Sebastian Reichel wrote:
> > > > This fixes compilation for files, that try to include the
> > > > cpcap header in
On Thu, Mar 23, 2017 at 5:55 AM, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers call of NULL timer func:
>
> https://gist.githubusercontent.com/dvyukov/c210d01c74b911273469a93862ea7788/raw/2a3182772a6a6e20af3e71c02c2a1c2895d803fb/gistfile1.txt
>
>
> BUG: unable to handle kernel
1301 - 1400 of 1994 matches
Mail list logo
