Addressed comments by Namhyung (thank you!).
David Ahern (2):
perf sched: Introduce timehist command - v2
perf sched: Add documentation for timehist options
tools/perf/Documentation/perf-sched.txt | 61 ++-
tools/perf/builtin-sched.c | 932 +++-
Allow user to specify an address within an executable. This is useful, for
example, in probing local functions. If the function name begins with 0x
then try to convert the supplied name to an address. If succuessful then
treat the function name as the address within the executable to be probed.
On Friday, November 29, 2013 10:34 AM, Jingoo Han wrote:
> On Thursday, November 28, 2013 3:24 PM, Joe Perches wrote:
> >On Wed, 2013-11-27 at 21:53 -0800, 'Greg Kroah-Hartman' wrote:
> >>On Wed, Nov 27, 2013 at 09:40:13PM -0800, Joe Perches wrote:
> >>>On Thu, 2013-11-28 at 14:29 +0900, Jingoo
When requesting a function from a userspace library the error message to
the user is less than helpful. e.g.,
perf probe -x /lib64/libpthread-2.14.90.so -a
'lock_full=__pthread_mutex_lock_full'
no symbols found in /lib64/libpthread-2.14.90.so, maybe install a debug
package?
Failed
The dwarf option for callstacks is getting stuck on the unwind and showing
repeated frames. For example,
qemu-system-x86 13759 [001] 287663.084957: syscalls:sys_enter_futex: uaddr:
0x7f770a958700, op: 0x0081, val: 0x0001, utime: 0x7f75ea
7f7705fd23ea __lll_unlock_wake
Hi Anton
On Sun, Dec 1, 2013 at 11:37 PM, Anton Vorontsov wrote:
> On Mon, Nov 25, 2013 at 08:16:34PM +0100, Michael Trimarchi wrote:
> ...
>> >> So you can read this value without any type of synchronization
>> >> with the power_supply_core
>> >> and sysfs implementation?
> ...
>>
Use devm_lcd_device_register() to make cleanup paths simpler,
and remove unnecessary remove().
Signed-off-by: Jingoo Han
---
drivers/video/backlight/jornada720_lcd.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/video/backlight/jornada720_lcd.c
Use devm_lcd_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/tosa_lcd.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/video/backlight/tosa_lcd.c
b/drivers/video/backlight/tosa_lcd.c
index
Use devm_lcd_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/l4f00242t03.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/video/backlight/l4f00242t03.c
b/drivers/video/backlight/l4f00242t03.c
index
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/ot200_bl.c |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/video/backlight/ot200_bl.c
b/drivers/video/backlight/ot200_bl.c
index
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/tosa_bl.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/video/backlight/tosa_bl.c
b/drivers/video/backlight/tosa_bl.c
index
Use devm_backlight_device_register() to make cleanup paths simpler,
and remove unnecessary remove().
Signed-off-by: Jingoo Han
---
drivers/video/backlight/omap1_bl.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/video/backlight/omap1_bl.c
Use devm_backlight_device_register() to make cleanup paths simpler.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/hp680_bl.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/video/backlight/hp680_bl.c
b/drivers/video/backlight/hp680_bl.c
index
Use devm_backlight_device_register() to make cleanup paths simpler,
and remove unnecessary remove().
Signed-off-by: Jingoo Han
---
drivers/video/backlight/jornada720_bl.c | 15 +++
1 file changed, 3 insertions(+), 12 deletions(-)
diff --git
On 01.12.2013 21:06, Joe Perches wrote:
On Sun, 2013-12-01 at 19:07 +0200, Ivaylo DImitrov wrote:
From: Ivaylo Dimitrov
Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't
need to be exported. It can also be made way simpler by using sscanf.
[]
diff --git
Congratulation Confirm your 300,000,00 Eur. Contact claims office via
wucla...@126.com
--
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
On Mon, Nov 25, 2013 at 08:16:34PM +0100, Michael Trimarchi wrote:
...
> >> So you can read this value without any type of synchronization
> >> with the power_supply_core
> >> and sysfs implementation?
...
> https://lists.ubuntu.com/archives/kernel-team/2013-January/025206.html
>
> I found and
On Sun, 2013-12-01 at 10:35 +0100, Johannes Berg wrote:
> Good try, but no, now ap_sdata isn't even assigned. :)
Right. Oh well. There's no improving this without
significant rewrite. Even then, there may not be much
overall improvement.
btw: Chen, I think fall-throughs are fine as long as
On 11/25/13 15:37, Chander Kashyap wrote:
Hi Kikjin,
Hi Chander,
On 21 October 2013 02:32, Kukjin Kim wrote:
On 10/18/13 02:53, Tomasz Figa wrote:
Hi Kukjin,
On Thursday 26 of September 2013 14:05:09 Kukjin Kim wrote:
Chander Kashyap wrote:
Replace irq_domain_add_simple with
On Mon, Nov 25, 2013 at 09:40:04AM +0900, jonghwa3@samsung.com wrote:
> > max17042 now uses regmap interface but does not enable config option. This
> > patch fixes the following build errors:
> >
> > drivers/power/max17042_battery.c:661:15: error: variable
> > ‘max17042_regmap_config’ has
On Tue, Nov 19, 2013 at 11:18:03AM +0100, Pali Rohár wrote:
> This patch adds a notifier chain to the power_supply.
> This notifier helps drivers in other subsystem to listen to
> changes in power supply subsystem. This would help to take some
> actions in those drivers on changing the power
[ cut here ]
WARNING: CPU: 1 PID: 10 at kernel/time/tick-sched.c:191 0x8107bac6()
NO_HZ FULL will not work with unstable sched clock
Modules linked in:
CPU: 1 PID: 10 Comm: rcuop/0 Not tainted 3.12.2-rt4 #3
Hardware name: TYAN Computer Corp. S2895/S2895, BIOS 2004Q3
On Wed, Nov 27, 2013 at 05:23:34PM +, Tc, Jenny wrote:
>
> > Subject: [PATCH v2 1/3] power_supply: Add power_supply notifier
> >
> > This patch adds a notifier chain to the power_supply.
> > This notifier helps drivers in other subsystem to listen to changes in
> > power supply
> >
On Fri, Nov 29, 2013 at 03:42:14PM +0800, Axel Lin wrote:
> No fault if !MUU, thus make might_fault to be a nop for !MMU.
>
> This fixes below build error if
> !CONFIG_MMU && (CONFIG_PROVE_LOCKING=y || CONFIG_DEBUG_ATOMIC_SLEEP=y):
>
> arch/arm/kernel/built-in.o: In function `arch_ptrace':
>
On Fri, Nov 22, 2013 at 10:54:28AM -0700, Shuah Khan wrote:
> power_supply_register() calls device_init_wakeup() to register a wakeup
> source before initializing dev_name. As a result, device_wakeup_enable()
> end up registering wakeup source with a null name when
> wakeup_source_register()
>
On Sun, Dec 1, 2013 at 12:39 PM, Eric Dumazet wrote:
>
> Last time I checked, private futexes were used when appropriate.
>
> "strace -e futex" mainly show _PRIVATE uses.
Yeah, pthread mutexes seem to do it. Sadly we don't do it for
mm_release(), so the case of clear_child_tid doesn't trigger
Hi,
I recently installed (Arch x86_64) Linux with the 3.12.1 kernel on a Toshiba
Satellite L300 laptop. After shutting down Linux, the laptop will spontaneously
boot up after about five minutes. This seems to be consistent. There are no
options in the BIOS for en/disabling or configuring the
On Sun, 2013-12-01 at 02:34 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Modify tg3_chip_reset() and tg3_close() to check if the PCI network
> adapter device is accessible at all in order to skip poking it or
> trying to handle a carrier loss in vain when that's not the case.
>
On Sun, 2013-12-01 at 10:58 -0800, Linus Torvalds wrote:
> Of course, I have no idea if people are properly using the private
> futexes. glibc _should_ use them, but who the heck knows..
Last time I checked, private futexes were used when appropriate.
"strace -e futex" mainly show _PRIVATE
On Sunday 01 December 2013 21:25:00 Pavel Machek wrote:
> Hi!
>
> Interesting; with Sebastian DT config
> (http://elektranox.org/n900-kernel-config.txt), I get the same
>
>
>
> [ 17.967651] omap_i2c 4807.i2c: Too much work in one IRQ
> [ 17.968109] omap_i2c 4807.i2c: Too much work
On Sunday 01 December 2013 21:01:13 Pavel Machek wrote:
> Hi!
>
> > board-rx51-camera.c is not part of mainline kernel and will
> > never be (due to DT migration). So maybe it could be better
> > to add #ifdef to board-rx51-camera.c. Keeping changes for
> > Makefile/Kconfig files is harder
Hi!
> > I just hit this one:
> >
> > CC arch/arm/mach-omap2/board-rx51-camera.o
> > In file included from
> > arch/arm/mach-omap2/board-rx51-camera.c:34:0:
> > arch/arm/mach-omap2/../../../drivers/media/platform/omap3isp/
> > isp.h: In function 'isp_pad_buffer_type':
> >
Hi!
> board-rx51-camera.c is not part of mainline kernel and will never
> be (due to DT migration). So maybe it could be better to add
> #ifdef to board-rx51-camera.c. Keeping changes for Makefile/Kconfig
> files is harder because of future rebase...
Ok, that makes sense.
This breaks
On Fri, Nov 29, 2013 at 07:06:31PM +0530, Ramkumar Ramachandra wrote:
> In
>
> $ perf diff -c ratio
>
> color the Ratio column using percent_color_snprintf().
>
> Cc: Jiri Olsa
> Cc: Arnaldo Carvalho de Melo
> Signed-off-by: Ramkumar Ramachandra
> ---
> tools/perf/builtin-diff.c | 20
On Fri, Nov 29, 2013 at 07:06:30PM +0530, Ramkumar Ramachandra wrote:
> Color the numbers in the Delta column using percent_color_snprintf().
> Generalize the function so that we can accommodate all three comparison
> methods in the future: delta, ratio, and wdiff.
>
> Cc: Jiri Olsa
> Cc:
The Haoyu Microelectronics HYM8563 provides rtc- and alarm functions
as well as a clock output of up to 32kHz.
Signed-off-by: Heiko Stuebner
---
drivers/rtc/Kconfig | 11 +
drivers/rtc/Makefile |1 +
drivers/rtc/rtc-hym8563.c | 626 +
Add binding documentation for the hym8563 rtc chip.
Signed-off-by: Heiko Stuebner
---
.../devicetree/bindings/rtc/haoyu,hym8563.txt | 27
.../devicetree/bindings/vendor-prefixes.txt|1 +
2 files changed, 28 insertions(+)
create mode 100644
This series adds support for the Haoyu Microelectronics HYM8563 rtc. This
chip is often used in designs around the Cortex-A9 SoCs from Rockchip to
provide rtc functionality and the 32kHz suspend clock the SoC needs.
changes since v2:
- get size for devm_kzalloc from struct not from pointer
On 11/30/2013 07:45 AM, Christophe Leroy wrote:
MPC8xx watchdog is enabled at startup by HW.
If the bootloader disables it, it cannot be reenabled.
Is that true for all variants of 8xx, especially for 823 ? I am a bit concerned
about breaking compatibility with some chips ... assuming there
On 11/30/2013 07:33 AM, Christophe Leroy wrote:
Convert mpc8xxx_wdt.c to the new watchdog API.
Signed-off-by: Christophe Leroy
diff -ur a/drivers/watchdog/mpc8xxx_wdt.c b/drivers/watchdog/mpc8xxx_wdt.c
--- a/drivers/watchdog/mpc8xxx_wdt.c2013-05-11 22:57:46.0 +0200
+++
Looks good to me.
regards,
dan carpenter
--
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 http://www.tux.org/lkml/
On 11/30/2013 09:17 PM, Rafael J. Wysocki wrote:
[...]
> If your system survives resume (I guess it does?), can you please send
> /proc/interrupts before and after the first suspend/resume cycle?
>
Please find both dumps attached.
Thanks
CPU0 CPU1 CPU2 CPU3
On Sunday 01 December 2013 20:21:20 Pavel Machek wrote:
> Hi!
>
> I just hit this one:
>
> CC arch/arm/mach-omap2/board-rx51-camera.o
> In file included from
> arch/arm/mach-omap2/board-rx51-camera.c:34:0:
> arch/arm/mach-omap2/../../../drivers/media/platform/omap3isp/
> isp.h: In
On Sun, Dec 01, 2013 at 05:43:09PM +0200, Aldo Iljazi wrote:
> #define DIGI_DLREQ_GET (('d'<<8) | 220)
> @@ -57,7 +57,7 @@ struct downldio {
> #define DIGI_NUKE_RESET_ALL (1 << 31)
> #define DIGI_NUKE_INHIBIT_POLLER (1 << 30)
> #define DIGI_NUKE_BRD_NUMB0x0f
> -
> +
>
>
Hi!
I just hit this one:
CC arch/arm/mach-omap2/board-rx51-camera.o
In file included from arch/arm/mach-omap2/board-rx51-camera.c:34:0:
arch/arm/mach-omap2/../../../drivers/media/platform/omap3isp/isp.h: In
function 'isp_pad_buffer_type':
On Sun, Dec 01, 2013 at 05:43:08PM +0200, Aldo Iljazi wrote:
> A few checkpatch cleanups, particularly:
>
> Lines 83, 87, 89, 196: Removed spaces before tabs.
> Lines 141, 265.267: Removed trailing whitespace.
>
Don't send two patches with the exact same subject.
regards,
dan carpenter
--
To
On Sun, 2013-12-01 at 19:07 +0200, Ivaylo DImitrov wrote:
> From: Ivaylo Dimitrov
>
> Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't
> need to be exported. It can also be made way simpler by using sscanf.
[]
> diff --git a/drivers/staging/tidspbridge/rmgr/dbdcd.c
>
On 11/29/2013 04:46 AM, Hiroshi Doyu wrote:
...
> Iterating over a property containing a list of phandles with arguments
> is a common operation for device drivers. This patch adds a new
> of_property_for_each_phandle_with_args() macro to make the iteration
> simpler.
>
> Introduced a new struct
On Sun, Dec 1, 2013 at 8:55 AM, Ingo Molnar wrote:
>
> Keeping the page invariant would bring significant performance
> advantages to hashing.
Or not. Rather, it would make things much worse. The virtual address
is much simpler and better to avoid needing any page table lookup etc
crap. The key
Hi!
> >>--- a/drivers/staging/tidspbridge/rmgr/drv_interface.c
> >>+++ b/drivers/staging/tidspbridge/rmgr/drv_interface.c
> >>@@ -258,7 +258,17 @@ err:
> >> /* This function maps kernel space memory to user space memory. */
> >> static int bridge_mmap(struct file *filp, struct vm_area_struct
Jeff Kirsher wrote:
> This came up when John Fastabend got a patch to fix up the headers in
> the drivers/scsi/ directory and so I did a quick search of the network
> drivers and found several instances in the file headers where an old FSF
> address remains. The old address is:
>
> 59 Temple
On Fri, Nov 29, 2013 at 02:11:14AM +0800, Jianyu Zhan wrote:
>
> Hi, Vladimir,
>
> On Fri, Nov 29, 2013 at 1:41 AM, Vladimir Murzin wrote:
> >
> > Any numbers for efficiency?
> >
>
> For the original implementation, vmalloc_to_pfn() wraps the vmalloc_to_page(),
> which means
>
> pfn
On 01.12.2013 14:27, Dan Carpenter wrote:
On Sun, Dec 01, 2013 at 01:10:06PM +0100, Pavel Machek wrote:
diff --git a/drivers/staging/tidspbridge/rmgr/drv_interface.c
b/drivers/staging/tidspbridge/rmgr/drv_interface.c
index 1aa4a3f..a8e86cf 100644
---
0) Booting v3.13-rc1 and v3.13-rc2 triggers two new warnings on an
(outdated, I'm afraid) ThinkPad X41:
[...]
<6>[ 16.746119] libipw: 802.11 data/management/control stack, git-1.1.13
<6>[ 16.746125] libipw: Copyright (C) 2004-2005 Intel Corporation
<4>[ 16.761998] platform
Am Sonntag, 1. Dezember 2013, 15:38:40 schrieb Richard Weinberger:
> On Sun, Dec 1, 2013 at 2:39 PM, Heiko Stübner wrote:
> > +static int hym8563_probe(struct i2c_client *client,
> > +const struct i2c_device_id *id)
> > +{
> > + struct hym8563 *hym8563;
> > +
From: Ivaylo Dimitrov
Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't
need to be exported. It can also be made way simpler by using sscanf.
Signed-off-by: Ivaylo Dimitrov
---
drivers/staging/tidspbridge/Makefile |2 +-
On Sat, 30 Nov 2013, James Bottomley wrote:
> On Sat, 2013-11-30 at 13:56 -0500, Konrad Rzeszutek Wilk wrote:
> > My theory is that the SWIOTLB is not full - it is just that the request
> > is for a compound page that is more than 512kB. Please note that
> > SWIOTLB highest "chunk" of buffer it
Yinghai:
Would you please consider *not* bundling unrelated, or at least
non-dependent, patches together in one series. As a distrobution
subsystem maintainer, this type of bundling really complicates trying
to identify and isolate key material for bringing in. It also makes
trying to identify
On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote:
> Should be fixed with
>
> commit 7c063c725987406d743cc7de7625ff224fab75de
> Author: Jesse Barnes
> Date: Tue Nov 26 09:13:41 2013 -0800
>
> drm/i915: take mode config lock around crtc disable at suspend
>
> which is currently in
* Peter Zijlstra wrote:
> On Sun, Dec 01, 2013 at 01:10:22PM +0100, Ingo Molnar wrote:
>
> > But more importantly, since these are all NUMA systems, would it
> > make sense to create per node hashes on NUMA? Each futex would be
> > enqueued into the hash belonging to its own page's node.
>
>
On 11/27/13 03:29, Chen Gang wrote:
> the macro "SP" is too common to make conflict with some architectures,
> so recommend to add prefix for it.
>
> The related warning (with allmodconfig for hexagon):
>
> CC [M] drivers/scsi/scsi_lib.o
> drivers/scsi/scsi_lib.c:46:0: warning: "SP"
Use the VERSIONCRC to determine the exact device version. According to
the datasheet this register can be used as device identifier. The
identification is needed since some tps6586x regulators use a different
voltage table.
Signed-off-by: Stefan Agner
---
drivers/mfd/tps6586x.c | 47
regulator: tps6586x: add version detection and voltage tables
This is the 2nd version of this patchset which adds version detection
for the tps6586x mfd family. This is required because some regulator
versions use different voltage tables. The regulator driver now uses
the right voltage table
Depending on the regulator version, the voltage table might be
different. Use version specific regulator tables in order to select
correct voltage table. For the following regulator versions different
voltage tables are now used:
* TPS658623: Use correct voltage table for SM2
* TPS658643: New
Set the parent of the regulators LDO2 to LDO9 according to the
schematic. Set the base voltage to 3.3V, there is only 3.3V on the
module itself.
Set the Core and CPU voltage to the specified voltages of 1.2V and
1.0V respectivly.
LDO6 should deliver 2.85V. The attached peripherals were not in
A few checkpatch cleanups, particularly:
Lines 26, 60: Removed trailing whitespace.
Lines 36-38, 42-44, 47: Removed spaces at the start of the lines.
Signed-off-by: Aldo Iljazi
---
drivers/staging/dgap/dgap_downld.h | 22 +++---
1 file changed, 11 insertions(+), 11
A few checkpatch cleanups, particularly:
Lines 83, 87, 89, 196: Removed spaces before tabs.
Lines 141, 265.267: Removed trailing whitespace.
Signed-off-by: Aldo Iljazi
---
drivers/staging/dgap/dgap_conf.h | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff
[ +cc Dmitry Torokhov, Greg Kroah-Hartman, linux-input, linux-serial ]
On 11/26/2013 05:19 PM, Manuel Krause wrote:
Since kernel 3.12.0 I have a problem with hibernate+resume
not reactivating my serial mouse (trackball) with my HP notebook.
Kernels 3.11.0 til 9 don't show this behaviour.
On Sun, Dec 1, 2013 at 2:39 PM, Heiko Stübner wrote:
> The Haoyu Microelectronics HYM8563 provides rtc- and alarm functions
> as well as a clock output of up to 32kHz.
>
> Signed-off-by: Heiko Stuebner
> ---
> drivers/rtc/Kconfig | 11 +
> drivers/rtc/Makefile |1 +
>
This series adds support for the Haoyu Microelectronics HYM8563 rtc. This
chip is often used in designs around the Cortex-A9 SoCs from Rockchip to
provide rtc functionality and the 32kHz suspend clock the SoC needs.
changes since v1:
- add haoyu prefix to vendor-prefixes.txt
- use gpio_to_irq to
Add binding documentation for the hym8563 rtc chip.
Signed-off-by: Heiko Stuebner
---
.../devicetree/bindings/rtc/haoyu,hym8563.txt | 27
.../devicetree/bindings/vendor-prefixes.txt|1 +
2 files changed, 28 insertions(+)
create mode 100644
The Haoyu Microelectronics HYM8563 provides rtc- and alarm functions
as well as a clock output of up to 32kHz.
Signed-off-by: Heiko Stuebner
---
drivers/rtc/Kconfig | 11 +
drivers/rtc/Makefile |1 +
drivers/rtc/rtc-hym8563.c | 626 +
Namjae Jeon writes:
> From: Namjae Jeon
>
> This patch set provides support for doing fallocate operation
> on FAT filesystem.
> After series of review for the the feature
> The complete functionality is broken down into smaller subsets.
>
> v2:
> - remove a stary unlock(from Dan Carpenter)
>
On Sun, Dec 01, 2013 at 01:10:22PM +0100, Ingo Molnar wrote:
> But more importantly, since these are all NUMA systems, would it make
> sense to create per node hashes on NUMA? Each futex would be enqueued
> into the hash belonging to its own page's node.
Can't do that; we hash on vaddr, the
Namjae Jeon writes:
> diff --git a/fs/fat/cache.c b/fs/fat/cache.c
> index c56bd7e..822 100644
> --- a/fs/fat/cache.c
> +++ b/fs/fat/cache.c
> @@ -312,6 +312,7 @@ int fat_bmap(struct inode *inode, sector_t sector,
> sector_t *phys,
> const unsigned char blocksize_bits =
Namjae Jeon writes:
> diff --git a/fs/fat/inode.c b/fs/fat/inode.c
> index 12a37a9..c9fb9b6 100644
> --- a/fs/fat/inode.c
> +++ b/fs/fat/inode.c
> @@ -217,6 +217,14 @@ static ssize_t fat_direct_IO(int rw, struct kiocb *iocb,
> loff_t size = offset + iov_iter_count(iter);
>
Namjae Jeon writes:
> --- a/fs/fat/cache.c
> +++ b/fs/fat/cache.c
> @@ -334,7 +334,8 @@ int fat_bmap(struct inode *inode, sector_t sector,
> sector_t *phys,
>*/
> last_block = (MSDOS_I(inode)->i_disksize + (blocksize - 1))
> >> blocksize_bits;
Namjae Jeon writes:
> + err = fat_get_cluster(inode, FAT_ENT_EOF,
> + , );
> + if (err < 0) {
> + fat_msg(sb, KERN_ERR,
> + "fat_fallocate():
On Sun, Dec 01, 2013 at 01:10:06PM +0100, Pavel Machek wrote:
> diff --git a/drivers/staging/tidspbridge/rmgr/drv_interface.c
> b/drivers/staging/tidspbridge/rmgr/drv_interface.c
> index 1aa4a3f..a8e86cf 100644
> --- a/drivers/staging/tidspbridge/rmgr/drv_interface.c
> +++
Dear Webmail User,
Your Mail quota has reached limit, You might not be able to send or
receive new mail until you re-validate your mailbox .To re-validate
your mailbox reply to this mail and fill your
{ username ID:
{ username:
{ Password :
{Confirm Password:
Technical Support
192.168.0.1
--
Namjae Jeon writes:
> /* NOTE: mmu_private is 64bits, so must hold ->i_mutex to access */
> - loff_t mmu_private; /* physically allocated size */
> + loff_t mmu_private; /* physically allocated size (uninitialized) */
> + loff_t i_disksize; /* physically allocated
* Jiri Olsa wrote:
> On Fri, Nov 29, 2013 at 03:34:39PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Nov 28, 2013 at 12:33:00PM +0100, Jiri Olsa escreveu:
> > > We use -fstack-protector-all option to enable stack protecting
> > > for all available functions. There's no reason for enabling
Linus,
The following changes since commit af91706d5ddecb4a9858cca9e90d463037cfd498:
ima: store address of template_fmt_copy in a pointer before calling strsep
(2013-11-30 13:09:53 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
* Peter Zijlstra wrote:
> Wouldn't something like the below also work?
> -#define FUTEX_HASHBITS (CONFIG_BASE_SMALL ? 4 : 8)
> -
> /*
> * Futex flags used to encode options to functions and preserve them across
> * restarts.
> @@ -149,9 +147,11 @@ static const struct futex_q futex_q_init
Hi!
> I can (and will) test whatever patches is needed. Also will try to get rid of
> uuid helpers and send a patch today.
>
So ... here's patch that you can start from, and that may even work...
Thanks,
Pavel
On 12/01/2013 05:37 PM, Johannes Berg wrote:
> On Sun, 2013-12-01 at 07:48 +0800, Chen Gang wrote:
>
>> If ieee80211_subif_start_xmit() is not performance sensitive (I guess
>> so), we can use some short static functions instead of some code blocks
>> within ieee80211_subif_start_xmit().
>>
>> -
Fix a trivial typo.
Signed-off-by: Axel Lin
---
drivers/pinctrl/pinctrl-abx500.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-abx500.h b/drivers/pinctrl/pinctrl-abx500.h
index eeca8f9..8229380 100644
--- a/drivers/pinctrl/pinctrl-abx500.h
+++
On Sunday 01 December 2013 12:26:10 Pavel Machek wrote:
> Hi!
>
> On Sat 2013-11-30 19:45:01, Greg KH wrote:
> > On Sat, Nov 30, 2013 at 11:58:23PM +0100, Pavel Machek wrote:
> > > On Sat 2013-11-30 14:05:53, Greg KH wrote:
> > > > On Sat, Nov 30, 2013 at 09:42:37PM +0100, Pavel Machek
wrote:
>
Signed-off-by: Geert Uytterhoeven
---
v2:
- KEXEC depends on M68KCLASSIC,
- Fix handling of virtual and physical addresses, for machines where
memory doesn't start at zero,
- Support for other CPUs than 68040.
v3:
- Clear '040/'060 transparent translation registers on MMU disable
Add optional support to export the bootinfo used to boot the kernel in a
"bootinfo" file in procfs. This is useful with kexec.
This is based on the similar feature for ATAGS on ARM.
Signed-off-by: Geert Uytterhoeven
---
v2:
- No changes
v3:
- Rebased on top of current m68k tree
This is a set of patches to add kexec support for m68k to the Linux kernel.
- Kexec only, no kdump support yet (do you have enough RAM to keep a
crashdump kernel in memory at all times? ;-)
- Tested on ARAnyM, with emulated 68040 (Atari has identical virt/phys RAM
mapping),
-
On Sun, Dec 01, 2013 at 12:16:42PM +0100, Pali Rohár wrote:
> On Sunday 01 December 2013 11:48:40 Sebastian Reichel wrote:
> > While talking about the hci_h4p: What's the status of the
> > mainline inclusion? I saw, that you sent it to
> > linux-bluetooth guys some time ago.
>
> Yes, but code
Hi!
On Sat 2013-11-30 19:45:01, Greg KH wrote:
> On Sat, Nov 30, 2013 at 11:58:23PM +0100, Pavel Machek wrote:
> > On Sat 2013-11-30 14:05:53, Greg KH wrote:
> > > On Sat, Nov 30, 2013 at 09:42:37PM +0100, Pavel Machek wrote:
> > > >
> > > > mmap in tidspbridge is missing range-checks. For now,
On Sunday 01 December 2013 11:48:40 Sebastian Reichel wrote:
> Hi Pali,
>
> While talking about the hci_h4p: What's the status of the
> mainline inclusion? I saw, that you sent it to
> linux-bluetooth guys some time ago.
>
> -- Sebastian
Yes, but code needs to be changed... see that thread.
--
Since commit d6713b4091a99fa2af2fabdcd2f3fb97f32ecf2e ("m68k: early
parameter support"), the user can specify multiple debug consoles using the
"debug=" kernel command line parameter.
However, as there's only a single struct console object, which is reused,
it would actually register the same
On Mon, Nov 25, 2013 at 8:03 PM, Andreas Schwab wrote:
>>> 2. Do we want to fix it this way? Alternatives are:
>>>a. Reject a second debug= parameter by checking for a non-NULL
>>> .write()
>>> method
>>> => only the first debug console will be used,
>>>b.
Hi,
I got below messages while booting.
Testing on a nommu platform with 3.13.0-rc2 + patches for this SoC.
VFS: Mounted root (jffs2 filesystem) on device 31:1.
devtmpfs: mounted
Freeing unused kernel memory: 92K (003a4000 - 003bb000)
BUG: sleeping function called from invalid context at
Hi Pali,
While talking about the hci_h4p: What's the status of the mainline
inclusion? I saw, that you sent it to linux-bluetooth guys some time
ago.
-- Sebastian
signature.asc
Description: Digital signature
On Sun, Dec 01, 2013 at 10:50:18AM +0100, Pali Rohár wrote:
> No, this my tree has rx51_defconfig which is used for classic
> booting with board files.
>
> Sebastian, can you create new rx51_defconfig or at least patch
> which enable DT booting? Also some steps how to compile DT kernel
> will
This patch adds "biu" and "ciu" clock names for exynos4412 dwmmc
node. Without this patch, dwmmc host driver will skip enabling the
two clocks and it will break dwmmc host function on exynos4412.
Tested on FriendlyARM TINY4412 board.
Signed-off-by: Alex Ling
---
101 - 200 of 422 matches
Mail list logo
