On Wed, Apr 01, 2015 at 09:32:08AM -0500, Aravind Gopalakrishnan wrote:
> GART registers are not present in newer processors (Fam15h, Model 10h
> and later). So, avoid accesses to GART registers in PCI config
> space by returning early in early_gart_iommu_check() and
> gart_iommu_hole_init() if GAR
On Wed, 1 Apr 2015 20:05:24 -0300
Eduardo Habkost wrote:
> > >
> > > If you don't want to encode that knowledge in libvirt or other
> > > management software for s390, it looks like you need something like a
> > > "stable-abi-safe" field on CpuDefinitionInfo?
> >
> > Exactly that fulfills the
On Thu, 02 Apr 2015, Jassi Brar wrote:
> On Wed, Apr 1, 2015 at 7:12 AM, Michael Turquette
> wrote:
> > Quoting Jassi Brar (2015-03-02 02:28:44)
> >> On 2 March 2015 at 15:48, Lee Jones wrote:
> >> > On Mon, 02 Mar 2015, Jassi Brar wrote:
> >> >
> >> >> On Mon, Mar 2, 2015 at 2:06 PM, Lee Jones
On Thu, 02 Apr 2015, Ramakrishna Pallala wrote:
> This patch adds the mfd cell info for axp288 extcon device.
>
> Signed-off-by: Ramakrishna Pallala
> ---
> drivers/mfd/axp20x.c | 28
> include/linux/mfd/axp20x.h |5 +
> 2 files changed, 33 insertion
DT Ack please.
On Wed, 01 Apr 2015, Bjorn Andersson wrote:
> Add the regulator subnodes to the Qualcomm RPM MFD device tree bindings.
>
> Signed-off-by: Bjorn Andersson
> ---
> Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 217
> +++--
> 1 file changed, 205 insertions(+
Hi Russell,
On Wed, Apr 1, 2015 at 11:59 PM, Russell King - ARM Linux
wrote:
> On Wed, Apr 01, 2015 at 02:54:59PM -0700, Kevin Hilman wrote:
>> Your patch on top of Geert's still compiles fine for me with gcc-4.7.3.
>> However, I'm not sure how specific we can be on the versions.
>>
>> /me goes t
On Thu 02-04-15 08:39:02, Dave Chinner wrote:
> On Wed, Apr 01, 2015 at 05:19:20PM +0200, Michal Hocko wrote:
> > On Mon 30-03-15 11:32:40, Dave Chinner wrote:
> > > On Fri, Mar 27, 2015 at 11:05:09AM -0400, Johannes Weiner wrote:
> > [...]
> > > > GFP_NOFS sites are currently one of the sites that
On 2 April 2015 at 03:47, Wanpeng Li wrote:
> Hi Vincent,
> On Fri, Feb 27, 2015 at 04:54:03PM +0100, Vincent Guittot wrote:
>>This patchset consolidates several changes in the capacity and the usage
>>tracking of the CPU. It provides a frequency invariant metric of the usage of
>>CPUs and general
(2015/03/09 11:15), Masami Hiramatsu wrote:
> Fix perf probe to track down unnamed union/structure members.
> perf probe did not track down the tree of unnamed union/structure
> members, since it just failed to find given "name" in a parent
> structure/union. To solve this issue, I've introduced 2
Hello,
On Wed, Apr 01, 2015 at 04:31:43PM +0300, Stefan Strogin wrote:
> Add trace events for cma_alloc() and cma_release().
>
> The cma_alloc tracepoint is used both for successful and failed allocations,
> in case of allocation failure pfn=-1UL is stored and printed.
>
> Signed-off-by: Stefan
On 04/02/15 at 12:29pm, Herbert Xu wrote:
> On Thu, Apr 02, 2015 at 12:11:35PM +0800, Fengguang Wu wrote:
> >
> > Yes it is contained in next-20150401 which is bad:
> >
> > # extra tests on tree/branch next/master
> > git bisect bad e954104e2b634b42811dad8d502cbf240f206df2 # 21:22 0-
>
On Wed, Mar 18, 2015 at 9:56 PM, Daniel Baluta wrote:
> We need this earlier in the boot process to allow various subsystems
> to use configfs (e.g Industrial IIO).
>
> Also, debugfs is at core_initcall level and configfs should be on
> the same level from infrastructure point of view.
>
> Suggest
Fix perf probe to track down unnamed union/structure members.
perf probe did not track down the tree of unnamed union/structure
members, since it just failed to find given "name" in a parent
structure/union. To solve this issue, I've introduced 2 changes.
- Fix die_find_member() to track down the
Some buggy firmware implementations update VariableNameSize on success
such that it does not include the final NUL character which results in
garbage in the efivarfs name entries. Use kzalloc on the efivar_entry
(as is done in efivars.c) to ensure that the name is always
NUL-terminated.
The buggy
Hi Michael, Bjorn and all,
On Sun, 29 Mar 2015 15:36:55 +0200, Michael S. Tsirkin wrote:
> The macros in pci_ids.h are pretty useful for userspace
> using the pci sysfs interface, e.g. to decode class
> device and vendor sysfs files.
>
> At the moment userspace is forced to duplicate these macros
2015-04-01 18:12 GMT+02:00 Joe Perches :
> Neaten the logging a bit by adding #define pr_fmt
>
> Miscellanea:
>
> o Remove __FILE__/__func__ uses
> o Coalesce formats adding missing spaces
> o Align arguments
> o (rtc-cmos) Integrated 2 consecutive messages
>
> Signed-off-by: Joe Perches
Reviewed
On 04/02/2015 03:01 PM, Pratyush Anand wrote:
On Thursday 02 April 2015 11:07 AM, AKASHI Takahiro wrote:
Pratyush,
On 04/02/2015 01:58 PM, Pratyush Anand wrote:
On Thursday 02 April 2015 04:57 AM, AKASHI Takahiro wrote:
Please try my latest kexec-tools in my linaro repo (branch name is
kd
Hi all,
There will be no linux-next releases on Friday or Monday (mainly due to
hot cross buns and chocolate eggs :-)).
Changes since 20150401:
*crickets*
Non-merge commits (relative to Linus' tree): 7955
7152 files changed, 327404 insertions(+), 153265 deletions(-)
--
On Wed, Apr 01, 2015 at 08:34:41PM -0700, John Stultz wrote:
> Ingo suggested that the timekeeping debugging variables
> recently added should not be global, and should be tied
> to the timekeeper's read_base.
But why? its the same hardware clock for both tkr's. Surely if one goes
funny the other
On Thu, Apr 02, 2015 at 09:44:24AM +0200, Jean Delvare wrote:
> It could be that a small subset of pci_ids.h could be shared with
> user-space. I'm thinking of classes, because that list is short and
> stable, so we can give some stability guarantees. But I don't know if
> the user-space projects y
* Peter Zijlstra wrote:
> On Wed, Apr 01, 2015 at 08:34:41PM -0700, John Stultz wrote:
> > Ingo suggested that the timekeeping debugging variables
> > recently added should not be global, and should be tied
> > to the timekeeper's read_base.
>
> But why? its the same hardware clock for both tkr
Hi Steve,
On Wed, Apr 01, 2015 at 09:56:54PM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Several tracepoints use the helper functions __print_symbolic() or
> __print_flags() and pass in enums that do the mapping between the
> binary data stored and the value to print. Thi
On Thu, Apr 02, 2015 at 09:06:09AM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git
> timer/alloc_tvec_statically
> commit 17cdf560f2727f687ab159707d0aa591f8a2f82d ("timer: Allocate per-cpu
> tvec_base's staticall
Hi Lee,
On Fri, 27 Feb 2015, Lee Jones wrote:
> Lots of platforms contain clocks which if turned off would prove fatal.
> The only way to recover is to restart the board(s). This driver takes
> references to clocks which are required to be always-on in order to
> prevent the common clk framework
According to the technical update (No. TN-RCS-B011A/E), the UGSTS LOCK
bit location is bit 8, not bits 1 and 0. It also says that the register
address offset of UGSTS is 0x88, not 0x90.
So, this patch fixes the USBHS_UGSTS_LOCK value and some comments.
Signed-off-by: Yoshihiro Shimoda
---
driver
Hi,
> > diff --git a/include/linux/mfd/axp20x.h b/include/linux/mfd/axp20x.h
> > index dfabd6d..4ed8071 100644
> > --- a/include/linux/mfd/axp20x.h
> > +++ b/include/linux/mfd/axp20x.h
> > @@ -275,4 +275,9 @@ struct axp20x_fg_pdata {
> > int thermistor_curve[MAX_THERM_CURVE_SIZE][2];
> > };
>
Using a fixed (by DTS) parent for clocks when turning on the power domain
may introduce issues in other drivers. For example when such driver
changes the parent during runtime and expects that he is the only place
of such change.
Do not rely entirely on DTS providing the fixed parent for such cloc
Replace fixed parent with last parent (obtained with clk_get_parent())
of clocks for devices in mfc and disp power domains. This should improve
behavior if such clocks were reparented by the drivers and new parents
are different than those specified in DTS.
Signed-off-by: Krzysztof Kozlowski
---
dprintk has some name collisions with other frameworks and drivers. It
is also not necessary to have these custom debug print filters. Dynamic
debug offers the same amount of filtered debugging.
This patch replaces all dprintks with dev_dbg(). It also removes the
ioctl dprintk which prints the ing
Hi Lee,
On Fri, 27 Feb 2015, Lee Jones wrote:
> Some hardware contains bunches of clocks which must never be
> turned off. If drivers a) fail to obtain a reference to any
> of these or b) give up a previously obtained reference
> during suspend, the common clk framework will attempt to
> disable
Reformat the existing documentation to have more structure. This allows
for more documentation seperated from the existing paragraphs.
Signed-off-by: Markus Pargmann
---
Documentation/blockdev/nbd.txt | 34 +++---
1 file changed, 19 insertions(+), 15 deletions(-)
dif
The mentioned problem is not present anymore.
Signed-off-by: Markus Pargmann
---
drivers/block/nbd.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index 217b570dd7a5..6e7a7b06efcb 100644
--- a/drivers/block/nbd.c
+++ b/driv
Signed-off-by: Markus Pargmann
Acked-by: Pavel Machek
---
Notes:
Changes in v2:
- Remove unnecessary brackets
drivers/block/nbd.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index e41fb4ccf39a..bd8f4caf53bd 10064
By returning the error code directly, we can avoid the jump label
error_out.
Signed-off-by: Markus Pargmann
Acked-by: Pavel Machek
---
drivers/block/nbd.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index 6e7a7b06efcb..e41
Add a list of available module parameters as attachment to the
documentation.
Signed-off-by: Markus Pargmann
---
Documentation/blockdev/nbd.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/blockdev/nbd.txt b/Documentation/blockdev/nbd.txt
index 337946bd460e..db24
* Peter Zijlstra wrote:
> With some feedback from Jolsa, who showed me how to trigger the actual
> outputs.
>
> ---
>
> Subject: perf, tools: Merge all perf_event_attr print functions
> From: Peter Zijlstra
> Date: Tue Mar 31 13:01:54 CEST 2015
>
> Currently there's 3 (that I found) differen
The header is not included anywhere. Remove it and include the private
nbd_device struct in nbd.c.
Signed-off-by: Markus Pargmann
---
drivers/block/nbd.c | 22 ++
include/linux/nbd.h | 46 --
2 files changed, 22 insertions(+), 46 de
On 01/04/2015 at 21:33:42 +0100, Mark Brown wrote :
> On Mon, Mar 30, 2015 at 09:40:37PM +0200, Alexandre Belloni wrote:
> > atmel-pcm-dma is not limited to a buffer size of 64kB like atmel-pcm-pdc.
> > Increase buffer_bytes_max to 512kB to allow for higher bit rates (i.e.
> > 32bps at
> > 192kHz)
kthread_run includes the wake_up_process() call, so instead of
kthread_create() followed by wake_up_process() we can use this macro.
Signed-off-by: Markus Pargmann
Acked-by: Pavel Machek
---
drivers/block/nbd.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/bl
The block subsystem uses loff_t to store the device size. Change the
type for nbd_device bytesize to loff_t.
Signed-off-by: Markus Pargmann
Acked-by: Pavel Machek
---
drivers/block/nbd.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/block/nbd.c b/drivers/block/nb
Hi Jens,
This pull request contains some NBD cleanups.
The documentation was updated to be extensible for future features and the
module parameters were added.
NBD had an internal header located at include/linux/nbd.h which was only used
by nbd.c. So I moved the header content from include/ to t
On Thu, Apr 02, 2015 at 01:19:24PM +0800, Wang Nan wrote:
> Additional information:
>
> With following patch it seems to work:
>
> diff --git a/tools/perf/util/symbol-elf.c b/tools/perf/util/symbol-elf.c
> index 476268c..1177f02 100644
> --- a/tools/perf/util/symbol-elf.c
> +++ b/tools/perf/util/
On Thu, Apr 02, 2015 at 06:04:52AM +, Wang Nan wrote:
> There is a bug in perf annotate that it doesn't respect user provided
> '-i'/'--input' option:
>
> # perf record ls
>[ perf record: Woken up 1 times to write data ]
>[ perf record: Captured and wrote 0.001 MB perf.data (8 samples
On Wed, Apr 01, 2015 at 01:36:48PM -0300, Arnaldo Carvalho de Melo wrote:
> Hi David, Jiri,
>
> Please take a look if it is ok for you guys
>
> Adrian, there is another thing:
>
> db_export__sample(&tables->dbe, event, sample, evsel, al->thread, al);
>
> In tools/perf/util/scripting-eng
The class ids are a hardware defintion, not a kernel API. Just use the
definitions from libpci, or copy over the kernel header if you prefer
it over the libpci definutions.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.
On Thu, Apr 02, 2015 at 06:04:52AM +, Wang Nan wrote:
> There is a bug in perf annotate that it doesn't respect user provided
> '-i'/'--input' option:
>
> # perf record ls
>[ perf record: Woken up 1 times to write data ]
>[ perf record: Captured and wrote 0.001 MB perf.data (8 samples
On Wed, Apr 01, 2015 at 11:46:10PM +0200, Rafael J. Wysocki wrote:
> > > ---
> > > kernel/time/tick-internal.h |2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > Index: linux-pm/kernel/time/tick-internal.h
> > > ===
> > > -
Hi Lee,
On Thu, Mar 26, 2015 at 8:38 PM, Lee Jones wrote:
> On Thu, 26 Mar 2015, Geert Uytterhoeven wrote:
>> On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote:
>> > On Wed, 25 Mar 2015, Geert Uytterhoeven wrote:
>> >> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote:
>> >> > On Fri, 06 Mar 2015
From: Beomho Seo
This patch adds the UART3 devicetree node for Exynos5433 SoC. The UART3 device
is included in AUD_DOMAIN.
Cc: Kukjin Kim
Signed-off-by: Beomho Seo
Signed-off-by: Chanwoo Choi
Acked-by: Inki Dae
---
arch/arm64/boot/dts/exynos/exynos5433-pinctrl.dtsi | 7 +++
arch/arm64/
From: Jaewon Kim
This patch adds EHCI and OHCI device tree node
to usb USB2.0 Host and HSCI(High Speed Inter-Chip) function.
Cc: Kukjin Kim
Signed-off-by: Jaewon Kim
Signed-off-by: Chanwoo Choi
Acked-by: Inki Dae
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 43 ++
From: Jaewon Kim
This patch adds USB DRD(Dual Role Device) and PHY
device tree node to use USB Device.
Cc: Kukjin Kim
Signed-off-by: Jaewon Kim
Signed-off-by: Chanwoo Choi
Acked-by: Inki Dae
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 47 ++
1 file changed,
On Thu, Apr 02, 2015 at 05:16:09PM +0900, Namhyung Kim wrote:
> On Wed, Apr 01, 2015 at 01:36:48PM -0300, Arnaldo Carvalho de Melo wrote:
> > Hi David, Jiri,
> >
> > Please take a look if it is ok for you guys
> >
> > Adrian, there is another thing:
> >
> > db_export__sample(&tables->dbe,
This patch-set add the following devicetree to support USB/PWM/UART3/reboot.
- USB 3.0 DRD (Dual Role Device) and host
- PWM (Pulse Width Modulation)
- UART3
- System reboot
Depend on:
This patch-set have the dependnecy on following patch[1] to support USB 3.0
Host and DRD (Dual Role Device) for
On Thu, Apr 02, 2015 at 09:51:51AM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > On Wed, Apr 01, 2015 at 08:34:41PM -0700, John Stultz wrote:
> > > Ingo suggested that the timekeeping debugging variables
> > > recently added should not be global, and should be tied
> > > to the tim
From: Joonyoung Shim
This patch adds the reboot node which uses the syscon-reboot driver.
Cc: Kukjin Kim
Signed-off-by: Joonyoung Shim
Signed-off-by: Chanwoo Choi
Acked-by: Inki Dae
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arc
From: Jaewon Kim
This patch adds PWM(Pulsle Width Modulation) device tree node
to support for PWM Timer on Exynos5433 SoC.
Cc: Kukjin Kim
Signed-off-by: Jaewon Kim
Signed-off-by: Chanwoo Choi
Acked-by: Inki Dae
---
arch/arm64/boot/dts/exynos/exynos5433-pinctrl.dtsi | 28
From: Jaewon Kim
This patch adds PHY and USB3.0 Host device tree node
using DWC3 chip and set USB3.0 Host related clock parent
for Exynos5433.
Cc: Kukjin Kim
Signed-off-by: Jaewon Kim
Signed-off-by: Chanwoo Choi
Acked-by: Inki Dae
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 46
Andy, Kumar,
On Mon, Mar 16, 2015 at 10:03 PM, Kumar Gala wrote:
> Andy Gross (1):
> soc: qcom: gsbi: Add support for ADM CRCI muxing
this commit seems to break the boot on IFC6410, it was initially
reported on kernelci.org, see report and bootlog [1].
running git bisect led me to:
e5fda
On Wed, Mar 18, 2015 at 07:17:33PM +0530, Rameshwar Prasad Sahu wrote:
> This patch set implements the APM X-Gene SoC DMA driver support to offload
> the DMA operations such as memory copy(memcpy), scatter gather memory copy,
> raid5 xor and raid6 p+q.
Applied, now
Thanks
--
~Vinod
--
To unsubscr
On Thu, Apr 02, 2015 at 10:36:47AM +0200, Peter Zijlstra wrote:
> Sure, struct timekeeper would work, the debug code already references
> the global tk_core to access that.
While looking at that, the comment near tk_core says:
/*
* The most important data for readout fits into a single 64 byte
This patch adds check that prevents futile attempts to move dl tasks to
a CPU with active tasks of equal or earlier deadline. The same behavior as
commit 80e3d87b2c55 ("sched/rt: Reduce rq lock contention by eliminating
locking of non-feasible target") for rt class.
Signed-off-by: Wanpeng Li
---
On 01/04/15 22:55, a...@linux-foundation.org wrote:
> * mm-move-memtest-under-mm.patch
> * mm-move-memtest-under-mm-fix.patch
It was noticed by Paul Bolle (and his clever bot) that patch above
simply disables MEMTEST altogether [1]. Could you fold fix for that, please?
diff --git a/lib/Kconfig.de
Function pick_next_earliest_dl_task is used to pick earliest and pushable
dl task from overloaded cpus in pull algorithm, however, it traverses
runqueue rbtree instead of pushable task rbtree which is also ordered by
tasks' deadlines. This will result in getting no candidates from overloaded
cp
It's a bootstrap function, make init_sched_dl_class() __init.
Signed-off-by: Wanpeng Li
---
kernel/sched/deadline.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index 2313a4f..37425fd 100644
--- a/kernel/sched/deadline.c
++
On 04/02/2015 11:29 AM, Jason Low wrote:
> On Wed, 2015-04-01 at 18:04 +0100, Morten Rasmussen wrote:
>> On Wed, Apr 01, 2015 at 07:49:56AM +0100, Preeti U Murthy wrote:
>
>>> I am sorry I don't quite get this. Can you please elaborate?
>>
>> I think the scenario is that we are in nohz_idle_balanc
On Thu, Apr 02, 2015 at 04:30:34AM +0100, Jason Low wrote:
> On Wed, 2015-04-01 at 18:04 +0100, Morten Rasmussen wrote:
> > On Wed, Apr 01, 2015 at 07:49:56AM +0100, Preeti U Murthy wrote:
> > >
> > > On 04/01/2015 12:24 AM, Jason Low wrote:
> > > > On Tue, 2015-03-31 at 14:07 +0530, Preeti U Murt
On Wed, Apr 01, 2015 at 08:34:39PM -0700, John Stultz wrote:
> Ingo noted that the description of clocks_calc_max_nsecs()'s
> 50% safety margin was somewhat circular. So this patch tries
> to improve the comment to better explain what we mean by the
> 50% safety margin and why we need it.
>
> Cc:
On Wed, Apr 01, 2015 at 03:55:43PM -0700, Bjorn Andersson wrote:
> Introduce "regulator-allow-drms" to make it possible for board
> configuration to enable drms for regulators.
I don't think this is a good name, nobody unfamiliar with a fairly
obscure feature in the Linux regulator API is going to
Hi folks,
I hit a segfault when try to analysis a perf.data generated in an aarch 64
board.
I tried execute perf report on x86 and arm64, both of them hit similar segfault:
$ perf report -i ./buggy/perf.data --objdump=/path/to/aarch64-oe-linux-objdump
--kallsyms /path/to/kallsyms
perf: Segmen
On 01/04/15 19:52, Jiri Olsa wrote:
> On Wed, Apr 01, 2015 at 06:26:38PM +0200, Peter Zijlstra wrote:
>>
>> With some feedback from Jolsa, who showed me how to trigger the actual
>> outputs.
>
> adding Adrian to CC as he's the original author AFAIK
I wanted a compact format, and the omission of n
Le Thursday 02 April 2015 à 01:23 -0700, Christoph Hellwig a écrit :
> The class ids are a hardware defintion, not a kernel API. Just use the
> definitions from libpci, or copy over the kernel header if you prefer
> it over the libpci definutions.
I agree with Christoph, such defines would better
On Thu, Apr 02, 2015 at 10:11:39AM +0200, Markus Pargmann wrote:
> +/*
> + * Forcibly shutdown the socket causing all listeners to error
> + */
> static void sock_shutdown(struct nbd_device *nbd, int lock)
> {
> - /* Forcibly shutdown the socket causing all listeners
> - * to error
> -
Robert Jarzmik writes:
> This is a new driver for pxa SoCs, which is also compatible with the former
> mmp_pdma.
All right, I have a v2 for this patch, with a minor change for muxed interrupt
probe case (1 interrupt for all channels).
I'll release it this week. Did you have the time to have a l
On Wed, Apr 01, 2015 at 10:01:45AM -0700, Feng Kan wrote:
> On Wed, Apr 1, 2015 at 12:45 AM, Mika Westerberg
> wrote:
> > On Tue, Mar 31, 2015 at 02:18:00PM -0700, Feng Kan wrote:
> >> This will add support for ACPI parsing of the mboxes attribute
> >> when booting with ACPI table. The client will
* Andy Lutomirski wrote:
> When I wrote the opportunistic SYSRET code, I missed an important
> difference between SYSRET and IRET. Both instructions are capable
> of setting EFLAGS.TF, but they behave differently when doing so.
> IRET will not issue a #DB trap after execution when it sets TF Th
Hi Alex,
your commit ("memory: jz4780-nemc: driver for the NEMC on JZ4780
SoCs") sets MACH_JZ4780 as Kconfig dependency for the JZ4780_NEMC
driver.
+config JZ4780_NEMC
[...]
+ depends on MACH_JZ4780
MACH_JZ4780 is not defined in Kconfig, so that JZ4780_NEMC is always
false and the driver c
On Wed, 01 Apr 2015 21:56:50 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> New code will require TRACE_SYSTEM to be a valid C variable name,
> but some tracepoints have TRACE_SYSTEM with '-' and not '_', so
> it can not be used. Instead, add a TRACE_SYSTEM_VAR that can
> gi
On Wed, Apr 01, 2015 at 08:04:55PM -0700, Joe Perches wrote:
> On Thu, 2015-04-02 at 10:59 +0800, kbuild test robot wrote:
> > Signed-off-by: Fengguang Wu
> []
> > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c
> > b/drivers/gpu/drm/vgem/vgem_drv.c
> []
> > @@ -195,7 +195,7 @@ static int vgem_gem_d
On Wed, Apr 1, 2015 at 8:22 PM, Peter Hurley wrote:
> The documented behavior of console=ttyS options, to which your
> quote refers, clearly states:
>
> Default is "9600n8".
drivers/tty/serial/8250/8250_early.c:early_serial8250_setup
still have calling to probe_baud, but it is not
On Thu, Apr 02, 2015 at 06:59:07AM +0100, Jason Low wrote:
> On Wed, 2015-04-01 at 18:04 +0100, Morten Rasmussen wrote:
> > On Wed, Apr 01, 2015 at 07:49:56AM +0100, Preeti U Murthy wrote:
>
> > > I am sorry I don't quite get this. Can you please elaborate?
> >
> > I think the scenario is that we
Hi Valentin,
MACH_JZ4780 will definitely be added via arch/mips
But the patch series for core jz4780 SOC support still needs a bit of
refresh/refining.
For reference, see
http://www.spinics.net/lists/mips/msg55258.html
https://github.com/torvalds/linux/compare/master...paulburton:wip-ci20-v4.0
On 01/04/15 19:36, Arnaldo Carvalho de Melo wrote:
> Hi David, Jiri,
>
> Please take a look if it is ok for you guys
>
> Adrian, there is another thing:
>
> db_export__sample(&tables->dbe, event, sample, evsel, al->thread, al);
>
> In tools/perf/util/scripting-engines/trace-event-python
On Wed, Apr 01, 2015 at 06:26:38PM +0200, Peter Zijlstra wrote:
SNIP
> - ret += PRINT_ATTR_U32(wakeup_events);
> - ret += PRINT_ATTR_U32(wakeup_watermark);
> - ret += PRINT_ATTR_X32(bp_type);
> - ret += PRINT_ATTR_X64(bp_addr);
> - ret += PRINT_ATTR_X64(config1);
> - ret +
Hi Zubair,
thanks for your answer and the references.
Kind regards,
Valentin
On Thu, Apr 2, 2015 at 11:19 AM, Zubair Lutfullah Kakakhel
wrote:
> Hi Valentin,
>
> MACH_JZ4780 will definitely be added via arch/mips
>
> But the patch series for core jz4780 SOC support still needs a bit of
> refr
On Wed, Apr 01, 2015 at 05:25:22PM +0300, Boaz Harrosh wrote:
> pfn = PFN_DOWN(ei->addr + ei->size);
>
> - switch (ei->type) {
> - case E820_RAM:
> - case E820_PRAM:
> - case E820_RESERVED_KERN:
> - break;
> -
On Wed, Apr 01, 2015 at 06:18:54PM +0300, Boaz Harrosh wrote:
> You might as well rw & WRITE also for the above pmem_do_bvec call.
> If there can be such problem than the rw == READ inside
> pmem_do_bvec will fail as well.
Might be worth to pass a bool to pmem_do_bvec, but we're getting into
serio
On Wed, Apr 01, 2015 at 07:33:38PM +, Elliott, Robert (Server Storage)
wrote:
> I triggered a paging error in the memcpy call for a block read
> from system-udevd (actually in a modified memcpy() for the cache
> attribute experiments).
>
> 1. This triggered an illegal schedule() call from a
On Thu, Apr 02, 2015 at 02:05:34AM -0700, Christoph Hellwig wrote:
> On Thu, Apr 02, 2015 at 10:11:39AM +0200, Markus Pargmann wrote:
> > +/*
> > + * Forcibly shutdown the socket causing all listeners to error
> > + */
> > static void sock_shutdown(struct nbd_device *nbd, int lock)
> > {
> > -
* Christoph Hellwig wrote:
> On Wed, Apr 01, 2015 at 05:25:22PM +0300, Boaz Harrosh wrote:
> > pfn = PFN_DOWN(ei->addr + ei->size);
> >
> > - switch (ei->type) {
> > - case E820_RAM:
> > - case E820_PRAM:
> > - case E820_RESERVED_KERN:
> > -
Am Mittwoch, 1. April 2015, 11:28:32 schrieb Stephen Warren:
> On 03/31/2015 09:46 AM, Andrey Danin wrote:
> > On 31.03.2015 17:09, Stephen Warren wrote:
> >> On 03/31/2015 12:40 AM, Andrey Danin wrote:
> >>> Hi,
> >>>
> >>> Thanks for the review.
> >>>
> >>> On 03.02.2015 0:20, Stephen Warren w
Signed-off-by: Piotr Witoslawski
---
drivers/staging/rtl8723au/hal/rtl8723au_xmit.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723au/hal/rtl8723au_xmit.c
b/drivers/staging/rtl8723au/hal/rtl8723au_xmit.c
index 1759487..256958e 100644
--- a/drivers/st
On Thu, Apr 02, 2015 at 11:37:40AM +0200, Ingo Molnar wrote:
> So assuming this works on your test setup I'm inclined to squash
> Boaz's fixes into the original patch, assuming you see no outright bug
> in them. Anything else can be done as delta improvements.
It looks sensible, but I'd really l
A few nits follow.
On Wed, 2015-04-01 at 17:12 -0400, Jilai Wang wrote:
> --- a/drivers/gpu/drm/msm/Kconfig
> +++ b/drivers/gpu/drm/msm/Kconfig
> +config DRM_MSM_WB
> + bool "Enable writeback support for MSM modesetting driver"
> + depends on DRM_MSM
> + depends on VIDEO_V4L2
> +
Hi Peter, Lee,
With these series as they are, we need 'clk_ignore_unused' on
sthi407-b2120.dts and stih418-b2199.dts.
We have to modificate stih407-clock.dtsi and stih418-clock.dtsi in same way.
BR
Gabriel
On 2 April 2015 at 10:12, Peter Griffin wrote:
> Hi Lee,
>
> On Fri, 27 Feb 2015, Lee
Hi Linus,
Please pull one powerpc fix for 4.0:
The following changes since commit e42391cd048809d903291d07f86ed3934ce138e9:
Linux 4.0-rc6 (2015-03-29 15:26:31 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git tags/powerpc-4.0-4
for
Signed-off-by: Fengguang Wu
---
xgene-dma.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/xgene-dma.c b/drivers/dma/xgene-dma.c
index 2383528..aa61935 100755
--- a/drivers/dma/xgene-dma.c
+++ b/drivers/dma/xgene-dma.c
@@ -1623,7 +1623,7 @@ static void xgene_d
tree: git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma.git
for-linus
head: fe90ced9e9d7bdba75ccae83100ae656807a6261
commit: 9f2fd0dfa594d857fbdaeda523ff7a46f16567f5 [26/28] dmaengine: Add support
for APM X-Gene SoC DMA engine driver
reproduce:
# apt-get install sparse
git che
* Linus Torvalds wrote:
> On Wed, Apr 1, 2015 at 7:32 AM, Chris J Arges
> wrote:
> >
> > I included the full patch in reply to Ingo's email, and when
> > running with that I no longer get the ack_APIC_irq WARNs.
>
> Ok. That means that the printk's themselves just change timing
> enough, or
Hi Herbert,
On Wednesday 01 April 2015 07:48 PM, Herbert Xu wrote:
> On Tue, Mar 31, 2015 at 09:52:23AM +0530, Lokesh Vutla wrote:
>> Commit 26a05489ee0e ("crypto: omap-sham - Map SG pages if they are HIGHMEM
>> before accessing")
>> says that HIGHMEM pages may not be mapped so we must
>> kmap the
* Aravind Gopalakrishnan wrote:
> GART registers are not present in newer processors (Fam15h, Model 10h
> and later). So, avoid accesses to GART registers in PCI config
> space by returning early in early_gart_iommu_check() and
> gart_iommu_hole_init() if GART is not available.
In what fashion
1 - 100 of 903 matches
Mail list logo
