On Wed, Jul 09, 2014 at 03:30:08PM +0400, Andrey Ryabinin wrote:
> Some code in slub could validly touch memory marked by kasan as unaccessible.
> Even though slub.c doesn't instrumented, functions called in it are
> instrumented,
> so to avoid false positive reports such places are protected by
Hi Guenter,
On Mon, 14 Jul 2014 22:43:42 -0700 Guenter Roeck wrote:
>
> On 07/14/2014 08:29 PM, Stephen Rothwell wrote:
> >
> > After merging the v4l-dvb tree, today's linux-next build (powerpc
> > ppc64_defconfig)
> > failed like this:
> >
> > arch/powerpc/kernel/smp.c:764:2: error:
On 15 July 2014 11:06, Saravana Kannan wrote:
> Btw, I tried to take a stab at removing any assumption in cpufreq code about
> policy->cpu being ONLINE. There are 160 instances of those of with 23 are in
> cpufreq.c
>
> So, even if we are sure cpufreq.c is fine, it's 137 other uses spread across
On 07/14/2014 06:58 PM, abhijit naik wrote:
> Hi,
>
> I am studying ASP driver of DM6446 EVM in main line kernel 3.14.
> I referred to both sound/soc/davinci/davinci-mcasp.c
> and sound/soc/davinci/davinci-i2s.c
For DM6446 the correct driver would be the davinci-i2s. The audio interface is
On Wed, Jul 09, 2014 at 03:30:04PM +0400, Andrey Ryabinin wrote:
> This patch shares virt_to_cache() between slab and slub and
> it used in cache_from_obj() now.
> Later virt_to_cache() will be kernel address sanitizer also.
I think that this patch won't be needed.
See comment in 15/21.
Thanks.
On 07/15/2014 03:48 AM, Iyappan Subramanian wrote:
This patch adds documentation for APM X-Gene SoC ethernet DTS binding.
Signed-off-by: Iyappan Subramanian
Signed-off-by: Ravi Patel
Signed-off-by: Keyur Chudgar
---
.../devicetree/bindings/net/apm-xgene-enet.txt | 72
On Wed, Jul 09, 2014 at 03:30:02PM +0400, Andrey Ryabinin wrote:
> Add kernel address sanitizer hooks to mark allocated page's addresses
> as accessible in corresponding shadow region.
> Mark freed pages as unaccessible.
>
> Signed-off-by: Andrey Ryabinin
> ---
> include/linux/kasan.h | 6
On 07/14/2014 08:29 PM, Stephen Rothwell wrote:
Hi Mauro,
After merging the v4l-dvb tree, today's linux-next build (powerpc
ppc64_defconfig)
failed like this:
arch/powerpc/kernel/smp.c:764:2: error: initialization from incompatible
pointer type [-Werror]
{ cpu_smt_mask, powerpc_smt_flags,
On 07/14/2014 09:35 PM, Viresh Kumar wrote:
On 15 July 2014 00:38, Saravana Kannan wrote:
Yeah, it definitely crashes if policy->cpu if an offline cpu. Because the
mutex would be uninitialized if it's stopped after boot or it would never
have been initialized (depending on how you fix
> > +For one device driver, which will run in different scenarios above
> > +on different SoCs using the devicetree, we need one way to simplify
> > +this.
> > +
> > +Required properties:
> > +- {big,little}-endian: these are boolean properties, if absent
> > + meaning that the CPU and the Device
On 07/15/2014 09:53 AM, Xiubo Li wrote:
Device-Tree binding for device endianness
Index Device Endianness properties
---
1 BE 'big-endian'
2 LE 'little-endian'
For one device driver, which will run in
Hi Rafael/Daniel,
Did you get a chance to review the patch?
--
Thanks,
-Meraj
On Sat, Jul 12, 2014 at 7:29 PM, Mohammad Merajul Islam Molla
wrote:
> cpuidle driver name sysfs node is read-only. So permission should be 0444.
>
> Signed-off-by: Mohammad Merajul Islam Molla
> ---
>
On Mon, Jul 14, 2014 at 11:38 PM, Rafael J. Wysocki wrote:
> On Monday, July 14, 2014 12:40:24 PM pramod gurav wrote:
>> Hi Rafael,
>>
>> Can we consider these changes if there are no issues with this?
>
> Well, are you "fixing" checkpatch.pl warnings just for the sake of
> this or is there a
On Mon, Jul 14, 2014 at 10:39:48PM +, Haiyang Zhang wrote:
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Monday, July 14, 2014 5:31 PM
> > To: Haiyang Zhang
> > Cc: KY Srinivasan; David S. Miller; de...@linuxdriverproject.org; linux-
> >
On (Tue) 15 Jul 2014 [12:45:56], Herbert Xu wrote:
> On Tue, Jul 15, 2014 at 10:10:28AM +0530, Amit Shah wrote:
> > On (Mon) 14 Jul 2014 [20:50:06], Herbert Xu wrote:
> > > On Thu, Jul 10, 2014 at 03:42:33PM +0530, Amit Shah wrote:
> > > > v3:
> > > > - Kees Cook pointed out a weird side-effect:
On 07/14/2014 06:09 PM, David Rientjes wrote:
> + if (node == NUMA_NO_NODE) {
> + node = page_to_nid(page);
> + } else {
> + int distance = node_distance(page_to_nid(page), node);
> +
> + /*
> +
On Tue, Jul 15, 2014 at 10:10:28AM +0530, Amit Shah wrote:
> On (Mon) 14 Jul 2014 [20:50:06], Herbert Xu wrote:
> > On Thu, Jul 10, 2014 at 03:42:33PM +0530, Amit Shah wrote:
> > > v3:
> > > - Kees Cook pointed out a weird side-effect: devices which have
> > >->init() registered get their
On (Mon) 14 Jul 2014 [20:50:06], Herbert Xu wrote:
> On Thu, Jul 10, 2014 at 03:42:33PM +0530, Amit Shah wrote:
> > v3:
> > - Kees Cook pointed out a weird side-effect: devices which have
> >->init() registered get their randomness added to the system each
> >time they're switched in, but
From: Chris Ball
Subject: [PATCH] mmc: core: sdio: Fix unconditional wake_up_process() on sdio
thread
781e989cf59 ("mmc: sdhci: convert to new SDIO IRQ handling") and
bf3b5ec66bd ("mmc: sdio_irq: rework sdio irq handling") disabled
the use of our own custom threaded IRQ handler, but left in an
On Fri, May 16, 2014 at 10:18:40PM -0400, Theodore Ts'o wrote:
> On Fri, May 16, 2014 at 05:46:22PM -0700, Hannes Frederic Sowa wrote:
> > This should do the trick:
> > dd if=/dev/urandom of=/dev/zero bs=67108707
> >
> > I suspect ee1de406ba6eb1 ("random: simplify accounting logic") as the
Device-Tree binding for device endianness
Index Device Endianness properties
---
1 BE 'big-endian'
2 LE 'little-endian'
For one device driver, which will run in different scenarios above
on different SoCs
On 14 July 2014 18:37, Christian König wrote:
>> I vote for HSA module that expose ioctl and is an intermediary with the
>> kernel driver that handle the hardware. This gives a single point for
>> HSA hardware and yes this enforce things for any hardware manufacturer.
>> I am more than happy to
On 15 July 2014 00:38, Saravana Kannan wrote:
> Yeah, it definitely crashes if policy->cpu if an offline cpu. Because the
> mutex would be uninitialized if it's stopped after boot or it would never
> have been initialized (depending on how you fix policy->cpu at boot).
>
> Look at this snippet on
Hi,
Please ignore this V5 patch series.
Thanks,
BRs
> -Original Message-
> From: Xiubo Li [mailto:li.xi...@freescale.com]
> Sent: Tuesday, July 15, 2014 12:18 PM
> To: broo...@kernel.org; mark.rutl...@arm.com
> Cc: robh...@kernel.org; pawel.m...@arm.com;
Hi Borislav,
(2014/07/11 19:59), Borislav Petkov wrote:
On Fri, Jul 11, 2014 at 09:48:27AM +0900, Yasuaki Ishimatsu wrote:
+static int get_cpuid(int apicid)
Btw this "cpuid" is misleading. Call it "cpu_num" or so.
O.K.
I'll update it.
+{
+ int cpuid;
+
+ cpuid =
Changes in V6:
- there is some mistake for V5 patch series, resend it.
Changes in V5:
- remove the register's dt endianness support for it will always be BE
for now.
- only support the register values buffers dt endianness support.
Xiubo Li (2):
regmap: add DT endianness binding support.
Device-Tree binding for device endianness
Index Device Endianness properties
---
1 BE 'big-endian'
2 LE 'little-endian'
For one device driver, which will run in different scenarios above
on different SoCs
For many drivers which will support rich endianness of Devices
need define DT properties by itself with the binding support.
The endianness using regmap:
Index Device Properties if needs bytes-swap,
or just ignore it
For many drivers which will support rich endianness of Devices
need define DT properties by itself with the binding support.
The endianness using regmap:
Index Device Properties if needs bytes-swap,
or just ignore it
Changes in V5:
- remove the register's dt endianness support for it will always be BE
for now.
- only support the register values buffers dt endianness support.
Xiubo Li (2):
regmap: add DT endianness binding support.
dt/bindings: Add the DT binding documentation for endianness
Quoting chenhanx...@cn.fujitsu.com (chenhanx...@cn.fujitsu.com):
> Hi,
>
> Let me summarize our discussions of ID conversion by pros/cons:
>
> A) make new system call for translation
> A-1) systemcall(ID, NS1, NS2) into (ID).
> pros:
> - has a reference ns(NS2)
>
On 07/14/2014 07:46 PM, Andy Lutomirski wrote:
>
> On espfix-less kernels (Xen and non-Xen), 16-bit CS w/ 16-bit SS
> always fails. Native (32-bit or 64-bit, according to the binary) CS
> with 16-bit SS fails for sigreturn_32, but passes for sigreturn_64. I
> find this somewhat odd. Native ss
On 07/15/2014 11:54 AM, Fu, Zhonghui wrote:
>
> Hi,
>
> The data type of "host" is "struct mmc_host", and there is not "quirks"
> member in this structure.
Sorry for wrong typo.
You use the "host->caps2" instead of "host->quirks".
Best Regards,
Jaehoon Chung
>
>
> Thanks,
> Zhonghui
>
> On
On Tue, Jul 15, 2014 at 12:50:27AM +0200, Stephane Eranian wrote:
> On Tue, Jul 15, 2014 at 12:49 AM, Stephane Eranian wrote:
> > On Tue, Jul 15, 2014 at 12:39 AM, Andi Kleen wrote:
> >>> I have a problem with this patch.
> >>>
> >>> It makes: perf mem -t store rec record OP_NA for the store.
>
On Tue, 15 Jul 2014 11:48:33 +0800 Ian Kent wrote:
...
> So far I've tracked this to something that was introduced between 3.11
> and 3.12. One change that went into 3.12 was Jeff Laytons' umount
> specific path resolution for umount. I've found this is also broken on
> recent RHEL-6 kernels and
On Mon, Jul 14, 2014 at 4:22 AM, Ian Abbott wrote:
> On 2014-07-12 23:44, Chase Southwood wrote:
>>
>> Use the addi_watchdog module to provide support for the watchdog
>> subdevice.
>>
>> Also, rearrange the subdevice init blocks so that the order makes sense.
>> Digital input/output subdevices
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in
drivers/acpi/acpi_extlog.c between commits 2dfb7d51a61d ("trace, RAS:
Add eMCA trace event interface") and d6cae935ec5b ("trace, eMCA: Add a
knob to adjust where to save event log") from the ia64 tree and commit
0a00fd5e20fd
在 2014年7月15日，上午9:40，Greg Kroah-Hartman 写道：
> On Mon, Jul 14, 2014 at 08:04:15PM +0800, Chen Gang wrote:
>>
>> For drivers/staging/lustre/lustre/include/lustre_sec.h:391:
>>
>> - staging tree: use '\t ' between 'die' and '('.
>>
>> - linux-next tree: use ' ' between 'die' and '('.
>>
>>
On Mon, 2014-07-14 at 10:53 +1000, NeilBrown wrote:
> Here is a revised version of this one patch.
> This one fixes a problem with refcounts on dentry and adds a comment to
> clarify the behaviour of should_expire().
I have some bad news I'm afraid, not about the patches.
As I mentioned I'm well
In bootp.c I am hitting lots of warnings this fixes two on lines 71,72
in order to pass checkpatch and follow kernel coding style.
---
arch/alpha/boot/bootp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/alpha/boot/bootp.c b/arch/alpha/boot/bootp.c
index
This patch removes all the whitespace an tab issues that this file
has when running checkpatch
---
arch/alpha/boot/bootp.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/alpha/boot/bootp.c b/arch/alpha/boot/bootp.c
index 3ee529d..6227e4f 100644
---
When running checkpatch on this file I get lots of warnings and even a few
errors. This patch cleans up the coding style warning I get on line 26.
---
arch/alpha/boot/bootp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/alpha/boot/bootp.c b/arch/alpha/boot/bootp.c
This patch removes errors on lines 205,206 to fit kernel coding
style.
---
arch/alpha/boot/bootp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/alpha/boot/bootp.c b/arch/alpha/boot/bootp.c
index 47e33cb..ac0351d 100644
--- a/arch/alpha/boot/bootp.c
+++
Hi all
Sorry, add more maintainers.
Best regards
Wang shengjiu
-Original Message-
From: alsa-devel-boun...@alsa-project.org
[mailto:alsa-devel-boun...@alsa-project.org] On Behalf Of Shengjiu Wang
Sent: Monday, July 14, 2014 6:40 PM
To: broo...@linaro.org
Cc:
This patch fixes the if statement on line 180 to be changed to having
no brackets as defined by kernel coding style for one line if statements.
---
arch/alpha/boot/bootp.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/alpha/boot/bootp.c b/arch/alpha/boot/bootp.c
index
Kernel coding style. Remove useless else statement after return.
Signed-off-by: Lucas Tanure
---
drivers/staging/android/sync.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/android/sync.c b/drivers/staging/android/sync.c
index c9a0c2c..e7b2e02 100644
---
o a change that (when suggested) was shown to cause more
problems than it was worth and dropped. I can't imagine how it ended
up in the merge commit.
I have used the v4l-dvb tree from next-20140714 for today. Please fix
this up.
--
Cheers,
Stephen Rothwells...@canb.a
On Mon, Jul 14, 2014 at 7:46 PM, Andy Lutomirski wrote:
> On Mon, Jul 14, 2014 at 3:23 PM, H. Peter Anvin wrote:
>> On 07/14/2014 02:35 PM, Andy Lutomirski wrote:
>>> Presumably the problem is here:
>>>
>>> ENTRY(xen_iret)
>>> pushq $0
>>> 1:jmp hypercall_iret
>>> ENDPATCH(xen_iret)
>>>
On Wed, 2014-07-02 at 07:00 +, Masami Hiramatsu wrote:
> On ia64 and ppc64, the function pointer does not point the
> entry address of the function, but the address of function
> discriptor (which contains the entry address and misc
> data.) Since the kprobes passes the function pointer stored
From: Sam Asadi
several style issues fixed.
Signed-off-by: Sam Asadi
modified: drivers/staging/comedi/drivers/adl_pci9118.c
---
drivers/staging/comedi/drivers/adl_pci9118.c | 124 +-
1 file changed, 62 insertions(+), 62 deletions(-)
diff --git
From: Kan Liang
x86, perf: Protect LBR and extra_regs against KVM lying
With -cpu host, KVM reports LBR and extra_regs support, if the host has
support.
When the guest perf driver tries to access LBR or extra_regs MSR,
it #GPs all MSR accesses,since KVM doesn't handle LBR and extra_regs
This patch adds reference counting for query handlers in order to eliminate
kmalloc()/kfree() usage.
Signed-off-by: Lv Zheng
Tested-by: Steffen Weber
---
drivers/acpi/ec.c | 46 --
1 file changed, 36 insertions(+), 10 deletions(-)
diff --git
This patch refines EC command storm prevention support.
Ideally, we should only enable storm prevention for the current command so
that the next command can try the efficient interrupt mode again.
Signed-off-by: Lv Zheng
---
drivers/acpi/ec.c | 21 +
1 file changed, 9
This patch refines event/query debugging messages to use a unified format
as commands. Developers can clearly find different processes by checking
different log seperators. No functional changes.
Signed-off-by: Lv Zheng
---
drivers/acpi/ec.c | 14 --
1 file changed, 8
On Tue, 2014-07-15 at 11:24 +0900, Masami Hiramatsu wrote:
> (2014/07/15 11:11), Michael Ellerman wrote:
> > On Mon, 2014-07-14 at 10:17 -0700, Tony Luck wrote:
> >> On Tue, Jul 8, 2014 at 5:07 AM, Masami Hiramatsu
> >> wrote:
> >>> Ping?
> >>>
> >>> This patch can be applied without 1/2, and
There are cases that BIOS doesn't provide _Qxx handler for the returned
query value, in this case, acpi_set_gpe(ACPI_GPE_DISABLE) need to be
invoked to prevent event IRQ storms.
This patch implements such storm prevention using new GPE APIs.
Signed-off-by: Lv Zheng
---
drivers/acpi/ec.c | 50
This patch splits query handler scheduling into a new seperate function
acpi_ec_notify_query_handlers() and adds a warning message in it to
indicate a BIOS bug. It is reported that EC event storm can happen in case
there is no handler prepared for the event. No functional changes.
Reference:
From: Sam Asadi
fixed a coding style issue.
Signed-off-by: Sam Asadi
modified: drivers/staging/comedi/drivers/8255.c
---
drivers/staging/comedi/drivers/8255.c | 150 -
1 file changed, 74 insertions(+), 76 deletions(-)
diff --git
This patch adds facility to test future EC modification.
All EC commits should enable TEST_HOTPLUG, and try a build/boot test.
Since EC is currently a built-in module, this is the only mean for us to
test the hotplug code.
Signed-off-by: Lv Zheng
---
drivers/acpi/ec.c | 19 +++
This patch implements command flushing support. It's better to wait all
command transactions to be completed before disabling the EC GPE when the
system is going to be suspended. By doing so, the EC hardware can be
ensured to be in the idle state when the system is resumed.
The system
This patch deploys the following GPE handling model:
1. acpi_enable_gpe()/acpi_disable_gpe():
This set of APIs are used for EC usage reference counting.
2. acpi_set_gpe(ACPI_GPE_ENABLE)/acpi_set_gpe(ACPI_GPE_DISABLE):
This set of APIs are used for preventing GPE storm.
Note that this patch
From: Kan Liang
With -cpu host KVM reports LBR and extra_regs support, so the perf driver may
accesses the LBR and extra_regs MSRs.
However, there is no LBR and extra_regs virtualization support yet. This could
causes guest to crash.
As a workaround, KVM just simply ignore the LBR and extra_regs
Developers really don't need to translate EC commands in mind. This patch
adds detailed debugging information for the EC commands.
The address can be found in the follow-up sequential EC_DATA(W) accesses,
thus this patch also removes some of the redundant address information.
Signed-off-by: Lv
By using the 2 flags, we can indicate an inter-mediate state where the
current transactions should be completed while the new transactions should
be blocked.
Signed-off-by: Lv Zheng
---
drivers/acpi/ec.c | 56 +++--
1 file changed, 42
This patchset is based on the previous ACPI/EC bug fixes series and the GPE
API enhancement series.
During the bug fix, there is a dmesg showing Linux EC driver doesn't
support EC event storm prevention.
https://bugzilla.kernel.org/show_bug.cgi?id=70891
The comment 55 contains the dmesg log
From: Sam Asadi
Signed-off-by: Sam Asadi
modified: drivers/staging/comedi/drivers/8253.h
---
drivers/staging/comedi/drivers/8253.h |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/comedi/drivers/8253.h
b/drivers/staging/comedi/drivers/8253.h
The stale GPE indication is not a problem. Drivers should always check the
underlying hardware status and be ready to handle invalid status.
The GPE clearing implemented in acpi_ev_enable_gpe() on the contrary
introduces issues for acpi_enable_gpe() logic. When the usage count of GPE is
increased
The acpi_os_wait_events_complete() is used for flushing the deferred executed
handlers, invoking it for GPE interrupt handlers doesn't help to protect
GPE handler callback. On the contrary, it prevents GPE APIs from being
invoked in the deferred notify handlers.
Actually, the GPE interrupt
Clearing the status bit means OSPM acknowledges the GPE and the hardware
then can bring follow-up events up. Acklowdging it too early causes OSPM
seeing level triggered GPE storms or missing edge-triggered GPEs if the
OSPM driver responds slowly. Some drivers may choose to implement GPE
condition
The originally_enabled check is not paired between acpi_install_gpe_handler()
and acpi_remove_gpe_handler(). Lv Zheng.
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/evxface.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git
The return value of ACPICA SCI will contain ACPI_REENABLE_GPE. This patch
cleans up the OSL code to reflect this change.
Signed-off-by: Lv Zheng
---
drivers/acpi/osl.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index
This can help to reduce source code differences between Linux and ACPICA
upstream. Further driver cleanups also require these APIs to eliminate GPE
storms.
1. acpi_set_gpe(): An API that driver should invoke in the case it wants
to disable/enable IRQ without honoring the
This patch adds unconditional GPE enabling support into acpi_set_gpe().
Originally this function checks if the GPE has been enabled with handlers
and performs acknowledging before enabling it.
First, IRQ enabling/disabling has 2 use cases:
1. When upper layers (the users of the driver) submit
This patchset enables the ideal GPE handling model. The ideal GPE handling
model should be able to handle the following cases:
1. When upper layers (the users of the driver) submit requests to the
drivers, it means they care about the underlying hardware. For this
case,
This patch reduces indent divergences first in order to reduce human
intervention work for the follow-up linuxized event patches.
This patch reduces indent divergences of the event files. Though the
divergences report doesn't care about these differences, they do hurt
patches maintanence.
The GPE APIs should be invoked inside of an IRQ context GPE handler or in
the task context with a driver provided lock held. This driver provided
lock should be safe to be held in the GPE handler by the driver.
While currently we cannot do this, thus we can only use the GPE APIs for
limitted
The p->u.board.status is allocated and set a string as
"No" once within allocating a node of BNODE type.
But it also set again with kstrdup() in case of "STATUS"
or "ID". If it is not allocated yet, use kstrdup().
If not, use just memcpy().
Signed-off-by: Daeseok Youn
---
When a configration file is parsed with dgap_parsefile(),
makes nodes for saving configrations for board.
Making a node will allocate node memory and strings for saving
configrations with kstrdup().
So these are freed when dgap is unloaded or failed to initialize.
Signed-off-by: Daeseok Youn
The dgap_err() is printing a message with pr_err(),
so all those are replaced.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c | 226 --
1 files changed, 108 insertions(+), 118 deletions(-)
diff --git a/drivers/staging/dgap/dgap.c
The dgap_newnode() is useless for creating new node.
So just use kzalloc and set a type in case statement.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c | 104 ++
1 files changed, 74 insertions(+), 30 deletions(-)
diff --git
The "p" as parameter is unused.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/dgap/dgap.c b/drivers/staging/dgap/dgap.c
index 17514c8..1e52092 100644
--- a/drivers/staging/dgap/dgap.c
On Mon, Jul 14, 2014 at 9:04 PM, Sylwester Nawrocki
wrote:
> On 11/07/14 14:00, Tushar Behera wrote:
>> @@ -103,17 +140,11 @@ static int exynos_audss_clk_probe(struct
>> platform_device *pdev)
>> return PTR_ERR(reg_base);
>> }
>>
>> - clk_table = devm_kzalloc(>dev,
>> -
The "boar" should be "board".
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/staging/dgap/dgap.c b/drivers/staging/dgap/dgap.c
index 470ae7b..17514c8 100644
--- a/drivers/staging/dgap/dgap.c
+++
If rc is zero, this function will returns with an error and
cannot reach switch-case statement.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/dgap/dgap.c b/drivers/staging/dgap/dgap.c
index
The retval in dgap_block_til_ready() is initialized to zero,
and if no error has occurred in this function, the retval has a zero.
So it doesn't need to check "retval" itself.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgap/dgap.c |5 +
1 files changed, 1 insertions(+), 4
Hi,
The data type of "host" is "struct mmc_host", and there is not "quirks" member
in this structure.
Thanks,
Zhonghui
On 2014/7/14 21:26, Chris Ball wrote:
> Hi Zhonghui,
>
> On Tue, Jul 08 2014, Fu, Zhonghui wrote:
>> Why add "mmc->caps2 |= MMC_CAP2_SDIO_IRQ_NOTHREAD;" ? How to fix this
On Mon, Jul 14, 2014 at 3:23 PM, H. Peter Anvin wrote:
> On 07/14/2014 02:35 PM, Andy Lutomirski wrote:
>> Presumably the problem is here:
>>
>> ENTRY(xen_iret)
>> pushq $0
>> 1:jmp hypercall_iret
>> ENDPATCH(xen_iret)
>>
>> This seems rather unlikely to work on the espfix stack.
>>
>>
From: Olivier Sobrie
Date: Mon, 14 Jul 2014 12:08:50 +0200
> When the module sends bursts of data, sometimes a deadlock happens in
> the hso driver when the tty buffer doesn't get the chance to be flushed
> quickly enough.
>
> Remove the endless while loop in function put_rxbuf_data() which is
From: Olivier Sobrie
Date: Mon, 14 Jul 2014 12:08:49 +0200
> The workqueue "retry_unthrottle_workqueue" is not scheduled anywhere
> in the code. So, remove it.
>
> Signed-off-by: Olivier Sobrie
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
(2014/07/15 11:11), Michael Ellerman wrote:
> On Mon, 2014-07-14 at 10:17 -0700, Tony Luck wrote:
>> On Tue, Jul 8, 2014 at 5:07 AM, Masami Hiramatsu
>> wrote:
>>> Ping?
>>>
>>> This patch can be applied without 1/2, and will fix ia64/ppc64 problem.
>>
>> Is somebody going to push this upstream?
On Mon, Jul 14, 2014 at 11:55:39AM +0200, Peter Zijlstra wrote:
> On Mon, Jul 14, 2014 at 05:37:13PM +0800, Xie Miao wrote:
> > Hi, Jason
> >
> > Could you re-sent this patch? Because it seems it is ignored.
>
> Its not ignored; its not merged because of unrelated stability issues.
Is it going
On Tue, 15 Jul 2014 12:05:55 +1000
Benjamin Herrenschmidt wrote:
> Cheers,
> Ben.
>
While I got your attention, could you please ack my patch with subject:
[RFA][PATCH 09/27] powerpc/ftrace: Add call to ftrace_graph_is_dead() in
function graph code
so that I can push it through my tree.
From: varkabhad...@gmail.com
Date: Mon, 14 Jul 2014 14:09:03 +0530
> This series cleanup for AMD8111E ethernet driver
>
> v1: fix checkpatch warnings.
> v2: added new line in debug messages
Series applied, thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Tue, 15 Jul 2014 12:05:55 +1000
Benjamin Herrenschmidt wrote:
> On Mon, 2014-07-14 at 20:12 -0400, Steven Rostedt wrote:
> > I wanted to test some new ftrace code on my PASemi electra powerpc box.
> > But unfortunately it failed to build. It failed with this:
> >
> > LD
On Mon, 2014-07-14 at 10:17 -0700, Tony Luck wrote:
> On Tue, Jul 8, 2014 at 5:07 AM, Masami Hiramatsu
> wrote:
> > Ping?
> >
> > This patch can be applied without 1/2, and will fix ia64/ppc64 problem.
>
> Is somebody going to push this upstream? Another week has gone by,
> we are at -rc5, and
Pages allocated using the DMA API have a coherent memory mapping. Make
this mapping visible to drivers so they can decide to use it instead of
creating their own redundant one.
This is not a mere optimization: for instance, on ARM it is illegal to
have several memory mappings to the same memory
On Mon, 2014-07-14 at 20:12 -0400, Steven Rostedt wrote:
> I wanted to test some new ftrace code on my PASemi electra powerpc box.
> But unfortunately it failed to build. It failed with this:
>
> LD init/built-in.o
> arch/powerpc/kernel/head_64.o:arch/powerpc/kernel/exceptions-64s.S:874:
>
On 07/15/2014 04:59 AM, Kees Cook wrote:
Hi James,
Is this series something you would carry in the security-next tree?
That has traditionally been where seccomp features have landed in the
past.
-Kees
On Fri, Jul 11, 2014 at 10:55 AM, Kees Cook wrote:
On Fri, Jul 11, 2014 at 9:49 AM, Oleg
On Mon, Jun 23, 2014 at 02:50:15PM -0500, Dinh Nguyen wrote:
> On Mon, 2014-06-23 at 14:21 -0500, Graham Moore wrote:
> > The Denali NAND driver reads only 5 bytes of ID, but some Hynix and Samsung
> > have size parameters in the 6th byte. As a result, the page and oob size
> > for a Hynix
On Sun, Jul 13, 2014 at 09:14:21PM +0100, Rob Ward wrote:
> From ae6ea29f112475aa1e2da20caabe36e318fd51c4 Mon Sep 17 00:00:00 2001
> From: Rob Ward
> Date: Sun, 13 Jul 2014 20:39:01 +0100
> Subject: [PATCH] mtd: phram: Fix whitespace issues
>
> Fix various whitespace issues.
>
> No functional
1 - 100 of 2130 matches
Mail list logo
