In the cpu_load decay usage, we mixed the long term, short term load with
balance bias, randomly pick a big/small value from them according to balance
destination or source. This mix is wrong, the balance bias should be based
on task moving cost between cpu groups, not on random history or
On Thu, 13 Mar 2014 04:29:34 + Al Viro wrote:
> On Thu, Mar 13, 2014 at 03:08:00PM +1100, NeilBrown wrote:
> > + inode = mddev->bitmap_info.file->f_mapping->host;
> > + if (!S_ISREG(inode->i_mode)) {
> > + printk(KERN_ERR "%s: error: bitmap file must be
sparse reported dgap_do_fep_load is redeclared with different type. while
fixing, I noticed __user attribute is used incorrectly in declaration.
There is no need to define __user for firware->data.
Replaced the __user with 'const uchar *' from function dgap_do_fep_load and
did the same for
This patch adds LP8860 backlight device driver.
LP8860 is a low EMI and High performance 4 channel LED Driver of TI.
This device driver provides the way to control brightness and current
of each channel and provides the way to change values in the eeprom.
Signed-off-by: Daniel Jeong
---
Thank you for your comments
On Monday, March 03, 2014 6:15 PM, Daniel Jeong wrote:
(+CC Bryan Wu, Lee Jones)
Please add Bryan Wu, Lee Jones to CC list, when you send
patches for backlight.
This patch adds LP8860 backlight device driver.
LP8860 is a low EMI and High performance 4 channel
On Fri, 2014-02-28 at 14:03 +1100, James Morris wrote:
> Ok, which tree should take this? I'm happy to, although most of it is
> outside security/ .
Should I be looking for someone else to take them instead? :)
--
Matthew Garrett
On Mon, Mar 10, 2014 at 9:54 PM, Mika Westerberg
wrote:
> Sometimes it is useful to allow GPIO chips themselves to request GPIOs they
> own through gpiolib API. One use case is ACPI ASL code that should be able
> to toggle GPIOs through GPIO operation regions.
>
> We can't use gpio_request()
Kees Cook writes:
> Why not just do this with 0-base-address detection like my v2? That
> would mean we don't need to remember to add this flag in the future to
> imagined new architectures that might want this 0-based per_cpu
> feature.
Because future architectures will get this right and emit
On Thu, Mar 13, 2014 at 03:08:00PM +1100, NeilBrown wrote:
> + inode = mddev->bitmap_info.file->f_mapping->host;
> + if (!S_ISREG(inode->i_mode)) {
> + printk(KERN_ERR "%s: error: bitmap file must be a
> regular file\n",
> +
On Wed, Mar 12, 2014 at 08:03:03PM -0700, Andrew Morton wrote:
> On Thu, 13 Mar 2014 11:46:17 +0900 Joonsoo Kim wrote:
>
> > + while (n >= PAGE_SIZE) {
> > + /*
> > +* discard request can be too large so that the zram can
> > +* be stucked for a long time if
Hi Bartlomiej,
On 03/13/2014 11:15 AM, Chanwoo Choi wrote:
> Hi Batlomiej,
>
> On 03/13/2014 12:17 AM, Bartlomiej Zolnierkiewicz wrote:
>>
>> Hi,
>>
>> On Wednesday, March 12, 2014 08:48:01 PM Chanwoo Choi wrote:
>>> There are not the clock controller of ppmudmc0/1. This patch control the
>>>
於 三，2014-03-12 於 20:59 -0700，H. Peter Anvin 提到：
> On 03/12/2014 08:55 PM, joeyli wrote:
> >
> > So do not care "CMOS RTC Not Present", if TAD is present then we use it
> > instead of CMOS RTC in all kernel code? or we still can use CMOS RTC?
> >
>
> Why would we use *both*!? How would that
On Wed, Feb 26, 2014 at 10:02:40AM +0100, Alexander Gordeev wrote:
> Changes since v1:
> - cciss: patch #1: a weird 'goto' removed;
> - cciss: patch #2: pci_enable_msix_exact() used, not
> pci_enable_msix_range();
> - rsxx: patch dropped - no need to change anything;
>
> As result of
On Wed, 12 Mar 2014 18:19:25 + Al Viro wrote:
> On Tue, Mar 11, 2014 at 12:05:09PM -0700, Linus Torvalds wrote:
> >
> > which returns ETXTBSY (most easily seen by just stracing it).
> >
> > The patch would also seem to make sense, with the i_readcount_inc()
> > being immediately below for
On Mon, Feb 24, 2014 at 09:02:00AM +0100, Alexander Gordeev wrote:
> Hello!
>
> This series is against James Bottomley's SCSI tree [1], but it needs
> commit f7fc32c ("PCI/MSI: Add pci_enable_msi_exact() and
> pci_enable_msix_exact()") from from Bjorn Helgaas's PCI tree [2]:
>
> 1.
On 03/12/2014 08:55 PM, joeyli wrote:
>
> So do not care "CMOS RTC Not Present", if TAD is present then we use it
> instead of CMOS RTC in all kernel code? or we still can use CMOS RTC?
>
Why would we use *both*!? How would that possibly make sense?
-hpa
--
To unsubscribe from this
於 三，2014-03-12 於 20:11 -0700，H. Peter Anvin 提到：
> On 03/12/2014 07:38 PM, joeyli wrote:
> >
> > I sent rtc-acpitad driver for RTC subsystem on last month, I will send
> > second version.
> >
> > For using TAD to set wall clock is because in ACPI 5.0 spec, there have
> > a "CMOS RTC Not Present"
On Thu, Mar 06, 2014 at 09:11:22PM +0100, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() or
On 03/12/2014 04:11 PM, stef...@seibold.net wrote:
>
> I will do this when your patch is pulled into tip. For now we have the
> choice, but i preferer our solution removing the compat vdso.
>
Sorry, that didn't parse from me.
Also, if you state a preference, could you please motivate it?
On Wed, Mar 12, 2014 at 6:34 AM, Liu Shuo wrote:
> From: Liu ShuoX
>
> After sucessful decompressing, the buffer which pointed by 'buf' will be
> lost as 'buf' is overwrite by 'big_oops_buf' and will never be freed.
> Signed-off-by: Liu ShuoX
Thanks again!
Acked-by: Kees Cook
-Kees
> ---
>
On 03/12/2014 05:54 PM, Thomas Gleixner wrote:
>
> From the timekeeping POV there is absolutely no need to set the wall
> clock time early. The kernel boot phase does not care about wall time
> at all. We should have it done before we hit userspace, but not even
> that is a hard requirement.
>
For slow CPU, the frequent bulk transfer would cause poor throughput.
One solution is to increase the timeout of the aggregation. It let
the hw could complete the bulk transfer later and fill more packets
into the buffer. Besides, it could reduce the frequency of the bulk
transfer efficiently and
Add opportunity to change the default setting and reduce the tx/rx
buffers.
v2: modify the patch #1 to let the value readable.
Hayes Wang (2):
r8152: add RTL8152_EARLY_AGG_TIMEOUT_SUPER
r8152: reduce the numbers of the bulks
drivers/net/usb/Kconfig | 11 +++
drivers/net/usb/r8152.c
It is not necessary to have many transfer buffers. Reduce the number
from 10 to 4.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 293b4d8..1826fcf 100644
---
On Wed, Mar 12, 2014 at 2:15 AM, Pablo Neira Ayuso wrote:
> Hi!
>
> I'm going to reply to Daniel and you in the same email, see below.
>
> struct sk_filter
> {
> atomic_trefcnt;
> - unsigned intlen;/* Number of filter blocks */
> + /* len -
Steven Rostedt writes:
> Mathieu, you should have added a v2 to the subject ie: [PATCH V2]
>
> Rusty,
>
> If you want to take this, please add my
> Acked-by: Steven Rostedt
Thanks, I updated my copy and have pushed this into modules-next.
Cheers,
Rusty.
--
To unsubscribe from this list: send
Randy Dunlap writes:
> From: Randy Dunlap
>
> virtio-dev mailing list is for subscribers only according to the
> returned message after trying to send to it.
Thanks, applied.
Cheers,
Rusty.
> Signed-off-by: Randy Dunlap
> ---
> MAINTAINERS |6 +++---
> 1 file changed, 3 insertions(+), 3
- Original Message -
> From: "Andi Kleen"
> To: "Mathieu Desnoyers"
> Cc: "Andi Kleen" , "Steven Rostedt"
> , "Frank Ch. Eigler" ,
> linux-kernel@vger.kernel.org, "Ingo Molnar" , "Frederic
> Weisbecker" , "Andrew
> Morton" , "Johannes Berg"
> , "Linus Torvalds"
> , "Peter Zijlstra" ,
Here's a few fixes I've been carrying around. I've now tested them
on as many systems / environments as I can. They should be ready.
Luis R. Rodriguez (3):
bridge: preserve random init MAC address
bridge: trigger a bridge calculation upon port changes
bridge: fix bridge root block on
From: "Luis R. Rodriguez"
If netlink is used to tune a port we currently don't trigger a
new recalculation of the bridge id, ensure that happens just as
if we're adding a new net_device onto the bridge.
Cc: Stephen Hemminger
Cc: bri...@lists.linux-foundation.org
Cc: net...@vger.kernel.org
Cc:
From: "Luis R. Rodriguez"
Root port blocking was designed so that a bridge port can opt
out of becoming the designated root port for a bridge. If a port
however first becomes the designated root port and we then toggle
the root port block on it we currently don't kick that port out of
the
On Wed, Mar 12, 2014 at 08:47:07PM +, Mathieu Desnoyers wrote:
> - Original Message -
> > From: "Andi Kleen"
> > To: "Mathieu Desnoyers"
> > Cc: "Steven Rostedt" , "Frank Ch. Eigler"
> > , linux-kernel@vger.kernel.org, "Ingo
> > Molnar" , "Frederic Weisbecker" ,
> > "Andrew Morton"
From: "Luis R. Rodriguez"
As it is now if you add create a bridge it gets started
with a random MAC address and if you then add a net_device
as a slave but later kick it out you end up with a zero
MAC address. Instead preserve the original random MAC
address and use it.
If you manually set the
On 03/12/2014 07:38 PM, joeyli wrote:
>
> I sent rtc-acpitad driver for RTC subsystem on last month, I will send
> second version.
>
> For using TAD to set wall clock is because in ACPI 5.0 spec, there have
> a "CMOS RTC Not Present" flag in FADT to indicate OSPM should use TAD
> when this flag
- Original Message -
> From: "Steven Rostedt"
> To: "Mathieu Desnoyers"
> Cc: "Frank Ch. Eigler" , linux-kernel@vger.kernel.org, "Ingo
> Molnar" , "Frederic
> Weisbecker" , "Andrew Morton"
> , "Johannes Berg"
> , "Linus Torvalds" ,
> "Peter Zijlstra"
> , "Thomas Gleixner" , "Greg
>
On Thu, 13 Mar 2014 11:46:17 +0900 Joonsoo Kim wrote:
> + while (n >= PAGE_SIZE) {
> + /*
> + * discard request can be too large so that the zram can
> + * be stucked for a long time if we handle the request
> + * at once. So handle the
於 四，2014-03-13 於 00:49 +0100，Thomas Gleixner 提到：
> On Thu, 13 Mar 2014, Rafael J. Wysocki wrote:
> > I agree, and we need to fix that for 3.14. Patch is appended.
>
> You beat me by a few minutes. Was about to send out the same, just
> with a more spicy changelog :)
>
> > ---
> > From: Rafael
On Wed, 12 Mar 2014 22:29:48 -0400 Mark Salter wrote:
> Hi Andrew,
>
> Could you add this series into the -mm tree for v3.15?
>
> The following changes since commit c3bebc71c4bcdafa24b506adf0c1de3c1f77e2e0:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2014-03-04
>
On Wed, Mar 12, 2014 at 01:33:18PM -0700, Andrew Morton wrote:
> On Wed, 12 Mar 2014 17:01:09 +0900 Joonsoo Kim wrote:
>
> > zram is ram based block device and can be used by backend of filesystem.
> > When filesystem deletes a file, it normally doesn't do anything on data
> > block of that
於 四，2014-03-13 於 01:54 +0100，Thomas Gleixner 提到：
> On Thu, 13 Mar 2014, Rafael J. Wysocki wrote:
> > Thus follow the original idea to execute acpi_early_init() before
> > efi_enter_virtual_mode() to help the EFI people for now and we can
> > revisit the other problem that commit 73f7d1ca3263
Changed in v3:
- fix a bug when request the dma faild.
- some minor fixes for coding style.
- other minor fixes.
Changed in v2:
- remove has_dma_support property
- unify i2c_imx_dma_rx and i2c_imx_dma_tx
- unify i2c_imx_dma_read and i2c_imx_pio_read
- unify i2c_imx_dma_write and
Add i2c dts node properties for eDMA support, them depend on the eDMA driver.
Signed-off-by: Yuan Yao
---
Documentation/devicetree/bindings/i2c/i2c-imx.txt | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-imx.txt
Add dma support for i2c. This function depend on DMA driver.
You can turn on it by write both the dmas and dma-name properties in dts node.
Signed-off-by: Yuan Yao
---
drivers/i2c/busses/i2c-imx.c | 354 +--
1 file changed, 306 insertions(+), 48
Hi Andrew,
Could you add this series into the -mm tree for v3.15?
The following changes since commit c3bebc71c4bcdafa24b506adf0c1de3c1f77e2e0:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2014-03-04
08:44:32 -0800)
are available in the git repository at:
On Wed, 2014-03-12 at 00:02 +0100, Sebastian Hesselbarth wrote:
> phy_ethtool_get_wol is a helper to get current WOL settings from
> a phy device. When using this helper on a PHY without .get_wol
> callback, struct ethtool_wolinfo is never set-up correctly and
> may contain misleading information
2014-03-13 0:50 GMT+08:00 Kees Cook :
> On Wed, Mar 12, 2014 at 6:24 AM, Liu Shuo wrote:
>> From: Liu ShuoX
>>
>> In case new offset is equal to prz->buffer_size, it won't wrap at this
>> time and will return old(overflow) value next time.
>>
>> Signed-off-by: Liu ShuoX
>
> This seems correct;
Hi Batlomiej,
On 03/12/2014 11:37 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi Chanwoo,
>
> On Wednesday, March 12, 2014 08:47:59 PM Chanwoo Choi wrote:
>> This patch support DT(DeviceTree) method to probe exynos4_bus and get device
>> id of each Exynos4 SoC by using dt helper function.
>>
>>
Hi Batlomiej,
On 03/13/2014 12:17 AM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Wednesday, March 12, 2014 08:48:01 PM Chanwoo Choi wrote:
>> There are not the clock controller of ppmudmc0/1. This patch control the
>> clock
>> of ppmudmc0/1 which is used for monitoring memory bus
On Wed, Mar 12, 2014 at 6:43 PM, Simo Sorce wrote:
> On Wed, 2014-03-12 at 18:21 -0700, Andy Lutomirski wrote:
>> On Wed, Mar 12, 2014 at 6:17 PM, Simo Sorce wrote:
>> > On Wed, 2014-03-12 at 14:19 -0700, Andy Lutomirski wrote:
>> >> On Wed, Mar 12, 2014 at 2:16 PM, Simo Sorce wrote:
>> >>
>>
On Wednesday, March 12, 2014 at 01:53:14 PM, Matt Ranostay wrote:
> AS3935 chipset can detect lightning strikes and reports those back as
> events and the estimated distance to the storm.
>
> Signed-off-by: Matt Ranostay
Reviewed-by: Marek Vasut
Best regards,
Marek Vasut
--
To unsubscribe
Hi Robert,
On 03/12/2014 10:37 PM, Robert Baldyga wrote:
> This patch modifies mfd driver to use regmap for handling interrupts.
> It allows to simplify irq handling process. This modifications needed
> to make small changes in function drivers, which use interrupts.
>
> Signed-off-by: Robert
When used 64bit compiler GCC warns as
drivers/mfd/sec-core.c:199:10: warning:
cast from pointer to integer of different size [-Wpointer-to-int-cast]
Signed-off-by: Pankaj Dubey
---
drivers/mfd/sec-core.c |6 +++---
include/linux/mfd/samsung/core.h |2 +-
2 files changed, 4
Dear Kukjin,
On 03/12/2014 08:21 PM, Tomasz Figa wrote:
> Hi Chanwoo,
>
> On 12.03.2014 07:19, Chanwoo Choi wrote:
>> This patch add missing dt data of Exynos4x12 to bring up kernel feature and
>> code clean. This patchset is based on 'v3.15-next/dt-clk-exynos' branch.
>> -
On Fri, Mar 07, 2014 at 01:01:35PM +, Ben Dooks wrote:
> Add nodes for the four video input channels on the R8A7790.
Please update the prefix of this subject of this patch to:
ARM: shmobile: r8a7790:
>
> Signed-off-by: Ben Dooks
> ---
> arch/arm/boot/dts/r8a7790.dtsi | 32
On Fri, Mar 07, 2014 at 01:01:36PM +, Ben Dooks wrote:
> Add device-tree for vin1 (composite video in) on the
> lager board.
Please update the prefix of the subject of this patch to:
ARM: shmobile: lager:
>
> Signed-off-by: Ben Dooks
> ---
> arch/arm/boot/dts/r8a7790-lager.dts | 38
>
> "Jeff" == Jeff Moyer writes:
>> The case that we were seeing was with an SSD that required TRIM on 8k
>> boundaries and with an 8k granularity. Since the file system was
>> trying to do discards based on 4k alignment the driver complained
>> mightily.
Jeff> but you managed to read my
On Wed, Mar 12, 2014 at 07:55:50PM +0100, Geert Uytterhoeven wrote:
> Hi Joe,
>
> On Tue, Mar 11, 2014 at 6:10 PM, Joe Perches wrote:
> > Add missing newlines and coalesce formats.
> > Realign arguments.
>
> Thanks!
>
> > Signed-off-by: Joe Perches
>
> Acked-by: Geert Uytterhoeven
On Tue, Mar 11, 2014 at 11:30:52AM +0100, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patches.
>
> I had patches similar to 3/4 and 4/4 in my tree, that's a sign you're going
> in
> the right direction (or at least the direction I consider to be right :-)).
> For the whole
Hi Fengguang,
Can you try out this patch?
https://lkml.org/lkml/2014/3/12/243
--
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 Wed, 2014-03-12 at 18:21 -0700, Andy Lutomirski wrote:
> On Wed, Mar 12, 2014 at 6:17 PM, Simo Sorce wrote:
> > On Wed, 2014-03-12 at 14:19 -0700, Andy Lutomirski wrote:
> >> On Wed, Mar 12, 2014 at 2:16 PM, Simo Sorce wrote:
> >>
> >> >
> >> > Connection time is all we do and can care about.
On 03/12/2014 07:00 PM, Guenter Roeck wrote:
> On 03/12/2014 03:12 PM, Alex Elder wrote:
>> Starting with this commit:
>> 047ef2fa rename ARCH_BCM to ARCH_BCM_MOBILE (clocksource)
>> the meaning of the ARCH_BCM config option is changed to represent
>> all Broadcom chips with code in the
Based on Bjorn's latest response it looks as if pci_acpi_scan_root()
is only used as a fallback when the platform's BIOS has not put a
proper ACPI SRAT table and/or _PXM method in place. It will be
interesting to see if the 'dmesg' log and 'acpidump' information ends
up proving this out.
On Wed, Mar 12, 2014 at 6:17 PM, Simo Sorce wrote:
> On Wed, 2014-03-12 at 14:19 -0700, Andy Lutomirski wrote:
>> On Wed, Mar 12, 2014 at 2:16 PM, Simo Sorce wrote:
>>
>> >
>> > Connection time is all we do and can care about.
>>
>> You have not answered why.
>
> We are going to disclose
On Wed, 2014-03-12 at 14:19 -0700, Andy Lutomirski wrote:
> On Wed, Mar 12, 2014 at 2:16 PM, Simo Sorce wrote:
> > On Wed, 2014-03-12 at 14:12 -0700, Andy Lutomirski wrote:
> >> On Wed, Mar 12, 2014 at 2:00 PM, Andy Lutomirski
> >> wrote:
> >> > On 03/12/2014 01:46 PM, Vivek Goyal wrote:
> >>
On Wed, Mar 12, 2014 at 5:53 PM, Steven Rostedt wrote:
> Your timing here isn't that great either, because I leave tomorrow for
> another conference, and I'm currently trying to get everything ready
> for that trip. Could you ping me again on Tuesday?
Will do.
Vaibhav
--
To unsubscribe from
On Thu, 13 Mar 2014, Thomas Gleixner wrote:
> On Thu, 13 Mar 2014, Rafael J. Wysocki wrote:
> > Thus follow the original idea to execute acpi_early_init() before
> > efi_enter_virtual_mode() to help the EFI people for now and we can
> > revisit the other problem that commit 73f7d1ca3263 attempted
On Thu, 13 Mar 2014, Rafael J. Wysocki wrote:
> Thus follow the original idea to execute acpi_early_init() before
> efi_enter_virtual_mode() to help the EFI people for now and we can
> revisit the other problem that commit 73f7d1ca3263 attempted to
> address in the future (if really necessary).
On Wed, 12 Mar 2014 17:16:20 -0700
Vaibhav Nagarnaik wrote:
> Hi Steven,
>
> Any chance you can take a look at this patch?
>
Grumble, I thought I pulled this in already. I may have been working on
it and then got distracted by my day job, and it got lost in the
shuffle.
Your timing here
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/media/v4l2-core/v4l2-of.c between commit b9db140c1e4644d
("[media] v4l: of: Support empty port nodes") from the v4l tree and
commit fd9fdb78a9bf ("[media] of: move graph helpers from
drivers/media/v4l2-core to
On Wed, 12 Mar 2014 19:51:01 + (UTC)
Mathieu Desnoyers wrote:
> This only leaves tracepoints in header files and the impact of LTO as
> requirements for having tracepoint callsites with the same name across
> modules.
The only thing that needs to be unique is the struct tracepoint
On Wed, 12 Mar 2014, Joonsoo Kim wrote:
> SLUB already try to allocate high order page with clearing __GFP_NOFAIL.
> But, when allocating shadow page for kmemcheck, it missed clearing
> the flag. This trigger WARN_ON_ONCE() reported by Christian Casteyde.
>
>
On Wed, Mar 12, 2014 at 5:30 PM, Rusty Russell wrote:
> Kees Cook writes:
>> On Fri, Mar 7, 2014 at 5:00 PM, Kees Cook wrote:
>>> This forces the entire per_cpu range to be reported as absolute
>>> without losing their linker symbol types, when the per_cpu area is
>>> 0-based. Without this, the
On Wed, 2014-03-12 at 16:21 -0400, Tejun Heo wrote:
> It's a series of rather complex patches. I really don't think
> duplicating them is a good idea. We can either resurrect the old API
> to kill it again or set up a merge branch which I don't think is too
> unusual in situations like this.
On Wed, Mar 12, 2014 at 11:30:09PM +0100, David Herrmann wrote:
> Hi
>
> > I think it's trying to fix the problem in the wrong place. The bug is real,
> > all right, but it's not that alloc_file() for non-regulars doesn't grab
> > writecount; it's that drop_file_write_access() drops it for
Okay, i'll practice on file in drivers/staging.
Thank you for your help :)
--
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 at
Kees Cook writes:
> On Fri, Mar 7, 2014 at 5:00 PM, Kees Cook wrote:
>> This forces the entire per_cpu range to be reported as absolute
>> without losing their linker symbol types, when the per_cpu area is
>> 0-based. Without this, the variables are incorrectly shown as relocated
>> under kASLR
> -Original Message-
> From: Ulf Hansson [mailto:ulf.hans...@linaro.org]
> Sent: Wednesday, March 12, 2014 8:41 PM
> To: Chris Ball; Lu, Aaron; Wang, Xiaoming; Dong, Chuanxiao
> Cc: linux-...@vger.kernel.org; Liu, Chuansheng; linux-kernel@vger.kernel.org;
> NeilBrown; Rafael J. Wysocki
>
Hi Steven,
Any chance you can take a look at this patch?
Thanks
Vaibhav
On Thu, Feb 13, 2014 at 7:51 PM, Vaibhav Nagarnaik
wrote:
> In event format strings, the array size is reported in two locations.
> One in array subscript and then via the "size:" attribute. The values
> reported there
On Wed, 12 Mar 2014 04:00:15 -0700 Christoph Hellwig
wrote:
> The SLES12 tree has various patches to implement special
> O_DIRECT|O_NONBLOCK semantics for block devices:
>
>
>
On Wed, Mar 12, 2014 at 05:41:33PM +0900, Jingoo Han wrote:
> On Wednesday, March 05, 2014 8:49 PM, Liviu Dudau wrote:
> >
> > Use the generic host bridge functions to provide support for
> > PCI Express on arm64. There is no support for ISA memory.
> >
> > Signed-off-by: Liviu Dudau
> >
On Thu, Mar 13, 2014 at 12:30:39AM +0100, Pavel Machek wrote:
> Hi!
>
> This cost me two half-written mails...
>
> So far it happened once, so it may be very infrequent; but I do not
> think I seen similar failure from i915 before, so it may be an
> regression. Well...
It's a userspace
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
arch/x86/Kconfig between commit b4df597ae51f ("audit: Add
CONFIG_HAVE_ARCH_AUDITSYSCALL") from the tip tree and commit 2b9c1f03278 ("x86:
align x86 arch with generic CPU modalias handling") from the driver-core tree.
On 03/12/2014 03:12 PM, Alex Elder wrote:
Starting with this commit:
047ef2fa rename ARCH_BCM to ARCH_BCM_MOBILE (clocksource)
the meaning of the ARCH_BCM config option is changed to represent
all Broadcom chips with code in the mach-bcm directory.
Configuration options related to specific
On Thursday, March 13, 2014 12:49:07 AM Thomas Gleixner wrote:
> On Thu, 13 Mar 2014, Rafael J. Wysocki wrote:
> > I agree, and we need to fix that for 3.14. Patch is appended.
>
> You beat me by a few minutes. Was about to send out the same, just
> with a more spicy changelog :)
>
> > ---
> >
On Wed, Mar 12, 2014 at 07:15:03AM +0100, Peter Zijlstra wrote:
> On Wed, Mar 12, 2014 at 01:31:53PM +1100, Dave Chinner wrote:
> > With the queuing spinlock, I expected to see somewhat better
> > results, but I didn't at first. Turns out if you have any sort of
> > lock debugging turned on, then
On Thu, 2014-03-13 at 00:00 +0100, Pavel Machek wrote:
> On Tue 2014-02-18 23:15:08, Matthew Garrett wrote:
> > For example, if you load the ACPI power meter driver before you've
> > installed the ACPI IPMI driver you'll typically get failures (most
> > vendors implement it via IPMI).
>
> Would
On Thu, 13 Mar 2014, Rafael J. Wysocki wrote:
> I agree, and we need to fix that for 3.14. Patch is appended.
You beat me by a few minutes. Was about to send out the same, just
with a more spicy changelog :)
> ---
> From: Rafael J. Wysocki
> Subject: ACPI / init: Invoke early ACPI
On 03/12/2014 04:43 PM, Andy Lutomirski wrote:
>>
>> I do hear vsyscall=native still being used as a workaround for problems,
>> but yes, just making it call the kernel is fine, of course.
>
> Next time you hear that, can you let me know? I haven't heard of any
> issues since 3.4 IIRC.
>
Will
On Tue, Mar 11, 2014 at 02:05:38AM +0530, Srivatsa S. Bhat wrote:
> Subsystems that want to register CPU hotplug callbacks, as well as perform
> initialization for the CPUs that are already online, often do it as shown
> below:
>
> get_online_cpus();
>
> for_each_online_cpu(cpu)
>
On Wed, Mar 12, 2014 at 4:06 PM, H. Peter Anvin wrote:
> On 03/12/2014 02:49 PM, Andy Lutomirski wrote:
>> On Wed, Mar 12, 2014 at 2:46 PM, Linus Torvalds
>> wrote:
>>> On Wed, Mar 12, 2014 at 2:37 PM, H. Peter Anvin
>>> wrote:
How would that deal with the legacy vsyscall case for
Hi!
This cost me two half-written mails...
So far it happened once, so it may be very infrequent; but I do not
think I seen similar failure from i915 before, so it may be an
regression. Well...
-22 should be EINVAL afaict.
Any ideas?
During dentry path lookups we can end up corrupting memory if the
destination path buffer is too small. This is because prepend_path()
and prepend() adjust the passed buffer length unconditionally, allowing
for the buffer length to go negative. Then a later prepend_name() call
will receive a
The mm-of-the-moment snapshot 2014-03-12-16-04 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Wednesday, March 12, 2014 05:39:15 PM Thomas Gleixner wrote:
> On Wed, 12 Mar 2014, Thomas Gleixner wrote:
> > On Wed, 12 Mar 2014, Thomas Gleixner wrote:
> >
> > > On Wed, 12 Mar 2014, joeyli wrote:
> > > > I think maybe still using ACPI_FADT_NO_CMOS_RTC to check does
> > > >
Zitat von Andy Lutomirski :
Since no one seems to object to the latest patch I sent out, wouldn't
it make more sense to base this on top of my patch?
I will do this when your patch is pulled into tip. For now we have the choice,
but i preferer our solution removing the compat vdso.
-
On 03/12/2014 02:49 PM, Andy Lutomirski wrote:
> On Wed, Mar 12, 2014 at 2:46 PM, Linus Torvalds
> wrote:
>> On Wed, Mar 12, 2014 at 2:37 PM, H. Peter Anvin wrote:
>>>
>>> How would that deal with the legacy vsyscall case for x86-64? Just rely
>>> on the "legacy vsyscall emulation" (which seems
On 03/12/2014 03:41 PM, Aaro Koskinen wrote:
From: Huacai Chen
In _restore_fp_context/_restore_fp_context32, t0 is used for both
CP0_Status and CP1_FCSR. This is a mistake and cause FP exeception on
boot, so fix it.
Signed-off-by: Huacai Chen
Tested-by: Aaro Koskinen
Tested-by: Andreas
On 03/12/2014 03:41 PM, Aaro Koskinen wrote:
From: Paul Bolle
Commit 597ce1723e0f ("MIPS: Support for 64-bit FP with O32 binaries")
introduced references to two undefined Kconfig macros. CONFIG_MIPS32_R2
should clearly be replaced with CONFIG_CPU_MIPS32_R2. And CONFIG_MIPS64
should apparently
On Wed, Mar 12, 2014 at 3:58 PM, H. Peter Anvin wrote:
> On 03/12/2014 03:51 PM, Stefani Seibold wrote:
>> This patch enables 32 bit vDSO which are larger than a page. Currently
>> two pages are reserved, this should be enough for future improvements.
>>
>> Signed-off-by: Stefani Seibold
>> ---
On Tue 2014-02-18 23:15:08, Matthew Garrett wrote:
> On Wed, 2014-02-19 at 00:26 +0100, Rafael J. Wysocki wrote:
> > On Tuesday, February 18, 2014 11:28:29 AM Matthew Garrett wrote:
> > >
> > > The ACPI IPMI driver implements IPMI operation region support for the ACPI
> > > core. Systems that
1 - 100 of 1432 matches
Mail list logo
