Hi Rob,
> On Feb 12, 2016, at 01:18 , Rob Herring wrote:
>
> On Wed, Feb 3, 2016 at 12:09 PM, Amitoj Kaur Chawla
> wrote:
>> In __of_find_node_by_full_name, add an of_node_get when detecting the
>> desired element, to ensure that it ends up with a reference count that is
>> one greater than on
2016-02-11 23:19 GMT+03:00 Ильяс Гасанов :
> 2016-02-11 22:08 GMT+03:00 Matwey V. Kornilov :
>> Thanks for pointing out. serial8250_unregister_port should set
>> serial8250_ports[line].em485 to NULL in order to prevent unneeded
>> activation when this struct is reused.
>
> Then the
On 02/11/2016, 06:32 PM, Willy Tarreau wrote:
> Hi Jiri,
>
> On Thu, Feb 11, 2016 at 02:59:08PM +0100, Jiri Slaby wrote:
>> From: willy tarreau
>>
>> 3.12-stable review patch. If anyone has any objections, please let me know.
>>
>> ===
>>
>> [ Upstream commit
On Feb 11 2016 or thereabouts, Andrew Duggan wrote:
> On 02/11/2016 02:05 AM, Benjamin Tissoires wrote:
> >On Feb 10 2016 or thereabouts, Andrew Duggan wrote:
> >>This is the v5 patch series which fixes the issues identified by kbuild
> >>and coccinelle in the previous patch series. These include:
Use eth_zero_addr to assign the zero address to the given address
array instead of memset when second argument is address of zero.
The Coccinelle semantic patch used to make this change is as follows:
//
@eth_zero_addr@
expression e;
@@
-memset(e,0x00,ETH_ALEN);
+eth_zero_addr(e);
//
On 2016.02.11 14:50 Doug Smythies wrote:
> On 2016.02.10 22:03 Srinivas Pandruvada wrote:
>> On Wednesday, February 10, 2016 03:11:43 PM Doug Smythies wrote:
>>> My test computer has an older model i7 (Intel(R) Core(TM) i7-2600K CPU @
>>> 3.40GHz)
>> Thanks Doug. If you have specific workloads,
setup_access_params_addr has 2 goals-
-Initialize the access_params field so that it can be used to send and read
commands from the device in access_with_param
-Get a bus address for the allocated memory to transfer to the device.
Replace the combination of devm_kzalloc and _pa() with
Please pull this patch for the EVM code, which fixes CVE-2016-2085.
The following changes since commit c05235d50f681bf685e7290cae05ab3b4fa493f3:
Merge tag 'gpio-v4.5-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio (2016-02-11
11:25:55 -0800)
are available in the git
CC'ing Jens Axboe.
On 11 February 2016 at 09:54, Jens Rosenboom wrote:
> 2016-02-11 4:48 GMT+01:00 Sitsofe Wheeler :
>> Trying to cc the GNU parted and linux-block mailing lists.
>>
>> On 9 February 2016 at 13:02, Jens Rosenboom wrote:
>>> While trying to reproduce some performance issues I
This patch fixes the alignment issue reported by checkpatch.pl:
CHECK: Alignment should match open parenthesis
Add a unsigned char *sgbuffer in rtsx_stor_access_xfer_buffer to make the
following memcpy logic easier to read.
Add a struct scatterlist *sg in the use_sg branch of
Hi Suman,
On Friday 12 February 2016 02:13 AM, Suman Anna wrote:
> On 02/09/2016 11:38 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Wednesday 10 February 2016 07:12 AM, Suman Anna wrote:
>>> Hi Paul,
>>>
>>> On 02/09/2016 01:36 PM, Paul Walmsley wrote:
Hi Suman
On Tue, 9 Feb
Hi,
On Friday 12 February 2016 12:57 AM, Paul Walmsley wrote:
> Hi Kishon, Suman,
>
> On Wed, 10 Feb 2016, Kishon Vijay Abraham I wrote:
>
>> On Wednesday 10 February 2016 07:12 AM, Suman Anna wrote:
>>> On 02/09/2016 01:36 PM, Paul Walmsley wrote:
On Tue, 9 Feb 2016, Suman Anna wrote:
Static checkers complain that the this is a potential array overflow.
We verify that it's not on the next line so this code is OK, but
static checker warnings are annoying.
Signed-off-by: Dan Carpenter
---
We would have caught CVE-2015-5327 if we had ordered it to check first
before using the
Swap the printk and kfree() to avoid a use after free bug.
Fixes: 61e9c905df78 ('misc: mic: Enable VOP host side functionality')
Signed-off-by: Dan Carpenter
diff --git a/drivers/misc/mic/vop/vop_vringh.c
b/drivers/misc/mic/vop/vop_vringh.c
index c1dd000..c3613f3 100644
---
We accidentally test "config.regmap" which is zero instead of
"vreg->regmap".
Fixes: 18bba3b50355 ('regulator: qcom-saw: Add support for SAW regulators')
Signed-off-by: Dan Carpenter
diff --git a/drivers/regulator/qcom_saw-regulator.c
b/drivers/regulator/qcom_saw-regulator.c
index
On 02/11/2016 04:32 PM, Guenter Roeck wrote:
> On Thu, Feb 11, 2016 at 07:45:11AM +0100, Andrzej Hajda wrote:
>> On 02/11/2016 04:38 AM, Guenter Roeck wrote:
>>> On 02/10/2016 07:21 AM, Arnd Bergmann wrote:
On Tuesday 09 February 2016 18:37:46 Guenter Roeck wrote:
> On 02/09/2016 07:26
copy_to_user() returns the number of bytes not copied but we want to
return an error code.
Fixes: a45bfc36bf0d ('rapidio: add mport char device driver')
Signed-off-by: Dan Carpenter
diff --git a/drivers/rapidio/devices/rio_mport_cdev.c
b/drivers/rapidio/devices/rio_mport_cdev.c
index
On 11-02-16, 02:25, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The show() and store() routines in the cpufreq core don't need to
> acquire all of the locks to check if the struct freq_attr they want
> to use really provides the callbacks they need as expected, so change
> them to
On Wed, Jan 20, 2016 at 11:18:08AM -0500, Insu Yun wrote:
> Since sizeof(ext_new_group_data) > sizeof(ext_new_flex_group_data),
> integer overflow could be happened.
> Therefore, need to fix integer overflow sanitization.
>
> Signed-off-by: Insu Yun
Thanks, applied.
On Wed, Feb 03, 2016 at 02:12:44PM -0700, Andreas Dilger wrote:
>
> > On Feb 3, 2016, at 6:19 AM, Huaitong Han wrote:
> >
> > This patch adds a line break for proc mb_groups display.
> >
> > Signed-off-by: Huaitong Han
>
> Reviewed-by: Andreas Dilger
Thanks, applied.
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160211:
since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
allmodconfig builds are failing with the error:
"arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 i
00 00 00 00 00 00 00 00 00
00 00 00 00
[6035791.333886] Object 880052e5c1f0: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
[6035791.334813] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GB W
4.5.0-rc3-next-20160211-sasha-00028-g542d18e-dirty #2898
A set of seven fixes. Two regressions in the new hisi_sas arm driver,
a blacklist entry for the marvell console which was causing a reset
cascade without it, a race fix in the WRITE_SAME/DISCARD routines, a
retry fix for the rdac driver, without which, it would prematurely
return EIO and a couple
Hello Maxime,
On Thu, Feb 4, 2016 at 4:01 PM, Maxime Ripard
wrote:
> On Thu, Feb 04, 2016 at 02:06:45PM +0800, Vishnu Patekar wrote:
>> Hello Maxime,
>>
>>
>> On Tue, Feb 2, 2016 at 9:17 PM, Maxime Ripard
>> wrote:
>> > Hi,
>> >
>> > On Sun, Jan 31, 2016 at 09:20:56AM +0800, Vishnu Patekar
Hi all,
Changes since 20160211:
The kvm-arm tree gained a conflict against the arm64 tree.
The aio tree still had a build failure so I used the version from
next-20160111.
Non-merge commits (relative to Linus' tree): 4277
3754 files changed, 149171 insertions(+), 67859 deletions
On (02/11/16 17:10), Petr Mladek wrote:
[..]
> > well, I believe it's ok. __rcu_read_lock() for CONFIG_PREEMPT_RCU
> > does current->rcu_read_lock_nesting++, so rcu_preempt_depth() works
> > as expected. otherwise, for !CONFIG_PREEMPT_RCU kernel,
> > __rcu_read_lock() does
> >
> > if
On Thu, Feb 11, 2016 at 10:58:58AM -0500, Anton Protopopov wrote:
> The ext4_ioctl_setflags() function which is used in the ioctls
> EXT4_IOC_SETFLAGS and EXT4_IOC_FSSETXATTR may return the positive value
> EPERM instead of -EPERM in case of error. This bug was introduced by a
> recent commit
On 2/11/16, Theodore Ts'o wrote:
> On Thu, Feb 11, 2016 at 11:12:12AM -0700, Jeff Merkey wrote:
>>
>> That's good to know, they could be false positives, but it was kind of
>> wierd behavior caused by that macro.
>
> If it is true, it sounds more like a compiler bug to me. Any
> statements a
On Thu, Feb 11, 2016 at 06:14:35PM +0100, Jens Wiklander wrote:
> +static int tee_ioctl_shm_alloc(struct tee_context *ctx,
> + struct tee_ioctl_shm_alloc_data __user *udata)
> +{
> + long ret;
> + struct tee_ioctl_shm_alloc_data data;
> + struct tee_shm *shm;
> +
> +
Hi Shaun,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.5-rc3 next-20160211]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Shaun-Ren/Staging-rts5208-Fix
On 2/11/16, Jeff Merkey wrote:
>> In your case, for example, I looked through several dozen warnings,
>> and they were ***all*** bogus. Keep in mind that this might make me
>> less inclined to pay attention to complaints from you in the future.
>> The story of the buy who cried wolf too often
On Thu, 2016-02-11 at 20:07 -0800, Shaun Ren wrote:
> This patch fixes the alignment issue reported by checkpatch.pl:
>
> CHECK: Alignment should match open parenthesis
[]
> diff --git a/drivers/staging/rts5208/rtsx_transport.c
> b/drivers/staging/rts5208/rtsx_transport.c
[]
> @@ -52,12 +55,14
The max77686 MFD driver supports both the Maxim 77686 and Maxim 77802
PMICs but only the OF device table contains entries for both devices.
The max77802 entry is missing in the I2C device ID table which isn't
a problem currently since the driver only supports DT but it will be
needed if the
The driver's Kconfig symbol is a boolean but nothing prevents the driver
to be built as a module instead of built-in. It is true that most system
integrators will choose the latter but the config should not restrict it.
Signed-off-by: Javier Martinez Canillas
---
drivers/mfd/Kconfig | 4 ++--
Hello,
The Maxim77802 PMIC driver uses a boolean Kconfig symbol but there isn't
really a reason to require the driver to be built-in.
It is true that since the PMIC provides clocks and regulators that could
be critical on a system, most integrators are not going to build it as a
module but it
When the device is registered via OF, the OF table is used to match the
driver instead of the I2C device ID table but the entries in the latter
are used as aliasses to load the module if the driver was not built-in.
This is because the I2C core always reports an I2C module alias instead
of an OF
The driver's init and exit function don't do anything besides adding and
deleting the I2C driver so the module_i2c_driver() macro could be used.
Currently is not being used because the driver is initialized at subsys
initcall level, claiming that this is done to allow consumers devices to
use the
> In your case, for example, I looked through several dozen warnings,
> and they were ***all*** bogus. Keep in mind that this might make me
> less inclined to pay attention to complaints from you in the future.
> The story of the buy who cried wolf too often comes to mind.
>
> Perhaps you could
Hi Linus,
Been pretty quiet, this is an amdgpu fixes pull from AMD,
a bunch of powerplay stability fixes, race fix, hibernate fix,
and a possible circular locking fix.
Dave.
The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95:
Linux 4.5-rc3 (2016-02-07 15:38:30
On 2/11/16, Theodore Ts'o wrote:
> On Thu, Feb 11, 2016 at 11:12:12AM -0700, Jeff Merkey wrote:
>>
>> That's good to know, they could be false positives, but it was kind of
>> wierd behavior caused by that macro.
>
> If it is true, it sounds more like a compiler bug to me. Any
> statements a
This patch fixes the alignment issue reported by checkpatch.pl:
CHECK: Alignment should match open parenthesis
Add a unsigned char *sgbuffer in rtsx_stor_access_xfer_buffer to make the
following memcpy logic easier to read.
Add a struct scatterlist *sg in the use_sg branch of
This patch fixes the following styling issue in rtsx_transport.c
as reported by checkpatch.pl:
CHECK: spaces preferred around that '-' (ctx:VxV)
Signed-off-by: Shaun Ren
---
drivers/staging/rts5208/rtsx_transport.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
This patch removes all unnecessary parentheses found by checkpatch.pl.
Signed-off-by: Shaun Ren
---
Changes since v3
* Fixed patch conflicts due to commit 9a66d05d82db
("Staging: rts5208: fix check for dma mapping error"), and
commit b3232842dbef ("Staging: rts5208: remove unnecessary
This patch fixes the following naming convention issue in rtsx_transport.c,
as reported by checkpatch.pl:
CHECK: Avoid CamelCase:
Signed-off-by: Shaun Ren
---
drivers/staging/rts5208/rtsx_transport.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
This patch fixes the following issues in rtsx_transport.c as reported by
checkpatch.pl:
CHECK: Blank lines aren't necessary after an open brace '{'
CHECK: Please don't use multiple blank lines
Signed-off-by: Shaun Ren
---
drivers/staging/rts5208/rtsx_transport.c | 3 ---
1 file changed, 3
This patch removes all spaces after casts in rtsx_transport.c, as reported
by checkpatch.pl:
CHECK: No space is necessary after a cast
Signed-off-by: Shaun Ren
---
drivers/staging/rts5208/rtsx_transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch changes all comparsions to NULL with !..., as reported by
checkpatch.pl.
Signed-off-by: Shaun Ren
---
drivers/staging/rts5208/rtsx_transport.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rts5208/rtsx_transport.c
This set of patches fixes the coding style issues in rtsx_transport.c.
Changes since v3
* Removed the extraneous SCSI comment in the first patch
* Removed the last patch (Staging: rts5208: Add missing dma_mapping_error)
as it is already done in change 9a66d05d82db
(Staging: rts5208: fix
This patch fixes all multiline comments to conform to the coding style,
which states that multiline comments should start with "/*" and end
with "*/" on a separate line.
Also cleans up some comments to make them more clear and/or reflect what
the code is doing.
Signed-off-by: Shaun Ren
---
The max77686 and max77802 regulator drivers are for sub-devices of a MFD
driver for some PMIC blocks. But the same object file name (max77686.o)
was used for both the common MFD driver and the max77686 regulator one.
This confuses kbuild if both drivers are built as module causing the MFD
driver
On Wed, Feb 10, 2016 at 12:15:04PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for this -rc cycle below. It contains a fix in
> phy core, twl4030-usb phy driver and a fix in Kconfig.
>
> Consider merging it to this -rc cycle. Let me know if you want me to
Gerald Schaefer writes:
> On Thu, 11 Feb 2016 21:09:42 +0200
> "Kirill A. Shutemov" wrote:
>
>> On Thu, Feb 11, 2016 at 07:22:23PM +0100, Gerald Schaefer wrote:
>> > Hi,
>> >
>> > Sebastian Ott reported random kernel crashes beginning with v4.5-rc1 and
>> > he also bisected this to commit
On Wed, Feb 10, 2016 at 10:09:28PM +0100, Colin Vidal wrote:
> Set constant operand on right of test, and refactor the code in a more
> compact and readable way.
Please don't do two different things in the same patch, break this up
into different patches.
thanks,
gregk -h
On 10/02/2016 10:51, Eric Anholt wrote:
> Martin Sperl writes:
>
>>> On 09.02.2016, at 01:32, Eric Anholt wrote:
>>>
>>> Hi Florian. Here's the first set of patches for bcm2835 for 4.6.
>>> We've got more DT patches that are going to happen for new boards,
>>> too, but they're still getting
Hi Linus,
Can you please pull the XFS commit from the tag below? It contains a
fix for a regression introduced in 4.5-rc1 by the new log recovery
CRC validation code. Thanks!
-Dave.
The following changes since commit 36f90b0a2ddd60823fe193a85e60ff1906c2a9b3:
Linux 4.5-rc2 (2016-01-31
On Thu, Feb 11, 2016 at 12:34:15PM -0700, Jason Gunthorpe wrote:
> On Tue, Feb 09, 2016 at 05:30:30AM +0200, Jarkko Sakkinen wrote:
> > If the initialization fails before tpm_chip_register(), put_device()
> > will be not called, which causes release callback not to be called.
> > This patch fixes
On Thu, Feb 11, 2016 at 01:05:01AM +0200, Michael S. Tsirkin wrote:
> Looks like the HPET spec at intel.com got moved.
> It isn't hard to find so drop the link, just mention
> the revision assumed.
>
> Suggested-by: Thomas Gleixner
> Signed-off-by: Michael S. Tsirkin
> ---
>
> Changes from v1:
On Wed, Feb 10, 2016 at 11:47:28AM +0100, Marek Szyprowski wrote:
> From: Tomeu Vizoso
>
> Allow implementations of the match() callback in struct bus_type to
> return errors and if it's -EPROBE_DEFER then queue the device for
> deferred probing.
>
> This is useful to buses such as AMBA in
On Wed, Feb 10, 2016 at 08:07:05PM +0100, Christian Brauner wrote:
> Simple patch that changes the return value of kernfs_name_locked and
> kernfs_name
> to size_t which alignes these functions with kernfs_path_len which also
> returns
> size_t.
>
> Patch was made against for-4.5 branch of
On Thu, Feb 11, 2016 at 06:14:35PM +0100, Jens Wiklander wrote:
> Initial patch for generic TEE subsystem.
> This subsystem provides:
> * Registration/un-registration of TEE drivers.
> * Shared memory between normal world and secure world.
> * Ioctl interface for interaction with user space.
> *
On Fri, Feb 12, 2016 at 7:42 AM, Florian Fainelli wrote:
> As is now common in a lot of organization having an internal code review
> process (be it through Gerritt or other tools), patches extracted from
> this review process and submitted to public mailing-lists will have
> pre-existing
On Thu, Feb 11, 2016 at 11:12:12AM -0700, Jeff Merkey wrote:
>
> That's good to know, they could be false positives, but it was kind of
> wierd behavior caused by that macro.
If it is true, it sounds more like a compiler bug to me. Any
statements a BUG() call are unreachable. If the compiler
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
arch/arm/kvm/arm.c
between commit:
6a26b548a2c4 ("arm64: kvm: deal with kernel symbols outside of linear
mapping")
from the arm64 tree and commit:
aa0bf2030bca ("ARM: KVM: Remove
As is now common in a lot of organization having an internal code review
process (be it through Gerritt or other tools), patches extracted from
this review process and submitted to public mailing-lists will have
pre-existing Reviewed-by tags. Add a note about why these tags exists,
and what a
On Fri, 2016-02-05 at 14:52 +0100, Linus Walleij wrote:
> On Thu, Feb 4, 2016 at 4:03 AM, Hongzhou Yang
> wrote:
> > On Wed, 2016-02-03 at 09:24 +0800, Biao Huang wrote:
> >> Since input-enable/disable and input-schmitt-enable/disable are
> >> workable when gpio direction is input, so add
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Acked-by: Maxime Ripard
Acked-by: Rob Herring
Acked-by: Lee Jones
Hi everyone,
This is v8 of the AXP223 PMIC series. All the driver bits are acked.
Lee, please merge the first 8 patches. Once they're in, Maxime can take
the DTS patches.
Changes since v7:
- Shortened commit message of "mfd: axp20x: Add missing copyright notice"
Changes since v6:
- Add
In axp20x_match_device(), match the of_device_id table bound to the
device driver instead of pointing to axp20x_of_match directly. This
will allow us to keep axp20x_match_device() unmodified when we expand
the axp20x driver into multiple ones covering different interface
types.
This fixes some leftover code style issues in the axp20x core.
Signed-off-by: Chen-Yu Tsai
Acked-by: Lee Jones
---
drivers/mfd/axp20x.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index 8e569bcfe3bc..3054ea4b95e8
The first argument passed to axp20x_match_device(), struct axp20x_dev *,
already contains a pointer to the device. By rearranging some code,
moving the assignment of the pointer before axp20x_match_device() is
called, we can eliminate the second parameter.
Suggested-by: Andy Shevchenko
On Thu, Feb 11, 2016 at 11:24 PM, Lee Jones wrote:
> On Mon, 25 Jan 2016, Lee Jones wrote:
>
>> On Wed, 13 Jan 2016, Chen-Yu Tsai wrote:
>>
>> > When the driver was merged, the original author did not include a proper
>> > copyright notice. This patch adds the notice, backdated to when the
>> >
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Reviewed-by: Mark Brown
---
drivers/regulator/axp20x-regulator.c |
A23/A33 Q8 tablets have an X-Powers AXP223 PMIC connected via RSB. Its
regulators provide power to various parts of the SoC and the board.
Also add lcd regulator supply for simplefb and update the existing
vmmc-supply for mmc0.
Signed-off-by: Chen-Yu Tsai
---
This board has a X-Powers AXP223 PMIC connected via RSB. Its regulators
provide power to various parts of the SoC and the board.
Also update the regulator supply phandles.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts | 76 +-
1 file
The axp20x driver assumes the device is i2c based. This is not the
case with later chips, which use a proprietary 2 wire serial bus
by Allwinner called "Reduced Serial Bus".
This patch follows the example of mfd/wm831x and splits it into
an interface independent core, and an i2c specific glue
Supply a backdated copyright notice.
Cc: Carlo Caione
Signed-off-by: Chen-Yu Tsai
Acked-by: Carlo Caione
Acked-by: Lee Jones
---
drivers/mfd/axp20x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index 3e186f2dcac3..cec51e689d1d 100644
---
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Acked-by: Lee Jones
---
drivers/mfd/Kconfig| 11 +++
On Thu, Feb 11, 2016 at 6:50 PM, Frank Rowand wrote:
> On 2/2/2016 11:02 AM, Frank Rowand wrote:
>> From: Frank Rowand
>>
>> If kernel config options are not properly set, "make scripts" will not
>> compile dtc. Update the unable to find dtc error message to check
>> the kernel config and give
On Fri, Feb 12, 2016 at 2:02 AM, Doug Smythies wrote:
> On 2016.02.11 15:28 Rafael J. Wysocki wrote:
>> On 2106.02.11 14:50 Doug Smythies wrote:
>
>>> What I do have from my 2 hour idle tests is the of total number of passes
>>> through
>>> the intel_pstate driver:
>>>
>>> Control sample: Kernel
On Thu, Feb 11, 2016 at 3:47 PM, Andy Lutomirski wrote:
> On Thu, Feb 11, 2016 at 11:27 AM, Borislav Petkov wrote:
>> Hey Andy,
>>
>> can you make any sense of this:
>>
>> [ 90.573923] [ cut here ]
>> [ 90.574977] WARNING: CPU: 0 PID: 3031 at
>>
On 2016.02.11 15:28 Rafael J. Wysocki wrote:
> On 2106.02.11 14:50 Doug Smythies wrote:
>> What I do have from my 2 hour idle tests is the of total number of passes
>> through
>> the intel_pstate driver:
>>
>> Control sample: Kernel 4.3-rc3: 37949 passes.
>> Kernel 4.3-rc3 + rjw 3 patch set v5:
On Thu, Feb 11, 2016 at 11:49 AM, Borislav Petkov wrote:
> On Mon, Jan 25, 2016 at 01:34:14PM -0800, Andy Lutomirski wrote:
>
>> + * with a flat 32-bit selector.
How about:
Sigreturn restores SS as follows:
if (saved SS is valid || UC_STRICT_RESTORE_SS is set || saved CS is not 64-bit)
new SS
Daniel Stone collabora.com> writes:
>
> Fixes: ffc30b74fd6d01588bd3fdebc3b1acc0857e6fc8
> Signed-off-by: Daniel Stone collabora.com>
Tested-by: Akshay Bhat
Tested on imx6 processor based board where re-probe was broken after a
probe deferral.
On 2/2/2016 11:02 AM, Frank Rowand wrote:
> From: Frank Rowand
>
> If kernel config options are not properly set, "make scripts" will not
> compile dtc. Update the unable to find dtc error message to check
> the kernel config and give better advice on how to create dtc.
>
> Reword another
On Thu, Feb 11, 2016 at 11:53 AM, Borislav Petkov wrote:
> On Mon, Jan 25, 2016 at 01:34:15PM -0800, Andy Lutomirski wrote:
>> This tests the two ABI-preserving cases that DOSEMU cares about, and
>> it also explicitly tests the new UC_SIGCONTEXT_SS and
>> UC_STRICT_RESTORE_SS flags.
>>
>>
On Fri, 12 Feb 2016 08:27:01 +0800
kbuild test robot wrote:
> Hi Sebastian,
>
> [auto build test ERROR on tip/sched/core]
> [also build test ERROR on v4.5-rc3 next-20160211]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving the syst
> Actually that is a 4.2 kernel according to the dmesg in the bug tracker.
It's both. I had reproduced on 4.4.
> The oops is a genuine driver bug probably unearthed by the irq issue. That
> should be reported seperately to the megasas folks.
Thanks, I sent an email to their list.
> - whether
On 12/15, Georgi Djakov wrote:
> diff --git a/drivers/clk/qcom/clk-rpm.c b/drivers/clk/qcom/clk-rpm.c
> new file mode 100644
> index ..7b0e85eefe70
> --- /dev/null
> +++ b/drivers/clk/qcom/clk-rpm.c
> @@ -0,0 +1,290 @@
> +
> +static int clk_rpm_prepare(struct clk_hw *hw)
> +{
> +
On 12/15, Georgi Djakov wrote:
>
> .../devicetree/bindings/clock/qcom,rpmcc.txt | 37 ++
> drivers/clk/qcom/Kconfig | 29 ++
> drivers/clk/qcom/Makefile |2 +
> drivers/clk/qcom/clk-rpm.c | 290
On Thu, Feb 11, 2016 at 05:22:10PM -0500, Tejun Heo wrote:
> > +/**
> > + * struct bfq_data - per device data structure.
> > + * @queue: request queue for the managed device.
> > + * @sched_data: root @bfq_sched_data for the device.
> > + * @busy_queues: number of bfq_queues containing requests
On 12/01, Rajendra Nayak wrote:
> Add all data for the GDSCs which are part of msm8996 GCC block
>
> Signed-off-by: Rajendra Nayak
> ---
Forgot to mention that I left out the dtsi change here too.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation
On 12/01, Rajendra Nayak wrote:
> With gdsc driver capable of handling hierarchical power domains,
> specify oxili_gdsc as parent of oxilicx_gdsc.
>
> Remove all direct calls to genpd from the mmcc clock driver. The
> adding and removing of subdomains is now handled from within
> the gdsc driver.
On 12/01, Rajendra Nayak wrote:
> Add all gdsc data which are part of mmcc on msm8996 family
>
> Signed-off-by: Rajendra Nayak
> ---
Applied to clk-next, but I dropped dtsi changes and squashed in
this patch
---8<---
diff --git a/drivers/clk/qcom/mmcc-msm8996.c
On 12/01, Rajendra Nayak wrote:
> Add all data for the GDSCs which are part of msm8996 GCC block
>
> Signed-off-by: Rajendra Nayak
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 2016-02-02 17:06, Stefan Agner wrote:
> Using flat regmap cache instead of RB-tree to avoid the following
> lockdep warning on driver load:
> [0.697285] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2755
> lockdep_trace_alloc+0x15c/0x160()
> [0.697449]
On 12/01, Rajendra Nayak wrote:
> Some qcom SoCs' can have hierarchical power domains. Let the gdsc structs
> specify the parents (if any) and the driver add genpd subdomains for them.
>
> Signed-off-by: Rajendra Nayak
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member
On 12/01, Rajendra Nayak wrote:
> Some gdsc power domains can have a gds_hw_controller block inside
> to help ensure all slave devices within the power domain are idle
> before the gdsc is actually switched off.
> This is mainly useful in power domains which host a MMU, in which
> case its
On 12/01, Rajendra Nayak wrote:
> Some gdscs might be controlled via voting registers and might not
> really disable when the kernel intends to disable them (due to other
> votes keeping them enabled)
> Mark these gdscs with a flag for we do not check/wait on a disable
> status for these gdscs
Hi Sebastian,
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.5-rc3 next-20160211]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Sebastian-Andrzej-Siewior/ftrace-move
From: Suravee Suthikulpanit
This is a fix-up patch based on the review comment from
Arnd regarding:
* fix ccn504 address in the node name
* remove kcs interrupt-name
Signed-off-by: Brijesh Singh
Signed-off-by: Suravee Suthikulpanit
Cc: Arnd Bergmann
---
Hi Olof,
Here are the
1 - 100 of 1734 matches
Mail list logo
