On Mon, Feb 15, 2016 at 6:01 PM, Clemens Gruber
wrote:
> +static int marvell_config_init(struct phy_device *phydev)
> +{
> + int err;
> +
> + /* Set registers from marvell,reg-init DT property */
> + err = marvell_of_reg_init(phydev);
> + if
On Mon 15-02-16 13:21:25, Tejun Heo wrote:
> Hello, Michal.
>
> On Mon, Feb 15, 2016 at 06:33:46PM +0100, Michal Hocko wrote:
> > On Wed 10-02-16 10:55:03, Tejun Heo wrote:
> > [...]
> > > --- a/kernel/workqueue.c
> > > +++ b/kernel/workqueue.c
> > > @@ -570,6 +570,16 @@ static struct
On Mon, Feb 15, 2016 at 06:31:23PM +0800, Chen-Yu Tsai wrote:
> The X-Powers AXP809 PMIC has a similar set of regulators as the AXP221,
> though a few LDOs were removed, and a new switch output added. Like the
> AXP221, AXP809 also has DC1SW and DC5LDO, which are internally chained
> to DCDC1 and
The DMA chip has a fixed number of requestor lines used for flow
control. This number is platform dependent. The pxa_dma dma driver will
use this value to activate or not the flow control.
There won't be any impact on mmp_pdma driver.
Signed-off-by: Robert Jarzmik
---
For pxa based platforms, the number of requestor lines should be
specified, so that the driver can check if the flow control should be
activated (when a requestor line is asked for) or not.
Signed-off-by: Robert Jarzmik
---
Since v1: rename of property to #dma-requests
Declare the number of DMA requestor lines per platform :
- for pxa25x: 40 requestor lines
- for pxa27x: 75 requestor lines
- for pxa3xx: 100 requestor lines
This information will be used to activate the DMA flow control or not.
Signed-off-by: Robert Jarzmik
---
Since
The current number of requestor lines is limited to 31. This was an
error of a previous commit, as this number is platform dependent, and is
actually :
- for pxa25x: 40 requestor lines
- for pxa27x: 75 requestor lines
- for pxa3xx: 100 requestor lines
The previous testing did not reveal the
2016-02-12 16:42+0100, Vitaly Kuznetsov:
> wait_for_completion() may sleep, it enables interrupts and this
> is something we really want to avoid on crashes because interrupt
> handlers can cause other crashes. Switch to the recently introduced
> vmbus_wait_for_unload() doing busy wait instead.
On Mon, Feb 15, 2016 at 06:31:29PM +, Sudeep Holla wrote:
> Understood. I knew lkml.org is broken if we tried very old links but
> expected to work at-least for couple of month old patches. Anyways
> hopefully [1] still works.
It's not old links in particular AFAICT, just general
2016-02-12 16:42+0100, Vitaly Kuznetsov:
> We have 3 functions dealing with messages and they all implement
> the same logic to finalize reads, move it to vmbus_signal_eom().
>
> Suggested-by: Radim Krcmar
Reviewed-by: Radim Krčmář
From: Zubair Lutfullah Kakakhel
To compile for little-endian systems, you need to pass -EL to CC and LD.
EXTRA_CFLAGS works to pass -EL to CC.
Add EXTRA_LDFLAGS to pass -EL to LD.
Signed-off-by: Zubair Lutfullah Kakakhel
Cc: Peter
From: Taeung Song
To print syscall names, the audit-libs-python package is required.. If
not installed, it prints this error string:
# perf script syscall-counts
Install the audit-libs-python package to get syscall names.
But the package name is different in
From: Wang Nan
We were just freeing them, better unlink and init its nodes to catch
bugs faster if we keep dangling references to them.
Signed-off-by: Wang Nan
Acked-by: Jiri Olsa
Cc: Alexei Starovoitov
Cc: He Kuang
From: Arnaldo Carvalho de Melo
We were doing column alignment in the format function for each cell,
returning a string padded with spaces so that when the next column is
printed the cursor is at its column alignment.
This ends up needlessly printing trailing spaces, do it at
Hello, Michal.
On Mon, Feb 15, 2016 at 09:54:38PM +0100, Michal Hocko wrote:
> I am not sure I understand. Does that mean that a node with no memory
> would have its WQ specific pool? I might be missing something but I
Yeah, I think it should.
> thought that cpu_to_node will return NUMA_NO_NODE
From: Taeung Song
The '--system' option means $(sysconfdir)/perfconfig and '--user' means
$HOME/.perfconfig. If none is used, both system and user config file are
read. E.g.:
# perf config [] [options]
With an specific config file:
# perf config --user |
From: Wang Nan
Fixing a leak, since code calling parse_events__free_terms() expect it
to free the list_head too.
Signed-off-by: Wang Nan
Acked-by: Jiri Olsa
Cc: Alexei Starovoitov
Cc: He Kuang
From: Wang Nan
Before this patch, if a sample is triggered inside a module not in
/lib/modules/`uname -r`/, even if the module is in buildid-cache, 'perf
report' will still be unable to find the correct symbol. For example:
# rm -rf ~/.debug/
# perf buildid-cache -a
From: Arnaldo Carvalho de Melo
fixing the following problems, for instance, on RHEL6.7:
CC /tmp/build/perf/tests/bp_signal.o
cc1: warnings being treated as errors
tests/bp_signal.c: In function ‘__event’:
tests/bp_signal.c:106: error: declaration of ‘signal’
From: Wang Nan
A new patch in libbabeltrace [1] reveals a object leak problem in
'perf data' CTF support: perf code never releases the event_class
which is allocated in add_event() and stored in evsel's private field.
If libbabeltrace has the above patch applied, leaking
On Mon, Feb 15, 2016 at 06:12:01PM +0100, Uwe Kleine-König wrote:
> Hello Greg,
>
> On Mon, Feb 15, 2016 at 08:49:37AM -0800, Greg Kroah-Hartman wrote:
> > On Mon, Feb 15, 2016 at 05:27:53PM +0100, Uwe Kleine-König wrote:
> > > Greg, can you drop this patch, or do you need a proper changelog for
From: Arnaldo Carvalho de Melo
To follow convention used in other tools/perf/ areas. Also remove the
need to check if it is NULL before calling the destructor, again, to
follow convention that goes back to free().
Cc: Alexei Starovoitov
Cc: He Kuang
The patch
regulator: vexpress: rename vexpress regulator implementation
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
From: Arnaldo Carvalho de Melo
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-4j67nvlfwbnkg85b969ew...@git.kernel.org
Signed-off-by: Arnaldo
From: Arnaldo Carvalho de Melo
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit a7636d9ecfa3ab7800a7c04c1f89378229eff609:
kprobes: Optimize hot path by using percpu counter to collect 'nhit'
statistics (2016-02-09 11:08:58 +0100)
are
From: Arnaldo Carvalho de Melo
In these two cases, a 'perf test' entry and in the PMU code the
list_head is on the stack, so we can't use perf_event__free_terms()
(soon to be renamed to perf_event_terms__delete()), because it will
free the list_head as well.
Acked-by: Jiri Olsa
From: Arnaldo Carvalho de Melo
Purges 'struct parse_event_term' entries from a list_head.
Some users need this because they don't allocate space for the list
head, it maybe on the stack or embedded into some other struct.
Next patch will convert users that need just purging
2016-02-12 16:42+0100, Vitaly Kuznetsov:
> Message header is modified by the hypervisor and we read it in a loop,
> we need to prevent compilers from optimizing accesses. There are no such
> optimizations at this moment, this is just a future proof.
>
> Suggested-by: Radim Krcmar
On Mon, Feb 15, 2016 at 9:38 PM, Arnd Bergmann wrote:
> On Monday 15 February 2016 21:56:42 Viresh Kumar wrote:
>> We are currently required to do two checks for regulator pointer:
>> IS_ERR() and IS_NULL().
>>
>> And multiple instances are reported, about both of these not being
Hi Caesar,
Am Montag, 15. Februar 2016, 11:30:58 schrieb Caesar Wang:
> This patch fixes the incorrect Over-temperature protection pin.
> since the rk3368 io list said the otp pin is gpio0a3.
>
> Anyway, that should be fixed in here.
>
> Signed-off-by: Caesar Wang
applied
On Fri, Feb 12, 2016 at 05:22:21PM -0600, Serge E. Hallyn wrote:
> On Fri, Feb 12, 2016 at 11:09:06AM -0500, Tejun Heo wrote:
> > Hello,
> >
> > On Fri, Feb 12, 2016 at 12:18:28AM +0100, Alban Crequy wrote:
> > > I just noticed commit c38c4597e4bf ("netfilter: implement xt_cgroup
> > > cgroup2
On Mon, Feb 15, 2016 at 04:17:05PM -0500, Tejun Heo wrote:
> I'm getting the following on top of the current for-4.6. Can you
> please look into it?
>
> [kernel/cgroup.c:219:13: error: ‘cgroupns_operations’ undeclared here (not in
> a function)
> .ns.ops = _operations,
>^
Currently, workaround for broken WD drives is applied always, slowing
down all drives. And it has a bug - it's not applied after resume.
Apply the workaround only if the error really appears
(SErr == 0x1000500). This allows unaffected drives to run at full speed
(provided that no affected drive
Am Montag, 15. Februar 2016, 11:33:57 schrieb Shawn Lin:
> Check return value of syscon_node_to_regmap for
> rockchip_pm_domain_probe. If err value is returned, probe
> procedure should abort.
>
> Signed-off-by: Shawn Lin
applied to my armsoc/drivers branch for 4.6
The first substantial thing that ser_gigaset's open() operation does, is
calling gigaset_initcs(). That function is well behaved: if it fails it
cleans up after itself and returns NULL. So if we receive a NULL here we
might as well bail out directly. (Note that both the bas_gigaset driver
and the
Hi Dmitry,
I've cobbled together a two part series to fix the leak syzkaller uncovered in
ser_gigaset. I'd really appreciate it if you'd unleash syzkaller on this small
series one more time. Just to be sure that this also fixes the leak on your box
and that it doesn't introduce neww horrors.
The purpose of gigaset_device_release() is to kfree() the struct
ser_cardstate that contains our struct device. This is done via a bit of
a detour. First we make our struct device's driver_data point to the
container of our struct ser_cardstate (which is a struct cardstate). In
; >> >https://kernelci.org/boot/all/job/next/kernel/next-20160215/
> >> >
> >> >The SMP ones seem to fail with some regulator issues?
> >> >
> >>
> >> There is another problem, introduced with 6a0712f6f199e ("PM / OPP: Add
Am Montag, 15. Februar 2016, 11:33:15 schrieb Shawn Lin:
> Add clk_disable_unprepare to handle cpuclk->alt_parent if
> rockchip_clk_register_cpuclk fails.
>
> Signed-off-by: Shawn Lin
applied to my clk branch for 4.6
Am Montag, 15. Februar 2016, 11:33:25 schrieb Shawn Lin:
> rockchip_clk_get_grf pass on return value from
> syscon_regmap_lookup_by_phandle, so we check grf to
> make sure whether to do the following things or not.
>
> Signed-off-by: Shawn Lin
applied to my clk-branch
From: Rafael J. Wysocki
Introduce a mechanism by which parts of the cpufreq subsystem
("setpolicy" drivers or the core) can register callbacks to be
executed from cpufreq_update_util() which is invoked by the
scheduler's update_load_avg() on CPU utilization changes.
On Mon, Feb 8, 2016 at 3:37 PM, Krzysztof Adamski
wrote:
> Default function of a pin in sunxi SoCs is "disabled". By default gpios
> exported by sysfs are set as input and indeed, when reading "direction"
> file you will get "in". The "value" pin won't return proper
On 02/12/2016 03:23 PM, Peter Zijlstra wrote:
On Fri, Feb 12, 2016 at 12:32:12PM -0500, Waiman Long wrote:
This patch adds a new waiter parameter to the mutex_optimistic_spin()
function to prepare it to be used by a waiter-spinner that doesn't
need to go into the OSQ as there can only be one
On Mon, Feb 15, 2016 at 12:26 PM, Kirill A. Shutemov
wrote:
> On Mon, Feb 15, 2016 at 03:32:55AM +0200, Grazvydas Ignotas wrote:
>> Hi,
>>
>> since remap_file_pages() rework the following simple program fails.
>> I haven't actually bisected this, only know it
Quoting Stephen Boyd (2016-02-08 17:45:29)
> Now that we've converted the only caller over to another clkdev
> API, remove this one.
>
> Cc: Andy Shevchenko
> Cc: Russell King
> Signed-off-by: Stephen Boyd
Looks
Quoting Stephen Boyd (2016-02-08 17:45:30)
> We've largely split the clk consumer and provider APIs along
> struct clk and struct clk_hw, but clk_register() still returns a
> struct clk pointer for each struct clk_hw that's registered.
> Eventually we'd like to only allocate struct clks when
Quoting Stephen Boyd (2016-02-08 17:45:28)
> Convert this driver to use clkdev_create() instead of
> clk_register_clkdevs(). The latter API is only used by this driver,
> although this driver only allocates one clk to add anyway.
> Furthermore, this driver allocates the clk_lookup structure with
>
On Tue, Feb 16, 2016 at 12:08:34AM +0200, Grazvydas Ignotas wrote:
> On Mon, Feb 15, 2016 at 12:26 PM, Kirill A. Shutemov
> wrote:
> > On Mon, Feb 15, 2016 at 03:32:55AM +0200, Grazvydas Ignotas wrote:
> >> Hi,
> >>
> >> since remap_file_pages() rework the
On Mon, Feb 15, 2016 at 03:04:08PM +0100, Torsten Duwe wrote:
> If you use "-pg -mprofile-kernel", gcc seems to forget that, and omits the TOC
> load, for a similar assembler calling sequence.
>
> Looking at the code I can _understand_ why this is so, but my GCC knowledge
> is not that deep that
On 15 February 2016 at 17:05, Guenter Roeck <li...@roeck-us.net> wrote:
> I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace
> timers with utilization update callbacks' with next-20160215. An example
> crash log and bisect results are attached below.
>
&g
Hi Fabio,
On Mon, Feb 15, 2016 at 06:54:29PM -0200, Fabio Estevam wrote:
> On Mon, Feb 15, 2016 at 6:01 PM, Clemens Gruber
> wrote:
>
> > +static int marvell_config_init(struct phy_device *phydev)
> > +{
> > + int err;
> > +
> > + /* Set registers from
From: Colin Ian King
device_decode is now no longer used, so we may as well remove it.
Fixes gcc 6 warning:
drivers/acpi/acpi_video.c:221:19: warning: ‘device_decode’ defined
but not used [-Wunused-const-variable]
static const char device_decode[][30] = {
Am Montag, 15. Februar 2016, 11:33:41 schrieb Shawn Lin:
> Avoid return NULL if rockchip_clk_register_mmc fails, otherwise
> rockchip_clk_register_branches print "unknown clock type". The acutal
> case is that it's a known clock type but we fail to regiser it, which
> may makes user confuse the
Am Montag, 15. Februar 2016, 11:33:33 schrieb Shawn Lin:
> Avoid return NULL if rockchip_clk_register_inverter fails, otherwise
> rockchip_clk_register_branches print "unknown clock type". The acutal
> case is that it's a known clock type but we fail to regiser it, which
> may makes user confuse
Am Montag, 15. Februar 2016, 11:33:50 schrieb Shawn Lin:
> Fix the issue reported by checkpatch:
> ERROR: space prohibited before that ',' (ctx:WxW)
> + writel(clksel->val , cpuclk->reg_base + clksel->reg);
>
> Signed-off-by: Shawn Lin
applied to my
For the Marvell 88E1510, marvell_of_reg_init was called too late, in the
config_aneg function.
Since commit 113c74d83eef ("net: phy: turn carrier off on phy attach"),
this lead to the link not coming up at boot anymore, due to the phy
state machine being stuck at waiting for interrupts (off by
On Wed, Feb 10, 2016 at 2:23 PM, 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:
>
> - Using ARRAY_SIZE instead of a custom macro to calculate the size of the
>
From: Colin Ian King
Ever since commit 04ed3e741d0f133e02bed7fa5c98edba128f90e7
("net: change netdev->features to u32") the format string
fmt_long_hex has not been used, so we may as well remove it.
Signed-off-by: Colin Ian King
---
On 02/07/2016 02:05 PM, Darren Hart wrote:
> On Tue, Feb 02, 2016 at 03:38:51PM -0600, Mario Limonciello wrote:
>> I've got some extensions for the alienware-wmi driver that have
>> been introduced for a few new platforms and can be controlled via the WMI
>> interface.
> Thanks Mario, and
On Mon, Feb 15, 2016 at 07:32:02PM +, Jon Medhurst (Tixy) wrote:
> It seems to me that for other error cases (that don't result in deletion
> of objects) we would want to leave the references between components and
> masters intact once they have been created.
Indeed we do - because we want
On 15.02.2016 22:38, Javier Martinez Canillas wrote:
>>
>> In some of the DTSI this was under "soc" node, not at top-level.
>> Unfortunately we do not have consistency here - some DTSI have "soc",
>
> Yes, I noticed this but as you said not all DTSI have a soc node
> and that's why I made it top
On Mon, Feb 15, 2016 at 10:19:54AM -0800, Daniel Walker wrote:
> On 02/14/2016 01:18 PM, Dave Chinner wrote:
> >On Fri, Feb 12, 2016 at 12:14:39PM -0800, Daniel Walker wrote:
> >>From: Khalid Mughal
> >>
> >>Currently there is no way to figure out the droppable pagecache size
>
On Thu, Feb 11, 2016 at 10:20 AM, Lee Jones wrote:
> Very well, applied.
>
> I also know Linus W likes dicing with death, so this is going into my
> main branch. As this is a new driver, it shouldn't be an issue;
Haha as long as there are no collisions in Makefile or
On Thu, Feb 11, 2016 at 12:56 PM, Laxman Dewangan wrote:
> Maxim Semiconductor's PMIC MAX77620/MAX20024 has 8 GPIO pins
> which act as GPIO as well as special function mode.
>
> Add DT binding document to support these pins in GPIO
> mode via GPIO framework.
>
>
On Thu, Feb 11, 2016 at 12:56 PM, Laxman Dewangan wrote:
> Maxim Semiconductor's PMIC MAX77620/MAX20024 has 8 GPIO pins
> which act as GPIO as well as special function mode.
>
> Add DT binding document to configure pins in function mode as
> well as pin configuration
On Thu, Feb 11, 2016 at 12:56 PM, Laxman Dewangan wrote:
> MAXIM Semiconductor's PMIC, MAX77620/MAX20024 has 8 GPIO
> pins. It also supports interrupts from these pins.
>
> Add GPIO driver for these pins to control via GPIO APIs.
>
> Signed-off-by: Laxman Dewangan
From: Borislav Petkov
When gcc cannot do constant folding for this macro, it falls back to
cpu_has(). But static_cpu_has() is optimal and it works at all times
now. So use it and speedup the fallback case.
Before we had this:
mov0x99d674(%rip),%rdx# 81b0d9f4
On 02/15/2016 02:29 PM, Peter Maydell wrote:
On 15 February 2016 at 17:05, Guenter Roeck <li...@roeck-us.net> wrote:
I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace
timers with utilization update callbacks' with next-20160215. An example
crash log and bisect r
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
>> On 12.02.2016 13:30, Javier Martinez Canillas wrote:
>>> The driver's init and exit function don't do anything besides adding and
>>> deleting the I2C driver so the
On Mon, Feb 15, 2016 at 07:37:02PM +0100, Gerald Schaefer wrote:
> On Mon, 15 Feb 2016 13:31:59 +0200
> "Kirill A. Shutemov" wrote:
>
> > On Sat, Feb 13, 2016 at 12:58:31PM +0100, Sebastian Ott wrote:
> > >
> > > On Sat, 13 Feb 2016, Kirill A. Shutemov wrote:
> > > > Could
On 15.02.2016 23:11, Javier Martinez Canillas wrote:
> The S3C binding doc says that the RTC and RTC source clocks are required
> but the S3C driver supports different HW IP and only the s3c6410 needs a
> source clock.
>
> Fix the binding explaining that the source clock is only needed for the
>
On Thu, Feb 11, 2016 at 4:12 PM, Maxime Ripard
wrote:
> On Thu, Feb 11, 2016 at 02:47:57PM +0100, Linus Walleij wrote:
>> Can you guys supply a MAINTAINERS entry for the sunxi
>> stuff?
>
> We have one, and Chen-Yu is listed as co-maintainer:
>
Am Montag, 15. Februar 2016, 15:33:25 schrieb Caesar Wang:
> Hello Eduardo, Heiko, Michael & Stephen:
>
> This series pacthes to support the rk3228 SoCs thermal.
>
> They have the following patches to work on rk3228 SoCs.
>
> 1a6f334 clk: rockchip: add id of the tsadc clock found on rk3228
On Sun, Feb 14, 2016 at 11:59:00PM +0100, Jiri Kosina wrote:
> On Wed, 10 Feb 2016, Jiri Kosina wrote:
>
> > > > Remove the livepatch module notifier in favor of directly enabling and
> > > > disabling patches to modules in the module loader. Hard-coding the
> > > > function calls ensures that
On Mon, 15 Feb 2016, Josh Poimboeuf wrote:
> So I think the commit causing the regression is 5156dca34a3e, which
> occurred in the 4.5 cycle, *not* in 4.4.
Agreed, by "4.4 regresion" I mean "regression compared to 4.4"; i.e.
regression that will become real issue once 4.5 is released.
> Also
On 02/15/2016 03:05 PM, Dave Chinner wrote:
On Mon, Feb 15, 2016 at 10:19:54AM -0800, Daniel Walker wrote:
On 02/14/2016 01:18 PM, Dave Chinner wrote:
On Fri, Feb 12, 2016 at 12:14:39PM -0800, Daniel Walker wrote:
From: Khalid Mughal
Currently there is no way to figure
On 02/12/2016 05:02 PM, Davidlohr Bueso wrote:
On Fri, 12 Feb 2016, Waiman Long wrote:
This patch adds a new waiter parameter to the mutex_optimistic_spin()
function to prepare it to be used by a waiter-spinner that doesn't
need to go into the OSQ as there can only be one waiter-spinner which
Signed-off-by: Sergio Prado
---
As requested by Rob Herring on patch
https://patchwork.ozlabs.org/patch/580862/
---
Documentation/devicetree/bindings/net/macb.txt | 2 +-
drivers/net/ethernet/cadence/macb.c| 2 +-
2 files changed, 2 insertions(+), 2
Hi Jon,
[auto build test WARNING on next-20160215]
url:
https://github.com/0day-ci/linux/commits/Jon-Hunter/PM-OPP-Fix-NULL-pointer-dereference-crash-when-setting-the-OPP/20160215-220238
config: x86_64-randconfig-s0-02160737 (attached as .config)
reproduce:
# save the attached
Please keep me in CC.
I've been seeing the following on some of my VMs ran under qemu. The VMs do
not have internet connectivity. This happened when some files were accessed
via NFS to another VM (NOTE: Both VMs throw these warnings. Both VMs are
running the exact same kernel). The host is
On Mon, Feb 15, 2016 at 5:41 PM, Sinan Kaya wrote:
> A crash has been observed when assigning penalty on x86 systems.
>
> It looks like this problem happens on x86 platforms with IOAPIC and an SCI
> interrupt override in the ACPI table with interrupt number greater than
>
Hi
Ping, it seems inno hdmi driver is ready, So I'd like to merge it into
drm/rockchip if there is no doubt these days.
Thanks.
Mark
On 2016年01月29日 14:42, Yakir Yang wrote:
Here are a brief introduction to Innosilicon HDMI IP:
- Support HDMI 1.4a, HDCP 1.2 and DVI 1.0 standard compliant
On Mon, Feb 15, 2016 at 03:52:31PM -0800, Daniel Walker wrote:
> >>We need it to determine accurately what the free memory in the
> >>system is. If you know where we can get this information already
> >>please tell, we aren't aware of it. For instance /proc/meminfo isn't
> >>accurate enough.
>
>
On Mon, Feb 15, 2016 at 11:07:41AM -0500, Steven Rostedt wrote:
> On Mon, 15 Feb 2016 12:04:50 +0900
> js1...@gmail.com wrote:
>
> > From: Joonsoo Kim
> >
> > CMA allocation should be guaranteed to succeed by definition, but,
> > unfortunately, it would be failed
On 15-02-16, 22:13, Rafael J. Wysocki wrote:
> That should be something like -ENXIO IMO.
Thanks for modifying and applying the patch :)
--
viresh
On 15-02-16, 11:34, Guenter Roeck wrote:
> omap3 overo boots crash with
>
> Unable to handle kernel NULL pointer dereference at virtual address 0030
> pgd = c0204000
> [0030] *pgd=
> Internal error: Oops: 17 [#1] SMP ARM
> ...
> [] (regulator_set_voltage) from []
+++ Jiri Kosina [16/02/16 00:42 +0100]:
On Mon, 15 Feb 2016, Josh Poimboeuf wrote:
So I think the commit causing the regression is 5156dca34a3e, which
occurred in the 4.5 cycle, *not* in 4.4.
Agreed, by "4.4 regresion" I mean "regression compared to 4.4"; i.e.
regression that will become
On Sun, Feb 14, 2016 at 10:05:22PM -0800, Paul E. McKenney wrote:
> On Sun, Feb 14, 2016 at 09:50:18AM +0300, Denis Kirjanov wrote:
> > Tracepoints use RCU for protection and they must not be called on
> > offline CPUS. So make this tracepoint conditional.
>
> Good catch! Queued for review and
On Tuesday, February 16, 2016 06:17:16 AM Viresh Kumar wrote:
> On 15-02-16, 22:13, Rafael J. Wysocki wrote:
> > That should be something like -ENXIO IMO.
>
> Thanks for modifying and applying the patch :)
Well, you're welcome.
I wanted it to be fixed in the tomorrow's linux-next so people can
On Friday, January 15, 2016 11:04:13 AM Jacob Pan wrote:
> Reduce remote CPU calls for MSR access by combining read
> modify write into one function. Also optimize search for active CPU on
> package such that remote CPU is not used if the current CPU is already
> on the target package.
>
>
On Mon, 2016-02-15 at 18:49 -0500, Oleg Drokin wrote:
> Hello!
>
>
> As I am going over Lustre to clean up the code style, I noticed this bunch
> below.
>
> Those all are function definitions, though I guess it might have been
> foiled by
> return type on the previous line?
> Now
Cc'ing Mark as well.
On 15-02-16, 21:38, Arnd Bergmann wrote:
> There is usually something else wrong if you have to check for both.
> Why exactly do you need to check for both IS_ERR and NULL?
And here is the reasoning behind it:
- It is normally said that 'NULL' is a valid clk. The same is
On Thu, Feb 04, 2016 at 12:45:12AM +0800, Boqun Feng wrote:
> The variables protected by an RCU read-side critical section are
> sometimes hard to figure out, especially when the critical section is
> long or has some function calls in it. However, figuring out which
> variable a RCU read-side
On 09/02/2016 at 22:56:29 +0530, Laxman Dewangan wrote :
> Based on discussion on patch series of MAX77620 when adding separate
> driver for max77620 RTC, it is discussed to reuse the max77686 driver
> for all CHips MAX77802, MAX77686 and MAX77620. For this, the rtc-max77686
> need to make as IP
On 15-02-16, 19:41, Rafael J. Wysocki wrote:
> On Mon, Feb 15, 2016 at 6:05 PM, Guenter Roeck wrote:
> > [1.34] [] (__cpufreq_driver_target) from []
> > (dbs_check_cpu+0x1ac/0x1e8)
> > [1.34] [] (dbs_check_cpu) from []
> > (cpufreq_governor_dbs+0x1fc/0x608)
>
On Tue, 16 Feb 2016 09:47:20 +0900
Joonsoo Kim wrote:
> > They return true when CONFIG_TRACEPOINTS is configured in and the
> > tracepoint is enabled, and false otherwise.
>
> This implementation is what you proposed before. Please refer below
> link and source.
>
>
On Wednesday, January 20, 2016 08:29:26 PM Aleksey Makarov wrote:
> Factor out the code that finds the first physical device
> of a given ACPI device. It is used in several places.
>
> Reviewed-by: Andy Shevchenko
I guess the above doesn't apply any more, does it?
>
On Wednesday, January 20, 2016 05:12:18 PM Andy Shevchenko wrote:
> On Wed, Jan 20, 2016 at 4:29 PM, Aleksey Makarov
> wrote:
> > Factor out the code that finds the first physical device
> > of a given ACPI device. It is used in several places.
> >
> > Reviewed-by:
Some quite excellent fixes from Joe Perches that belong
back in the original. Submitting to Joe for inclusion. Joe
was the original author of these fixes that save a lot of time
rewriting code. Thanks Joe.
Signed-off-by: Jeffrey Merkey
---
scripts/checkpatch.pl | 23
On Wednesday, January 20, 2016 08:29:27 PM Aleksey Makarov wrote:
> From: Graeme Gregory
>
> On ARM64 some devices use the AMBA device and not the platform bus for
> probing so add support for this. Uses a dummy clock for apb_pclk as ACPI
> does not have a suitable
601 - 700 of 1850 matches
Mail list logo