This patch adds PPMU (Performance Profiling Monitoring Unit) dt node
Exynos5260 SoC.
Exynos5260 SoC has following PPMU IPs:
- PPMU_DREX0_S0 0x10c6
- PPMU_DREX0_S1 0x10c7
- PPMU_DREX1_S0 0x10c8
- PPMU_DREX1_S1 0x10c9
- PPMU_EAGLE0x10cc
- PPMU_KFC 0x10cd
- PPMU_MFC
John,
On Mon, 2014-10-27 at 11:44 +0100, Paul Bolle wrote:
> Your commit 715f2e581856 ("MIPS: ralink: cleanup early_printk") landed
> in today's linux-next (ie, next-20141027). It adds two checks for
> CONFIG_SOC_MT7621. The patch to add Kconfig symbol SOC_MT7621 is still
> pending (see
This patch add PPMU (Platform Performance Monitoring Unit) dt node
to estimate the utilization of each IP in Exynos SoC throught DEVFREQ Event
subsystem.
This patch adds following PPMU dt nodes:
- PPMU_DMC0 0x106a
- PPMU_DMC1 0x106b
- PPMU_RIGHTBUS 0x112A
- PPMU_LEFTBUS
On 01/12/2015 01:26 PM, Ahmed S. Darwish wrote:
> On Mon, Jan 12, 2015 at 12:51:49PM +0100, Marc Kleine-Budde wrote:
>> On 01/08/2015 04:19 PM, Ahmed S. Darwish wrote:
>>
>> [...]
>>
> MODULE_DEVICE_TABLE(usb, kvaser_usb_table);
> @@ -463,7 +631,18 @@ static int
John,
On Mon, 2014-10-27 at 11:06 +0100, Paul Bolle wrote:
> Your commit 0b162e003c2c ("MIPS: ralink: add rt2880 pci driver") landed
> in today's linux-next (ie, next-20141027). It adds a check for
> CONFIG_SOC_RT2880. But there's no Kconfig symbol SOC_RT2880.
>
> Did you perhaps mean
(2015/01/10 19:33), Namhyung Kim wrote:
> The find_probe_trace_events_from_map() searches matching symbol from a
> map (so from a backing dso). For uprobes, it'll create a new map (and
> dso) and loads it using a filter. It's a little bit inefficient in that
> it'll read out the symbol table
John,
On Mon, 2014-11-10 at 13:32 +0100, Paul Bolle wrote:
> On Mon, 2014-10-27 at 11:03 +0100, John Crispin wrote:
> > On 27/10/2014 10:54, Paul Bolle wrote:
> > > Your commit 78865eacb4aa ("MIPS: ralink: add illegal access
> > > driver") landed in today's linux-next (ie, next-20141027). That
>
On Mon, Jan 12, 2015 at 12:51:49PM +0100, Marc Kleine-Budde wrote:
> On 01/08/2015 04:19 PM, Ahmed S. Darwish wrote:
>
> [...]
>
> >>> MODULE_DEVICE_TABLE(usb, kvaser_usb_table);
> >>> @@ -463,7 +631,18 @@ static int kvaser_usb_get_software_info(struct
> >>> kvaser_usb *dev)
> >>> if (err)
>
On Mon, Jan 12, 2015 at 10:25:28AM +0100, Philipp Zabel wrote:
> Jean-Francois' reply already reflects this, but the 'port' nodes should
> correspond to physical ports of the device if possible. If you can
> configure the device to have dedicated input pins for I2S, SPDIF0, and
> SPDIF1 at the
Hi Linus,
On Sat, Jan 10, 2015 at 10:33:46PM +0100, Linus Walleij wrote:
> On Tue, Dec 2, 2014 at 2:55 PM, Sascha Hauer wrote:
>
> Sorry for taking eternities to get back on this, I ran into a merge window
> and some christmas. I do hope we can resolve this in the current
> development cycle so
(2015/01/10 19:33), Namhyung Kim wrote:
> The commit dfef99cd0b2c ("perf probe: Use ref_reloc_sym based address
> instead of the symbol name") converts kprobes to use ref_reloc_sym
> (i.e. _stext) and offset instead of using symbol's name directly. So
> on my system, adding do_fork ends up with
Peter Zijlstra writes:
> On Fri, Nov 14, 2014 at 03:43:45PM +0200, Alexander Shishkin wrote:
>> +static void pt_event_stop(struct perf_event *event, int mode)
>> +{
>> +struct pt *pt = this_cpu_ptr(_ctx);
>> +
>> +ACCESS_ONCE(pt->handle_nmi) = 0;
>
> Why is this needed? Will the hardware
Original code failed to disarm the probed instruction after
echo 0 > /sys/kernel/debug/kprobes/enabled
if OPTPROBE is enabled.
This patch checks kprobes_all_disarmed in unoptimized_kprobe().
Signed-off-by: Wang Nan
---
kernel/kprobes.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
On Sat, Jan 10, 2015 at 09:36:13PM +, Arnd Bergmann wrote:
> On Saturday 10 January 2015 13:00:27 Linus Torvalds wrote:
> > > IIRC, AIX works great with 64k pages, but only because of two
> > > reasons that don't apply on Linux:
> >
> > .. there's a few other ones:
> >
> > (c) nobody really
On Mon, 2015-01-12 at 11:57 +0100, Boris Brezillon wrote:
> at91sam9rl SoC has an erratum forcing us to toggle the BIAS on USB
> suspend/resume events.
>
> This specific handling is only activated when CONFIG_ARCH_AT91SAM9RL is
> set and this option is only set when building a non-DT kernel,
On Fri, Jan 09, 2015 at 06:21:32PM +0100, Wolfram Sang wrote:
> +static int i2c_quirk_error(struct i2c_adapter *adap, struct i2c_msg *msg,
> char *err_msg)
> +{
> + dev_err(>dev, "quirk: %s (addr 0x%04x, size %u)\n", err_msg,
> msg->addr, msg->len);
> + return -EOPNOTSUPP;
> +}
So, what
(2015/01/12 20:26), Jiri Olsa wrote:
> On Sat, Jan 10, 2015 at 07:33:47PM +0900, Namhyung Kim wrote:
>> The commit dfef99cd0b2c ("perf probe: Use ref_reloc_sym based address
>> instead of the symbol name") converts kprobes to use ref_reloc_sym
>> (i.e. _stext) and offset instead of using symbol's
Hi Marc,
On Mon, Jan 12, 2015 at 12:43:56PM +0100, Marc Kleine-Budde wrote:
> On 01/11/2015 09:36 PM, Ahmed S. Darwish wrote:
[...]
> > diff --git a/drivers/net/can/usb/kvaser_usb.c
> > b/drivers/net/can/usb/kvaser_usb.c
> > index 0eb870b..da47d17 100644
> > ---
Hi Jiri,
On Monday 12 January 2015 04:39 PM, Jiri Olsa wrote:
> On Sat, Jan 10, 2015 at 04:40:52PM +0530, Vineet Gupta wrote:
>> This is due to duplicated unistd inclusion (via uClibc headers + kernel
>> headers)
>> Also seen on ARM uClibc based tools
>>
>> --- ARC build
On Sat, Jan 10, 2015 at 03:14:33PM +, George Bush wrote:
> Hi all
>
> I notice we have hibernation.c in arm/kernel, however, I don't find it in
> arm64.
> Does it mean arm64 do not support hibernation/suspend-to-disk function?
Yes, not at the moment, but we have planned to implement it.
>
From: Kent Overstreet
Allow __blk_queue_bounce() to handle bios with more than BIO_MAX_PAGES
segments. Doing that, it becomes possible to simplify the block layer
in the kernel.
The issue is that any code that clones the bio and must clone the biovec
(i.e. it can't use bio_clone_fast()) won't
At Mon, 12 Jan 2015 11:59:25 +0100,
David Henningsson wrote:
>
>
>
> On 2015-01-11 22:44, Hans de Bruin wrote:
> > running 3.19-rc1 alsamixer show these options:
> >
> > Master
> > PCM
> > Line Out
> > Mic Boost
> > Auto Mute mode
> >
> > Line out now controls the vole of the speaker (this
From: Kent Overstreet
There has been workarounds only in bcache, for splitting pool as well
as submitting bios. Since generic_make_request() is able to handle
arbitrarily sized bios, it's now possible to delete those hacks.
Cc: linux-bca...@vger.kernel.org
Signed-off-by: Kent Overstreet
On Sat, Jan 10, 2015 at 08:16:02PM +, Arnd Bergmann wrote:
> Regarding ARM64 in particular, I think it would be nice to investigate
> how to extend the THP code to cover 64KB TLBs when running with the 4KB
> page size. There is a hint bit in the page table to tell the CPU that
> a set of 16
From: Kent Overstreet
Btrfs has been doing bio splitting from btrfs_map_bio(), by checking
device limits as well as calling ->merge_bvec_fn() etc. That is not
necessary any more, because generic_make_request() is now able to
handle arbitrarily sized bios. So clean up unnecessary code paths.
Cc:
From: Kent Overstreet
Remove bio_fits_rdev() completely, because ->merge_bvec_fn() has now
gone. There's no point in calling bio_fits_rdev() only for ensuring
aligned read from rdev.
Cc: Neil Brown
Cc: linux-r...@vger.kernel.org
Signed-off-by: Kent Overstreet
[dpark: add more description in
From: Kent Overstreet
Since generic_make_request() can now handle arbitrary size bios, all we
have to do is make sure the bvec array doesn't overflow.
__bio_add_page() doesn't need to call ->merge_bvec_fn(), where
we can get rid of unnecessary code paths.
Note that removing call to
From: Kent Overstreet
Call pre-defined helper bio_add_page() instead of open coding for
iterating through bi_io_vec[]. Doing that, it's possible to make some
parts in filesystems and mm/page_io.c simpler than before.
Acked-by: Dave Kleikamp
Cc: Christoph Hellwig
Cc: Al Viro
Cc:
On 01/08/2015 04:19 PM, Ahmed S. Darwish wrote:
[...]
>>> MODULE_DEVICE_TABLE(usb, kvaser_usb_table);
>>> @@ -463,7 +631,18 @@ static int kvaser_usb_get_software_info(struct
>>> kvaser_usb *dev)
>>> if (err)
>>> return err;
>>>
>>> - dev->fw_version =
From: Kent Overstreet
As generic_make_request() is now able to handle arbitrarily sized bios,
it's no longer necessary for each individual block driver to define its
own ->merge_bvec_fn() callback. Remove every invocation completely.
Cc: Jens Axboe
Cc: Lars Ellenberg
Cc:
On Mon, 2015-01-12 at 18:53 +0800, 曾婷葳 (tammy_tseng) wrote:
> Hi,
> This package of patch is to add support for multitouch behavior for SiS touch
> products.
> The patch of SiS i2c multitouch driver is in input/touchscreen.
>
> Signed-off-by: Tammy Tseng
>
> ---
> diff --git
Update block/biovecs.txt so that it includes a note on what kind of
effects arbitrarily sized bios would bring to the block layer.
Also fix a trivial typo, bio_iter_iovec.
Cc: Christoph Hellwig
Cc: Kent Overstreet
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Signed-off-by: Dongsu Park
Rewrite __bio_copy_iov() so that it can call either _read() or _write()
variant, which is determined by direction to_iov, given as either READ
or WRITE. Moreover, make __bio_copy_iov() take its parameter iov_iter
by value, to avoid awkward situations like ref-/dereferencing pointer
and value
This is the second attempt of simplifying block layer based on immutable
biovecs. Immutable biovecs, implemented by Kent Overstreet, have been
available in mainline since v3.14. Its original goal was actually making
generic_make_request() accept arbitrarily sized bios, and pushing the
splitting
From: Kent Overstreet
The way the block layer is currently written, it goes to great lengths
to avoid having to split bios; upper layer code (such as bio_add_page())
checks what the underlying device can handle and tries to always create
bios that don't need to be split.
But this approach
Hi Paul,
> You got stack traces with the stall warnings, correct? If so, please look
> at them and at Documentation/RCU/stallwarn.txt and see if the kernel is
> looping somewhere inappropriate.
Yes and no. I have a stack trace, but it is not generated by a stall warning.
More
precise: I can
From: Al Viro
> > I think the problem with wmnet is not that it was expecting the fields
> > to be aligned because it never had problems before (when definitely more
> > than 10 megabytes were received, wmnet is crappy but not _that_ crappy).
> >
> > I think the problem really was here,
> >
> >
On Mon, Jan 12, 2015 at 04:38:16PM +0530, Rahul Sharma wrote:
> Hi Pablo, Hannes
>
> On Fri, Jan 9, 2015 at 9:20 PM, Hannes Frederic Sowa
> wrote:
> > On Fr, 2015-01-09 at 12:45 +0100, Pablo Neira Ayuso wrote:
> >> Hi Hannes,
> >>
> >> On Fri, Jan 09, 2015 at 12:34:15PM +0100, Hannes Frederic
On Thu, 08 Jan, at 06:48:32PM, Ard Biesheuvel wrote:
> @@ -46,4 +54,26 @@ extern void efi_idmap_init(void);
>
> #define EFI_ALLOC_ALIGN SZ_64K
>
> +/*
> + * On ARM systems, virtually remapped UEFI runtime services are set up in
> three
> + * distinct stages:
> + * - The stub
From: Kent Overstreet
Split up a part of the code that was in __bio_map_user_iov() into
a new function bio_get_user_pages(). This helper is going to be used
by future block layer rewriting, especially from direct-IO part.
Note that this relies on the recent change to make
generic_make_request()
correct.
Acked-by: Dmitry Kasatkin
Dmitry
On 12 January 2015 at 13:43, David Howells wrote:
> Dmitry Kasatkin wrote:
>
>> Ack.
>
> To what email address do I translate that now?
>
> Acked-by: Dmitry Kasatkin
>
> perchance?
>
> David
--
Thanks,
Dmitry
--
To unsubscribe from this
From: Kent Overstreet
Make use of a new interface provided by iov_iter, backed by
scatter-gather list of iovec, instead of the old interface based on
sg_iovec. Also use iov_iter_advance() instead of manual iteration.
This commit should contain only literal replacements, without
functional
From: Kent Overstreet
Refactor the common part in bio_copy_user_iov() and
__bio_map_user_iov() to separate out iov_count_pages() into the general
iov_iter API, instead of open coding iov iterations as done previously.
This commit should contain only literal replacements, without
functional
From: Kent Overstreet
Make _submit_bh() handle refcounting by increasing bio->bi_remaining,
followed by bio_endio(). Since bio chaining was introduced with
196d38bccfcf ("block: Generic bio chaining"), refcounting should be
done on bi_remaining instead of ancient bio_cnt. Doing that, calling
From: Kent Overstreet
Refactor sync_request_write() of md/raid10 to use bio_copy_data()
instead of open coding bio_vec iterations.
Cc: Christoph Hellwig
Cc: Neil Brown
Cc: linux-r...@vger.kernel.org
Signed-off-by: Kent Overstreet
[dpark: add more description in commit message]
Signed-off-by:
This is a preparation series for simplifying block layer based on immutable
biovecs, a spin off of the v1 of simplifying patchset. [1] The original
goal of simplifying block layer was actually making generic_make_request()
accept arbitrarily sized bios, and pushing the splitting down to the
From: Kent Overstreet
Make bio submission in kernel/power/block_io.c to properly submit
bios also when bio_chain is not available. In that case, it's not
necessary to handle refcount with bio_get(), but it's saner to simply
call a predefined helper submit_bio_wait(). So call bio_get() only
when
Intro:
Smatch is a C static checker with a lot of kernel specific checks. You
can download it from: http://repo.or.cz/w/smatch.git.
Notes:
It has been a year and a half since the last release so there have been
a lot of changes everywhere. The main thing continues to be tracking
values
On 01/11/2015 09:36 PM, Ahmed S. Darwish wrote:
> From: Ahmed S. Darwish
>
> CAN to USB interfaces sold by the Swedish manufacturer Kvaser are
> divided into two major families: 'Leaf', and 'UsbcanII'. From an
> Operating System perspective, the firmware of both families behave
> in a not too
(2015/01/10 19:33), Namhyung Kim wrote:
> The exclusive options are to prohibit use of conflicting options at the
> same time. But it had a side effect that it also limits a such option
> can be used at most once. Currently the only user of the flag is perf
> probe and it allows to use such
Dmitry Kasatkin wrote:
> Ack.
To what email address do I translate that now?
Acked-by: Dmitry Kasatkin
perchance?
David
--
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
(2015/01/05 21:32), Wang Nan wrote:
> Original code failed to disarm the probed instruction after
>
> echo 0 > /sys/kernel/debug/kprobes/enabled
>
> if OPTPROBE is enabled.
>
> This is caused by a piece of logically inconsistent code:
>
> unoptimize_kprobe(p, false);
> if
On Mon, Jan 12, 2015 at 04:26:41AM +, Hanjun Guo wrote:
> On 2015年01月10日 03:04, Lorenzo Pieralisi wrote:
> > On Sun, Jan 04, 2015 at 10:55:09AM +, Hanjun Guo wrote:
> >> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
> >> the former signals to the OS that the firmware is
On Sat, Jan 10, 2015 at 10:36:13PM +0100, Arnd Bergmann wrote:
> On Saturday 10 January 2015 13:00:27 Linus Torvalds wrote:
> > so I feel pretty confident in saying it won't happen. It's just too
> > much of a bother, for little to no actual upside. It's likely a much
> > better approach to try to
On 01/12/2015 12:19 PM, Kirill A. Shutemov wrote:
> On Mon, Jan 12, 2015 at 02:26:29PM +1100, Stephen Rothwell wrote:
>> [Just cc'ing Andrew as this patch is in his tree]
>>
>> On Mon, 12 Jan 2015 11:19:01 +0800 Huang Ying wrote:
>> >
>> > FYI, we noticed the below changes on
>> >
>> >
El 12/01/15 a les 8.09, Bob Liu ha escrit:
>
> On 01/09/2015 11:51 PM, Roger Pau Monné wrote:
>> El 06/01/15 a les 14.19, Bob Liu ha escrit:
>>> When there is no enough free grants, gnttab_alloc_grant_references()
>>> will fail and block request queue will stop.
>>> If the system is always lack
On Sat, Jan 10, 2015 at 1:33 AM, Rich Felker wrote:
> On Fri, Jan 09, 2015 at 07:17:41PM -0600, Eric W. Biederman wrote:
>> Rich Felker writes:
>>
>> > I'm not proposing code because I'm a libc developer not a kernel
>> > developer. I know what's needed for userspace to provide a conforming
>> >
On Mon, 2014-11-10 at 20:32 +0100, Paul Bolle wrote:
> On Mon, 2014-11-10 at 08:40 -0700, Mathieu Poirier wrote:
> > On 10 November 2014 03:34, Paul Bolle wrote:
> > > On Mon, 2014-11-03 at 11:07 -0700, mathieu.poir...@linaro.org wrote:
> > >> +#ifdef CONFIG_CORESIGHT_SOURCE_ETM_DEFAULT_ENABLE
>
On 08/01/15 15:06, Imre Palik wrote:
> On 01/07/15 17:30, Ian Campbell wrote:
>> On Wed, 2015-01-07 at 17:16 +0100, Imre Palik wrote:
>>> From: "Palik, Imre"
>>>
>>> In Dom0's the use of the TSC clocksource (whenever it is stable enough to
>>> be used) instead of the Xen clocksource should not
Hello, Vladimir.
On Mon, Jan 12, 2015 at 11:01:14AM +0300, Vladimir Davydov wrote:
> Come to think of it, I wonder how many users actually want to mount
> different controllers subset after unmount. Because we could allow
It wouldn't be a common use case but, on the face of it, we still
support
Am 12.01.2015 um 12:26 schrieb Harald Geyer:
> Richard Weinberger writes:
>> Am 10.01.2015 um 12:14 schrieb Jonathan Cameron:
>>> On 07/01/15 12:15, Harald Geyer wrote:
As we access i-1 we must not start with i=0.
From: Richard Weinberger
Signed-off-by: Richard Weinberger
Richard Weinberger writes:
> Am 10.01.2015 um 12:14 schrieb Jonathan Cameron:
> > On 07/01/15 12:15, Harald Geyer wrote:
> >> As we access i-1 we must not start with i=0.
> >>
> >> From: Richard Weinberger
> >> Signed-off-by: Richard Weinberger
> >> Acked-by: Hartmut Knaack
> >> Acked-by:
On Sat, Jan 10, 2015 at 07:33:47PM +0900, Namhyung Kim wrote:
> The commit dfef99cd0b2c ("perf probe: Use ref_reloc_sym based address
> instead of the symbol name") converts kprobes to use ref_reloc_sym
> (i.e. _stext) and offset instead of using symbol's name directly. So
> on my system, adding
(2015/01/05 21:31), Wang Nan wrote:
> In original code, the probed instruction doesn't get optimized after
>
> echo 0 > /sys/kernel/debug/kprobes/enabled
> echo 1 > /sys/kernel/debug/kprobes/enabled
>
> This is because original code checks kprobes_all_disarmed in
> optimize_kprobe(), but this
On Fri, Jan 09, 2015 at 09:14:01PM -0500, Johannes Weiner wrote:
> The swap controller code is scattered all over the file. Gather all
> the code that isn't directly needed by the memory controller at the
> end of the file in its own CONFIG_MEMCG_SWAP section.
>
> Signed-off-by: Johannes Weiner
Hi Marc,
On Sun, Jan 11, 2015 at 03:36:12PM -0500, Ahmed S. Darwish wrote:
> From: Ahmed S. Darwish
>
> CAN to USB interfaces sold by the Swedish manufacturer Kvaser are
> divided into two major families: 'Leaf', and 'UsbcanII'. From an
> Operating System perspective, the firmware of both
Hi Liviu,
Welcome back! ;-)
On 12/01/15 11:15, Liviu Dudau wrote:
> On Mon, Jan 05, 2015 at 09:05:06AM +, Marc Zyngier wrote:
>> Hi Liviu,
>
> Hi Marc,
>
>>
>> On 01/12/14 12:45, Liviu Dudau wrote:
>>> During a recent cleanup of the arm64 DTs it has become clear that
>>> the handling of
On Mon, Jan 12, 2015 at 02:26:29PM +1100, Stephen Rothwell wrote:
> [Just cc'ing Andrew as this patch is in his tree]
>
> On Mon, 12 Jan 2015 11:19:01 +0800 Huang Ying wrote:
> >
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(2015/01/10 19:33), Namhyung Kim wrote:
> When it failed to write probe commands to the probe_event file in
> debugfs, it needs to propagate the error code properly. Current code
> blindly uses the return value of the write(2) so it always uses
> -1 (-EPERM) and it might confuse users.
>
Good
Dear Myungjoo,
On 01/12/2015 04:15 PM, MyungJoo Ham wrote:
>>
>> This patch adds the list of supported devfreq-event type as following.
>> Each devfreq-event device driver would support the various devfreq-event type
>> for devfreq governor at the same time.
>> - DEVFREQ_EVENT_TYPE_RAW_DATA
This extends the Unified Property Interface by adding
"Generic Property" to it for cases where device tree or ACPI
are not being used.
That makes the Unified Property Interface cover most of the
cases where information is extracted from custom
platform_data in the drivers, i.e. removing also the
On Mon, Jan 05, 2015 at 09:05:06AM +, Marc Zyngier wrote:
> Hi Liviu,
Hi Marc,
>
> On 01/12/14 12:45, Liviu Dudau wrote:
> > During a recent cleanup of the arm64 DTs it has become clear that
> > the handling of PPIs in _set_type() is incorrect. The ARM TRMs
> > for GICv2 and later allow
On Fri, Jan 09, 2015 at 09:14:00PM -0500, Johannes Weiner wrote:
> The initialization code for the per-cpu charge stock and the soft
> limit tree is compact enough to inline it into mem_cgroup_init().
>
> Signed-off-by: Johannes Weiner
> ---
> mm/memcontrol.c | 57
>
On Mon, Jan 12, 2015 at 11:01:46AM +0100, Jiri Slaby wrote:
> On 01/10/2015, 06:01 AM, Hugh Dickins wrote:
> > On Fri, 9 Jan 2015, Jiri Slaby wrote:
> >
> >> From: Hugh Dickins
> >>
> >> 3.12-stable review patch. If anyone has any objections, please let me
> >> know.
> >>
> >> ===
Hi Jiri,
On Monday 12 January 2015 04:35 PM, Jiri Olsa wrote:
> On Sat, Jan 10, 2015 at 04:40:54PM +0530, Vineet Gupta wrote:
>
> SNIP
>
>> [SNIP]
>> test-timerfd.bin\
>> test-libdw-dwarf-unwind.bin \
>> @@ -47,6 +48,9 @@ test-all.bin:
>> test-hello.bin:
>>
On Fri, Jan 09, 2015 at 09:13:59PM -0500, Johannes Weiner wrote:
> kzalloc_node() automatically falls back to nodes with suitable memory.
>
> Signed-off-by: Johannes Weiner
Reviewed-by: Vladimir Davydov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Hi Beomho,
On Mon, 2015-01-12 at 19:51 +0900, Beomho Seo wrote:
> On 01/12/2015 07:40 PM, Paul Bolle wrote:
> > When is the Kconfig symbol MFD_RT5033 expected to be included in the
> > tree?
>
> MFD_RT5033 have been applied in 09 Dec 2014.
> http://marc.info/?l=linux-pm=141822463218774=2
>
On 12/01/15 05:05, Juergen Gross wrote:
> In the setup code of the linear mapped p2m list several bugs have
> been found, especially for 32 bit dom0. These patches correct the
> errors and make 32 bit dom0 bootable again.
Applied to stable/for-linus-3.19, thanks.
David
--
To unsubscribe from
On 01/11/2015 09:15 PM, Ahmed S. Darwish wrote:
> From: Ahmed S. Darwish
>
> Let the error counters be more accurate in case of Out of
> Memory conditions.
Please have a look at kvaser_usb_rx_error(), the whole state handling is
omitted in case of OOM.
Marc
--
Pengutronix e.K.
On Sat, Jan 10, 2015 at 04:40:52PM +0530, Vineet Gupta wrote:
> This is due to duplicated unistd inclusion (via uClibc headers + kernel
> headers)
> Also seen on ARM uClibc based tools
>
> --- ARC build -->8-
>
> CC util/evlist.o
> In file included from
>
Le 12/01/2015 11:57, Boris Brezillon a écrit :
> Hello,
>
> Here is a set of patches porting existing at91sam9rl erratum handling to
> DT and adding new code to handle at91sam9g45/9x5 erratum.
> It also adds several compatible strings to differentiate those errata.
>
> These patches should be
Hi Pablo, Hannes
On Fri, Jan 9, 2015 at 9:20 PM, Hannes Frederic Sowa
wrote:
> On Fr, 2015-01-09 at 12:45 +0100, Pablo Neira Ayuso wrote:
>> Hi Hannes,
>>
>> On Fri, Jan 09, 2015 at 12:34:15PM +0100, Hannes Frederic Sowa wrote:
>> > On Fri, Jan 9, 2015, at 08:18, Rahul Sharma wrote:
>> > > Hi
Hi Dave,
This is actually a fix for 3.19, can you take it for the next rc ?
Thanks!
On 08/01/2015 at 11:55:58 +0100, Nicolas Ferre wrote :
> Le 07/01/2015 23:59, Alexandre Belloni a écrit :
> > The clock is enabled without being prepared, this leads to:
> >
> > WARNING: CPU: 0 PID: 1 at
Robert Jarzmik writes:
> Once reviewed, I'd like this serie to go through the pxa tree. Therefore an
> ack
> from Mike is necesary for the last patch (add missing pxa27x clocks).
>
> This is targeted at 3.20 window.
Well, no review is good news ... or not. Mike I still need an ack for patch
On Sat, Jan 10, 2015 at 04:40:50PM +0530, Vineet Gupta wrote:
> From: Alexey Brodkin
>
> ARC Linux uses the no legacy syscalls abi and corresponding uClibc headers
> statfs defines f_type to be U32 which causes perf build breakage
>
>
On 01/11/2015 09:49 PM, Ahmed S. Darwish wrote:
> From: Ahmed S. Darwish
>
> We should not touch the packet after a netif_rx: it might
> get freed behind our back.
>
> Suggested-by: Marc Kleine-Budde
> Signed-off-by: Ahmed S. Darwish
Applied to can/master.
tnx,
Marc
--
Pengutronix e.K.
On Sat, Jan 10, 2015 at 04:40:54PM +0530, Vineet Gupta wrote:
SNIP
> @@ -198,6 +198,7 @@ CORE_FEATURE_TESTS = \
> libpython-version \
> libslang\
> libunwind \
> + pthread-attr-setaffinity-np
(2015/01/10 18:51), Namhyung Kim wrote:
> Hi Jiri,
>
> On Fri, Jan 09, 2015 at 04:44:21PM +0100, Jiri Olsa wrote:
>> On Fri, Jan 09, 2015 at 04:30:56PM +0100, Jiri Olsa wrote:
>>> On Sat, Jan 10, 2015 at 12:21:13AM +0900, Namhyung Kim wrote:
On Fri, Jan 09, 2015 at 03:55:39PM +0100, Jiri
Avoid interpreting useless status flags when we're not waiting for such
events by masking the status variable with the interrupt enabled register
value.
Reported-by: Patrice VILCHEZ
Signed-off-by: Boris Brezillon
Acked-by: Alexandre Belloni
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 6
On 2015-01-11 22:44, Hans de Bruin wrote:
running 3.19-rc1 alsamixer show these options:
Master
PCM
Line Out
Mic Boost
Auto Mute mode
Line out now controls the vole of the speaker (this 'new' channel had
volume 0 so did not hear anything). Changing PCM has no effect.
So, now that you have
at91sam9g45, at91sam9x5 and sama5 SoCs should not use
"atmel,at91sam9rl-udc" for their USB device compatible property since
this compatible is attached to a specific hardware bug fix.
Signed-off-by: Boris Brezillon
Acked-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9g45.dtsi | 2 +-
at91sam9g45 and at91sam9x5 SoCs have an hardware bug forcing us to
generate a pulse on the BIAS signal on "USB end of reset" and
"USB end of resume" events.
Reported-by: Patrice VILCHEZ
Signed-off-by: Boris Brezillon
Acked-by: Alexandre Belloni
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 28
Cache INT_ENB register value in order to avoid uncached iomem access, and
thus improve access time to INT_ENB value.
Signed-off-by: Boris Brezillon
Acked-by: Alexandre Belloni
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 52 ++---
Hello,
Here is a set of patches porting existing at91sam9rl erratum handling to
DT and adding new code to handle at91sam9g45/9x5 erratum.
It also adds several compatible strings to differentiate those errata.
These patches should be backported to 3.17 and 3.18 stable releases but
they do not
at91sam9rl SoC has an erratum forcing us to toggle the BIAS on USB
suspend/resume events.
This specific handling is only activated when CONFIG_ARCH_AT91SAM9RL is
set and this option is only set when building a non-DT kernel, which is
problematic since non-DT support for at91sam9rl SoC has been
Luis Henriques writes:
> On Sun, Jan 11, 2015 at 10:39:08PM +, Ben Hutchings wrote:
> Thanks Ben.
>
> Robert, do you think this is a problem? I can revert this patch as
> it has already been released in 3.16.7-ckt3.
Hi Luis,
No, no problem. It'll be an unused kconfig variable, that's all,
Hi,
This package of patch is to add support for multitouch behavior for SiS touch
products.
The patch of SiS hid multitouch driver is in hid.
Signed-off-by: Tammy Tseng
--
diff --git a/linux-3.18.1/drivers/hid/Kconfig b/linux-3.18.1/drivers/hid/Kconfig
index f42df4d..2be7677 100644
---
Hi,
This package of patch is to add support for multitouch behavior for SiS touch
products.
The patch of SiS i2c multitouch driver is in input/touchscreen.
Signed-off-by: Tammy Tseng
---
diff --git a/linux-3.18.1/drivers/input/touchscreen/Kconfig
Thank you reply.
On 01/12/2015 07:40 PM, Paul Bolle wrote:
> Beomho,
>
> On Fri, 2015-01-09 at 17:45 +0900, Beomho Seo wrote:
>> This patchset adds driver for Richtek rt5033 chip The chip contains
>> switching charge mode Li-Ion/Li-Polymer battery charger, fuelgauge.
>> Additionally, This
[s/lee.j...@linaro.org/lee.jo...@linaro.org]
On Mon, 2015-01-12 at 11:40 +0100, Paul Bolle wrote:
> Beomho,
>
> On Fri, 2015-01-09 at 17:45 +0900, Beomho Seo wrote:
> > This patchset adds driver for Richtek rt5033 chip The chip contains
> > switching charge mode Li-Ion/Li-Polymer battery
901 - 1000 of 2278 matches
Mail list logo
