On Sun, Nov 22, 2015 at 10:21:34PM -, David Woodhouse wrote:
>
>
> > There's that, and there's an "I care about security, but
> > do not want to burn up cycles on fake protections that
> > do not work" case.
>
> It would seem to make most sense for this use case simply *not* to expose
>
Hi,
With the attached vfat disk image (fuzzed), I get the following WARNING:
WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
CPU: 0 PID: 913 Comm: a.out Not tainted 4.2.5+ #39
Stack:
e0931b50 60075412 e13981e8 0009
605cc684 e0931b60 605cf637
e0931bc0 60040f6d
Hello Guenter,
first of all thanks for picking this series up again.
I think all of this feedback doesn't need to stop your patches getting
in. It should all be possible to improve afterwards.
On Sun, Nov 22, 2015 at 07:20:58PM -0800, Guenter Roeck wrote:
> @@ -160,7 +176,11 @@ they are
On Fri, Nov 20, 2015 at 09:54:12AM +0100, Marek Szyprowski wrote:
> From: Ruslan Bilovol
>
> Change behavior during registration of gadgets and
> gadget drivers in udc-core. Instead of previous
> approach when for successful probe of usb gadget driver
> at least one usb gadget should be already
Hi,
while trying to find the reason for a hanging kernel during resume
handling I found a strange inconsistency in arch/x86/kernel/apic/apic.c
regarding usage of config options.
Attached patch addresses this, no test done as I'm not sure whether
this is a correct approach. Can you have a look at
On Fri, Nov 20, 2015 at 11:27:36AM -0500, Alan Stern wrote:
> On Fri, 20 Nov 2015, Marek Szyprowski wrote:
>
> > From: Ruslan Bilovol
> >
> > Change behavior during registration of gadgets and
> > gadget drivers in udc-core. Instead of previous
> > approach when for successful probe of usb
On Thu, Nov 5, 2015 at 2:47 PM, Jean-Francois Moine wrote:
> On Wed, 4 Nov 2015 08:30:14 -0800
> Maxime Ripard wrote:
>
>> Hi Arnd,
>>
>> On Fri, Oct 30, 2015 at 09:27:03AM +0100, Arnd Bergmann wrote:
>> > On Tuesday 27 October 2015 17:50:24 Jens Kuske wrote:
>> > >
>> > > +static int
On (11/23/15 13:18), Minchan Kim wrote:
[..]
> > https://lkml.org/lkml/2015/6/16/465
>
> Sorry, I have missed that.
> It's worth to fix that you proved it that could happen.
> But when I read your patch, GFP_NOIO instead GFP_NOFS would
> better way. Could you resend it?
no problem.
agree. we
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git
libnvdimm-pending
commit 4b29978299ae61b278fcbc6cf393c85265d78517 ("list: introduce
list_del_poison()")
[ 29.194068] Write protecting the kernel text: 7156k
[ 29.195054] Write protecting
On 21/11/15 12:49, Vassilis Virvilis wrote:
> On 11/20/2015 02:23 PM, Juergen Gross wrote:
>> On 20/11/15 11:04, vas...@iit.demokritos.gr wrote:
I've just found a potential issue: In case MTRR is disabled by the BIOS
the PAT register of the boot processor won't be restored after resume.
Hi Jianchuan,
[auto build test ERROR on: v4.4-rc2]
[also build test ERROR on: next-20151120]
url:
https://github.com/0day-ci/linux/commits/jianchuan-wang-windriver-com/locking_selftest-Save-restore-migrate_disable_atomic-in-locking-selftest/20151123-152217
config:
>
> This patch initialize the freq_table array of each devfreq device by using
> the devfreq_set_freq_table(). If freq_table is NULL, the devfreq framework
> is not able to support the frequency transtion information through sysfs.
>
> The OPP core uses the integer type for the number of opps
On Thu, Nov 19, 2015 at 6:04 AM, Julia Lawall wrote:
> for_each_child_of_node performs an of_node_get on each iteration, so
> a break out of the loop requires an of_node_put.
>
> A simplified version of the semantic patch that fixes this problem is as
> follows (http://coccinelle.lip6.fr):
>
> //
Dear Sebastian,
On Fri, 20 Nov 2015 22:06:59 +0100
Sebastian Hesselbarth wrote:
> On 20.11.2015 09:42, Jisheng Zhang wrote:
> > Add syspll, mempll, cpupll, gateclk and berlin-clk nodes.
> >
> > Signed-off-by: Jisheng Zhang
> > ---
> > arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 38
> >
On (11/23/15 15:35), Minchan Kim wrote:
[..]
> >
> > Signed-off-by: Kyeongdon Kim
> Acked-by: Minchan Kim
Acked-by: Sergey Senozhatsky
-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
[]
> >
> > The value 0 is used for min/max_freq to declare
> > that min/max_freq is deactivated. Therefore, it is not
> > required to do so; they are not intended to show the hardware
> > configuration as well.
>
> This case consider the devfreq device using OPP because
>
From: Jianchuan Wang
System will hang when enabling the kernel option
CONFIG_DEBUG_LOCKING_API_SELFTESTS and CONFIG_SCHED_CONFIG
in the preempt-rt kernel.
In the preempt-rt kernel, migrate_enable()/migrage_disable() are called
in the spinlock and read/write lock; The lock()/unlock() aren't used
On Thu, Nov 19, 2015 at 6:50 PM, LABBE Corentin
wrote:
> The data_year_param struct is never modified, so lets constify it.
> This permit to remove cast since of_device_id is const also.
>
> Signed-off-by: LABBE Corentin
Acked-by: Chen-Yu Tsai
--
To unsubscribe from this list: send the line
On Thu, Nov 19, 2015 at 6:50 PM, LABBE Corentin
wrote:
> The variable year must be set as unsigned since it is used with
> sunxi_rtc_data_year{.min|.max} and as parameter of is_leap_year() which
> wait for unsigned int.
> Only tm_year is not unsigned, but it is long.
> This patch fix also the
On Thu, Nov 19, 2015 at 6:50 PM, LABBE Corentin
wrote:
> The usage of of_device_get_match_data reduce the code size a bit.
>
> Signed-off-by: LABBE Corentin
Acked-by: Chen-Yu Tsai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi Tejun,
On 11/21/2015 05:13 PM, Tejun Heo wrote:
> This is v3 of the xt_cgroup2 patchset. Changes from the last take are
>
> * Folded cgroup2 path matching into xt_cgroup as a new revision rather
> than a separate xt_cgroup2 match as suggested by Pablo.
>
> * Refreshed on top of Nina's
Hi Peter,
On 20.11.2015 18:16, Peter Hurley wrote:
> On 11/20/2015 11:58 AM, Sören Brinkmann wrote:
>> On Fri, 2015-11-20 at 11:30AM -0500, Peter Hurley wrote:
>>> On 11/20/2015 10:28 AM, Sören Brinkmann wrote:
On Fri, 2015-11-20 at 07:13AM -0500, Peter Hurley wrote:
> On 11/19/2015
On 11/20/2015 04:28 PM, Ewan Milne wrote:
On Fri, 2015-11-20 at 15:55 +0100, Hannes Reinecke wrote:
Can't we have a joint effort here?
I've been spending a _LOT_ of time trying to debug things here, but
none of the ideas I've come up with have been able to fix anything.
Yes. I'm not the one
>
> This patch modifies the indentation of 'trans_stat' sysfs to improve
> readability.
> The 1GHz is 1000,000,000. So it needs the least 10 position to show the GHz
> unit.
Applied with resolution of merge conflict described at:
> This patch initialize the freq_table array of each devfreq device by using
> the devfreq_set_freq_table(). If freq_table is NULL, the devfreq framework
> is not able to support the frequency transtion information through sysfs.
>
> The OPP core uses the integer type for the number of opps in
> On Nov 18, 2015, at 3:00 AM, Stephen Boyd wrote:
>
> The drivers don't really need to know which PMIC they're for, so
> make a generic binding for them. This alleviates us from updating
> the drivers every time a new PMIC comes out. It's still
> recommended that we update the binding with new
On Mon, Nov 23, 2015 at 03:21:15PM +0900, Kyeongdon Kim wrote:
> When we're using LZ4 multi compression streams for zram swap,
> we found out page allocation failure message in system running test.
> That was not only once, but a few(2 - 5 times per test).
> Also, some failure cases were
>
> This patch adds the 'show_one' macro to simplify the duplicate code
> of both max_freq_show() and min_freq_show().
>
> Signed-off-by: Chanwoo Choi
Applied.
Thanks.
> ---
> drivers/devfreq/devfreq.c | 20 +---
> 1 file changed, 9 insertions(+), 11 deletions(-)
>
On 10/20/2015 11:02 PM, Wolfram Sang wrote:
> On Thu, Sep 24, 2015 at 02:26:23PM +0800, Fu, Zhonghui wrote:
>> Now, PM core supports asynchronous suspend/resume mode for devices
>> during system suspend/resume, and the power state transition of one
>> device may be completed in separate kernel
When we're using LZ4 multi compression streams for zram swap,
we found out page allocation failure message in system running test.
That was not only once, but a few(2 - 5 times per test).
Also, some failure cases were continually occurring to try allocation
order 3.
In order to make parallel
The i.MX7Dual/Solo is a new series of the i.MX SOC family.
The existing cpufreq driver for 'i.MX6' or 'cpufreq-dt' can
NOT match the requirement of this new SOC. This patch adds the
cpufreq driver for i.MX7Dual/Solo.
Signed-off-by: Bai Ping
---
drivers/cpufreq/Kconfig.arm | 10 ++
On 11/16/2015 11:26 PM, Jiri Kosina wrote:
> On Mon, 16 Nov 2015, Fu, Zhonghui wrote:
>
>> Hi Jiri,
>>
>> Any comments about this patch?
>>
>> After enabling the HID devices suspend/resume asynchronously on ASUS
>> T100TA(Baytrail-T platform), the system suspend-to-idle/resume time is
>>
On Fri, 20 Nov 2015 21:56:34 +0100
Sebastian Hesselbarth wrote:
> On 20.11.2015 09:42, Jisheng Zhang wrote:
> > This patch supports the gateclk and berlin-clk in berlin4ct SoC.
> >
> > Signed-off-by: Jisheng Zhang
> > ---
> > drivers/clk/berlin/Makefile| 2 +-
> >
On 2015/11/23 10:01, Wangnan (F) wrote:
On 2015/11/20 23:34, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 20, 2015 at 09:25:36PM +0800, Wangnan (F) escreveu:
+case BPF_MAP_PRIV_KEY_INDICS:
+for (i = 0; i < priv->key.indics.nr_indics; i++) {
+u64 _idx =
On Wed, Oct 21, 2015 at 11:10:08AM +0100, Sudeep Holla wrote:
> Though the keyboard and other driver will continue to support the legacy
> "gpio-key,wakeup", "linux,wakeup" boolean property to enable the wakeup
> source, "wakeup-source" is the new standard binding.
>
> This patch replaces all the
On 11/21/2015 01:25 AM, Alex Williamson wrote:
On Fri, 2015-11-20 at 08:10 +, Tian, Kevin wrote:
Here is a more concrete example:
KVMGT doesn't require IOMMU. All DMA targets are already replaced with
HPA thru shadow GTT. So DMA requests from GPU all contain HPAs.
When IOMMU is enabled,
On Fri, 20 Nov 2015 21:19:46 +0100
Sebastian Hesselbarth wrote:
> On 20.11.2015 04:34, Jisheng Zhang wrote:
> > On Thu, 19 Nov 2015 21:47:05 +0100
> > Sebastian Hesselbarth wrote:
> >> On 16.11.2015 12:09, Jisheng Zhang wrote:
> >>> The Marvell Berlin BG2Q has 3 watchdogs which are compatible
On 11/21/2015 12:40 AM, Alex Williamson wrote:
Thanks for confirmation. For QEMU/KVM, I totally agree your point; However,
if we take XenGT to consider, it will be a bit more complex: with Xen
hypervisor and Dom0 kernel running in different level, it's not a straight-
forward way for QEMU to do
Hi all,
Changes since 20151120:
The sunxi tree gained a conflict against the samsung-krzk tree.
The sound-soc tree lost its build failures.
The clockevents tree gained a conflict against the samsung-krzk tree.
Non-merge commits (relative to Linus' tree): 2243
2870 files changed, 89284
>
> This patch just fixes following error and warning by using
> scripts/checkpatch.pl.
>
> - Follwoing issue from checkpatch.pl:
> ERROR: space prohibited before that close parenthesis ')'
> + if (count < 0 ) {
>
> WARNING: line over 80 characters
> + ptr =
>
> This patch just removes the error log when
> devfreq_event_get_edev_by_phandle()
> fail to get the instance of devfreq-event device. It is related to sequence of
> the probe() of each driver. So, this error log might show the always during
> kernel booting. Instead, each driver using this
New thread
On Mon, Nov 23, 2015 at 12:14:00PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> On (11/23/15 11:15), Minchan Kim wrote:
> [..]
> > > static void *zcomp_lz4_create(void)
> > > {
> > > - return kzalloc(LZ4_MEM_COMPRESS, GFP_KERNEL);
> > > + void *ret;
> > > +
> > > + ret =
Any comments are welcome.
Thanks,
Zhonghui
On 11/16/2015 2:23 PM, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the power state transition of one
> device may be completed in separate kernel thread. PM core ensures
Any comments are welcome.
Thanks,
Zhonghui
On 11/16/2015 12:20 AM, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the power state transition of one
> device may be completed in separate kernel thread. PM core ensures
On 11/17/2015 9:48 PM, Fu, Zhonghui wrote:
>
> On 11/16/2015 7:30 PM, Ulf Hansson wrote:
>> On 15 November 2015 at 14:53, Fu, Zhonghui
>> wrote:
>>> Now, PM core supports asynchronous suspend/resume mode for devices
>>> during system suspend/resume, and the power state transition of one
>>>
On Sun, Oct 18, 2015 at 11:18:48AM +0530, Sanchayan Maity wrote:
> Something seems to have gone wrong during the merging of the device
> tree changes with the following patch
>
> "ARM: dts: add property for maximum ADC clock frequencies"
>
> The property "fsl,adck-max-frequency" instead of being
On Sun, Nov 22, 2015 at 10:54:08AM +0200, Denis Turischev wrote:
> Hi Rui,
>
> On 11/20/2015 04:33 AM, Huang Rui wrote:
> > 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
On (11/23/15 12:14), Sergey Senozhatsky wrote:
>
> yes, GFP_KERNEL looks a bit fragile to me too. And may be zcomp_strm_alloc()
> and comp->backend->create() deserve GFP_NOFS. I believe I sent a patch doing
> this a while ago: https://lkml.org/lkml/2015/6/16/465
>
perhaps just __GFP_RECLAIM
Introduce an optional hardware maximum timeout in the watchdog core.
The hardware maximum timeout can be lower than the maximum timeout.
Drivers can set the maximum hardware timeout value in the watchdog data
structure. If the configured timeout exceeds the maximum hardware timeout,
the watchdog
For some watchdogs, the hardware timeout is fixed, and the
watchdog driver depends on the watchdog core to handle the
actual timeout. In this situation, the watchdog driver might
only set the 'timeout' variable but do nothing else.
This can as well be handled by the infrastructure, so make
the
Some watchdogs require a minimum time between heartbeats.
Examples are the watchdogs in DA9062 and AT91SAM9x.
Signed-off-by: Guenter Roeck
---
v5: Rebased to v4.4-rc1
Fixed typo in documentation.
v4: Added patch
---
Documentation/watchdog/watchdog-kernel-api.txt | 4
From: Ma Jun
This patch set adds the driver of mbigen and binding document for Hisilicon
Mbigen chips.
Compared with previous version, this version changed much.
Because during the time between V3 and V4 of my patch, there are two
related patches were committed by Mr.Marc Zyngier and Mr. Mark
Drop 'cancel' parameter; simply cancel worker unconditionally
if not needed.
Signed-off-by: Guenter Roeck
---
v5: Added patch.
drivers/watchdog/watchdog_dev.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/watchdog/watchdog_dev.c
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
The infrastructure now also supports generating additional heartbeats
if the maximum hardware timeout is smaller than or close to the
configured timeout. Convert the
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v5: Rebased to v4.4-rc1
v4: No changes
v3: No changes
v2: No changes
---
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v5: Rebased to v4.4-rc1
v4: No changes
v3: No changes
v2: No changes
---
The WDOG_RUNNING flag is expected to be set by watchdog drivers if
the hardware watchdog is running. If the flag is set, the watchdog
subsystem will ping the watchdog even if the watchdog device is closed.
The watchdog driver stop function is now optional and may be omitted
if the watchdog can
The watchdog infrastructure is currently purely passive, meaning
it only passes information from user space to drivers and vice versa.
Since watchdog hardware tends to have its own quirks, this can result
in quite complex watchdog drivers. A number of scanarios are especially common.
- A
From: Ma Jun
For peripheral devices which connect to mbigen,mbigen is a interrupt
controller. So, we create irq domain for each mbigen device and add
mbigen irq domain into irq hierarchy structure.
Signed-off-by: Ma Jun
---
drivers/irqchip/irq-mbigen.c | 119
From: Ma Jun
Add the interrupt controller chip operation functions of mbigen chip.
Signed-off-by: Ma Jun
---
drivers/irqchip/irq-mbigen.c | 84 ++
1 files changed, 84 insertions(+), 0 deletions(-)
diff --git a/drivers/irqchip/irq-mbigen.c
From: Ma Jun
Mbigen means Message Based Interrupt Generator(MBIGEN).
Its a kind of interrupt controller that collects
the interrupts from external devices and generate msi interrupt.
Mbigen is applied to reduce the number of wire connected interrupts.
As the peripherals increasing, the
From: Ma Jun
Add the mbigen msi interrupt controller bindings document.
This patch based on Mark Rutland's patch
https://lkml.org/lkml/2015/7/23/558
Signed-off-by: Ma Jun
---
Documentation/devicetree/bindings/arm/mbigen.txt | 69 ++
1 files changed, 69 insertions(+), 0
Hello,
On (11/23/15 11:15), Minchan Kim wrote:
[..]
> > static void *zcomp_lz4_create(void)
> > {
> > - return kzalloc(LZ4_MEM_COMPRESS, GFP_KERNEL);
> > + void *ret;
> > +
> > + ret = kzalloc(LZ4_MEM_COMPRESS,
> > + __GFP_NORETRY|__GFP_NOWARN|__GFP_NOMEMALLOC);
> > +
On Sat, Oct 17, 2015 at 09:05:21PM -0700, Stefan Agner wrote:
> So far, only the bus clock has been assigned, but in reality the
> SAI IP has for clock inputs. The driver has been updated to
s/for/four
Will fix it up when applying.
Shawn
> make use of the additional clock inputs by
On 11/21/2015 02:08, Mark Brown wrote:
On Thu, Nov 19, 2015 at 11:26:30AM +0800, Songjun Wu wrote:
Set GCK's parent clock as audio clock, make
sure the GCK's parent clock is audio clock.
+ ret = clk_set_parent(dd->gclk, dd->aclk);
+ if (ret) {
+ dev_err(dev,
Dear Sebastian,
On Fri, 20 Nov 2015 22:19:32 +0100
Sebastian Hesselbarth wrote:
> On 20.11.2015 10:47, Jisheng Zhang wrote:
> > Enable all i2c nodes for the Marvell berlin BG4CT STB board.
> >
> > Signed-off-by: Jisheng Zhang
> > ---
> > arch/arm64/boot/dts/marvell/berlin4ct-stb.dts | 50
> >
On Fri, 20 Nov 2015 22:21:55 +0100
Sebastian Hesselbarth wrote:
> On 20.11.2015 10:47, Jisheng Zhang wrote:
> > The Marvell Berlin BG4CT SoC has 4 TWSI which are compatible with the
> > Synopsys DesignWare I2C driver. Add the corresponding nodes.
> >
> > Signed-off-by: Jisheng Zhang
> > ---
>
Hi Mark,
On Mon, Nov 23, 2015 at 9:50 AM, Mark Salter wrote:
> On Mon, 2015-11-23 at 08:36 +0800, Ming Lei wrote:
>> On Mon, Nov 23, 2015 at 7:20 AM, Mark Salter wrote:
>> > On Sun, 2015-11-22 at 00:56 +0800, Ming Lei wrote:
>> > > On Sat, 21 Nov 2015 12:30:14 +0100
>> > > Laurent Dufour
On Sat, 2015-11-21 at 16:22 +0100, Christian König wrote:
> On 21.11.2015 15:49, Daniel Stone wrote:
> > Hi,
> >
> > On 21 November 2015 at 14:22, Christian König > .com> wrote:
> > > On 20.11.2015 16:52, cp...@redhat.com wrote:
> > > > This is somewhat rare on most cards (depending on what
On Sun, 22 Nov 2015, Arnd Bergmann wrote:
> I've also found some /proc/cpuinfo output to cross-reference SoCs
> to their core names.
>
> variant partrevisionnamefeatures
> dove: 0 0x581 5 PJ4 idivt
I just managed to
On Fri, Nov 20, 2015 at 02:19:55PM +0100, Peter Zijlstra wrote:
> On Tue, Nov 10, 2015 at 09:36:02AM +0900, byungchul.p...@lge.com wrote:
> > +++ b/kernel/sched/fair.c
> > @@ -4419,10 +4419,11 @@ static void update_idle_cpu_load(struct rq *this_rq)
> > /*
> > * Called from tick_nohz_idle_exit()
>>>
>>> Can it be like
>>>
>>> /sys/…/DEVICExx/
>>> channelYY/
>>> attr1
>>> attr2
>>> …
>>>
>>> ?
>>
>> I'll work on it. I didn't know that you are allowed to create subdirectories
>> in sysfs. I was just creating attributes to keep it simple. But, your
>> suggestion is cleaner.
>>
>>>
>>> I
On Fri, Nov 20, 2015 at 06:58:59PM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Tim Bird writes:
> > On 11/16/2015 09:21 AM, Felipe Balbi wrote:
> >>
> >> Hi,
> >>
> >> Peter Chen writes:
> >>> On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird wrote:
>
>
> On 11/10/2015 07:14 PM,
Creating a QCOM directory for all QCOM DMA source files.
Signed-off-by: Sinan Kaya
---
drivers/dma/Kconfig| 11 ++-
drivers/dma/Makefile | 2 +-
drivers/dma/qcom/Kconfig | 8
drivers/dma/qcom/Makefile
The Qualcomm Technologies HIDMA device has been designed
to support virtualization technology. The driver has been
divided into two to follow the hardware design.
1. HIDMA Management driver
2. HIDMA Channel driver
Each HIDMA HW consists of multiple channels. These channels
share some set of
This patch adds support for hidma engine. The driver consists
of two logical blocks. The DMA engine interface and the
low-level interface. The hardware only supports memcpy/memset
and this driver only support memcpy interface. HW and driver
doesn't support slave interface.
Signed-off-by: Sinan
The Qualcomm Technologies HIDMA device has been designed
to support virtualization technology. The driver has been
divided into two to follow the hardware design.
1. HIDMA Management driver
2. HIDMA Channel driver
Each HIDMA HW consists of multiple channels. These channels
share some set of
OK, I see. Thanks for the explanation.
2015-11-23 2:34 GMT+08:00 Matias :
> On 11/22/2015 02:51 PM, Wenwei Tao wrote:
>>
>> In the original calculation, the relationships among
>> block, plane and lun was confusing, refine it on the
>> basis of Open-channelSSDInterfaceSpecification.
>>
>>
Hello,
On Fri, Nov 20, 2015 at 07:02:44PM +0900, Kyeongdon Kim wrote:
> When we're using LZ4 multi compression streams for zram swap,
> we found out page allocation failure message in system running test.
> That was not only once, but a few(2 - 5 times per test).
> Also, some failure cases were
On 2015/11/20 23:34, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 20, 2015 at 09:25:36PM +0800, Wangnan (F) escreveu:
+ case BPF_MAP_PRIV_KEY_INDICS:
+ for (i = 0; i < priv->key.indics.nr_indics; i++) {
+ u64 _idx =
>Although from the earlier discussion it still isn't quite clear to me:
>Why must the HPET RTC emulation need to fire the alarm every 16ms? Is that not
>something that can be fixed?
This is hpet driver's behavior. Please check the following comment which is
copied from the file hpet.c
/* HPET
On Mon, 2015-11-23 at 08:36 +0800, Ming Lei wrote:
> On Mon, Nov 23, 2015 at 7:20 AM, Mark Salter wrote:
> > On Sun, 2015-11-22 at 00:56 +0800, Ming Lei wrote:
> > > On Sat, 21 Nov 2015 12:30:14 +0100
> > > Laurent Dufour wrote:
> > >
> > > > On 20/11/2015 13:10, Michael Ellerman wrote:
> > > >
On Sat, Oct 17, 2015 at 09:05:20PM -0700, Stefan Agner wrote:
> The Synchronous Audio Interface (SAI) instances are clocked by
> independent clocks: The bus clock and the audio clock (as shown in
> Figure 51-1 in the Vybrid Reference Manual). The clock gates in
> CCGR0/CCGR1 for SAI0 through SAI3
On 23.11.2015 10:22, Stephen Rothwell wrote:
> Hi Daniel,
>
> Today's linux-next merge of the clockevents tree got a conflict in:
>
> arch/arm/mach-exynos/Kconfig
>
> between commit:
>
> 23067d397616 ("ARM: EXYNOS: Switch to syscon reboot and poweroff")
>
> from the samsung-krzk tree and
On Mon, Nov 23, 2015 at 12:44 AM, Dave Chinner wrote:
> On Sat, Nov 21, 2015 at 12:26:47AM +0200, Octavian Purdila wrote:
>> On Fri, Nov 20, 2015 at 11:08 PM, Dave Chinner wrote:
>> > On Fri, Nov 20, 2015 at 03:43:20PM +0200, Octavian Purdila wrote:
>> >> On Fri, Nov 20, 2015 at 1:24 AM, Dave
On Sun, Nov 22, 2015 at 11:31:00PM +0100, Arnd Bergmann wrote:
> On Sunday 22 November 2015 13:53:44 kbuild test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > head: 3ad5d7e06a96d54a55acb5ab25938a06814605c8
> > commit:
On 11/20/15 at 12:55pm, Johannes Berg wrote:
> On Sun, 2015-11-15 at 19:25 +0100, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-11-15, Dave Young wrote:
> > > cfg80211 module prints a lot of messages like below. Actually
> > > printing once is acceptable but sometimes it will print again
Hi Heiko,
On 11/22/2015 04:14 AM, Heiko Stuebner wrote:
Hi Yakir,
Am Mittwoch, 11. November 2015, 15:47:32 schrieb Yakir Yang:
Signed-off-by: Yakir Yang
---
.../display/rockchip/inno_hdmi-rockchip.txt| 50 ++
1 file changed, 50 insertions(+)
create mode
Hi Daniel,
Today's linux-next merge of the clockevents tree got a conflict in:
arch/arm/mach-exynos/Kconfig
between commit:
23067d397616 ("ARM: EXYNOS: Switch to syscon reboot and poweroff")
from the samsung-krzk tree and commit:
b21f38ccbc1d ("clocksource/drivers/exynos_mct: Fix
Things are looking fairly normal in 4.4-land, with no huge surprises
in rc2. There were a couple of late features: parisc hugepage support
and some late slub bulk allocator patches were not only merged at the
end of the week, but they strictly speaking should have been merge
window things.
But
On Mon, 23 Nov 2015 10:35:59 +1100
Michael Ellerman wrote:
> It's mostly a tracing patch, so I'd need an ACK from Steve at least.
>
> It would probably be best if you split it into a "tracing: .. " patch which
> adds the new macros and then a powerpc patch which uses them.
Yes please do that.
On Mon, Nov 23, 2015 at 7:20 AM, Mark Salter wrote:
> On Sun, 2015-11-22 at 00:56 +0800, Ming Lei wrote:
>> On Sat, 21 Nov 2015 12:30:14 +0100
>> Laurent Dufour wrote:
>>
>> > On 20/11/2015 13:10, Michael Ellerman wrote:
>> > > On Thu, 2015-11-19 at 00:23 -0800, Christoph Hellwig wrote:
>> > >
Hi Jacek,
On 11/20/2015 6:22 PM, Jacek Anaszewski wrote:
On 11/10/2015 08:38 AM, Kim, Milo wrote:
[...]
+cat /sys/class/leds//pattern_levels
+low brightness: 0, high brightness: 255
+
+What:/sys/class/leds//run_pattern
+Date:Oct 2015
On Fri, 2015-11-20 at 15:22 +0300, Denis Kirjanov wrote:
> On 11/3/15, Denis Kirjanov wrote:
> > On 11/3/15, Michael Ellerman wrote:
> > > On Thu, 2015-10-29 at 22:10 +0300, Denis Kirjanov wrote:
> > > > ./drmgr -c cpu -a -r gives the following warning:
> > > >
> > > > [ 2327.035563] RCU used
On Sun, 2015-11-22 at 00:56 +0800, Ming Lei wrote:
> On Sat, 21 Nov 2015 12:30:14 +0100
> Laurent Dufour wrote:
>
> > On 20/11/2015 13:10, Michael Ellerman wrote:
> > > On Thu, 2015-11-19 at 00:23 -0800, Christoph Hellwig wrote:
> > >
> > > > It's pretty much guaranteed a block layer bug, most
From: Len Brown
Fix a Linux-4.3 performance regression:
commit f1ccd249319e ("x86/smpboot: Fix cpu_init_udelay=1 corner case
boot parameter misbehavior")
allowed the cmdline "cpu_init_udelay=" to work
with all values, including the default of 1.
But in setting the default of 1, it
Saurabh Sengar wrote:
> replacing kmalloc and memset by a single call of kzalloc
>
> Signed-off-by: Saurabh Sengar
> ---
> v2 : I didn't got any response for my initial patch,
> I am sending it again on top of latest kernel(today's)
>
> drivers/scsi/lpfc/lpfc_els.c | 3 +--
> 1 file changed, 1
Punit Vara wrote:
> This patch is to the lpfc_els.c which resolves following warning
> reported by coccicheck:
>
> WARNING: kzalloc should be used for rdp_context, instead of
> kmalloc/memset
>
> Signed-off-by: Punit Vara
> ---
> drivers/scsi/lpfc/lpfc_els.c | 3 +--
> 1 file changed, 1
Hi Maxime,
Today's linux-next merge of the sunxi tree got a conflict in:
arch/arm/configs/multi_v7_defconfig
between commit:
23a526f0478c ("ARM: multi_v7_defconfig: Build ChromeOS EC drivers as modules")
from the samsung-krzk tree and commit:
83e9e1f84074 ("ARM: multi_v7_defconfig:
> There's that, and there's an "I care about security, but
> do not want to burn up cycles on fake protections that
> do not work" case.
It would seem to make most sense for this use case simply *not* to expose
virtio devices to guests as being behind an IOMMU at all. Sure, there are
esoteric
1 - 100 of 550 matches
Mail list logo
