On 12/04/2013 03:56 PM, Dan Williams wrote:
On Tue, Dec 3, 2013 at 11:05 PM, Qiao Zhou wrote:
sram driver can be used by many chips besides CPU_MMP2, and so build
it alone.
Reported-by: Dan Williams
Signed-off-by: Qiao Zhou
---
arch/arm/mach-mmp/Kconfig |5 +
arch/arm/mach-mmp/Ma
On Wed, 2013-12-04 at 10:12 +0800, Chen Gang wrote:
> It is really not urgent, and for keeping quality, it is necessary to
> spend suitable time resource (e.g 1 hour or more) to make, review and
> test this kind of patch carefully by oneself.
>
> So could you please help improve it when you have
> Could you check this patchset?
> Driver documentation was moved from 'Documentation' to
> 'drivers/mfd/lp3943.c'.
Well because the reset of the patch-set wasn't sent as replies to
[PATCH 0/X], it's now lost in the ulu. You will have to resubmit.
--
Lee Jones
Linaro STMicroelectronics Landing T
On 12/04/2013 07:09 AM, Nishanth Menon wrote:
> Due to the cross dependencies between hwmod for automanaged device
> information for OMAP and dts node definitions, we can run into scenarios
> where the dts node is defined, however it's hwmod entry is yet to be
> added. In these cases:
> a) omap_dev
> +int tps6586x_get_version(struct device *dev)
> +{
> + struct tps6586x *tps6586x = dev_get_drvdata(dev);
> +
> + return tps6586x->version;
> +}
> +EXPORT_SYMBOL_GPL(tps6586x_get_version);
I thought Mark suggested that this routine was converted to a 'static
inline' and moved into the hea
This patch set is to allow kdump 2nd kernel to wake up multiple CPUs,
a continueing work from:
[PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP
https://lkml.org/lkml/2013/10/16/300.
At v4, basic design has changed. Now users need to figure out initial
APIC ID of BSP in the 1st k
Hi,
> > + if (btype == META)
> > + rw |= REQ_META;
> > +
> > + if (is_read_io(rw)) {
> > + if (sync)
> > + rw |= READ_SYNC;
> > + submit_bio(rw, io->bio);
> > + trace_f2fs_submit_read_bio(sbi->sb, rw, type, io->bio);
> > + io-
I can constantly hit this issue:
I trace it to mm/filemap.c: add_to_page_cache_locked
I print the in_atomic status at BEGIN and END of add_to_page_cache_locked call.
Then I got in_atomic is true at the end of add_to_page_cache_locked call.
int add_to_page_cache_locked(struct page *page, struct ad
On Fri, 08 Nov 2013, Mark Brown wrote:
> From: Mark Brown
>
> This helps move us towards removing the bus custom operations.
>
> Signed-off-by: Mark Brown
> ---
> drivers/mfd/wm831x-i2c.c | 8 +---
> drivers/mfd/wm831x-spi.c | 8 +---
> 2 files changed, 10 insertions(+), 6 deletions(-
On Wed, Dec 04, 2013 at 08:38:08AM +0800, Lv Zheng wrote:
> In Linux kernel, ACPICA is wrapped and safely exported by CONFIG_ACPI. So
> all external modules should depend on CONFIG_ACPI rather than using ACPICA
> header directly for stubbing. But if we moves inclusions
> into "#ifdef CONFIG_ACPI
On Tue, 2013-12-03 at 10:29 -0800, Joe Perches wrote:
> Remove the unnecessary duplicate test of "if (skb) {"
> when !CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS.
>
> Remove now unnecessary __maybe_unused, neaten comment
> Remove unnecessary parenthesis around align cast.
> Substitute reference to depr
On 12/04/13 at 09:56am, Baoquan He wrote:
> On 11/20/13 at 12:50pm, Vivek Goyal wrote:
> > + * that kexec_mutex is held.
> > + */
>
> I think kexec_add_buffer is guaranteed to be called before allocating
> control pages, why not updating image->control_page after each time
> kexec_add_buffer is ca
On Tue, Dec 03, 2013 at 06:46:06PM +0530, Laxman Dewangan wrote:
> This new header file defines pincontrol constants for Tegra to
> use from Tegra's DTS file for pincontrol properties option.
>
> Signed-off-by: Laxman Dewangan
> ---
> Changes from V1:
> - Get rid of lots of macro and converge it
V1 -> V0:
No need for help text for MMP_SRAM in Kconfig and move it into MMP_TDMA
text in Kconfig.
Qiao Zhou (2):
arm: mmp: build sram driver alone
dma: mmp-tdma: select sram driver
arch/arm/mach-mmp/Kconfig |3 +++
arch/arm/mach-mmp/Makefile |3 ++-
drivers/dma/Kconfig|
sram driver can be used by many chips besides CPU_MMP2, and so build
it alone.
Reported-by: Dan Williams
Signed-off-by: Qiao Zhou
---
arch/arm/mach-mmp/Kconfig |3 +++
arch/arm/mach-mmp/Makefile |3 ++-
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-mmp/Kc
Reported-by: Dan Williams
Signed-off-by: Qiao Zhou
---
drivers/dma/Kconfig |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index dd2874e..599f0ae 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -288,9 +288,11 @@ co
Thank you Andrew.
On 12/04/2013 04:08 AM, Andrew Morton wrote:
On Tue, 3 Dec 2013 16:06:17 +0530 Raghavendra K T
wrote:
On a cpu with an empty numa node,
This makes no sense - numa nodes don't reside on CPUs.
I think you mean "on a CPU which resides on a memoryless NUMA node"?
You are
You and I generally agree on style preferences... I think the warning
should be limited to grep " ;$".
I did a grep on the kernel for ' ;' and found 8000 results. 6000 of
them are caught by my semicolon before the newline rule. The remaining
2000 are assembly, macros, and crappy for loops.
reg
Hi,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Wednesday, December 04, 2013 4:11 PM
> To: Chao Yu
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net;
> linux-fsde...@vger.kernel.org; 谭姝
> Subject: RE: [f2fs-dev] [PATCH v2] f2f
On Wed, Dec 4, 2013 at 8:46 AM, Suki Buryani wrote:
> hi,
>
> i have few changes in my mtd partitions, i want to change the erasesize of a
> partition. can any one tell me where i should look to change erasesize of
> mtd3...
The erase size is defined by the MTD device, you cannot change it.
--
I though it would be configurable some where in kernel
On Wednesday, December 4, 2013 1:25 PM, Richard Weinberger
wrote:
On Wed, Dec 4, 2013 at 8:46 AM, Suki Buryani wrote:
> hi,
>
> i have few changes in my mtd partitions, i want to change the erasesize of a
> partition. can any one tell
On Tue, 29 Oct 2013, Geert Uytterhoeven wrote:
> Commit 1e29af62f2b285bd18685da93c3ce8c33ca2d1db ("mfd: Add refcounting
> support to mfd_cells") had to drop the "const" keyword on the "cell"
> parameter of mfd_add_devices(), as it added the refcounting pointers
> to the objects of the passed mfd_c
On Wed, 04 Dec 2013 16:13:31 +0800 Axel Lin wrote:
> I can constantly hit this issue:
>
> I trace it to mm/filemap.c: add_to_page_cache_locked
> I print the in_atomic status at BEGIN and END of add_to_page_cache_locked
> call.
> Then I got in_atomic is true at the end of add_to_page_cache_locke
On Tue, 29 Oct 2013, Geert Uytterhoeven wrote:
> If the first call to mfd_add_device() fails, no child devices have been
> registered to the parent yet, and thus mfd_remove_devices() won't find
> anything to remove nor free.
> Hence the previously allocated array of atomic_t objects will leak.
>
Hello Alan,
On 03/12/2013 16:32, Alan Stern wrote:
On Tue, 3 Dec 2013, Nicolas Ferre wrote:
On 03/12/2013 15:07, Boris BREZILLON :
Replace clk_get calls by devm_clk_get calls.
Signed-off-by: Boris BREZILLON
Tested-by: Robert Nelson
Acked-by: Nicolas Ferre
Thanks Boris for these fixes.
Am 2013-12-04 09:10, schrieb Lee Jones:
>> +int tps6586x_get_version(struct device *dev)
>> +{
>> +struct tps6586x *tps6586x = dev_get_drvdata(dev);
>> +
>> +return tps6586x->version;
>> +}
>> +EXPORT_SYMBOL_GPL(tps6586x_get_version);
>
> I thought Mark suggested that this routine was conv
The EVENT_CONSTRAINT_END macro defines the end marker as
a constraint with a weight of zero. This was all fine
until we blacklisted the corrupting memory events on
Intel IvyBridge. These events are blacklisted by using
a counter bitmask of zero. Thus, they also get a constraint
weight of zero.
Th
Hi Peter,
Thank you for reviewing this patch.
On Wed, 2013-12-04 at 13:40 +0800, Peter Chen wrote:
> On Mon, Nov 11, 2013 at 03:35:34PM +0200, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
>
> Please add something in commit log
>
> > Signed-off-by: Ivan T. Ivanov
> > Cc: devicet...@
On fail path alloc_super() calls destroy_super(), which issues a warning
if list_empty() returns false on the s_mounts field. That said s_mounts
should be initialized in alloc_super() before any possible failure.
Signed-off-by: Vladimir Davydov
Cc: Al Viro
---
fs/super.c |3 ++-
1 file chan
On 12/04/2013 04:04 PM, Johannes Berg wrote:
> On Wed, 2013-12-04 at 10:12 +0800, Chen Gang wrote:
>
>> It is really not urgent, and for keeping quality, it is necessary to
>> spend suitable time resource (e.g 1 hour or more) to make, review and
>> test this kind of patch carefully by oneself.
>>
Hi
On 10/24/2013 03:31 PM, Gao feng wrote:
> Here is the v1 patchset: http://lwn.net/Articles/549546/
>
> The main target of this patchset is allowing user in audit
> namespace to generate the USER_MSG type of audit message,
> some userspace tools need to generate audit message, or
> these tools
* Christoph Lameter wrote:
> The kernel has never been audited to ensure that this_cpu operations
> are consistently used throughout the kernel. The code generated in
> many places can be improved through the use of this_cpu operations
> (which uses a segment register for relocation of per cp
On Wed, 04 Dec 2013 14:00:09 +0530 Raghavendra K T
wrote:
> > I don't recall the rationale for the current code and of course we
> > didn't document it. It might be in the changelogs somewhere - could
> > you please do the git digging and see if you can find out?
>
> Unfaortunately, from my se
On 4 December 2013 13:09, Masami Hiramatsu
wrote:
> (2013/12/04 11:54), Sandeepa Prabhu wrote:
>> On 4 December 2013 06:58, Masami Hiramatsu
>> wrote:
>>> Hi,
>>> Here is the version 4 of NOKPORBE_SYMBOL series.
>>>
>>> In this version, I removed the cleanup patches and
>>> add bugfixes I've foun
* Masami Hiramatsu wrote:
> Hi,
> Here is the version 4 of NOKPORBE_SYMBOL series.
>
> In this version, I removed the cleanup patches and
> add bugfixes I've found, since those bugs will be
> critical.
>
> Rest of the cleanup and visible blacklists will be proposed later in
> another series.
On Wed, 2013-12-04 at 16:41 +0800, Chen Gang wrote:
> According to our original discussion, it seems we agree that I am not
> the suitable member to finish it, so I suggest you or another members to
> try.
There's nothing to finish here. The code is fine. The compiler is wrong,
but we haven't fou
On 2013-12-02 20:25, Nicolas Ferre wrote:
> On 22/10/2013 18:36, Johan Hovold :
>> Add missing module device table which is needed for module autoloading.
>>
>> Signed-off-by: Johan Hovold
>
> Acked-by: Nicolas Ferre
>
> Jean-Christophe, Tomi,
>
> Can you please take this patch?
>
> Best rega
* tip-bot for H. Peter Anvin wrote:
> Commit-ID: 5551a34e5aeab868f8d37f70d8754868921b4ee5
> Gitweb: http://git.kernel.org/tip/5551a34e5aeab868f8d37f70d8754868921b4ee5
> Author: H. Peter Anvin
> AuthorDate: Wed, 20 Nov 2013 13:31:49 -0800
> Committer: H. Peter Anvin
> CommitDate: Tue,
On 12/04/2013 04:49 PM, Johannes Berg wrote:
> On Wed, 2013-12-04 at 16:41 +0800, Chen Gang wrote:
>
>> According to our original discussion, it seems we agree that I am not
>> the suitable member to finish it, so I suggest you or another members to
>> try.
>
> There's nothing to finish here. The
* H. Peter Anvin wrote:
> Hi guys,
>
> 0c44c2d0f459 x86: Use asm goto to implement better modify_and_test()
> functions
>
> causes a regression, because it incorrectly changed the constraints of
> bitops.
>
> Specifically, the GEN_BINARY_RMWcc() hardcodes a constraint as "er", but
> it needs
[repost because typo in Ingo's email address]
The EVENT_CONSTRAINT_END macro defines the end marker as
a constraint with a weight of zero. This was all fine
until we blacklisted the corrupting memory events on
Intel IvyBridge. These events are blacklisted by using
a counter bitmask of zero. Thus,
On 12/04/2013 02:11 PM, Andrew Morton wrote:
On Wed, 04 Dec 2013 14:00:09 +0530 Raghavendra K T
wrote:
Unfaortunately, from my search, I saw that the code belonged to pre git
time, so could not get much information on that.
Here: https://lkml.org/lkml/2004/8/20/242
It seems it was done as
* Stephane Eranian wrote:
> #define EVENT_CONSTRAINT_END \
> - EVENT_CONSTRAINT(0, 0, 0)
> + { .idxmsk64 = 0,\
> + .code = 0,\
> + .cmask = 0, \
> + .weight = -1, \
> + .overlap = 0,
On Tue, Dec 03, 2013 at 05:05:56PM +0800, Alex Shi wrote:
> Task migration happens when target just a bit less then source cpu load.
> To reduce such situation happens, aggravate the target cpu load with
> sd->imbalance_pct/100.
>
> This patch removes the hackbench thread regression on Daniel's
>
(2013/12/04 0:12), Vivek Goyal wrote:
On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote:
[..]
Even if copying partial pages into the 2nd kernel, we need to use ioremap()
once on them, and I think the ioremap() is exactly similar to
remap_pfn_range() for a single page. There seems
* ville.syrj...@linux.intel.com wrote:
> v2: Rewrite to use the TOM-TSEG_SIZE-stolen_size and TOUD methods
I guess v2 is a reaction to my review feedback? I got no reply to my
mail from you so I'm not sure and I'd like to know whether all
feedback was addressed.
Thanks,
Ingo
--
To u
On Wed, 2013-12-04 at 13:43 +0800, Peter Chen wrote:
> On Mon, Nov 11, 2013 at 03:35:36PM +0200, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
>
> The commit log is needed.
Will fix it.
Regards,
Ivan
>
> > Signed-off-by: Ivan T. Ivanov
> > ---
> > drivers/usb/chipidea/ci_hdrc_msm.
On 12/03/2013 10:33 PM, Rafael J. Wysocki wrote:
On Tuesday, December 03, 2013 10:59:58 AM Konrad Rzeszutek Wilk wrote:
If not, we could end up in the unfortunate situation where
we dereference a NULL pointer b/c we have cpuidle disabled.
This is the case when booting under Xen (which uses the
* Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the timers/core-v2 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/core-v2
>
> It's a rebase of the previous pull request against 3.13-rc2 which addresses
> your revi
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 0ed1e0bee0b2c6b4cc6d7a63787739a9d3ac8aa8:
>
> Merge tag 'perf-core-for-mingo' of
> git://git.kernel.org/pub/scm/linux/k
On Tue, Dec 03, 2013 at 10:10:29AM -0800, Linus Torvalds wrote:
> On Tue, Dec 3, 2013 at 12:52 AM, Ingo Molnar wrote:
> >
> > I'd expect such bugs to be more prominent with unlucky object
> > size/alignment: if mutex->count lies on a separate cache line from
> > mutex->wait_lock.
>
> I doubt tha
From: Daniel Tang
The SoC name was mistakenly used instead of the vendor name in the
device tree binding for nspire-usb.
This patch fixes this before the driver becomes widely adopted.
Signed-off-by: Daniel Tang
---
Documentation/devicetree/bindings/usb/ci-hdrc-nspire.txt |4 ++--
drivers
From: Daniel Tang
This patch adds the needed compatible key to the device tree for TI-Nspires.
Signed-off-by: Daniel Tang
---
arch/arm/boot/dts/nspire.dtsi |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/nspire.dtsi b/arch/arm/boot/dts/nspire.dtsi
index a22ffe6..baf715
On Tue, Dec 03, 2013 at 08:57:27PM +0100, Stefan Agner wrote:
> 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.
>
>
* Alexei Starovoitov wrote:
> It's possible to teach it for multi-level, but then analyzer will
> become too large and won't be suitable for kernel.
Btw., even if we want to start simple with most things, the above
statement is not actually true in the broad sense: the constraint for
the ker
From: Zhi Yong Wu
Signed-off-by: Zhi Yong Wu
---
drivers/net/macvtap.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
index 9093004..957cc5c 100644
--- a/drivers/net/macvtap.c
+++ b/drivers/net/macvtap.c
@@ -876,6 +876,8 @
From: Daniel Tang
Fix incorrect function definition of zevio_timer_add so the correct function
pointer is passed to CLOCKSOURCE_OF_DECLARE.
Signed-off-by: Daniel Tang
---
drivers/clocksource/zevio-timer.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a
On Tue, 2013-12-03 at 15:11 -0500, Konrad Rzeszutek Wilk wrote:
> > > If Konrad and Boris agree that breaking the kernel's ABI in this way is
> > > acceptable in this specific case, I'll defer to them.
> >
> > My opinion as Xen on ARM hypervisor maintainer is that this is the right
> > thing to do
From: Zhi Yong Wu
Signed-off-by: Zhi Yong Wu
---
drivers/net/macvtap.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
index 957cc5c..c0d412e 100644
--- a/drivers/net/macvtap.c
+++ b/drivers/net/macvtap.c
@@ -823,7 +823
From: Daniel Tang
Fix nspire_restart to take enum reboot_mode instead of a char so the
correct function pointer is passed to DT_MACHINE_START.
Signed-off-by: Daniel Tang
---
arch/arm/mach-nspire/nspire.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-nspire
On Tue, Dec 03, 2013 at 08:57:28PM +0100, Stefan Agner wrote:
[...]
> Changes since v2:
> - Removed reg_ from reg_version
> - Moved walk through version dependent tables to find_regulator_info,
> removed the inline definition. This reduces .o size and encapsulates
> the logic of finding
* Alexei Starovoitov wrote:
> On Tue, Dec 3, 2013 at 1:16 AM, Ingo Molnar wrote:
> >
> > Very cool! (Added various other folks who might be interested in
> > this to the Cc: list.)
> >
> > I have one generic concern:
> >
> > It would be important to make it easy to extract loaded BPF code
> >
Hi,
I've noticed this patch hasn't gotten a reply for a while now. Just wondering
what's the status of this patch and whether there is anything else I should fix
before this can get accepted.
Cheers,
Daniel Tang
On 25/11/2013, at 3:02 PM, dt.ta...@gmail.com wrote:
> From: Daniel Tang
>
> Th
Hi Peter,
On Wed, 2013-12-04 at 13:37 +0800, Peter Chen wrote:
> On Mon, Nov 11, 2013 at 04:36:09PM +0200, Ivan T. Ivanov wrote:
> >
> > Hi Peter,
> >
> > On Mon, 2013-11-11 at 21:59 +0800, Peter Chen wrote:
> > > On Mon, Nov 11, 2013 at 03:35:37PM +0200, Ivan T. Ivanov wrote:
> > > > From:
On Tue, 2013-12-03 at 16:14 -0500, Konrad Rzeszutek Wilk wrote:
> The user has the option of disabling the platform driver:
> 00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01)
>
> which is used to unplug the emulated drivers (IDE, Realtek 8169, etc)
> and allow the PV d
On Wed, Dec 04, 2013 at 03:56:58AM +, Alex Elder wrote:
> Document the device tree binding for Broadcom Kona architecture
> clock control units and clocks. Kona device nodes are represented
> with compatible strings having "bcm11351" in their name.
>
> Kona clocks are managed by "clock contro
On Tue, Dec 03, 2013 at 11:55:07PM +0100, Sebastian Hesselbarth wrote:
> On 12/03/2013 09:14 PM, Meelis Roos wrote:
> >>Currently, of_match_node compares each given match against all node's
> >>compatible strings with of_device_is_compatible.
> >>
> >>To achieve multiple compatible strings per node
On 04/12/13 10:28, Ian Campbell wrote:
> On Tue, 2013-12-03 at 15:11 -0500, Konrad Rzeszutek Wilk wrote:
If Konrad and Boris agree that breaking the kernel's ABI in this way is
acceptable in this specific case, I'll defer to them.
>>>
>>> My opinion as Xen on ARM hypervisor maintainer is
I Have a donation for you...Kindly contact me for more details
DAVE ANGELA
ang_dav...@3mail.ie
--
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
On Tue, Dec 03, 2013 at 11:18:47PM +0100, Stefan Agner wrote:
[...]
> diff --git a/drivers/regulator/tps6586x-regulator.c
> b/drivers/regulator/tps6586x-regulator.c
[...]
> + /* Search version specific table first */
> + if (table) {
> + for (i = 0; i < num; i++) {
> +
Hi Chris,
On Wed, Dec 04, 2013 at 03:16:21PM +0800, Chris Ruehl wrote:
> On Tuesday, December 03, 2013 04:15 PM, Heikki Krogerus wrote:
> >On Mon, Dec 02, 2013 at 03:05:19PM +0800, Chris Ruehl wrote:
> >>@@ -154,6 +164,27 @@ int usb_phy_gen_create_phy(struct device *dev, struct
> >>usb_phy_gen_xc
Hi all,
When I read the code and document of perf tool as a newbie,
I feel confused in some places. Then I made some patches here to make
them more clear.
Please help to review them.
Note: The last 3 commits are all about perf-kvm.txt. I splite them
to make the logic more clear. I
As option --host and --guest request no input for it, there should
not be a '=' after them in Document. And --output request a filename
as the input, so there should be a '=' after it. This patch remove
the wrong '=' after --guest and --host, and add a '=' after --output
in perf-kvm.txt.
Signed-of
As the buildid is read from /sys/kernel/notes, then if we use perf kvm
buildid-list
with a perf data file captured by perf kvm record with --guestkallsyms and
--guestmodules,
there is no result in output. This patch add a explanation about it and add a
limit
of using perf kvm buildid-list.
Sign
In machine__get_kernel_start_addr, the code, which is
using machine->root_dir to build filename, works for both
host and guests initialized from guestmount. So this patch
remove the branch for machine__is_host.
Signed-off-by: Dongsheng Yang
---
tools/perf/util/machine.c | 14 +-
1 fi
As we have changed the default behavior of perf kvm to --guest enabled,
the document about perf kvm record is outdated. This patch update it to
show the correct output with --host/--guest/neither/both of them.
Signed-off-by: Dongsheng Yang
---
tools/perf/Documentation/perf-kvm.txt | 15 +
* David Ahern wrote:
> On 12/2/13, 10:44 PM, Namhyung Kim wrote:
> >>Right now 'perf stat -i' i used for '--no-inherit', perhaps we can just
> >>have --no-inherit have no short option and grab -i to have the same
> >>meaning as in 'report', 'script', etc.
> >
> >Agreed. Maybe we could change it
Hi Arnd,
thanks for helping to review the code.
Am Dienstag, den 03.12.2013, 16:05 +0100 schrieb Arnd Bergmann:
> On Tuesday 03 December 2013, Frank Haverkamp wrote:
> > Ohh, sorry __u64 of course:
> >
> > /* common struct for chip image exchange */
> > struct genwqe_bitstream {
> > __u6
Check for cpu_map__dummy_new() or cpu_map__new() to be called in
perf_evlist__create_maps() is more complicated. This patch moves
the checking work into target.h, combining two conditions and making
perf_evlist__create_maps() more readable.
Signed-off-by: Dongsheng Yang
---
tools/perf/util/evlis
On 2013-12-03 16:25, Roger Quadros wrote:
> Hi,
>
> This is a follow up solution to the original series in [1]
>
> The first patch fixes the OMAP4 Panda USB detection problems on 3.13-rc1
> with u-boot v2013.10.
>
> The remaining 2 patches are required if SOFTRESET needs to be done for the
> USB
Hi Hiroshi,
On Wed, Dec 04, 2013 at 07:40:27AM +, Hiroshi Doyu wrote:
> On Mon, 25 Nov 2013 14:49:37 +0100
> Hiroshi Doyu wrote:
>
> > Hi Joerg,
> >
> > Do you have some time to review this patch along with the following ones?
> >
> > [PATCHv6 02/13] iommu/of: introduce a global iommu de
* Arnaldo Carvalho de Melo wrote:
> Em Mon, Dec 02, 2013 at 05:36:20PM +0100, Ingo Molnar escreveu:
> > * Namhyung Kim wrote:
> > > 2013-12-02 (월), 13:57 +0100, Ingo Molnar:
> > > > So basically, in the end I think it should be possible to have the
> > > > following behavior:
>
> > > >per
On Wed, Dec 04, 2013 at 10:02:44AM +0800, Chris Ruehl wrote:
> usb: phy-tegra-usb.c: wrong pointer check for remap UTMI
>
> A wrong pointer was used to test the result of devm_ioremap()
>
> Signed-off-by: Chris Ruehl
> Acked-by: Venu Byravarasu
> ---
> drivers/usb/phy/phy-tegra-usb.c |2 +-
Hi,
Am Dienstag, den 03.12.2013, 15:28 +0100 schrieb Frank Haverkamp:
> + */
> +struct genwqe_mem {
> + unsigned long addr;
> + unsigned long size;
> + int direction;
> +};
> +
> +#define GENWQE_PIN_MEM _IOWR(GENWQE_IOC_CODE, 40, struct
> genwqe_mem *)
> +#define GENWQE_UNP
On Wed, Dec 04, 2013 at 10:59:46AM +0800, Bo Shen wrote:
> Hi Thierry,
>
> On 12/03/2013 05:43 PM, Thierry Reding wrote:
> >On Tue, Dec 03, 2013 at 11:09:12AM +0800, Bo Shen wrote:
> >>On 12/02/2013 06:59 PM, Thierry Reding wrote:
> >>>On Mon, Nov 18, 2013 at 05:13:21PM +0800, Bo Shen wrote:
> >[.
On Wed, 04 Dec 2013, Stefan Agner wrote:
> Am 2013-12-04 09:10, schrieb Lee Jones:
> >> +int tps6586x_get_version(struct device *dev)
> >> +{
> >> + struct tps6586x *tps6586x = dev_get_drvdata(dev);
> >> +
> >> + return tps6586x->version;
> >> +}
> >> +EXPORT_SYMBOL_GPL(tps6586x_get_version);
>
>>
>> Could you do something clever with just one flag? Probably yes. But I
>> doubt it would
>> be that much cleaner, this is just the way that patching sites work.
>
> Thank you for spending your time to listen to me.
>
Don't worry! I thank you for carrying this forward.
> Let me try to explain
Add support for irq registration when pmu interrupt is percpu.
Signed-off-by: Vinayak Kale
Signed-off-by: Tuan Phan
---
arch/arm64/kernel/perf_event.c | 108 +---
1 file changed, 78 insertions(+), 30 deletions(-)
diff --git a/arch/arm64/kernel/perf_event.c
This patch series adds support to handle interrupt registration/deregistration
in arm64 pmu driver when pmu interrupt type is percpu.
Changelog:
V7:
* In arm64 pmu driver: Instead of passing 'struct arm_pmu' pointer, pass the
irq number directly to armpmu_[enable/disable]_percpu_irq().
Clean-u
Adding a phy driver for USB 3.0 PHY controller present on Exynos5
series of SoCs alongwith DWC3 controller for USB 3.0 operations.
Few functions used in this driver to translate ref clock rate are
common to Kamil's usb2.0 phy driver [1]. So we can figure out how
to re-use them across these drivers
Add device tree nodes for USB 3.0 PHY present alongwith
USB 3.0 controller Exynos 5420 SoC. This phy driver is
based on generic phy framework.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5420.dtsi | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --
This patch adds an accessor function for IRQ_PER_CPU flag.
The accessor function is useful to determine whether an IRQ is percpu or not.
This patch is based on an older patch posted by Chris Smith here [1].
There is a minor change w.r.t. Chris's original patch: The accessor function
is renamed as
* Arnaldo Carvalho de Melo wrote:
> Em Mon, Dec 02, 2013 at 12:58:35PM -0700, David Ahern escreveu:
> > On 12/2/13, 12:38 PM, Arnaldo Carvalho de Melo wrote:
> > >Can you suggest a better name for the option being discussed?
>
> > >Perhaps one of:
>
> > >--show-event-time
> > >--event-time
>
Arnaldo Carvalho de Melo wrote:
> static inline percent_color_snprintf(...)
> {
> return value_color_snprintf(...);
> }
The issue with this suggestion is that the prototype of
percent_color_snprintf() is:
int percent_color_snprintf(char *bf, size_t size, const char *fmt, ...)
So, I can
Update device tree bindings for DWC3 controller and
USB 3.0 phy present on Exynos 5250 SoC, to start using
the phy driver based on generic phy framework.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 16 ++--
1 files changed, 6 insertions(+), 10 deletions(-)
Add device tree nodes for DWC3 controller present on
Exynos 5420 SoC, to enable support for USB 3.0.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5420.dtsi | 38 +++-
1 files changed, 36 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/ex
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Thereby, removing old phy-samsung-usb3 driver and related code
used untill now which was based on usb/phy framework
On Wed, Dec 04, 2013 at 12:36:51AM +0800, Hanjun Guo wrote:
> Add Kconfigs to build ACPI on ARM64, and make ACPI runable on ARM64.
>
> acpi_idle driver is x86/IA64 dependent now, so make CONFIG_ACPI_PROCESSOR
> depends on X86 || IA64, and implement it on ARM in the furture.
>
> In order to make a
The conf and of_id variables are assigned but never used, so they may as
well just be removed.
Signed-off-by: Thierry Reding
---
arch/arm/mach-pxa/irq.c | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/mach-pxa/irq.c b/arch/arm/mach-pxa/irq.c
index b6cc1816463e..0eecd83c624e 10064
At Mon, 2 Dec 2013 11:05:41 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.72 release.
> There are 60 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
1 - 100 of 770 matches
Mail list logo
