On Thu, Jul 30, 2015 at 04:35:58PM +0200, Maciej S. Szmigiero wrote:
> Adjust set DAI format function in fsl_ssi driver so it
> doesn't fail and clears RXDIR in AC'97 mode.
>
> Signed-off-by: Maciej Szmigiero
> ---
> sound/soc/fsl/fsl_ssi.c |8 +---
> 1 files changed, 5 insertions(+), 3
On 30-07-15, 22:51, Stephen Boyd wrote:
> > + opp->u_volt = microvolt[0];
> > + opp->u_volt_min = microvolt[1];
> > + opp->u_volt_max = microvolt[2];
>
> Should the default be 0 and ULONG_MAX for volt_min/volt_max when
> there's on element?
I am not still sure how the regulator API is
On Fri, Jul 31, 2015 at 07:27:19AM +0200, Markus Pargmann wrote:
> Hi,
>
> On Thu, Jul 30, 2015 at 04:34:19PM +0200, Maciej S. Szmigiero wrote:
> > AC'97 bus can support asymmetric playback/capture rates
> > so enable them in this case in fsl_ssi driver.
> >
> > Signed-off-by: Maciej Szmigiero
On 07/29, Viresh Kumar wrote:
> This adds support in OPP library to parse and create list of OPPs from
> operating-points-v2 bindings. It takes care of most of the properties of
> new bindings (except shared-opp, which will be handled separately).
>
> For backward compatibility, we keep
Hello, Mel.
On Mon, Jul 20, 2015 at 09:00:18AM +0100, Mel Gorman wrote:
> From: Mel Gorman
>
> High-order watermark checking exists for two reasons -- kswapd high-order
> awareness and protection for high-order atomic requests. Historically we
> depended on MIGRATE_RESERVE to preserve
Hi all,
Changes since 20150730:
The at91 tree gained a conflict against the arm-soc tree.
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 4897
4980 files changed, 244177 insertions(+), 113249 deletions
On Fri, 2015-07-31 at 11:02 +0530, Shraddha Barke wrote:
> This patch fixes the following checkpatch.pl warning:
>
> WARNING: do not add new typedefs
> Signed-off-by: Shraddha Barke
> ---
> drivers/staging/wilc1000/coreconfigurator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
Hi.
2015-07-30 10:30 GMT+09:00 Masahiro Yamada :
> Hi,
>
>
> 2015-07-30 0:23 GMT+09:00 Rob Herring :
>> On Wed, Jul 29, 2015 at 8:22 AM, Ian Campbell
>> wrote:
>>> On Wed, 2015-07-29 at 20:07 +0900, Masahiro Yamada wrote:
Hi Ian,
2015-07-27 19:35 GMT+09:00 Ian Campbell :
On Thu, Jul 30, 2015 at 04:35:23PM +0200, Maciej S. Szmigiero wrote:
> Instantiate AC'97 CODEC in fsl_ssi driver AC'97 mode.
>
> Signed-off-by: Maciej Szmigiero
> ---
> sound/soc/fsl/fsl_ssi.c | 21 +
> 1 files changed, 21 insertions(+), 0 deletions(-)
>
> diff --git
On 07/29, Viresh Kumar wrote:
> Later commits would add support for new OPP bindings and this would be
> required then. So, lets do it in a separate patch to make it easily
> reviewable.
>
> Another change worth noticing is INIT_LIST_HEAD(>node). We weren't
> doing it earlier as we never tried to
This patch fixes the following checkpatch.pl warning:
WARNING: do not add new typedefs
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
This patch fixes the following checkpatch.pl warning:
WARNING: do not add new typedefs
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
On 31 Jul 2015 10:49, "Shraddha Barke" wrote:
>
> This patch fixes the following checkpatch.pl warning:
>
> WARNING: braces {} are not necessary for single statement blocks
There should be one line space between your commit log
and Signed-off-by line.
> Signed-off-by: Shraddha Barke
> ---
>
Hi,
On Thu, Jul 30, 2015 at 04:34:19PM +0200, Maciej S. Szmigiero wrote:
> AC'97 bus can support asymmetric playback/capture rates
> so enable them in this case in fsl_ssi driver.
>
> Signed-off-by: Maciej Szmigiero
> ---
> sound/soc/fsl/fsl_ssi.c |4 +++-
> 1 files changed, 3
This patch fixes the following checkpatch.pl warning:
WARNING: Missing a blank line after declarations
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
On 30-07-15, 15:04, Christoph Lameter wrote:
> You need to CC someone at SGI for this I guess. Robin? Nate? Dimitri?
>
> I am definitely not the right guy to be on the CC list.
Sorry about that. It happened because get_maintainers failed to
identify those people. Probably MAINTAINERS need some
Alexander Shishkin writes:
> Alexander Shishkin writes:
>
>> Alexander Shishkin writes:
>>
>>> Hi Greg and everybody,
>>
>> Seems like a polite nudge might be in order. :)
>
> Greg.
Ping.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This patch fixes the following checkpatch.pl warning:
WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
On Thu, Jul 30, 2015 at 9:22 PM, Borislav Petkov wrote:
> On Thu, Jul 30, 2015 at 02:22:06PM -0700, Andy Lutomirski wrote:
>> Great. There's an opcode that invokes an interrupt gate that's not
>> marked as allowing unprivileged access, and that opcode doesn't appear
>> in the SDM. It appears in
Sure, I'll do that. Just wanted to know whether I should split the patches and
send them in this same mail thread (may be something like [PATCH 01/04 V2])
or should I start new threads and send them separately to the respective
maintainers.
Thanks and Regards,
Saurabh Karajgaonkar
On Thu, Jul
On Thu, Jul 30, 2015 at 06:25:06PM +0200, Jan Lübbe wrote:
> On Mi, 2015-07-29 at 17:03 +0800, Haibo Chen wrote:
> > tuning-step is the delay cell steps in tuning procedure. The default
> > value of tuning-step is 1. For imx6 series usdhc, tuning procedure can
> > be passed when the tuning-step
Jan Kara writes:
>> > Yes, if userspace truncates the file, the situation we end up with is
>> > basically the same. However for truncate to happen some malicious process
>> > has to come and truncate the file - a failure scenario that is acceptable
>> > for most use cases since it doesn't
rcu: Don't disable preemption for Tiny and Tree RCU readers
Because preempt_disable() maps to barrier() for non-debug builds,
it forces the compiler to spill and reload registers. Because Tree
RCU and Tiny RCU now only appear in CONFIG_PREEMPT=n builds, these
barrier() instances generate
On Thu, 11 Jun 2015, Peter Zijlstra wrote:
> Right, I had a peek earlier at how fasync worked but came away confused.
>
> Today I seem to have had better luck. Installing fasync allocates memory
> and sets filp->f_flags |= FASYNC, which upon the demise of the file
> descriptor ensures the
Hi Florian,
On 07/31/2015 01:51 PM, Florian Fainelli wrote:
> On 30/07/15 15:51, David Miller wrote:
>> From: David Miller
>> Date: Thu, 30 Jul 2015 14:19:35 -0700 (PDT)
>>
>>> This looks fine, series applied, thanks.
>>
>> I think your control block is too large, you'll need to rework this
>>
On Thu, Jul 30, 2015 at 02:22:06PM -0700, Andy Lutomirski wrote:
> Great. There's an opcode that invokes an interrupt gate that's not
> marked as allowing unprivileged access, and that opcode doesn't appear
> in the SDM. It appears in the APM opcode map with no explanation at
> all.
>
> Thanks,
> On Jul 30, 2015, at 20:02, Neil Horman wrote:
>
> On Thu, Jul 30, 2015 at 11:48:17AM +0800, yalin wang wrote:
>>
>>> On Jul 29, 2015, at 18:34, Thomas Gleixner wrote:
>>>
>>> On Tue, 28 Jul 2015, Andrew Morton wrote:
>>>
On Tue, 28 Jul 2015 11:59:01 -0400 David Kershner
wrote:
On Fri, 2015-17-07 at 13:20:31 UTC, Luis Henriques wrote:
> After commit 0fd972a7d91d ("module: relocate module_init from init.h to
> module.h")
> ans-lcd module fails to build with:
>
> drivers/macintosh/ans-lcd.c:201:1: warning: data definition has no type or
> storage class [enabled by
On Mon, 2015-20-07 at 10:45:51 UTC, Alexey Kardashevskiy wrote:
> The existing code stores the amount of memory allocated for a TCE table.
> At the moment it uses @offset which is a virtual offset in the TCE table
> which is only correct for a one level tables and it does not include
> memory
On Thu, Jul 30, 2015 at 11:12:44AM -0700, Andy Lutomirski wrote:
> On Thu, Jul 30, 2015 at 6:09 AM, cee1 wrote:
> > Hi all,
> >
> > I'm interested in the idea of AF_BUS.
> >
> > There have already been varies discussions about it:
> > * Missing the AF_BUS - https://lwn.net/Articles/504970/
> > *
Hi Roger,
I add minor comment about code clean.
After I modified it by myself, I applied it on extcon-fixes.
Best Regards,
Chanwoo Choi
On 07/07/2015 10:06 PM, Roger Quadros wrote:
> Users of find_cable_index_by_name() will cause a kernel hang
> as the while loop counter is never incremented
On Thu, Jul 30, 2015 at 11:12 AM, Joe Stringer wrote:
> Signed-off-by: Joe Stringer
> ---
> net/openvswitch/vport.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/openvswitch/vport.c b/net/openvswitch/vport.c
> index d14f594..baa018f 100644
> --- a/net/openvswitch/vport.c
> +++
Range breakpoints will do the wrong thing if the address isn't
aligned. While we're there, add comments about why it's safe for
instruction breakpoints.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/hw_breakpoint.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
Hi, Peter-
Here are some baby steps toward eliminating nested NMIs. What do
you think?
Andy Lutomirski (3):
x86/perf/hw_breakpoint: Disallow kernel breakpoints unless kprobe-safe
x86/perf/hw_breakpoint: Improve range breakpoint validation
x86/perf/hw_breakpoint: Fix check for kernelspace
Code on the kprobe blacklist doesn't want unexpected int3
exceptions. It probably doesn't want unexpected debug exceptions
either. Be safe: disallow breakpoints in nokprobes code.
On non-CONFIG_KPROBES kernels, there is no kprobe blacklist. In
that case, disallow kernel breakpoints entirely.
The check looked wrong, although I think it was actually safe. TASK_SIZE
is unnecessarily small for compat tasks, and it wasn't possible to make
a range breakpoint so large it started in user space and ended in kernel
space.
Nonetheless, let's fix up the check for the benefit of future
readers.
Hi Linus,
this is the fixes pull for -rc5,
it has a bunch of nouveau fixes, as Ben has been hibernating and has lots
of small fixes for lots of bugs across nouveau.
radeon has one major fix for hdmi/dp audio regression that is larger than
Alex would like, but seems to fix up a fair few bugs,
The common kernel.h has already supplied it.
Signed-off-by: Peter Chen
---
drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/cxgbi/cxgb4i/cxgb4i.c
b/drivers/scsi/cxgbi/cxgb4i/cxgb4i.c
index de6feb8..908399a 100644
---
The UEFI driver would enable zero length, and the Linux driver doesn't
need it. Zero length let the hw complete the transfer with length 0,
when there is no received packet. It would add the load of USB host
controller and reduce the performance.
Signed-off-by: Hayes Wang
---
Thanks.
I will try to add more layman terms here to map cooling state with
frequencies. So, the cooling state 0 maps to the highest frequency the
cpufreq table supports, and the highest cooling state n maps to the
lowest frequency. Right ?
On 30-07-15, 13:21, Radivoje Jovanovic wrote:
> In this
On Wed, Jul 29, 2015 at 5:15 PM, Marc Zyngier wrote:
>
> On 29/07/15 09:52, Ley Foon Tan wrote:
> > On Wed, Jul 29, 2015 at 1:58 AM, Marc Zyngier wrote:
> >> Hi Ley,
> >>
> >> On 28/07/15 11:45, Ley Foon Tan wrote:
> >>> This patch adds Altera PCIe MSI driver. This soft IP supports configurable
Hi,
On Thu, 30 Jul 2015 11:23:17 +0200
Antoine Tenart wrote:
> Add a PWM controller driver for the Marvell Berlin SoCs. This PWM
> controller has 4 channels.
>
> Signed-off-by: Antoine Tenart
> ---
> drivers/pwm/Kconfig | 9 +++
> drivers/pwm/Makefile | 1 +
>
On Thu, Jul 30, 2015 at 3:50 PM, Andrew Cooper
wrote:
> On 30/07/2015 22:31, Andy Lutomirski wrote:
>> Note to -stable maintainers: by itself, this patch makes a
>> pre-existing Xen bug much easier to trigger; on a 32-bit Xen guest,
>> the new ldt_gdt selftest is likely to OOPS. Even without
On Thu, Jul 30, 2015 at 12:42 PM, Christoph Hellwig wrote:
> On Thu, Jul 30, 2015 at 07:36:24AM -0400, Ming Lei wrote:
>> + /*
>> + * When working at direct I/O, under very unusual cases,
>> + * such as unaligned direct I/O from application and
>> + * access to loop block
On Wed, 2015-07-22 at 16:14 +0800, Yingjoe Chen wrote:
> Spurious mtk timer interrupt is noticed at boot and cause kernel
> crash. It seems if GPT is enabled, it will latch irq status even
> when its IRQ is disabled. When irq is enabled afterward, we see
> spurious interrupt.
> Change init flow to
Hi Michal Nazarewicz,
Thanks for the review.
On Thu, 2015-07-30 at 15:59 +0200, Michal Nazarewicz wrote:
> On Thu, Jul 30 2015, Feng Tang wrote:
> > When system(one x86 soc) boot, we saw many normal dma allocation requests
> > goes to cma area. The call chain is
> >
Hi, list
Ping..., any feedback for this series?
Best Regards,
Josh Wu
On 6/17/2015 6:39 PM, Josh Wu wrote:
In the function configure_geometry(), we will setup the ISI CFG2
according to the sensor output format.
It make no sense to just read back the CFG2 register and just set part
of it.
So
On 07/30/2015 10:16 PM, Waiman Long wrote:
On 07/29/2015 06:21 PM, Eric W. Biederman wrote:
Two quick questions.
- What motivates this work? Are you seeing lots of
parallel reads on proc?
The micro-benchmark that I used was artificial, but it was used to
reproduce an exit hanging
On Thu, Jul 30, 2015 at 11:26:28PM +, Zhang, Yang Z wrote:
> Paolo Bonzini wrote on 2015-07-29:
> > Do not compute TMR in advance. Instead, set the TMR just before the
> > interrupt is accepted into the IRR. This limits the coupling between
> > IOAPIC and LAPIC.
> >
>
> Uh.., it back to
On Thu, 2015-07-30 at 21:29 +0200, Jonas Gorski wrote:
> Hi,
>
> On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> > Change in v4:
> > 1. fix Mark Brown review comment.
>
> You should say what you actually fixed/changed, not just that you
> changed something. Also the individual patches
Hi Jonas,
On Thu, 2015-07-30 at 21:27 +0200, Jonas Gorski wrote:
> Hi,
>
> On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> > Signed-off-by: Leilk Liu
> > ---
> > .../devicetree/bindings/spi/spi-mt65xx.txt | 38
> > ++
> > 1 file changed, 38 insertions(+)
> >
Hello
I have good news for you.
Your long awaited package containing $10.5 Million is en-route your address.
It will be delivered via Diplomatic Armored Vehicle. The Diplomatic Armored
Company has delegated an official to effect the delivery of the package to you.
So, you need to confirm
On 07/29/2015 06:21 PM, Eric W. Biederman wrote:
Two quick questions.
- What motivates this work? Are you seeing lots of
parallel reads on proc?
The micro-benchmark that I used was artificial, but it was used to
reproduce an exit hanging problem that I saw in real application. In
fact,
From: Alexey Brodkin
This patch has been added to the 3.18 stable tree. If you have any
objections, please let us know.
===
[ Upstream commit f51e2f1911122879eefefa4c592dea8bf794b39c ]
Currently instruction_pointer() returns pt_regs->ret and so return value
is of type "long",
The PCI subsystem always assumes that I/O is supported on PCIe bridges
and tries to assign an I/O window to each child bus even if that is not
the case.
This may result in messages such as:
pcieport :02:00.0: res[7]=[io 0x1000-0x0fff] get_res_add_size add_size
1000
pcieport
Hi Linus,
Can you please pull the XFS fixes from the tag below? There are a
couple of recently found, long standing remote attribute corruption
fixes caused by log recovery getting confused after a crash, and the
new DAX code in XFS (merged in 4.2-rc1) needs to actually use the
DAX fault path on
On 07/30/2015 10:44 AM, Peter Zijlstra wrote:
On Fri, Jul 17, 2015 at 04:29:24PM -0700, Paul E. McKenney wrote:
/*
+* First try directly acquiring the root lock in order to reduce
+* latency in the common case where expedited grace periods are
+* rare. We check
On Thu, Jul 30, 2015 at 5:54 PM, Pablo Neira Ayuso wrote:
> On Sun, Jul 26, 2015 at 05:27:37PM +0530, Vaishali Thakkar wrote:
>> For simple modules that contain a single xt_match without any
>> additional setup code then ends up being a block of duplicated
>> boilerplate. This patch adds a new
On 30/07/15 15:51, David Miller wrote:
> From: David Miller
> Date: Thu, 30 Jul 2015 14:19:35 -0700 (PDT)
>
>> This looks fine, series applied, thanks.
>
> I think your control block is too large, you'll need to rework this
> somehow.
So napi_gro_cb really is 48 bytes on 64-bits architectures
Dmitry,
Thank your very much.
Thanks,
Dudley
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 2015?7?31? 2:33
> To: Dudley Du
> Cc: mark.rutl...@arm.com; robh...@kernel.org; ble...@google.com;
> jmmah...@gmail.com; devicet...@vger.kernel.org;
On Thu, 2015-07-30 at 22:53 +0800, Henry Chen wrote:
> Implement the suspend/resume function in order to control rtc's irq_wake flag
> and handle as wakeup source.
>
> Signed-off-by: Henry Chen
> ---
> drivers/rtc/rtc-mt6397.c | 26 ++
> 1 file changed, 26 insertions(+)
On 07/31/2015 12:59 AM, Greg KH wrote:
On Thu, Jul 30, 2015 at 05:45:44PM +0100, Matt Fleming wrote:
On Thu, 30 Jul, at 09:31:02AM, Greg KH wrote:
Why isn't this an issue in newer kernel releases? Did this already get
fixed by some other patch? If so, why can't we just take that patch?
If
Signed-off-by: Moritz Fischer
---
arch/arm/boot/dts/zynq-7000.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.dtsi
index 0691508..6bebf02 100644
--- a/arch/arm/boot/dts/zynq-7000.dtsi
+++
Signed-off-by: Moritz Fischer
---
arch/arm/mach-zynq/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-zynq/Kconfig b/arch/arm/mach-zynq/Kconfig
index 78e5e00..77d7df7 100644
--- a/arch/arm/mach-zynq/Kconfig
+++ b/arch/arm/mach-zynq/Kconfig
@@ -1,5 +1,6 @@
config
This adds a reset controller driver to control the Xilinx Zynq
AP-SoC's various resets.
Signed-off-by: Moritz Fischer
---
drivers/reset/Makefile | 1 +
drivers/reset/reset-zynq.c | 155 +
2 files changed, 156 insertions(+)
create mode 100644
Signed-off-by: Moritz Fischer
---
.../devicetree/bindings/reset/zynq-reset.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/zynq-reset.txt
diff --git a/Documentation/devicetree/bindings/reset/zynq-reset.txt
Hi all,
I made another RFC addressing most of the feedback that I got so far.
I haven't completly given up on Sören's idea of getting rid of having
some sort of protection against people using wrong bits by accident,
but haven't come up with a clean way to do so yet (especially when looking at
On Thu, 2015-07-30 at 21:10 +0800, Axel Lin wrote:
Hi Axel,
Oh..it was 1.4V on data sheet, but I think you're right, MT6311_MAX_UV
should be 1393750 was more precisely, I will change that.
Thanks.
> Hi Henry,
> Seems something wrong in either buck_volt_range or MT6311_MAX_UV setting.
>
>
Almost description is copied from commit fb05e7a89f50
("net: don't wait for order-3 page allocation").
I saw excessive direct memory reclaim/compaction triggered by slub.
This causes performance issues and add latency. Slub uses high-order
allocation to reduce internal fragmentation and
On 07/30/2015 11:41 AM, Pali Rohár wrote:
CPU fan speed going up and down on Dell Studio XPS 8100 for
unknown reason. Without future debuggning on affected machine
it is not possible to detect where is problem. For more see:
https://bugzilla.kernel.org/show_bug.cgi?id=100121
Signed-off-by: Pali
On Thu, Jul 30, 2015 at 06:02:34PM -0700, Josh Triplett wrote:
> On Thu, Jul 30, 2015 at 01:03:43PM -0700, Kees Cook wrote:
> > On Thu, Jul 30, 2015 at 12:04 PM, Josh Triplett
> > wrote:
> > > On Thu, Jul 30, 2015 at 11:21:54AM -0700, Kees Cook wrote:
> > >> I like this, it's a good description
On Thu, Jul 30, 2015 at 01:03:43PM -0700, Kees Cook wrote:
> On Thu, Jul 30, 2015 at 12:04 PM, Josh Triplett wrote:
> > On Thu, Jul 30, 2015 at 11:21:54AM -0700, Kees Cook wrote:
> >> I like this, it's a good description of both options. I'm still biased
> >> about the approach: I prefer flags,
The hugetlb selftests provide minimal coverage. Have run script
point people at libhugetlbfs for better regression testing.
Signed-off-by: Mike Kravetz
---
tools/testing/selftests/vm/run_vmtests | 4
1 file changed, 4 insertions(+)
diff --git a/tools/testing/selftests/vm/run_vmtests
This manually reverts 7e50533d4b84289e4f01de56d6f98e9c64e2229e
The hugetlbfstest test depends on hugetlb pages being counted
in a task's rss. This functionality is not in the kernel, so
the test will always fail. Remove test to avoid confusion.
Signed-off-by: Mike Kravetz
---
The URL for libhugetlbfs has changed. Also, put a stronger emphasis
on using libgugetlbfs for hugetlb regression testing.
Signed-off-by: Mike Kravetz
---
Documentation/vm/hugetlbpage.txt | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git
As a followup to discussions of hugetlbfs fallocate, this provides
cleanup the vm hugetlb selftests. Remove hugetlbfstest as it tests
functionality not present in the kernel. Emphasize that libhugetlbfs
test suite should be used for hugetlb regression testing.
Mike Kravetz (3):
Reverted
On 07/30/2015 09:18 AM, Javier Martinez Canillas wrote:
The I2C core always reports the MODALIAS uevent as "i2c:
Applied.
Thanks,
Guenter
--
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
On 07/30/2015 09:18 AM, Javier Martinez Canillas wrote:
The I2C core always reports the MODALIAS uevent as "i2c:
Applied.
Thanks,
Guenter
--
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
Hi John,
On 07/30/2015 06:54 PM, John Ogness wrote:
> If DMA is active during a shutdown, a delayed restore of the
> registers may be pending. The restore must be performed after
> the DMA is stopped, otherwise the delayed restore remains
> pending and will fire upon the first DMA TX complete of
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/ti/netcp_ethss.c
between commit:
31a184b7acbc ("net: netcp: ethss: cleanup gbe_probe() and gbe_remove()
functions")
from the net tree and commit:
489e8a2f09d7 ("net: netcp: Fixes to CPSW
On Tue, Jul 28 2015 at 01:40:19 PM, Andrew Morton
wrote:
> On Mon, 27 Jul 2015 16:57:32 -0700 Ashutosh Dixit
> wrote:
>
>> From: Harish Chegondi
>>
>> This patch converts iova.c into a library, moving it from
>> drivers/iommu/ to lib/, and exports its virtual address allocation
>> and
On Thu, Jul 30 2015 at 7:14pm -0400,
Josh Boyer wrote:
> On Thu, Jul 30, 2015 at 7:27 AM, Josh Boyer wrote:
> > On Wed, Jul 29, 2015 at 8:29 PM, Ming Lei wrote:
> >> On Wed, Jul 29, 2015 at 12:36 PM, Josh Boyer
> >> wrote:
> >>> On Wed, Jul 29, 2015 at 11:32 AM, Ming Lei wrote:
> On
On 30/07/15 22:45, Peter Hurley wrote:
[ +cc Debian maintainer ]
On 07/30/2015 11:26 AM, Emil Velikov wrote:
On 30 July 2015 at 16:02, Ilia Mirkin wrote:
On Thu, Jul 30, 2015 at 10:56 AM, Bryan O'Donoghue
wrote:
On 30/07/15 15:52, Bryan O'Donoghue wrote:
On 30/07/15 15:49, Peter Hurley
On Thu, Jul 30, 2015 at 12:20:40PM -0400, Nicholas Krause wrote:
>
> diff --git a/net/ipv6/xfrm6_policy.c b/net/ipv6/xfrm6_policy.c
> index ed0583c..f60c670 100644
> --- a/net/ipv6/xfrm6_policy.c
> +++ b/net/ipv6/xfrm6_policy.c
> @@ -61,7 +61,9 @@ static int xfrm6_get_saddr(struct net *net,
>
Hi,
While testing builds containing this change (commit id:
92923ca3aacef63c92dc297a75ad0c6dfe4eab37), I've observed that memory fails to
come online in the hotplug case. When attempting to bring the hot added pages
online (via udev rules or manually writing to sysfs); it's failing with -EBUSY
Hi Paul,
On Thu, 30 Jul 2015 11:32:05 -0400 Paul Gortmaker
wrote:
>
> Well, it only shows up when we cross compile for mips. It does not
> seem to be showing up for any other arch (and we cover ~10 of them).
> Nor does it show up for x86 builds. Also note that the main linux-next
> build
On 07/30/2015 07:15 PM, Peter Hurley wrote:
> On 07/30/2015 06:54 PM, John Ogness wrote:
>> uart_write_wakeup() should be called without holding the port lock.
>> Otherwise a possible recursive spinlock issue can occur, such as
>> the following callchain:
>>
>> 8250_core.c:serial8250_tx_chars() -
On 07/30/2015 06:12 PM, Thomas Gleixner wrote:
> On Thu, 30 Jul 2015, Peter Hurley wrote:
>> Honestly, I'm not too sure this is the way to go.
>>
>> Messing around with irqsoff tracer for 30 mins turned up:
>> 3.664ms in intel_unmap_page
>> - iotlb flush, spinlock contention on iova_rbtree_lock
On Thu, Jul 30 2015 at 6:59pm -0400,
Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman
>
> With well over 200+ users of this api, there are a mere 12 users that
> actually cheked the return value of this function. And all of them
> really didn't do anything with that information as the
Paolo Bonzini wrote on 2015-07-29:
> Do not compute TMR in advance. Instead, set the TMR just before the
> interrupt is accepted into the IRR. This limits the coupling between
> IOAPIC and LAPIC.
>
Uh.., it back to original way which is wrong. You cannot modify the apic
page(here is the TMR
On 07/30/2015 06:54 PM, John Ogness wrote:
> That bitfield is modified by read + or + write operation. If someone
> sets any of the other two bits it might render the lock useless.
Good catch.
Let's just make all of the fields not bitfield though.
Regards,
Peter Hurley
> Signed-off-by: John
On 30/07/15 15:51, David Miller wrote:
> From: David Miller
> Date: Thu, 30 Jul 2015 14:19:35 -0700 (PDT)
>
>> This looks fine, series applied, thanks.
>
> I think your control block is too large, you'll need to rework this
> somehow.
Interesting, this only seems to show up with 64-bits build,
On 30 July 2015 at 11:40, Thomas Graf wrote:
> On 07/30/15 at 11:12am, Joe Stringer wrote:
>> Signed-off-by: Joe Stringer
>
> Can you write a few lines on why this is needed? I have flows which
> use the mark to communicate with netfilter through internal ports.
The problem I was seeing is when
On 07/30/2015 06:54 PM, John Ogness wrote:
> uart_write_wakeup() should be called without holding the port lock.
> Otherwise a possible recursive spinlock issue can occur, such as
> the following callchain:
>
> 8250_core.c:serial8250_tx_chars() - called with port locked
>
On Thu, Jul 30, 2015 at 7:27 AM, Josh Boyer wrote:
> On Wed, Jul 29, 2015 at 8:29 PM, Ming Lei wrote:
>> On Wed, Jul 29, 2015 at 12:36 PM, Josh Boyer
>> wrote:
>>> On Wed, Jul 29, 2015 at 11:32 AM, Ming Lei wrote:
On Wed, Jul 29, 2015 at 9:51 AM, Johannes Weiner
wrote:
> On
On Thu, Jul 30, 2015 at 10:00:34AM -0700, David Miller wrote:
> From: Nathan Sullivan
> Date: Thu, 30 Jul 2015 10:15:48 -0500
>
> > Changes for V2: Actually make sure it compiles this time.
>
> If V1 didn't compile, even for you, then I have a big problem.
>
> And that problem is that you
On Thu, 30 Jul 2015, Marcelo Tosatti wrote:
On Thu, Jul 30, 2015 at 10:47:23AM -0700, Vikas Shivappa wrote:
Marcello,
On Wed, 29 Jul 2015, Marcelo Tosatti wrote:
How about this:
desiredclos (closid p1 p2 p3 p4)
1 1 0 0 0
2 0 0 0 1
From: Sowmini Varadhan
Date: Thu, 30 Jul 2015 15:50:36 +0200
>
>
> The newsk returned by sk_clone_lock should hold a get_net()
> reference if, and only if, the parent is not a kernel socket
> (making this similar to sk_alloc()).
>
> E.g,. for the SYN_RECV path,
On Thu, 30 Jul 2015, Andy Lutomirski wrote:
> On Thu, Jul 30, 2015 at 8:41 AM, Paolo Bonzini wrote:
> >
> >
> > On 24/07/2015 23:08, Andy Lutomirski wrote:
> >> user_icebp is set if int $0x01 happens, except it isn't because user
> >> code can't actually do that -- it'll cause #GP instead.
>
From: Greg Kroah-Hartman
With well over 200+ users of this api, there are a mere 12 users that
actually cheked the return value of this function. And all of them
really didn't do anything with that information as the system or module
was shutting down no matter what.
So stop pretending like it
1 - 100 of 1786 matches
Mail list logo
