Hi Alex,
On 3/9/2015 6:00 PM, Alex Williamson wrote:
> On Mon, 2015-03-09 at 17:21 -0700, Ray Jui wrote:
>> Export symbols of the following PCI functions so they can be referenced
>> by a PCI driver compiled as a kernel loadable module:
>>
>> pci_common_swizzle
>> pci_create_root_bus
>>
Okay, thanks for the reviews. My hope was to avoid having to add that
feature into each driver, but that's okay.
-Charlie
On Fri, Mar 6, 2015 at 3:33 PM, Marcel Holtmann wrote:
> Hi Charles,
>
Specifically this was motivated by a situation where we have one
device with
The dw_mmc driver enables HLE errors as part of DW_MCI_ERROR_FLAGS but
nothing in the interrupt handler actually handles them and ACKs them.
That means that if we ever get an HLE error we'll just keep getting
interrupts and we'll wedge things.
We really don't expect HLE errors but if we ever get
On Tue, Mar 10, 2015 at 04:22:34PM +0100, Sascha Hauer wrote:
> + for (i = 0; i < 4; i++) {
> + pwrap_writel(wrp, i, PWRAP_SIDLY);
> + pwrap_read(wrp, PWRAP_DEW_READ_TEST, );
> + printk("%s: 0x%04x\n", __func__, rdata);
Is this really ready for submission,
On Tue, Mar 10, 2015 at 08:42:40AM -0700, Yinghai Lu wrote:
> In arch/x86/boot/header.S, we already use VO and ZO.
> So please keep on using them, and don't introduce "kernel proper" etc.
So you're suggesting commit messages should use variable names and
prefixes from the code instead of being
2015-03-10 16:08 GMT+01:00 Arnd Bergmann :
> On Friday 20 February 2015 19:01:11 Maxime Coquelin wrote:
>> +
>> +Example:
>> +usart1: usart@40011000 {
>> + compatible = "st,stm32-usart";
>>
>
> Please use generic node names everywhere. The standard name for a serial
> port is "serial".
I
On Mon, 9 Mar 2015, Andrew G. Morgan wrote:
> If this is new info, perhaps you might reconsider the rationale for your
> patch? I suspect you are focused on addressing a problem that you felt was
> unaddressed before, but given how much appears to have been unclear to you
> about the current
On Tue, Mar 10, 2015 at 03:36:08PM +, Mark Rutland wrote:
> On the assumption that the patch is otherwise OK, how about the commit
> message below?
Yeah, that'll do fine. Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Mar 10, 2015 at 8:21 AM, Borislav Petkov wrote:
> On Tue, Mar 10, 2015 at 08:17:01AM -0700, Yinghai Lu wrote:
>> Make it not confusing.
>>
>> ZO: arch/x86/boot/compressed/vmlinux
>> VO: vmlinux
>>
>> setup + ZO ==> bzImage.
>>
>> compressed kernel is just compressed VO.
>
> So the two end
This series adds support for the MediaTek SCPSYS unit.
The SCPSYS unit handles several power management related tasks such
as thermal measurement, DVFS, interrupt filter and low level sleep
control.
The initial support only contains the generic power domain handling.
This is needed to turn on
2015-03-10 16:02 GMT+01:00 Arnd Bergmann :
> On Friday 20 February 2015 19:01:06 Maxime Coquelin wrote:
>> +/* AHB1 */
>> +#define GPIOA_RESET0
>> +#define GPIOB_RESET1
>> +#define GPIOC_RESET2
>> +#define GPIOD_RESET3
>> +#define GPIOE_RESET4
>> +#define GPIOF_RESET5
>>
2015-03-10 16:02 GMT+01:00 Arnd Bergmann :
> On Friday 20 February 2015 19:01:06 Maxime Coquelin wrote:
>> +/* AHB1 */
>> +#define GPIOA_RESET0
>> +#define GPIOB_RESET1
>> +#define GPIOC_RESET2
>> +#define GPIOD_RESET3
>> +#define GPIOE_RESET4
>> +#define GPIOF_RESET5
>>
Enable support for generic power domains in the config.
Signed-off-by: Sascha Hauer
---
arch/arm64/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 1b8e973..aef77d2 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -174,6 +174,7
On Tue, Mar 10, 2015 at 04:24:47PM +0100, Philipp Zabel wrote:
> Hi Grant, Rob,
>
> Am Dienstag, den 03.03.2015, 08:59 +0100 schrieb Philipp Zabel:
> > Hi Grant, Rob,
> >
> > this series has been around for quite some time now, basically unchanged
> > except for adding fixes for new users of the
This adds the SCPSYS device node to the MT8173 dtsi file.
Signed-off-by: Sascha Hauer
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index
This adds a power domain driver for the Mediatek SCPSYS unit.
The System Control Processor System (SCPSYS) has several power
management related tasks in the system. The tasks include thermal
measurement, dynamic voltage frequency scaling (DVFS), interrupt
filter and lowlevel sleep control. The
This adds documentation for the MediaTek SCPSYS unit found in MT8173 SoCs.
Signed-off-by: Sascha Hauer
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 32 ++
1 file changed, 32 insertions(+)
create mode 100644
> >> So, for the sysfs interface, let's not allow loading from /lib. Let's
> >> not require a userland tool. Let's just do,
> >>
> >> # echo /path/to/my/awesome/capsule.bin > /sys/../capsule
> >
> >>
> >> and be done with it.
> >>
> >> Hmmm?
> >
> > I assume you're implying a) the capsule
* Linus Walleij [150310 03:39]:
> On Wed, Mar 4, 2015 at 1:00 AM, Nishanth Menon wrote:
>
> > +Configuration definition follows similar model as the pinctrl-single:
> > +The groups of pin configuration are defined under "pinctrl-single,pins"
> > +
> > +_iodelay_core {
> > +
> Why not handle both cases here?
>
> static void print_running(u64 run, u64 ena)
> {
> if (csv_output)
> fprintf(output, ...);
> else if (run != ena)
> fprintf(output, ...);
> }
print_running has 6 callers. run != ena is only needed
for two of them. So I
On Tue, Mar 10, 2015 at 12:53:51PM +, Peter Zijlstra wrote:
> On Tue, Mar 10, 2015 at 12:05:21PM +, Mark Rutland wrote:
> > On Tue, Mar 10, 2015 at 11:27:23AM +, Peter Zijlstra wrote:
> > > On Mon, Mar 09, 2015 at 12:46:30PM +, Suzuki K. Poulose wrote:
> > > > From: "Suzuki K.
2015-03-10 15:03 GMT+01:00 Jörg Otte :
> 2015-03-10 14:06 GMT+01:00 Mathias Nyman :
>> On 10.03.2015 11:40, Jörg Otte wrote:
>>> If I plug in my USB DVB-T stick I get the following in dmesg:
>>>
>>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>>> state.
>>> dvb-usb:
On Tue, 10 Mar 2015, Archit Taneja wrote:
> On 03/10/2015 03:35 PM, Daniel Vetter wrote:
>> On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
>>>
>>>
>>> On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
>>>
On 10 March 2015 at 15:06, Greg KH wrote:
> This doesn't apply anymore due to other patches I just took, so can you
> rebase this patch on my latest staging-testing branch of staging.git?
Fixed in v3 of staging: sm750fb: Cleanup the type of mmio75.
> Also, how about someone fixing the real
Hi Chanwoo,
your commit 96bd6224f07b ("clk: samsung: exynos5433: Add clocks using
common clock framework") is included in today's linux-next tree (i.e.,
next-20150310).
This patch conditionally compiles clk-exynos5433.c depending on the
Kconfig option ARCH_EXYNOS5433. However, t
Hi Paul,
On 03/03/15 17:42, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> This commit removes the open-coded CPU-offline notification with new
> common code. This change avoids calling scheduler code using RCU from
> an offline CPU that RCU is ignoring. This commit is compatible with
On Tue, Mar 10, 2015 at 03:10:46PM +0100, Maarten Lankhorst wrote:
> Op 10-03-15 om 13:37 schreef Peter Zijlstra:
> > So IIRC this is the function that checks who gets wounded (and gets to
> > do the whole retry thing), right?
> >
> > So for the RT case, I think we should extend it to not
2015-03-10 16:00 GMT+01:00 Arnd Bergmann :
> On Friday 20 February 2015 19:01:04 Maxime Coquelin wrote:
>> Some platforms need to initialize the reset controller before the timers.
>>
>> This patch introduces a reset_controller_of_init() function that can be
>> called before the timers
On 03/09/2015 02:12 PM, Guenter Roeck wrote:
On 03/09/2015 11:09 AM, Murali Karicheri wrote:
On 03/09/2015 01:34 PM, Guenter Roeck wrote:
On 03/09/2015 10:03 AM, Murali Karicheri wrote:
On 03/09/2015 12:07 PM, Guenter Roeck wrote:
On 03/09/2015 08:53 AM, Murali Karicheri wrote:
On
On Tue, Mar 10, 2015 at 8:21 AM, Peter Jones wrote:
> On Tue, Mar 10, 2015 at 12:26:52PM +, Matt Fleming wrote:
>> On Fri, 06 Mar, at 04:39:12PM, Peter Jones wrote:
>> >
>> > So again: do we really need or want to do this?
>>
>> One thing that we totally lose the ability to do is use the
This patch assigns the more appropriate void* type to the mmio750 variable
eliminating an unnecessary volatile qualifier in the process. Additionally it
updates parameter types as necessary where those parameters interact with
mmio750, removes unnecessary casts and updates the type of the
On Tue, Mar 10, 2015 at 10:56:32AM -0400, Peter Jones wrote:
> That said, I haven't sent my patch to add the capsule headers to gnu-efi
> yet, so you won't get very far - I'll make sure and send those this
> week, hopefully today.
Slight correction, I did actually do that - it's in the current
Since the previous patch ead3700d893654d440edcb66fb3767a0c0db54cf ("storvsc:
use cmd_size to allocate per-command data") fills .proc_name now anyway give it
a usable content for v4.0. Old mkinitrd in SLES makes use of this variable to
find the required storage driver.
Signed-off-by: Olaf Hering
From: Flora Fu
This adds support for the PMIC wrapper found on MediaTek MT8135 and
MT8173 SoCs. The PMIC wrapper is found on MT6xxx SoCs aswell but these
are currently not supported.
On MediaTek MT8135, MT8173 and other SoCs the PMIC is connected via
SPI. The SPI master interface is not
On some platforms such as that based on x86, ia64 etc, root bus is
created with parent node passed in as NULL to pci_create_root_bus().
On these platforms, the patch series "PCI: get DMA configuration from
parent device" when applied causes kernel crash. So add a check for this
in
[Note: This is v2 of this series which contains the PMIC wrapper patches only,
the patches themselves have been posted as part of other series already]
This series adds support for the PMIC wrapper found on MT8135 and
MT8173 SoCs. No further compile time dependencies.
Changes since last version:
On Tue, Mar 10, 2015 at 08:17:01AM -0700, Yinghai Lu wrote:
> Make it not confusing.
>
> ZO: arch/x86/boot/compressed/vmlinux
> VO: vmlinux
>
> setup + ZO ==> bzImage.
>
> compressed kernel is just compressed VO.
So the two end up being the "compressed kernel" and "kernel proper".
And then
This adds documentation for the PMIC wrapper unit found on Mediatek
SoCs. Currently support are the MT8135 and MT8173 SoCs, but the PMIC
wrapper can also be found on MT6xxx and possibly other SoCs.
Signed-off-by: Sascha Hauer
---
.../devicetree/bindings/soc/mediatek/pwrap.txt | 58
On 03/10/2015 03:22 PM, Jan Kara wrote:
> On Tue 10-03-15 06:03:23, Christoph Hellwig wrote:
>> On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
>>> Any updates?
>> Please just add disk quota support to tmpfs so thast the standard quota
>> netlink notifications can be used.
> If I
Hi Grant, Rob,
Am Dienstag, den 03.03.2015, 08:59 +0100 schrieb Philipp Zabel:
> Hi Grant, Rob,
>
> this series has been around for quite some time now, basically unchanged
> except for adding fixes for new users of the API that keep appearing
> over time in different subsystems.
>
> It would
return type of wait_for_completion_timeout is unsigned long not int. An
appropriately named unsigned long is added and the assignment fixed up.
Signed-off-by: Nicholas Mc Guire
---
This was only compile tested for x86_64_defconfig + CONFIG_CEPH_FS=m
Patch is against 4.0-rc2 linux-next
On Tue, Mar 10, 2015 at 12:26:52PM +, Matt Fleming wrote:
> On Fri, 06 Mar, at 04:39:12PM, Peter Jones wrote:
> >
> > So again: do we really need or want to do this?
>
> One thing that we totally lose the ability to do is use the capsule
> interface for things *other* than firmware updates,
From: "Suzuki K. Poulose"
We mask the event with the CCI_PMU_EVENT_MASK, before passing
the config to pmu_validate_hw_event(), which causes extra bits
to be ignored and qualifies an invalid event code as valid.
e.g,
$ perf stat -a -C 0 -e CCI_400/config=0x1ff,name=cycles/ sleep 1
From: "Suzuki K. Poulose"
This patch separates the PMU driver code from the low level
CCI driver code and enables the PMU driver for ARM64.
Introduces config options for both.
ARM_CCI400_PORT_CTRL - controls the low level driver code for
CCI400 ports.
From: "Suzuki K. Poulose"
Avoid secure transactions while probing the CCI PMU. The
existing code makes use of the Peripheral ID2 (PID2) register
to determine the revision of the CCI400, which requires a
secure transaction. This puts a limitation on the usage of the
driver on systems running
From: "Suzuki K. Poulose"
This series enables the PMU monitoring support for CCI400 on ARM64.
The existing CCI400 driver code is a mix of PMU driver and the MCPM
driver code. The MCPM driver is only used on ARM(32) and contains
arm32 assembly and hence can't be built on ARM64. This patch splits
From: "Suzuki K. Poulose"
CCI400 has different event specifications for PMU, for revsion
0 and revision 1. As of now, we check the revision every single
time before using the parameters for the PMU. This patch abstracts
the details of the pmu models in a struct (cci_pmu_model) and
stores the
Hello,
On Wed, Mar 11, 2015 at 01:51:06AM +1100, Aleksa Sarai wrote:
> Actually, I'm fairly sure we can do it all inside cgroup_post_fork() because
> inside cgroup_post_fork() we have access to both the old css_set and the new
> one. Then it's just a matter of reverting and re-applying the charge
From: "Suzuki K. Poulose"
No functional changes, only code re-arrangements for easier split of the
PMU code vs low level driver code. Extracts the port handling code
to cci_probe_ports().
Change since V2:
- Removed unnecessary goto. (Suggested-by: Sudeep Holla)
Signed-off-by: Suzuki K.
Hi Herbert,
I just fixed a small DRBG return code issue inside testmgr.c directly
related to the RNG changes Stephan submitted.
Regards,
Alex
--
Alexander Bergmann , Security Engineer,
SUSE Linux GmbH,
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton, HRB
On Tue, Mar 10, 2015 at 8:10 AM, Borislav Petkov wrote:
> On Tue, Mar 10, 2015 at 08:05:52AM -0700, Yinghai Lu wrote:
>> We need to keep VO and ZO here...
>
> Why?
Make it not confusing.
ZO: arch/x86/boot/compressed/vmlinux
VO: vmlinux
setup + ZO ==> bzImage.
compressed kernel is just
On Mon, 09 Mar 2015, Dmitry Torokhov wrote:
> Even if bus is not hot-pluggable, the devices can be unbound from the
> driver via sysfs, so we should not be using __exit annotations on
> remove() methods. The only exception is drivers registered with
> platform_driver_probe() which specifically
On Tue, Mar 10, 2015 at 08:11:03AM -0700, Yinghai Lu wrote:
> Also stop using "compressed kernel" please, that is confusing.
Why?
> Just use
>
> ZO: arch/x86/boot/compressed/vmlinux
> VO: vmlinux
and this is not confusing?
Yeah, right.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your
On Tue, Mar 10, 2015 at 03:05:26PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Tuesday, March 10, 2015 12:42 AM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> >
On 03/09/2015 04:29 PM, Shuah Khan wrote:
> On 03/09/2015 08:20 AM, Shuah Khan wrote:
>> On 03/05/2015 11:53 AM, Dave Jones wrote:
>>> On Tue, Mar 03, 2015 at 03:51:35PM +1100, Michael Ellerman wrote:
>>> > This adds make install support to selftests. The basic usage is:
>>> >
>>> > $ cd
On Tue, Mar 10, 2015 at 09:22:51AM -0500, Rob Herring wrote:
> On Wed, Feb 18, 2015 at 3:50 AM, Benjamin Herrenschmidt
> wrote:
> > On Tue, 2015-02-17 at 20:57 -0800, Greg Kroah-Hartman wrote:
> >
> >> > Acked-by: Rob Herring
> >>
> >> Thanks, I'll queue these up after 3.20-rc1 is out.
>
> It
On Tue, Mar 10, 2015 at 08:05:52AM -0700, Yinghai Lu wrote:
> We need to keep VO and ZO here...
Why?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Remove sysfs `num_migrated' attribute. We are moving away from
per-stat device attrs towards 3 stat files that will accumulate
io and mm stats in a format similar to block layer statistics in
/sys/block//stat. That will be easier to use in user space,
and reduce the number of syscalls needed to
On Tue, Mar 10, 2015 at 1:00 AM, Borislav Petkov wrote:
> Final patch:
>
> ---
> From: Yinghai Lu
> Date: Sat, 7 Mar 2015 14:07:16 -0800
> Subject: [PATCH] x86/setup: Move compressed kernel to the end of the buffer
setup should only about arch/x86/boot/setup.ld related.
So please keep x86,
On Friday 20 February 2015 19:01:10 Maxime Coquelin wrote:
> --- /dev/null
> +++ b/include/dt-bindings/pinctrl/pinctrl-stm32.h
> @@ -0,0 +1,43 @@
> +#ifndef _DT_BINDINGS_PINCTRL_STM32_H
> +#define _DT_BINDINGS_PINCTRL_STM32_H
> +
> +/* Modes */
> +#define IN 0
> +#define OUT
On Tue, Mar 10, 2015 at 01:27:48PM +, Lorenzo Stoakes wrote:
> This patch assigns the more appropriate void* type to the mmio750 variable
> eliminating an unnecessary volatile qualifier in the process. Additionally it
> updates parameter types as necessary where those parameters interact with
> I think we could still solve this problem by deferring the 'context'
> validation to the core. The PMUs could validate the group, within its
> context. i.e, if it can accommodate its events as a group, during
> event_init. The problem we face now, is encountering an event from a
> different
Per-device `zram/mm_stat' file provides accumulated mm statistics
of particular zram device in a format similar to block layer statistics.
The file consists of a single line and represents the following stats
(separated by whitespace):
orig_data_size
compr_data_size
Per-device `zram/io_stat' file provides accumulated I/O statistics
of particular zram device in a format similar to block layer statistics.
The file consists of a single line and represents the following stats
(separated by whitespace):
failed_reads
failed_writes
invalid_io
On Tue, Mar 10, 2015 at 04:07:28PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from include/linux/module.h:17:0,
> from drivers/staging/sm750fb/sm750.c:2:
>
Use bio generic_start_io_acct() and generic_end_io_acct() to account
device's block layer statistics. This will let users to monitor zram
activities using sysstat and similar packages/tools.
Apart from the usual per-stat sysfs attr, zram IO stats are now also
available in '/sys/block/zram/stat'
Hello,
This patch introduces rework to zram stats. We have per-stat sysfs
nodes, and it makes things a bit hard to use in user space: it doesn't
give an immediate stats 'snapshot', it requires user space to use
more syscals -- open, read, close for every stat file, with
appropriate error checks
On Friday 20 February 2015 19:01:11 Maxime Coquelin wrote:
> +
> +Example:
> +usart1: usart@40011000 {
> + compatible = "st,stm32-usart";
>
Please use generic node names everywhere. The standard name for a serial
port is "serial".
Arnd
--
To unsubscribe from this list: send the
Briefly describe exported device stat attrs in zram documentation.
We will eventually get rid of per-stat sysfs nodes and, thus,
clean up Documentation/ABI/testing/sysfs-block-zram file, which is
the only source of information about device sysfs nodes.
Add `num_migrated' description, since there
On 10 March 2015 at 15:04, Greg KH wrote:
> I can't apply patches that add new build warnings, sorry. Please fix
> this up in the patch itself.
>
> greg k-h
Hi Greg,
Apologies for this, I've resolved this issue in v2 of the patch, no
warning messages are added in the updated version of this
A cosmetic change. We have a new code layout and keep zram per-device
sysfs store and show functions in one place. Move compact_store() to
that handlers block to conform to current layout.
Signed-off-by: Sergey Senozhatsky
---
drivers/block/zram/zram_drv.c | 42
On Tue, Mar 10, 2015 at 2:34 AM, Borislav Petkov wrote:
> Final patch:
>
> ---
> From: Yinghai Lu
> Date: Sat, 7 Mar 2015 14:07:17 -0800
> Subject: [PATCH] x86/setup: Don't overlap vmlinux's brk with compressed
> kernel's data
We need to keep VO and ZO here...
Should use ZO to replace
On 03/10/2015 05:39 AM, Linus Walleij wrote:
> On Wed, Mar 4, 2015 at 1:00 AM, Nishanth Menon wrote:
>
>> +Configuration definition follows similar model as the pinctrl-single:
>> +The groups of pin configuration are defined under "pinctrl-single,pins"
>> +
>> +_iodelay_core {
>> +
On Tue, Mar 10, 2015 at 02:54:16PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> > Sent: Tuesday, March 10, 2015 12:41 AM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org;
On Tue, Mar 10, Christoph Hellwig wrote:
> On Tue, Mar 10, 2015 at 12:42:33PM +0100, Olaf Hering wrote:
> > It would be nice to change .proc_name to KBUILD_MODNAME before v4.0 is
> > released. We carry a patch which adds this field. Of cource we can just
> > change the patch, but if code gets
On Friday 20 February 2015 19:01:04 Maxime Coquelin wrote:
> Some platforms need to initialize the reset controller before the timers.
>
> This patch introduces a reset_controller_of_init() function that can be
> called before the timers intialization.
>
> Signed-off-by: Maxime Coquelin
>
Not
On Tue, Mar 10, 2015 at 12:47:44PM +, Lorenzo Stoakes wrote:
> On 10 March 2015 at 12:36, Sudip Mukherjee wrote:
> > but it is introducing two new build warnings:
> >
> > drivers/staging/sm750fb/sm750_hw.c: In function ‘hw_sm750_map’:
> > drivers/staging/sm750fb/sm750_hw.c:67:2: warning:
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, March 10, 2015 12:42 AM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com
> Subject: Re: [PATCH V2 1/7]
On Friday 20 February 2015 19:01:06 Maxime Coquelin wrote:
> +/* AHB1 */
> +#define GPIOA_RESET0
> +#define GPIOB_RESET1
> +#define GPIOC_RESET2
> +#define GPIOD_RESET3
> +#define GPIOE_RESET4
> +#define GPIOF_RESET5
> +#define GPIOG_RESET6
> +#define GPIOH_RESET7
>
On Tue, 10 Mar 2015 14:03:59 +0100, Yann Droneaud said:
> > Consider the following sequence of events:
> >
> > 0. Suppose a mutex is locked by task A and has no waiters.
> >
> > 1. Task B calls mutex_trylock().
> >
> > 2. mutex_trylock() calls the architecture-specific
> >
On Tue, Mar 10, 2015 at 08:51:59AM +, Lorenzo Stoakes wrote:
> This patch fixes the following sparse warning:-
>
> drivers/staging/sm750fb/ddk750_help.c: warning: incorrect type in assignment
> (different address spaces)
>
> In addition it eliminates an unnecessary volatile.
This doesn't
return type of wait_for_completion_timeout is unsigned long not int. An
appropriately named unsigned long is added and the
assignment fixed up.
Signed-off-by: Nicholas Mc Guire
---
Note that there does not seem to be any protection against the on stack
struct completion going out of scope if
Em Tue, Mar 10, 2015 at 10:44:00AM -0400, Jérémie Galarneau escreveu:
> On Tue, Mar 10, 2015 at 10:11 AM, Jiri Olsa wrote:
> > On Tue, Mar 10, 2015 at 11:01:34AM -0300, Arnaldo Carvalho de Melo wrote:
> >> Em Tue, Mar 10, 2015 at 01:00:35PM +0100, Jiri Olsa escreveu:
> >> > Adding proper header
On Mon, Mar 09, 2015 at 06:54:12PM -0700, Roy Franz wrote:
> On Mon, Mar 9, 2015 at 2:23 PM, Borislav Petkov wrote:
> > + pjones.
> >
> > So reportedly, there is already a capsule-loading thing which doesn't
> > need the kernel at all:
> >
> > https://github.com/rhinstaller/fwupdate
> >
> > So
On Tue, Mar 10, 2015 at 02:33:37PM +, Alexander Gordeev wrote:
> On Mon, Mar 09, 2015 at 02:35:42PM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 09, 2015 at 09:36:52AM +, Alexander Gordeev wrote:
> > > On Mon, Mar 09, 2015 at 09:34:04AM +0100, Alexander Gordeev wrote:
> > > > Hi Paul,
>
On Sun, Mar 8, 2015 at 9:35 PM, Wang Long wrote:
> Since the directory "drivers/of/testcase-data" is renamed
> to "drivers/of/unittest-data". so we should update the path
> in the of_selftest.txt.
>
> When the kernel is built with OF_SELFUNIT enabled, the output
Still wrong...
> dtb is
On Tue, 10 Mar 2015 13:47:15 +0200
Gilad Broner wrote:
> +++ b/include/trace/events/ufs.h
> @@ -0,0 +1,227 @@
> +/*
> + * Copyright (c) 2013-2015, The Linux Foundation. All rights reserved.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms
> -Original Message-
> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, March 10, 2015 12:41 AM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com
> Subject:
Hello Tejun,
On Tue, Mar 10, 2015 at 11:47 PM, Tejun Heo wrote:
>> of doing a charge that stops if you hit a certain `css` (unless we start
>> passing `css_set`s to the fork/exit callbacks -- and then we can uncharge the
>> old css_set and charge the new one).
>
> We'll have to pass the pointer
On Tue, Mar 10, 2015 at 9:44 AM, Rob Herring wrote:
> On Sun, Mar 8, 2015 at 9:35 PM, Wang Long wrote:
>> Since the directory "drivers/of/testcase-data" is renamed
>> to "drivers/of/unittest-data". so we should update the path
>> in the of_selftest.txt.
[...]
>> -Before executing OF selftest,
On Tue, Mar 10, 2015 at 03:36:17PM +0100, Petr Mladek wrote:
> On Tue 2015-03-10 09:22:04, Josh Poimboeuf wrote:
> > On Tue, Mar 10, 2015 at 01:01:07PM +0100, Petr Mladek wrote:
> > > On Mon 2015-03-09 09:40:55, Josh Poimboeuf wrote:
> > > > On Mon, Mar 09, 2015 at 02:25:28PM +0100, Petr Mladek
Device-tree binding documentation for Xilinx ZDMA Engine
Signed-off-by: Punnaiah Choudary Kalluri
---
.../devicetree/bindings/dma/xilinx/zdma.txt| 76
1 files changed, 76 insertions(+), 0 deletions(-)
create mode 100644
On Tue, Mar 10, 2015 at 02:39:39PM +, Alexander Gordeev wrote:
> On Mon, Mar 09, 2015 at 09:43:18PM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 09, 2015 at 04:49:43PM -0700, Paul E. McKenney wrote:
> > > On Mon, Mar 09, 2015 at 04:39:47PM -0700, Paul E. McKenney wrote:
> > > > On Mon, Mar
On Tue, Mar 10, 2015 at 10:11 AM, Jiri Olsa wrote:
> On Tue, Mar 10, 2015 at 11:01:34AM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Tue, Mar 10, 2015 at 01:00:35PM +0100, Jiri Olsa escreveu:
>> > On Mon, Mar 09, 2015 at 08:28:45PM -0300, Arnaldo Carvalho de Melo wrote:
>> > > Em Mon, Mar 09,
On Tue, Mar 10, 2015 at 10:41:42AM +0100, Sascha Hauer wrote:
> > > + if (data->bus_prot_mask) {
> > > + u32 mask = data->bus_prot_mask;
> > > + struct regmap *infracfg = scp->infracfg;
> > > +
> > > + regmap_update_bits(infracfg, INFRA_TOPAXI_PROTECTEN, mask, 0);
> > > +
>
These don't seem to be used anywhere.
Acked-by: Rik van Riel
Cc: Benjamin Herrenschmidt
Cc: Alexander Graf
Cc: Paul E. McKenney
Cc: Andy Lutomirski
Cc: Will deacon
Cc: Marcelo Tosatti
Cc: Christian Borntraeger
Cc: Luiz Capitulino
Cc: Paolo Bonzini
Signed-off-by: Frederic Weisbecker
---
From: Rik van Riel
With code elsewhere doing something conditional on whether or not
context tracking is enabled, we want a stub function that tells us
context tracking is not enabled, when CONFIG_CONTEXT_TRACKING is
not set.
Reviewed-by: Paul E. McKenney
Signed-off-by: Rik van Riel
Cc: Paul
On Tue 2015-03-10 09:22:04, Josh Poimboeuf wrote:
> On Tue, Mar 10, 2015 at 01:01:07PM +0100, Petr Mladek wrote:
> > On Mon 2015-03-09 09:40:55, Josh Poimboeuf wrote:
> > > On Mon, Mar 09, 2015 at 02:25:28PM +0100, Petr Mladek wrote:
> > > > diff --git a/kernel/module.c b/kernel/module.c
> > > >
From: Rik van Riel
Generalize the context tracking APIs to support various nature of
contexts. This is performed by splitting out the mechanism from
context_tracking_user_enter and context_tracking_user_exit into
context_tracking_enter and context_tracking_exit.
The nature of the context we
From: Rik van Riel
Export context_tracking_user_enter/exit so it can be used by KVM.
Reviewed-by: Paul E. McKenney
Signed-off-by: Rik van Riel
Cc: Paul E. McKenney
Cc: Andy Lutomirski
Cc: Will deacon
Cc: Marcelo Tosatti
Cc: Christian Borntraeger
Cc: Luiz Capitulino
Cc: Paolo Bonzini
501 - 600 of 1866 matches
Mail list logo
