A write to an efivarfs file will not always result in a variable of
'count' size after the EFI SetVariable() call. We may have appended to
the existing data (ie, with the EFI_VARIABLE_APPEND_WRITE attribute), or
even have deleted the variable (with an authenticated variable update,
with a zero data
On 10/04/2012 09:17 PM, Ben Hutchings wrote:
On Thu, 2012-10-04 at 20:14 +0200, Michal Simek wrote:
Allow user to access the MDIO from userspace.
Signed-off-by: Michal Simek
CC: Anirudha Sarangi
CC: John Linn
CC: Grant Likely
CC: Rob Herring
CC: David S. Miller
---
drivers/net/ethernet/
On Thu, Oct 4, 2012 at 9:51 PM, David Howells wrote:
> git://git.infradead.org/users/dhowells/linux-headers.git disintegrate-m68k
>
> for you to fetch changes up to b039235da939b28c539b3e1b4566107a9bdbdef8:
>
> UAPI: (Scripted) Disintegrate arch/m68k/include/asm (2012-10-04 18:20:56
> +0100)
On Thu 04-10-12 16:19:08, Johannes Weiner wrote:
> On Thu, Oct 04, 2012 at 08:49:58PM +0200, Michal Hocko wrote:
> > On Thu 04-10-12 14:09:16, Johannes Weiner wrote:
> > > page_referenced() counts only references of mm's that are associated
> > > with the memcg hierarchy that is being reclaimed. H
Hi David,
On 10/04/2012 08:26 PM, David Miller wrote:
Sorry, no.
I've announced on netdev very clearly that net-next submissions are not
appropriate at this time and that only pure bug fixes should be submitted.
Watch for the announcement on netdev of net-next openning up after the
merge wind
On Thu, Oct 4, 2012 at 8:50 PM, Rusty Russell wrote:
> Mimi Zohar writes:
>> Why? Not only have you had these patches sitting for a while, way
>> before you had the kernel module patches, they've been acked/signed off
>> by Kees, Serge, Eric, and myself. All security subtree maintainers.
>> The
Fix build failure in Intel PIIX4 I2C driver.
Signed-off-by: Daniel J Blueman
---
drivers/i2c/busses/i2c-piix4.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
index ef511df..8bbd6ec 100644
--- a/drivers/i2c/busses/i2c-piix4.
From: "Paul E. McKenney"
> b.Maybe sysfs setting. Initially, this can be simple "on" and "off",
> exported with root-only access (like you have above). If more
> elaborate use cases appear, this might become the adminstrative
> override. The key point is that this needs to
Commit-ID: 961c79761dda351b5fb263a0654b98daac130b7a
Gitweb: http://git.kernel.org/tip/961c79761dda351b5fb263a0654b98daac130b7a
Author: Dan Carpenter
AuthorDate: Tue, 2 Oct 2012 11:34:09 +0300
Committer: Ingo Molnar
CommitDate: Thu, 4 Oct 2012 13:28:08 +0200
x86/cache_info: Use ARRAY_SI
On 10/4/2012 8:49 PM, Ben Hutchings wrote:
On Wed, 2012-10-03 at 14:02 -0700, Divy Le Ray wrote:
On 9/28/2012 6:30 PM, Divy Le Ray wrote:
Hi,
Can you please pull from the following URL?
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
Hi,
Is there any problem with this pul
Commit-ID: e717bf4e4fe8adc519f25c4ff93ee50ed0a36710
Gitweb: http://git.kernel.org/tip/e717bf4e4fe8adc519f25c4ff93ee50ed0a36710
Author: Vince Weaver
AuthorDate: Wed, 26 Sep 2012 14:12:52 -0400
Committer: Ingo Molnar
CommitDate: Thu, 4 Oct 2012 13:32:37 +0200
perf/x86: Add support for In
From: G, Manjunath Kondaiah
SMSC ECE1099 is a keyboard scan or GPIO expansion device.The device
supports a keypad scan matrix of 23*8.This driver uses this
device as a keypad driver.
Tested on omap5430 evm with 3.6-rc6 custom kernel.
Cc: Benoit Cousson
Cc: Felipe Balbi
Cc: Santosh Shilimkar
On Fri, 5 Oct 2012 12:21:11 +0800, Daniel J Blueman wrote:
> Fix build failure in Intel PIIX4 I2C driver.
>
> Signed-off-by: Daniel J Blueman
> ---
> drivers/i2c/busses/i2c-piix4.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i
Mimi Zohar writes:
> Why? Not only have you had these patches sitting for a while, way
> before you had the kernel module patches, they've been acked/signed off
> by Kees, Serge, Eric, and myself. All security subtree maintainers.
> The module patches could have easily been built on top of Kees'
On 4 October 2012 18:06, MyungJoo Ham wrote:
>> This patchset updates devfreq core to add support for devices
>> which can idle. When device idleness is detected perhaps
>> through runtime-pm, need some mechanism to suspend devfreq
>> load monitoring and resume when device is back online.
>>
>> pa
Kees Cook writes:
> This adds the finit_module syscall to the generic syscall list.
This does ppc. Ben, please Ack.
From: Rusty Russell
Subject: powerpc: add finit_module syscall.
Signed-off-by: Rusty Russell
diff --git a/arch/powerpc/include/asm/systbl.h
b/arch/powerpc/include/asm/systbl
On Wed, 2012-10-03 at 14:02 -0700, Divy Le Ray wrote:
> On 9/28/2012 6:30 PM, Divy Le Ray wrote:
> > Hi,
> >
> > Can you please pull from the following URL?
> > git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
>
> Hi,
>
> Is there any problem with this pull request?
[...]
No, i
On Fri, 2012-10-05 at 07:22 +0200, Julia Lawall wrote:
> A tool was used to find a potential problem, and then Peter
> studied the code to see what fix was appropriate.
Hi Julia.
Was it true that a static analysis tool found the original
potential issue? If so, what tool was it?
But wasn't the
On Thu, 2012-10-04 at 18:29 +0200, Eric Dumazet wrote:
> On Thu, 2012-10-04 at 18:02 +0200, Maxime Bizon wrote:
> > On Fri, 2012-08-31 at 19:21 -0700, Hugh Dickins wrote:
> >
> > Hi,
> >
> > > Francois is right that a GFP_ATOMIC allocation from pskb_expand_head()
> > > is failing, which can easil
On 10/04/2012 05:17 PM, Florian Fainelli :
> Merge ohci_finish_controller_resume with ohci_resume as suggested by Alan
> Stern. Since ohci_finish_controller_resume no longer exists, update the
> various OHCI drivers to call ohci_resume() instead. Some drivers used to set
> themselves the bit HCD_FL
Hi all,
Do not add stuff destined for v3.8 to your linux-next included branches
until after v3.7-rc1 is released.
Changes since 201201004:
Conflicts are migrating as trees are merged by Linus.
The net tree lost its build failure.
The crypto tree lost its conflict.
The drm tree lost its confli
Hi Joey,
Since more people prefer to use "efivarfs", so, I modified the patch for
replace "efivars" to "efivarfs" like following:
I'd intentionally left this patch as-is. I think that the filesystem
should be called "efivarfs", while the directory should be called
"efivars". Same style as sy
On Thu, Oct 4, 2012 at 2:54 PM, H. Peter Anvin wrote:
>
> See my other post. This is bringing up the Kernel Summit algorithm again.
>
sure. please check if you are ok with attached one on top of x86/mm2
Thanks
Yinghai
fix_max_pfn_xx_11.patch
Description: Binary data
Il 04/10/2012 09:44, Rusty Russell ha scritto:
> -In particular, no implementation should use the descriptor
> -boundaries to determine the size of any header in a request.[footnote:
> -The current qemu device implementations mistakenly insist that
> -the first descriptor cover the header in these
On Thu, 2012-10-04 at 19:40 +0200, Michal Simek wrote:
> From: Wendy Liang
>
> Add the id and sector mappings for SPI flash chips.
An equivalent patch is already in David Woodhouse's l2-mtd tree:
http://git.infradead.org/users/dedekind/l2-mtd.git/commitdiff/3105875f6b8902628caee2fd7821af43707c6b
This patch set adds a MFD core driver which registers
touchscreen and ADC as its client drivers.
The existing touchscreen has been modified to work as
a MFD client driver and a new ADC driver has been added
in the IIO subsystem.
There are 8 analog input lines, which can be used as:
1. 8 general pu
Add the mfd core driver which supports touchscreen
and ADC.
With this patch we are only adding infrastructure to
support the MFD clients.
Signed-off-by: Patil, Rachna
---
Changes in v2:
Merged "[PATCH 5/5] MFD: ti_tscadc: Add check on number of i/p
channels",
patch submitted in p
This patch converts touchscreen into a MFD client.
All the register definitions, clock initialization,
etc has been moved to MFD core driver.
Signed-off-by: Patil, Rachna
---
Changes in v2:
No changes
Changes in v3:
No changes
Changes in v4:
No changes
Changes in v5:
Make way for addition of MFD driver.
The existing touchsreen driver is a MFD client.
For better readability we rename the file to
indicate its functionality as only touchscreen.
Signed-off-by: Patil, Rachna
---
Changes in v2:
Missed changing the name of touchscreen header file
in
This patch adds support for TI's ADC driver.
This is a multifunctional device.
Analog input lines are provided on which
voltage measurements can be carried out.
You can have upto 8 input lines.
Signed-off-by: Patil, Rachna
Acked-by: Jonathan Cameron
---
Changes in v2:
Addressed review co
On Saturday, September 29, 2012 6:36 AM Arnd Bergmann wrote
>
> Something is wrong with the exynos_dp_core logic, and gcc
> emits a warning about this. An array is declared in
> exynos_dp_process_equalizer_training with length '2',
> and exynos_dp_channel_eq_ok tries to access the third
> element
On Fri, Oct 05, 2012 at 12:36:35AM -0700, Joe Perches wrote:
> On Fri, 2012-10-05 at 07:22 +0200, Julia Lawall wrote:
> > A tool was used to find a potential problem, and then Peter
> > studied the code to see what fix was appropriate.
>
> Hi Julia.
>
> Was it true that a static analysis tool fou
On Thu, Oct 4, 2012 at 9:50 PM, Kurt H Maier wrote:
> On Wed, Oct 03, 2012 at 07:27:01PM +, Al Viro wrote:
>>
>> Al, that -><- close to volunteering for maintaining that FPOS kernel-side...
>>
>
> This would be fantastic.
And that would solve this very much worrying issue [1], quoting:
"(Yes,
On Fri, 5 Oct 2012, Joe Perches wrote:
On Fri, 2012-10-05 at 07:22 +0200, Julia Lawall wrote:
A tool was used to find a potential problem, and then Peter
studied the code to see what fix was appropriate.
Hi Julia.
Was it true that a static analysis tool found the original
potential issue? I
On 10/05/2012 02:01 AM, Sasha Levin wrote:
> Commit 9c650ffc ("TTY: ircomm_tty, add tty install") split _open() to
> _install() and _open(). It also moved the initialization of driver_data
> out of open(), but never added it to install() - causing a NULL ptr
> deref whenever the driver was used.
>
LP5521, LP5523 and L55231 have common features as below.
Register access via the I2C.
Device initialization/de-initialization.
Create LED class devices for multiple output channels.
Device attributes for user-space interface.
Therefore, this series of patch set enables removing duplicate co
This patch supports basic common driver code for LP5521, LP5523/55231 devices.
( Driver Structure Data )
lp55xx_led and lp55xx_chip
In lp55xx common driver, two different data structure is used.
o lp55xx_led
control multi output LED channels such as led current, channel index.
o lp55xx_c
Adding prefix old_ for variables for avoiding compile error with
new lp55xx structure.
This patch is preceding step for changing _probe().
Adding prefix old_ will be removed after _probe() cleanup.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 70 ---
The lp55xx_led and lp55xx_chip structures are used for supporting LP5521 and
LP5523 device functionality.
Core structures are allocated when each driver is probed.
Unused old data code were removed.
Additional headers are included.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp55
LP5521 and LP5523 devices have same sequence of initializing device.
(1) Call setup_resources() of platform data
(2) Call enable()
(3) Reset the device
(4) Detect the device using ENABLE register access
Those are merged into one function, lp55xx_init_device().
The setup_resources(), enable(
Device initialization can be divided into two sections.
One is common initialization code.
The other is the device specific initialization.
Common initialization is handled by the lp55xx_init_device().
Chip specific init code is processed by the lp55xx_post_init_device().
To configure this f
Initializing LEDs of LP55xx family devices is as follows.
(1) Register LED class device.
(2) Create the LED attributes (R/W LED current and get max current).
(3) Initialize a workqueue for the brightness control.
(4) Repeat (1) to (3) a number of channels.
Many lines of code are moved to th
The brightness function of LED classdev was moved to the lp55xx common driver
in previous patch.
To change the LED brightness, specific register should be updated.
This brightness register is the chip specific.
Therefore, actual operation should be handled in each driver.
This work function
The LP55xx common driver has general LED attributes.
(led_current and max_current)
To set this current, specific register should be updated.
Therefore, actual operation is handled in each driver.
This call is invoked on initializing LEDs and
setting current by an user-space.
Signed-off-by:
LP5521 has max 3 channels.
On the other hand, LP5523/55231 provides up to 9 channels.
A number of channels is used for validating platform data channel number
while initializing LEDs.(lp55xx_init_leds)
To support this, max_channel is configured in each driver.
Signed-off-by: Milo(Woogyom) Kim
This patch provides additional device attributes which enable
loading the firmware. ('select_engine' and 'run_engine')
LP55xx family chips have internal program memory which run various patterns.
Using this memory, LEDs continue on blinking/dimming without continuous I2C
commands. That means
To run a pattern, LP5521 and LP5523/55231 use different device attributes.
But it can be consolidated with common device attributes.
select_engine : Select which engine is used for running program data
run_engine: Start program which is loaded via the firmware interface
Use lp55xx_regist
The LP55xx common driver has a device attribute for running selected engine.
Then an application can run the engine via the sysfs.
Actual operation is accessing the register.
Therefore, run_engine internal function should be configured in each driver.
Related definitions and internal static f
On Friday 05 October 2012, Jingoo Han wrote:
> This problem was fixed. So, this patch is not necessary.
>
> As you mentioned, this problem was introduced by d5c0eed01
> "video: exynos_dp: adjust voltage swing and pre-emphasis
> during Link Training".
>
> However, this problem was resolved by e754
The LP55xx common driver supports general firmware interface
for running LED patterns.
The callback function is invoked after loading the firmware is done.
Actual operation is processed in this function.
Chip specific commands for loading and updating program memory.
Therefore, 'firmware_cb'
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 29a0fc9b2b6084e7a8810481df62a0fa496d8957:
>
> perf tools: Convert to LIBELF_SUPPORT (2012-09-28 21:07:36 -0300)
>
> are available in the git repository at:
This patch removes unused device attributes.
LP5521 has seven device attributes for accessing program memory.
engine1_mode
engine2_mode
engine3_mode
engine1_load
engine2_load
engine3_load
led_pattern
LP5523/55231 has nine device attributes for accessing program memory.
engine1_
The lp55xx_led and lp55xx_chip are used in _probe().
The lp5521_chip and lp5523_chip are not used any more.
To avoid the compile error, old variable name is changed.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 20 +++-
drivers/leds/leds-lp5523.c | 18
>>> On 05.10.12 at 08:48, Matt Fleming wrote:
> On Fri, 2012-10-05 at 07:39 +0100, Jan Beulich wrote:
>> >>> On 04.10.12 at 23:08, "H. Peter Anvin" wrote:
>> > On 10/03/2012 06:31 AM, Jan Beulich wrote:
>> > Matt Fleming 10/03/12 2:59 PM >>>
>> >>> +static int insert_identity_mapping(resourc
While unloading the driver, running engine should be stopped.
LP5521
Use lp5521_stop_engine() rather than old functions.
Unnecessary functions are removed.
LP5523
Reuse lp5523_stop_engine() rather than direct register access code.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp
While loading the driver, lp55xx common device attributes are registered.
On removing the driver, the attributes should be unregistered.
Old sysfs function is removed.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 10 ++
drivers/leds/leds-lp5523.c |9 +---
On Thu, 2012-10-04 at 21:03 -0700, Divy Le Ray wrote:
>
> > No, it appears David has pulled and pushed out your change.
>
> Great, thanks a lot!
Um, I hadn't. I have now.
--
David WoodhouseOpen Source Technology Centre
david.woodho...@intel.com
On _probe(), the lp55xx common function is used for LEDs registration.
While unloading the driver, use lp55xx common function to unregister LEDs
LP5521 driver uses cancel_work_sync(), but flush_work() makes sense
because the brightness is set to 0 on removing the driver.
The flush_work() is c
Use lp55xx common function to release the device.
Unnecessary old code lines are removed.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c |6 +-
drivers/leds/leds-lp5523.c |6 +-
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/leds/leds-l
LP55xx family chips have a selftest device attribute.
To maintain this sysfs, chip specific attribute is configurable.
Eventually those are created on registering the sysfs with common dev attrs.
Furthermore, this patch makes adding device attributes simple in each driver.
Signed-off-by: Milo(
The lp5521_chip and lp5523_chip are not used any more.
The R/W functions are replaced with lp55xx common functions.
LP5521 : Changes on checking the external clock
The selftest device attribute is created only when the platform data exists.
So no need to check whether the pdata is NULL or not
Old data structures and I2C functions are not used any more.
Each driver uses the lp55xx common data and functions.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 61 ---
drivers/leds/leds-lp5523.c | 62
Remove unused definitions and make hex values capital letters
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 26 +++--
drivers/leds/leds-lp5523.c | 54 ++--
2 files changed, 10 insertions(+), 70 deletions(-)
diff --
Remove unused headers and sort them alphabetically.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 17 +
drivers/leds/leds-lp5523.c | 17 +
2 files changed, 10 insertions(+), 24 deletions(-)
diff --git a/drivers/leds/leds-lp5521.c b/driver
The LP55xx common driver provides a new header, leds-lp55xx.h.
This driver enables removing duplicate code for both drivers and
making coherent driver structure.
LP5521 and LP5523/55231 platform data were merged into one common file.
Therefore, the LP5521/5523 platform code need to be fixed.
Add the author and copyright about the new lp55xx structure.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c |3 +++
drivers/leds/leds-lp5523.c |3 +++
2 files changed, 6 insertions(+)
diff --git a/drivers/leds/leds-lp5521.c b/drivers/leds/leds-lp5521.c
index 725eace..1
Relocate device attribute function nearby the declaration of the attribute.
This is really minor, but it may improve the legibility.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5521.c | 24 +++
drivers/leds/leds-lp5523.c | 154 +---
2
Add leds-lp55xx.txt.
Update the platform data information.
For the LED patterns, detailed information is described in lp55xx document.
Signed-off-by: Milo(Woogyom) Kim
---
Documentation/leds/00-INDEX|2 +
Documentation/leds/leds-lp5521.txt | 63 +++---
Documentat
Commit-ID: fee9e3732a377275a99b6f3c8b4e1f1569f17575
Gitweb: http://git.kernel.org/tip/fee9e3732a377275a99b6f3c8b4e1f1569f17575
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:31:57 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Sep 2012 21:07:36 -0300
perf tools: Mo
Commit-ID: e4898336a1b4d8a259663d15b12f359b6c2887a2
Gitweb: http://git.kernel.org/tip/e4898336a1b4d8a259663d15b12f359b6c2887a2
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:31:58 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Sep 2012 21:07:36 -0300
perf tools: Re
Commit-ID: 29a0fc9b2b6084e7a8810481df62a0fa496d8957
Gitweb: http://git.kernel.org/tip/29a0fc9b2b6084e7a8810481df62a0fa496d8957
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:31:59 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 28 Sep 2012 21:07:36 -0300
perf tools: Co
On Wed, Oct 03, 2012 at 05:18:56PM +0530, trisha yad wrote:
> I wish to know how can I support this function in 3.0 ?
If your description is correct, then all you need to do is to ensure
that you route interrupts to other CPUs.
You can do that by running the userspace irqbalance daemon.
--
To uns
Commit-ID: 95485b1cda827e4db7102ad5fde1791087a0f4c5
Gitweb: http://git.kernel.org/tip/95485b1cda827e4db7102ad5fde1791087a0f4c5
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:32:00 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 17:56:01 -0300
perf tools: Con
Commit-ID: f315e16850d00ae5b19f11810bc00bf68cf3c24a
Gitweb: http://git.kernel.org/tip/f315e16850d00ae5b19f11810bc00bf68cf3c24a
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:32:01 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:21 -0300
perf tools: Con
Commit-ID: 1254b51e32649f2d34ec6b070ed36717c5a6b825
Gitweb: http://git.kernel.org/tip/1254b51e32649f2d34ec6b070ed36717c5a6b825
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:32:02 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:22 -0300
perf tools: Con
Hi,
I'm getting this warning while running qemu-kvm 1.2.rc1 on the top of
3.6.0-next-20121001:
WARNING: at virt/kvm/kvm_main.c:1325 kvm_release_pfn_clean+0x70/0x80()
Hardware name: To Be Filled By O.E.M.
Modules linked in: nls_cp437 vfat fat dvb_usb_dib0700 dib0090 dib7000p
dib7000m dib0070 dib800
Commit-ID: f9f526ecdc09a851f4f5567ebcf9bc553778f6c2
Gitweb: http://git.kernel.org/tip/f9f526ecdc09a851f4f5567ebcf9bc553778f6c2
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:32:03 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:23 -0300
perf tools: Con
Commit-ID: d6e66832a710c0e6d1376e8d39ee108636a177e7
Gitweb: http://git.kernel.org/tip/d6e66832a710c0e6d1376e8d39ee108636a177e7
Author: Namhyung Kim
AuthorDate: Fri, 28 Sep 2012 18:32:08 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:24 -0300
perf tools: Con
On Wed, Oct 03, 2012 at 11:07:13AM -0700, David Rientjes wrote:
> On Wed, 3 Oct 2012, Stanislaw Gruszka wrote:
>
> > So, can this problem be solved like on below patch, or I should rather
> > split firmware loading into chunks similar like was already iwlwifi did?
Hmm, I looked at iwl3945 code an
Commit-ID: 5ded57ac1bdb99b716c1da96eb8b5d387f5eb676
Gitweb: http://git.kernel.org/tip/5ded57ac1bdb99b716c1da96eb8b5d387f5eb676
Author: Arnaldo Carvalho de Melo
AuthorDate: Sun, 30 Sep 2012 19:54:10 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:27 -0300
per
Commit-ID: 73ee3b276864af1ca042258e67237e8454d7b7b6
Gitweb: http://git.kernel.org/tip/73ee3b276864af1ca042258e67237e8454d7b7b6
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 13:58:17 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:28 -0300
perf
On 10/04/2012 12:59 PM, Gleb Natapov wrote:
On Wed, Oct 03, 2012 at 04:56:57PM +0200, Avi Kivity wrote:
On 10/03/2012 04:17 PM, Raghavendra K T wrote:
* Avi Kivity [2012-09-30 13:13:09]:
On 09/30/2012 01:07 PM, Gleb Natapov wrote:
On Sun, Sep 30, 2012 at 10:18:17AM +0200, Avi Kivity wrote:
Am Donnerstag, den 04.10.2012, 11:25 -0400 schrieb Matt Porter:
> On Fri, Sep 07, 2012 at 02:43:44PM +0200, Philipp Zabel wrote:
> > This driver requests and remaps a memory region as configured in the
> > device tree. It serves memory from this region via the genalloc API.
> >
> > Other drivers c
Commit-ID: 2bae1d1b1aa3b763b99431101a04dfe24ec5ba7f
Gitweb: http://git.kernel.org/tip/2bae1d1b1aa3b763b99431101a04dfe24ec5ba7f
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:31 -0300
perf
Commit-ID: 0433ffbe47d66c5c561b54340ee47adf8826bcc4
Gitweb: http://git.kernel.org/tip/0433ffbe47d66c5c561b54340ee47adf8826bcc4
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:32 -0300
perf
Commit-ID: c75d98afa7bb059169587b838e0a25436b8d3e62
Gitweb: http://git.kernel.org/tip/c75d98afa7bb059169587b838e0a25436b8d3e62
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:33 -0300
perf
Ingo reported (again!) that 'make clean' on perf/traceevent does not
work due to some reason with system header file. Quotes Ingo:
"Note that the old dependency related build failure thought to be
fixed in commit 860df5833e46 is back:
make[1]: *** No rule to make target
`/usr/lib/gcc/x86
On Mon, Oct 01, 2012 at 10:06:39AM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 01, 2012 at 04:39:53PM +0100, Dave Martin wrote:
> > > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
> > > LOAD 0x008000 0xc0008000 0x8000 0x372244 0x3a4310 RWE
> > > 0x8000
>
Commit-ID: 73bdc7159b0a83146fa8d1b8df7baf1cea992d4c
Gitweb: http://git.kernel.org/tip/73bdc7159b0a83146fa8d1b8df7baf1cea992d4c
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:34 -0300
perf
Commit-ID: 6ee4149736e39deb7ed6d11c5de3101b5b8c2669
Gitweb: http://git.kernel.org/tip/6ee4149736e39deb7ed6d11c5de3101b5b8c2669
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:36 -0300
perf
Commit-ID: 11c4e4a32b420db683cf58069c525e94797ce044
Gitweb: http://git.kernel.org/tip/11c4e4a32b420db683cf58069c525e94797ce044
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:37 -0300
perf
Commit-ID: be77284226374c75583f36dbbf43203039f6a44c
Gitweb: http://git.kernel.org/tip/be77284226374c75583f36dbbf43203039f6a44c
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 1 Oct 2012 15:20:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:38 -0300
perf
On Thu, 6 Sep 2012 13:28:16 -0700 Greg KH wrote:
> On Tue, Sep 04, 2012 at 05:01:05PM -0700, Greg Kroah-Hartman wrote:
> > From: Greg KH
> >
> > The CONFIG_HOTPLUG variable is tough to turn off, and almost all arches
> > default to it on.
> >
> > If you turn it off, it saves you a big 200 or s
Commit-ID: a1d668c3ffd38d611f8446615e8f797dcfdfc397
Gitweb: http://git.kernel.org/tip/a1d668c3ffd38d611f8446615e8f797dcfdfc397
Author: Namhyung Kim
AuthorDate: Wed, 3 Oct 2012 00:21:32 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:42 -0300
perf tools: Chec
On Thu, Oct 04, 2012 at 15:51:03, Philip, Avinash wrote:
> On Thu, Oct 04, 2012 at 00:50:45, Ivan Djelic wrote:
> > On Wed, Oct 03, 2012 at 03:29:49PM +0100, Philip, Avinash wrote:
> > > ELM module can be used for error correction of BCH 4 & 8 bit. Also
> > > support read & write page in one shot b
Commit-ID: 35c2fde1155cc7225361edf43d8efd0aabd28a0c
Gitweb: http://git.kernel.org/tip/35c2fde1155cc7225361edf43d8efd0aabd28a0c
Author: Namhyung Kim
AuthorDate: Wed, 3 Oct 2012 00:21:33 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:43 -0300
perf tools: Comp
Commit-ID: 4e34d9588b46f44a4dba718606913133f15e4b21
Gitweb: http://git.kernel.org/tip/4e34d9588b46f44a4dba718606913133f15e4b21
Author: Namhyung Kim
AuthorDate: Tue, 2 Oct 2012 01:32:51 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 2 Oct 2012 18:36:45 -0300
perf tools: Conv
Commit-ID: e60fc847cefa34d9b7a60f8fbbe3f7dc68fbd75e
Gitweb: http://git.kernel.org/tip/e60fc847cefa34d9b7a60f8fbbe3f7dc68fbd75e
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 3 Oct 2012 11:50:55 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 3 Oct 2012 11:52:07 -0300
perf
Commit-ID: ae359f193a80e19166efaed7d400d1476057b865
Gitweb: http://git.kernel.org/tip/ae359f193a80e19166efaed7d400d1476057b865
Author: Jiri Olsa
AuthorDate: Thu, 4 Oct 2012 21:49:35 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 4 Oct 2012 13:27:00 -0300
perf hists: Add str
Hi Ingo,
On Fri, 5 Oct 2012 10:18:04 +0200, Ingo Molnar wrote:
> I also noticed a 'perf trace' bug, after running 'perf trace' it
> outputs lines but then gets hung:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
>
> 6081 mingo 20 0
1 - 100 of 571 matches
Mail list logo
