On Tue, Nov 17, 2015 at 11:55:53PM +0100, Enric Balletbo Serra wrote:
> Hello Thierry,
>
> 2015-11-17 13:55 GMT+01:00 Thierry Reding :
> > On Mon, Nov 16, 2015 at 05:28:24PM +0100, Enric Balletbo Serra wrote:
> >> Hello Thierry,
> >>
> >> Many thanks for your comments.
> >>
>
> -Original Message-
> From: Nicholas Krause [mailto:xerofo...@gmail.com]
> Sent: Thursday, November 19, 2015 5:31 AM
> To: Ariel Elior
> Cc: netdev ; linux-kernel
>
> Subject: [PATCH] bnx2x:Fix error handling
On Thu, Nov 19, 2015 at 09:23:41PM +0900, Tetsuo Handa wrote:
> Fengguang Wu wrote:
> > Hi David,
> >
> > On Wed, Nov 18, 2015 at 05:00:07PM -0800, David Rientjes wrote:
> > > On Thu, 19 Nov 2015, kbuild test robot wrote:
> > >
> > > > Hi David,
> > > >
> > > > [auto build test ERROR on:
On Thu, Nov 19, 2015, at 12:43, Stefan Priebe - Profihost AG wrote:
>
> Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa:
> > On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote:
> >> OK it had a livelock again. It just took more time.
> >>
> >> So here is the data:
> >
> >
On 19/11/2015 12:21, Russell King wrote:
> When I wrote the MMIO clocksource implementation, there was no
> cacheline_aligned on struct clocksource, and the arrangement I came
> to for the structure put the 'reg' and 'read' within the same cache line
> (note that the MMIO clocksource
Hello,
On 11/18/2015 05:07 PM, Javier Martinez Canillas wrote:
> Hello Brian and Mark,
>
> On 11/16/2015 06:32 PM, Javier Martinez Canillas wrote:
>> On 11/16/2015 05:47 PM, Brian Norris wrote:
>>> On Mon, Nov 16, 2015 at 05:00:43PM -0300, Javier Martinez Canillas wrote:
On 11/16/2015 04:24
Am 19.11.2015 um 13:41 schrieb Hannes Frederic Sowa:
> On Thu, Nov 19, 2015, at 12:43, Stefan Priebe - Profihost AG wrote:
>>
>> Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa:
>>> On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote:
OK it had a livelock again. It just
On Wed, Nov 18, 2015 at 02:25:23PM +0100, Petr Mladek wrote:
> Kthreads are currently implemented as an infinite loop. Each
> has its own variant of checks for terminating, freezing,
> awakening. In many cases it is unclear to say in which state
> it is and sometimes it is done a wrong way.
>
>
On 11/18/2015 05:16 PM, Dan Bogdan Nechita wrote:
Currently writing the attributes with "echo" will result in comparing:
"enabled\n" with "enabled\0" and attribute is always set to false.
Use the sysfs_streq() instead because it treats both NUL and
new-line-then-NUL as equivalent string
From: Borislav Petkov
Add macros for the alternative XSAVE*/XRSTOR* operations which contain
the fault handling and use them. Kill xstate_fault().
Also, copy_xregs_to_kernel() didn't have the extended state as memory
reference in the asm.
Signed-off-by: Borislav Petkov
On Thursday 19 November 2015 12:34:22 Peter Ujfalusi wrote:
>
> I think we can go with a single API, but I don't really like that:
> dma_request_channel(dev, name, *mask, fn, fn_param);
>
> This would cover all current uses being legacy, DT/ACPI, compat, etc:
> dma_request_channel(NULL, NULL, ,
From: Borislav Petkov
Hi,
so that xstate_fault() thing did cause trouble in the past, see
06c8173eb92b ("x86/fpu/xsaves: Fix improper uses of __ex_table")
So lemme kill it.
I had an earlier version of that patch, here's an updated one and split
into two for better digestion.
From: Borislav Petkov
Add an XSTATE_OP macro which contains the XSAVE* fault handling and
replace all non-alternatives users of xstate_fault() with it.
This fixes also the buglet in copy_xregs_to_user() and
copy_user_to_xregs() where the inline asm didn't have @xstate as memory
On Thursday 19 November 2015 03:40:25 Chen Gang wrote:
> diff --git a/include/asm-generic/page.h b/include/asm-generic/page.h
> index 37d1fe2..67cfb7d 100644
> --- a/include/asm-generic/page.h
> +++ b/include/asm-generic/page.h
> @@ -24,9 +24,6 @@
>
> #ifndef __ASSEMBLY__
>
> -#define
Hi David,
On Wed, Nov 18, 2015 at 05:00:07PM -0800, David Rientjes wrote:
> On Thu, 19 Nov 2015, kbuild test robot wrote:
>
> > Hi David,
> >
> > [auto build test ERROR on: next-20151118]
> > [also build test ERROR on: v4.4-rc1]
> >
>
> You need to teach your bot what patches I'm proposing
On 21 October 2015 at 12:10, Sudeep Holla wrote:
> Though the mmc core driver should/will continue to support the legacy
> "enable-sdio-wakeup" property to enable SDIO as the wakeup source, we
> need to add support for the new standard property "wakeup-source".
>
> This
On 3 November 2015 at 12:37, Peter Ujfalusi wrote:
> The driver will not probe without valid DMA channels so no need to check
> if they are valid when the module is removed.
>
> Signed-off-by: Peter Ujfalusi
> CC: Ulf Hansson
On Thu, Nov 19, 2015 at 01:25:29AM +0200, Kirill A. Shutemov wrote:
> The idea borrowed from Peter's patch from patchset on speculative page
> faults[1]:
>
> Instead of passing around the endless list of function arguments,
> replace the lot with a single structure so we can change context
>
On 14 November 2015 at 18:05, Julia Lawall wrote:
> The mmc_pwrseq_ops structures are never modified, so declare them as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Thanks, applied for next!
Kind regards
Uffe
>
> ---
On Wed, Nov 18, 2015 at 12:21:56PM -0800, Andy Lutomirski wrote:
> Could we make this a little less subtle:
>
> ALTERNATIVE "testl %eax, %eax; lz .Lsyscall_32_done", "jmp
> .Lsyscasll_32_done", X86_FEATURE_XENPV
>
> Borislav, what do you think?
I don't mind either.
I would've said your version
On Wed, 21 Oct 2015 11:47:25 -0700
Suravee Suthikulpanit wrote:
Hi Suravee,
Sorry it took so long to get to this series. Comments below.
> This patch introduces pci_host_bridge_acpi_msi_domain(), which returns
> the MSI domain of the specified PCI host bridge
On 2015/11/19 19:22, Jiri Olsa wrote:
On Tue, Nov 17, 2015 at 04:05:36PM +0100, Jiri Olsa wrote:
SNIP
Tested on x86_64. The change is in generic code only,
so it should not affect other archs. Still it would be
nice to have some confirmation.. Wang Nan? ;-)
It'd be nice to have this for
It was <2015-11-18 śro 06:25>, when Ismail Kizir wrote:
> Hello,
>
> I've developed a new encryption algorithm, which dynamically changes
> the key according to plaintext and practically impossible to break.
[...]
> I will be glad to see my algorithm included in Linux distributions.
> Please feel
Use goodix_i2c_write_u8 instead of i2c_master_send to simplify code.
Signed-off-by: Irina Tirdea
Tested-by: Bastien Nocera
Tested-by: Aleksei Mamlin
---
drivers/input/touchscreen/goodix.c | 7 +--
1 file changed, 1
This patchset depends on Dmitry's patch that fixes the
GPIO ACPI API[1], so devm_gpiod_get_optional can be properly
used in the code.
[1] https://lkml.org/lkml/2015/11/11/465
Changes in v11:
- renamed irq-gpio and reset-gpio to irq-gpios and reset-gpios
- added Rob's Acked-by for the binding
Goodix devices can be configured by writing custom data to the device at
init. The configuration data is read with request_firmware from
"goodix__cfg.bin", where is the product id read from the device
(e.g.: goodix_911_cfg.bin for Goodix GT911, goodix_9271_cfg.bin for
GT9271).
The configuration
After power on, it is recommended that the driver resets the device.
The reset procedure timing is described in the datasheet and is used
at device init (before writing device configuration) and
for power management. It is a sequence of setting the interrupt
and reset pins high/low at specific
On 19/11/2015 12:14, Thomas Gleixner wrote:
> So yes, the alignment of the clocksource struct is not longer
> relevant. The case where we access clocksource->max_cycles is when
> CONFIG_DEBUG_TIMEKEEPING is enabled, which imposes worse performance
> problems to timekeeping than the extra
Add support for runtime power management so that the device is
turned off when not used (when the userspace holds no open
handles of the input device). The device uses autosuspend with a
default delay of 2 seconds, so the device will suspend if no
handles to it are open for 2 seconds.
The runtime
Implement suspend/resume for goodix driver.
The suspend and resume process uses the gpio pins.
If the device ACPI/DT information does not declare gpio pins,
suspend/resume will not be available for these devices.
This is based on Goodix datasheets for GT911 and GT9271
and on Goodix driver
From: Michal Hocko
Tetsuo Handa has reported that the system might basically livelock in OOM
condition without triggering the OOM killer. The issue is caused by
internal dependency of the direct reclaim on vmstat counter updates (via
zone_reclaimable) which are performed from
Francly Lucasz,
I am not an expert and never claimed it.
And I accept it's vulnerable to side channel attacks like the one you mentioned.
With this occasion, I want to emphasize one point:
I don't claim that the my algorithm is perfect.
But, take a look at this:
But, I am sure, this "dynamic key
A change to asm-generic/memory_model.h caused a new build error
in some configurations:
mach-clps711x/common.c:39:10: error: implicit declaration of function 'PHYS_PFN'
.pfn = __phys_to_pfn(CLPS711X_PHYS_BASE),
This includes the linux/pfn.h header from the same file to avoid the
error.
On 19 November 2015 at 18:28, Peter Hurley wrote:
> On 11/18/2015 09:35 PM, Baolin Wang wrote:
>> On 18 November 2015 at 23:32, Peter Hurley wrote:
>>> Hi Baolin,
>>>
>>> On 11/16/2015 02:05 AM, Baolin Wang wrote:
It dose not work when we
On Thu, 19 Nov 2015, Russell King - ARM Linux wrote:
> On Thu, Nov 19, 2015 at 11:42:48AM +0100, Thomas Gleixner wrote:
> > On Thu, 19 Nov 2015, Russell King - ARM Linux wrote:
> > > The basic cause of this problem is the cacheline_aligned annotation
> > > which effectively prevents wrapping
On Thu, Nov 19, 2015 at 08:38:58AM +0800, Huang, Ying wrote:
> Hi, Peter,
>
> Peter Zijlstra writes:
>
> > On Wed, Nov 18, 2015 at 02:33:00PM +0800, kernel test robot wrote:
> >> FYI, we noticed the below changes on
> >>
> >>
On 10 November 2015 at 20:12, Adrien Schildknecht
wrote:
> Fault-injection capability for MMC IO uses debugfs entries to configure
> the attributes.
> FAULT_INJECTION_DEBUG_FS must be enabled to use FAIL_MMC_REQUEST.
>
> Replace FAULT_INJECTION with
On 9 November 2015 at 15:03, Ludovic Desroches
wrote:
> Turn the informative message about no vmmc/vqmmc regulator found in
> debug one. There is no need to indicate that something optional is
> missing. Moreover, it can bring confusion, people who doesn't know
> it
Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa:
> On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote:
>> OK it had a livelock again. It just took more time.
>>
>> So here is the data:
>
> Thanks, I couldn't reproduce it so far with simple threaded resolver
> loop on your
Hi,
I've looked into blk-mq and possible support for I/O scheduling.
The reason for this is to minimize performance degradation with
rotational devices when scsi_mod.use_blk_mq=1 is switched on.
I think that the degradation is well reflected with fio measurements.
With an increasing number of
On 19/11/2015 13:01, Wanpeng Li wrote:
> > This is not correct. As far as I know, the SYSCALL bit is always
> > present in CPUID, even if the machine is running in 32-bit mode; CPUID
> > documentation (SDM Volume 2) explicitly documents bit 11 as "Bit 11:
> > SYSCALL/SYSRET available in 64-bit
2015-11-19 19:05 GMT+08:00 Paolo Bonzini :
>
>
> On 19/11/2015 11:45, Wanpeng li wrote:
>> Intel cpu doesn't support syscall/sysret in non 64-bit mode which
>> is different from AMD. Expose syscall/sysret to intel 32-bit guest
>> just makes no sense and leads to #UD which will
On Wed, Nov 18, 2015 at 03:06:16PM -0500, Boris Ostrovsky wrote:
> The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike
> the
> earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit
> (and sysret32 in compat mode) pv ops, as suggested by Andy. (I
Originally the driver would use of_irq_count to
calculate how much memory is required for storing the
interrupt names, since the number of interrupt sources
for the controller is variable.
Since of_irq_count cannot be used by the driver, use
fixed names.
Signed-off-by: John Garry
On Wed, Nov 18, 2015 at 04:55:10PM -0500, Nicolas Pitre wrote:
> On Wed, 18 Nov 2015, Will Deacon wrote:
> > On Wed, Nov 18, 2015 at 10:15:05AM -0800, Yang Shi wrote:
> > > +loops_per_jiffy / (50UL/HZ),
> > > +loops_per_jiffy / (5000UL/HZ) % 100);
>
>
It looks like no comment (no interest?) on this patch.
If nobody is opposed to this patch, I will put it into Russell's patch tracker.
2015-11-11 20:47 GMT+09:00 Masahiro Yamada :
> The function uniphier_cache_get_next_level_node() does the same thing
> as
The two unsigned int variables nb_in_sg and nb_out_sg can be assigned
signed value (-EINVAL) from sg_nents_for_len().
Furthermore they are used only by dma_map_sg and dma_unmap_sg which wait
for an signed int, so they must be set as int.
Fixes: 6c2b74d4774f ("crypto: sahara - check return value
The unsigned int variables [src|dst]_nents and nents can be assigned
signed value (-EINVAL) from sg_nents_for_len().
Furthermore they are used only by dma_map_sg and dma_unmap_sg which wait
for an signed int, so they must be set as int.
Fixes: f051f95eb47b ("crypto: picoxcell - check return value
On Wed 2015-11-18 23:32:28, Thomas Gleixner wrote:
> On Wed, 18 Nov 2015, Petr Mladek wrote:
> > timer_pending() checks whether the list of callbacks is empty.
> > Each callback is removed from the list before it is called,
> > see call_timer_fn() in __run_timers().
> >
> > Sometimes we need to
Several ARM default configurations give us warnings on recent
compilers about potentially uninitialized variables in the
nfnetlink code in two functions:
net/netfilter/nfnetlink_queue.c: In function 'nfqnl_build_packet_message':
net/netfilter/nfnetlink_queue.c:519:19: warning: 'nfnl_ct' may be
On 19/11/2015 11:45, Wanpeng li wrote:
> Intel cpu doesn't support syscall/sysret in non 64-bit mode which
> is different from AMD. Expose syscall/sysret to intel 32-bit guest
> just makes no sense and leads to #UD which will confuse the users.
>
> This patch disable expose syscall/sysret to
>
> From: Jarkko Sakkinen [jarkko.sakki...@linux.intel.com]
> Sent: Tuesday, November 17, 2015 17:27
>
> Support for sealing with a authorization policy.
>
> Two new options for trusted keys:
>
> * 'policydigest=': provide an auth policy digest for
On Thu, Nov 19, 2015 at 11:42:48AM +0100, Thomas Gleixner wrote:
> On Thu, 19 Nov 2015, Russell King - ARM Linux wrote:
> > The basic cause of this problem is the cacheline_aligned annotation
> > which effectively prevents wrapping struct clocksource to provide
> > implementation specific
On 10 November 2015 at 10:43, Haibo Chen wrote:
> Currently, we config the watermark_level register only in probe.
> This will cause the mmc write operation timeout issue after system
> resume back in LPSR mode. Because in LPSR mode, after system resume
> back, the
On Nov 12 2015 or thereabouts, Simon Wood wrote:
> This patch adds basic support for the Logitech G920 wheel when in HID
> mode. This wheel 'speaks' the HID++ protocol, and therefor is driven
> with hid-logitech-hidpp.
>
> At this stage the driver only shows that it can communicate with the
>
On Thu, Nov 19, 2015 at 11:55:46AM +0100, Marc Gonzalez wrote:
> If you just object to the ifdef, then perhaps 'reg' can be included
> unconditionally.
>
> diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
> index 278dd279a7a8..50725fd23ab0 100644
> ---
On 11 November 2015 at 19:11, Ludovic Desroches
wrote:
> Add runtime PM support and use runtime_force_suspend|resume() for system
> PM.
>
> Signed-off-by: Ludovic Desroches
Thanks, applied for next!
Kind regards
Uffe
> ---
>
> Changes:
On Thu, Nov 19, 2015 at 06:43:14PM +0800, Wangnan (F) wrote:
> Also, why not fixing rsp in kernel if that instruction is a 'callq'?
> For avoiding instruction decoding?
Why would the kernel do that? It doesn't need this.
Have userspace do it when trying to interpret the data.
If
On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote:
> OK it had a livelock again. It just took more time.
>
> So here is the data:
Thanks, I couldn't reproduce it so far with simple threaded resolver
loop on your kernel. :/
Your data is useless if you don't also provide the file
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: 18 November, 2015 23:24
> To: Tirdea, Irina
> Cc: Dmitry Torokhov; Bastien Nocera; Aleksei Mamlin; Karsten Merker;
> linux-in...@vger.kernel.org; Mark Rutland; Purdila, Octavian;
> linux-kernel@vger.kernel.org;
On 16 November 2015 at 17:08, Arnd Bergmann wrote:
> When compiling the sh_mmcif driver for ARM64, we currently
> get a harmless build warning:
>
> ../drivers/mmc/host/sh_mmcif.c: In function 'sh_mmcif_request_dma_one':
> ../drivers/mmc/host/sh_mmcif.c:417:4: warning: cast to
On Thursday 19 November 2015 13:00:48 Ulf Hansson wrote:
> Thanks, applied for next!
>
> FYI: There were some check patch warnings, I decided to fix them
> myself before applying.
>
Ok, thanks!
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On 2015/11/19 20:10, Wangnan (F) wrote:
On 2015/11/19 19:22, Jiri Olsa wrote:
On Tue, Nov 17, 2015 at 04:05:36PM +0100, Jiri Olsa wrote:
[SNIP]
In addition, just for your information, I find libdw can unwind call
chain I described yesterday in [1].
Please forget it. The problem is
Fengguang Wu wrote:
> Hi David,
>
> On Wed, Nov 18, 2015 at 05:00:07PM -0800, David Rientjes wrote:
> > On Thu, 19 Nov 2015, kbuild test robot wrote:
> >
> > > Hi David,
> > >
> > > [auto build test ERROR on: next-20151118]
> > > [also build test ERROR on: v4.4-rc1]
> > >
> >
> > You need to
Hello Thierry,
2015-11-19 12:51 GMT+01:00 Thierry Reding :
> On Tue, Nov 17, 2015 at 11:55:53PM +0100, Enric Balletbo Serra wrote:
>> Hello Thierry,
>>
>> 2015-11-17 13:55 GMT+01:00 Thierry Reding :
>> > On Mon, Nov 16, 2015 at 05:28:24PM +0100, Enric
Each of the Goodix devices supported by this driver has a fixed size for
the configuration information registers. The size varies depending on the
device and is specified in the datasheet.
Use the proper configuration length as specified in the datasheet for
each device model, so we do not read
Goodix devices have a configuration information register area that
specify various parameters for the device. The configuration information
has a specific format described in the Goodix datasheet. It includes X/Y
resolution, maximum supported touch points, interrupt flags, various
sesitivity
Add ESD (Electrostatic Discharge) protection mechanism.
The driver enables ESD protection in HW and checks a register
to determine if ESD occurred. If ESD is signalled by the HW,
the driver will reset the device.
The ESD poll time (in ms) can be set through the sysfs property
esd_timeout. If it
Hi,
While I was creating thousands of docker container on a power8 baremetal
(config: 4.3.0 kernel 1TB RAM, 20core (=160 cpu) system. After creating
around 5600 container
I have hit below problem.
[This is looking similar to
https://bugzilla.kernel.org/show_bug.cgi?id=101011, but
kernel had
rk3399 do ddr frequency scaling use devfreq framework,
use simple_ondemand policy, and use rk3399 dfi controller
to get ddr busy time.
Signed-off-by: Lin Huang
---
drivers/devfreq/Kconfig | 1 +
drivers/devfreq/Makefile | 1 +
support rk3399 dmc clock driver. Note, ddr set rate function will
use dcf controller which run in ATF, it need to fishish it when rk3399
arm trust firmware ready.
Signed-off-by: Lin Huang
---
drivers/clk/rockchip/Makefile | 1 +
these patchset bring up rk3399 ddr frequency scaling flow,
use devfreq framework and simple_ondemand policy. Ddr set
rate function will implement in dcf controller which run in
the ATF, and rk3399 ATF not ready now, so we need finish it
when rk3399 ATF ready.
Lin Huang (2):
clk: rockchip: dmc:
On 11/18/2015 09:35 PM, Baolin Wang wrote:
> On 18 November 2015 at 23:32, Peter Hurley wrote:
>> Hi Baolin,
>>
>> On 11/16/2015 02:05 AM, Baolin Wang wrote:
>>> It dose not work when we want to use the usb-to-serial port based
>>> on one usb gadget as a console. Thus
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive
- two functional fixes for wacom HID driver from Ping Cheng and Jiri
Kosina
Thanks
Jiri Kosina (1):
HID: wacom:
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching.git for-linus
to receive livepatching fix for module handling in case kASLR has been
enabled, from Zhou Chengming.
Thanks.
Zhou
On 11/18/2015 05:07 PM, Arnd Bergmann wrote:
> On Wednesday 18 November 2015 16:41:35 Peter Ujfalusi wrote:
>> On 11/18/2015 04:29 PM, Arnd Bergmann wrote:
>>> On Wednesday 18 November 2015 16:21:26 Peter Ujfalusi wrote:
2. non slave channel requests, where only the functionality matters,
Russell,
On Wed, 18 Nov 2015, Russell King - ARM Linux wrote:
> On Wed, Nov 18, 2015 at 02:43:34PM +0100, Marc Gonzalez wrote:
> > Since 'struct clocksource' is cacheline_aligned, gcc must insert
> > a lot of padding between reg and clksrc in 'struct clocksource_mmio'
> > (for example,
Hi Fi
please read comment
https://bugzilla.redhat.com/show_bug.cgi?id=1282706#c2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Thu, Nov 19, 2015 at 08:32:09AM +0530, Vinod Koul wrote:
> On Thu, Nov 19, 2015 at 11:35:28AM +1100, Stephen Rothwell wrote:
> > a86d505783e4 ("ASoC: Intel: Skylake: Adding nau88l25+ssm4567 machine
> > driver")
> Okay both went it same time, I will send a patch for this
> Somehow Feng's
Add Mediatek EFUSE driver to access hardware data like
thermal sensor calibration or HDMI impedance.
Signed-off-by: Andrew-CT Chen
---
drivers/nvmem/Kconfig | 11 ++
drivers/nvmem/Makefile| 2 ++
drivers/nvmem/mtk-efuse.c | 89
The sys.path should be scripts/gdb,
so that we can import linux lib correctly.
Signed-off-by: yalin wang
---
scripts/gdb/vmlinux-gdb.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/gdb/vmlinux-gdb.py b/scripts/gdb/vmlinux-gdb.py
index
On 19/11/2015 11:36, Russell King - ARM Linux wrote:
> On Thu, Nov 19, 2015 at 11:33:47AM +0100, Thomas Gleixner wrote:
>> Russell,
>>
>> On Wed, 18 Nov 2015, Russell King - ARM Linux wrote:
>>
>>> On Wed, Nov 18, 2015 at 02:43:34PM +0100, Marc Gonzalez wrote:
Since 'struct clocksource' is
On Thu, Nov 19, 2015 at 11:35:23AM +0800, Chris Zhong wrote:
> From: Liu Ying
>
> This patch adds device tree bindings for Synopsys DesignWare MIPI DSI
> host controller DRM bridge driver.
>
> Signed-off-by: Liu Ying
> Signed-off-by: Chris Zhong
On Thu, Nov 19, 2015 at 03:49:00PM +0100, Richard Weinberger wrote:
> Am 19.11.2015 um 15:37 schrieb Colin Walters:
> > On Thu, Nov 19, 2015, at 02:53 AM, Richard Weinberger wrote:
> >
> >> Erm, I don't want this in the kernel. That's why I've proposed the lklfuse
> >> approach.
> >
> > I
> Subject: Re: [PATCH] input: i8042: add quirk to implement i8042 detect for AMD
>
> On Fri, Oct 16, 2015 at 12:21:55PM +0200, Borislav Petkov wrote:
> > On Fri, Oct 16, 2015 at 05:35:40PM +0800, Wan ZongShun wrote:
> > > 2015-10-16 16:58 GMT+08:00 Borislav Petkov :
> > > > On
On Tuesday 17 November 2015 17:30:14 Punit Agrawal wrote:
> Arnd Bergmann writes:
>
> > The scpi_clock driver can be built-in when CONFIG_COMPILE_TEST
> > is set even when ARM_SCPI_PROTOCOL is a loadable module, and
> > that results in a link error:
> >
> > drivers/built-in.o: In
On Wed, Nov 18, 2015 at 12:00:17AM +0200, Octavian Purdila wrote:
> On Tue, Nov 17, 2015 at 10:12 PM, Richard Weinberger wrote:
> > Am 17.11.2015 um 20:25 schrieb Octavian Purdila:
> >> On Tue, Nov 17, 2015 at 9:21 PM, Seth Forshee
> >> wrote:
> >>>
>
On Thu, 2015-11-19 at 14:26 +0200, Irina Tirdea wrote:
> After power on, it is recommended that the driver resets the device.
> The reset procedure timing is described in the datasheet and is used
> at device init (before writing device configuration) and
> for power management. It is a sequence
The return value should be non-zero under error conditions.
Remove nvme_free(dev) to avoid free dev more than once.
Signed-off-by: Wenwei Tao
---
drivers/lightnvm/core.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/lightnvm/core.c
On Tuesday 17 November 2015 12:35:58 Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> This is the first "fixes" pull-request for AT91. I tried to collect little
> patches that didn't make it for -rc1.
> It can be due to synchronization between trees like the addition of some
> sama5d2 Xplained nodes
On Thu, Nov 19, 2015 at 3:26 PM, Al Viro wrote:
>
> 1) atime updates, according to POSIX, should happen in case of success.
> For example, giving readlink(2) an unmapped buffer should _not_ touch
> atime. Neither should calling readlink(2) in case if ->readlink() method
cs-gpios isn't required with patch "spi: mediatek: single
device does not require cs_gpios", so modify the description.
Signed-off-by: Leilk Liu
---
.../devicetree/bindings/spi/spi-mt65xx.txt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch revises failure flow while pm_runtime_enable().
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index
It's not need to re-read and re-write SPI_CMD_REG, so remove it.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index 7840067..6c1a96e 100644
---
On 2015/11/20 7:29, Sukadev Bhattiprolu wrote:
Wangnan (F) [wangn...@huawei.com] wrote:
|
|
| On 2015/11/19 7:14, Alexei Starovoitov wrote:
| >On Wed, Nov 18, 2015 at 05:50:39PM -0300, Arnaldo Carvalho de Melo wrote:
| >>Em Wed, Nov 18, 2015 at 11:26:04AM -0800, Sukadev Bhattiprolu escreveu:
|
Hi Denis,
On Thu, Nov 19, 2015 at 05:56:00PM +0800, Denis Turischev wrote:
> AMD Mullins watchdog is fully compatible to the previous Hudson chipset,
> reuse the existent sp5100_tco driver.
>
Thank you to add this support!
Actually, PCI_DEVICE_ID_AMD_HUDSON2_SMBUS is only the SMBus device id
on
On Wed, 18 Nov 2015, Jarkko Sakkinen wrote:
> On Wed, Nov 18, 2015 at 11:21:01AM +1100, James Morris wrote:
> > On Tue, 17 Nov 2015, Jarkko Sakkinen wrote:
> >
> > > }
> > > break;
> > > + case Opt_policydigest:
> > > + if (!tpm2 ||
> >
Hi Magnus,
Thank you for the patch.
On Tuesday 17 November 2015 12:18:32 Magnus Damm wrote:
> pinctrl: sh-pfc: r8a7794: DU support
>
> [PATCH 01/04] pinctrl: sh-pfc: r8a7794: Add DU pin groups
> [PATCH 02/04] pinctrl: sh-pfc: r8a7794: Separate DU CDE and DISP
> [PATCH 03/04] pinctrl: sh-pfc:
On 11/19/2015 11:52 PM, Alex Williamson wrote:
On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
On Thu, 19 Nov 2015, Jike Song wrote:
Hi Alex, thanks for the discussion.
In addition to Kevin's replies, I have a high-level question: can VFIO
be used by QEMU for both KVM and Xen?
On Thu, Nov 12, 2015 at 02:22:20PM +0100, Boris Brezillon wrote:
> On Wed, 11 Nov 2015 16:15:50 -0800
> Brian Norris wrote:
> > IOW, I think we can grab the reference in add_mtd_device() and drop it
> > in del_mtd_device(). This would handle both the partition and
> >
501 - 600 of 1776 matches
Mail list logo