Hi Kevin,
Thanks for your comments!
On Thu, Dec 18, 2014 at 10:29 PM, Kevin Hilman wrote:
>> However, if PM domains are active, drivers must be runtime PM-aware for the
>> gpd_dev_ops.start() method to be called in the first place (perhaps this is
>> just
>> one bug that's easy to fix --- the d
On Tue, 2014-04-15 at 10:56 -0700, Stephen Boyd wrote:
> On 04/04/14 11:45, Stephen Boyd wrote:
> > These patches add support for the multimedia GDSCs on the
> > apq8074 dragonboard. The first two patches (and potentially the last)
> > should go through Mike's tree and the DTS patch should go thro
On Wed, Dec 17, 2014 at 9:58 PM, Joe Perches wrote:
> It seems like early_printk can be configured into
> a few architectures but also appear not to be used.
>
> $ git grep -w "early_printk"
[...]
> arch/m68k/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK)+= early_printk.o
[...]
> These seem to
On Thu, Dec 18, 2014 at 10:04:09PM +0300, Cyrill Gorcunov wrote:
> case __NR_execveat:
>^
> arch/x86/ia32/audit.c:38:7: note: each undeclared identifier is reported only
> once for each function it appears in
> make[2]: *** [arch/x86/ia32/audit.o] Error 1
> make[1]: *** [arch/x86/ia32] E
Fri, Dec 19, 2014 at 01:35:10AM CET, tg...@suug.ch wrote:
>On 12/18/14 at 08:03am, John Fastabend wrote:
>> On 12/18/2014 07:30 AM, Varlese, Marco wrote:
>> Could you also document the attributes. I think they are mostly
>> clear but what is IFLA_SW_LOOPBACK. It will help later when we
>> try to re
On Fri, Dec 19, 2014 at 3:03 AM, Rafael J. Wysocki wrote:
> --- linux-pm.orig/arch/mips/configs/lemote2f_defconfig
> +++ linux-pm/arch/mips/configs/lemote2f_defconfig
> @@ -37,7 +37,7 @@ CONFIG_MIPS32_N32=y
> CONFIG_PM=y
^^^
> CONFIG_HIBERNATION=y
> CONFIG_PM_STD_PARTITION="/dev/hda3"
Thu, Dec 18, 2014 at 11:43:06PM CET, ronen.a...@intel.com wrote:
>
>
>>-Original Message-
>>From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
>>Behalf Of John Fastabend
>>Sent: Thursday, December 18, 2014 9:21 PM
>>To: Roopa Prabhu; Varlese, Marco
>>Cc: net...@vger
On Thu, 2014-12-18 at 15:43 -0800, Bjorn wrote:
> On Tue 16 Dec 16:54 PST 2014, Bryan Wu wrote:
>
> > On Mon, Dec 8, 2014 at 4:22 PM, Bjorn Andersson
>
> [..]
>
> > > diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
>
> [..]
>
> > > +config LEDS_PM8941_WLED
> > > + tristate "LED
tree: https://git.linaro.org/people/vireshk/linux cpufreq/stats/cleanups
head: f6439741b76da59257758838e8b24472831e850c
commit: 2194c3c381af6cbfe8ab4fda481e07a004446e30 [12/14] cpufreq: stats:
replace spinlock with mutex
reproduce:
# apt-get install sparse
git checkout 2194c3c381af6cbfe8ab
drivers/cpufreq/cpufreq_stats.c:19:1: sparse: symbol 'cpufreq_stats_lock' was
not declared. Should it be static?
Signed-off-by: Fengguang Wu
---
cpufreq_stats.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq_stats.c b/drivers/cpufreq/cpufreq_stats
Hi Alexandre,
Am Freitag 19 Dezember 2014, 00:13:10 schrieb Alexandre Belloni:
> From: Arnd Bergmann
>
> at91 will no longer export the mach/cpu.h and mach/hardware.h header files
> in the future, which would break building the atmel ac97c driver.
>
> Since the cpu_is_* check is only used to fi
On 19 December 2014 at 13:47, kbuild test robot wrote:
> tree: https://git.linaro.org/people/vireshk/linux cpufreq/stats/cleanups
> head: f6439741b76da59257758838e8b24472831e850c
> commit: 2194c3c381af6cbfe8ab4fda481e07a004446e30 [12/14] cpufreq: stats:
> replace spinlock with mutex
> reprodu
On 2014년 12월 19일 16:41, MyungJoo Ham wrote:
>>
>> Whenever battery status is changed, charger manager tries to trigger uevent
>> through private interface. This patch modifies it to use
>> power_supply_changed()
>> since it belongs to power supply subsystem.
>>
>> Signed-off-by: Jonghwa Lee
64KiB is allocated for qspi dtb partition which is not
sufficient, so updating the partition table size to 512KiB
for device tree partition.
This also aligns the QSPI partition definitions between
kernel and U-Boot.
Fixes: dc2dd5b8 ("ARM: dts: dra7: Add qspi device")
Signed-off-by: Mugunthan V N
Fri, Dec 19, 2014 at 12:48:28AM CET, ro...@cumulusnetworks.com wrote:
>On 12/18/14, 3:26 PM, Samudrala, Sridhar wrote:
>>
>>On 12/18/2014 3:07 PM, Roopa Prabhu wrote:
>>>On 12/18/14, 11:21 AM, John Fastabend wrote:
On 12/18/2014 10:14 AM, Roopa Prabhu wrote:
>On 12/18/14, 10:02 AM, Varlese,
Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com wrote:
>On 19 December 2014 at 05:18, Roopa Prabhu wrote:
>> On 12/18/14, 3:26 PM, Samudrala, Sridhar wrote:
>>>
>>>
>>> On 12/18/2014 3:07 PM, Roopa Prabhu wrote:
On 12/18/14, 11:21 AM, John Fastabend wrote:
>
> On 12/18/
On Tue, Dec 16, 2014 at 10:09:48AM +0800, Yuyang Du wrote:
>
> Sasha, it might be helpful to see this_load is from:
>
> this_load1: this_load = target_load(this_cpu, idx);
>
> or
>
> this_load2: this_load += effective_load(tg, this_cpu, -weight, -weight);
>
> It really does not seem to be this
On 2014년 12월 19일 16:52, MyungJoo Ham wrote:
>>
>> cm_notify_event() is introduced to get event associated with battery status
>> externally, but no one had been used. Moreover it makes charger manager
>> driver more complicated. This patch tries to drop the function and all data
>> related to
On 2014년 12월 19일 11:47, Jonghwa Lee wrote:
> After charger manager's initially introduced, it has kept its codes without
> any
> big change. However, the charger manager working operation isn't optimized and
> it also has unused codes and non-generic interface. This series tries to make
> charger
Hi all,
Please do not add any code destined for v3.20 to your linux-next included
trees/branches until after v3.19-rc1 is released.
There will only be intermittent releases of linux-next between now and
Jan 5.
Changes since 20141218:
The modules tree lost its build failure.
Non-merge commits (
On Thu, Dec 18, 2014 at 08:51:32PM +0100, Boris Brezillon wrote:
> Hi Thierry,
>
> On Thu, 18 Dec 2014 10:44:44 +0100
> Thierry Reding wrote:
>
> > On Thu, Dec 04, 2014 at 09:10:55AM -0700, Jim Davis wrote:
> > > Building with the attached random configuration file,
> > >
> > > ERROR: "ilog
On Thu, Dec 18, 2014 at 09:05:30PM +0100, Boris Brezillon wrote:
> The slow and system clock should never return a rate of zero, but this
> might happen if the clocks property defined in the DT is referencing the
> wrong clocks.
> Prevent any division by zero from happening by testing the clk_freq
Hi!
Just a minor nitpick, but...
On Thu, Dec 18, 2014 at 04:29:08PM -0600, at...@opensource.altera.com wrote:
> From: Alan Tull
>
> Add driver to fpga manager framework to allow configuration
> of FPGA in Altera SoCFPGA parts.
>
> Signed-off-by: Alan Tull
> Acked-by: Michal Simek
> ---
> v2:
Add 'polling_ms' sysfs node to change charger-manager's monitoring rate
in runtime. It can set only bigger than 2 jiffies (for 200 HZ system it
is 10 msecs.) as it's allowed for minimum poling rate in previous.
It resets poller and re-configure polling rate based on new input if next
polling time i
Add additional polling mode for sleep state to define different mode with
normal state. With this change, charger-manager can work differently in
normal state or sleep state. e.g, polling aways for normal and polling
only when charing for sleep. If there is no defined polling mode for
sleep state i
Don't submit the rx if the device is unplugged, linking down,
or stopped.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 59b70c5..b39b2e4 100644
--- a/drivers/net/usb/r8152.c
+
When charger-manager checks whether external power source is available,
it gets information from charger IC driver. However, it's not correct source,
charger IC doesn't have responsibilty to give cable connection status.
The charger-manager already gets cable information from EXTCON susbsystem,
so
Avoid r8152_submit_rx() from submitting rx during unexpected
moment. This could reduce the time of stopping rx.
For patch #1, the tp->speed should be updated early. Then,
the patch #2 could use it to check the current linking status.
Hayes Wang (2):
r8152: adjust set_carrier
r8152: check the
In cm_monitor() where charging management starts, it checks various charging
condition sequentially to decide next charging operation. However, as it
follows sequential process, cascaded IF statements, it does some duplicated
jobs which is already done in previous stage. It results delay in decisio
Update the tp->speed at the beginning of the function. Then,
the other fucntion could use it for checking linking status.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/us
It drops the way of using power_supply interface to reference battery's
temperature. Then it tries to use thermal subsystem's only. This makes driver
more simple and also can remove ifdeferies.
Signed-off-by: Jonghwa Lee
---
drivers/power/Kconfig |1 +
drivers/power/charger-m
Whenever battery status is changed, charger manager tries to trigger uevent
through private interface. This patch modifies it to use power_supply_changed()
since it belongs to power supply subsystem.
Signed-off-by: Jonghwa Lee
---
drivers/power/charger-manager.c | 91 +-
After charger manager's initially introduced, it has kept its codes without any
big change. However, the charger manager working operation isn't optimized and
it also has unused codes and non-generic interface. This series tries to make
charger manager more generic and maintainable with some fixes.
The POWER_SUPPLY_CHARGE_NOW/FULL property reflects battery's charges
in uAh unit, but charger-manager has been used it wrongly. This patch
makes it to use those propeties correctly and change to be optional.
Signed-off-by: Jonghwa Lee
---
drivers/power/charger-manager.c | 85 +-
Current charger-manager calls power_suuply_changed() whenever charging
status is changed. This patch removes seperated power_supply_changed()
use and let it be called at end of try_charger_enable() function which
is called to set charging/discharging.
Signed-off-by: Jonghwa Lee
---
drivers/power
This patch prevents direct charging control in cable notification.
It sets only input current limit according to cable type and yields charging
control to be done by cm_monitor() where charging management proceeds.
It may loose few ms to enable charging compared to before, even though it's
more imp
To guerantee proper charing and managing batteries even in suspend,
charger-manager has used rtc device with rtc framework interface.
However, it is better to use alarmtimer for cleaner and more appropriate
operation.
This patch makes driver to use alamtimer for polling work in suspend and
removes
cm_notify_event() is introduced to get event associated with battery status
externally, but no one had been used. Moreover it makes charger manager
driver more complicated. This patch tries to drop the function and all data
related to simplify the driver.
Signed-off-by: Jonghwa Lee
---
.../bindi
On 19 December 2014 at 13:57, Jiri Pirko wrote:
> Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com wrote:
>>On 19 December 2014 at 05:18, Roopa Prabhu wrote:
>>> On 12/18/14, 3:26 PM, Samudrala, Sridhar wrote:
We also need an interface to set per-switch attributes. Can th
Hey Alexandre!
On 17-12-14 20:58, Alexandre Belloni wrote:
Hi,
I finally got some time to work on that again.
awesome :D
On 18/11/2014 at 14:47:33 +0100, Olliver Schinagl wrote :
What I get from the datasheet is, that sun4i and sun5i are exactly the same,
with the exception that sun5i only
This patch is add regulator_nodes/ofmatch in the regulator descriptor
for using information from DT instead of specific codes.
That will be used regulation_of_get_init_data function for get regulator
property on device tree. Using that make driver simpler.
Cc: Chanwoo Choi
Cc: Krzysztof Kozlowski
Lokesh,
On 19/12/14 07:21, Lokesh Vutla wrote:
> Hi Roger,
> On Thursday 18 December 2014 09:22 PM, Roger Quadros wrote:
>> Fixing up Paul's email id.
>>
>> cheers,
>> -roger
>>
>> On 18/12/14 17:49, Roger Quadros wrote:
>>> There are quite a few hwmods that don't have sysconfig register and so
>>
Andrew Morton writes:
> On Wed, 10 Dec 2014 16:49:18 +0300 Dmitry Monakhov
> wrote:
>
>>
>> Hello. Someone please take care of this patch.
>>
>> W/o that patch unprivileged user may abuse system resources simply by
>> spawning
>> wast number of unkilable busyloops (works on ext2/ext3):
>>
>
Hi,
On 19/12/2014 at 09:20:47 +0100, Alexander Stein wrote :
> I recently send 3 patches to make DT working with this driver, you were on CC
> :). Please refer to http://comments.gmane.org/gmane.linux.alsa.devel/131686
> I wonder though why all 3 are listed there although they were sent to
> dif
Hi Linus,
Please pull the second batch of powerpc updates for 3.19:
The following changes since commit 56548fc0e86cb9156af7a7e1f15ba78f251dafaf:
powerpc/powernv: Return to cpu offline loop when finished in KVM guest
(2014-12-08 13:16:31 +1100)
are available in the git repository at:
git:/
On Fri, Dec 19, 2014 at 05:32:54AM +, Jonghwa Lee wrote:
> Current psci's cpu_suspend callback can be used only when common cpu idle
> configuration is enabled. However, it's also needed for system which only
> uses generic pm suspend not cpu idle. This patch modifies psci driver to
> support b
---
drivers/staging/comedi/drivers/ni_stc.h | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/comedi/drivers/ni_stc.h
b/drivers/staging/comedi/drivers/ni_stc.h
index bd69c3f..a79fd07 100644
--- a/drivers/staging/comedi/drivers/ni_stc.h
+++ b/drivers/
On 19 December 2014 at 14:31, B Viswanath wrote:
> On 19 December 2014 at 13:57, Jiri Pirko wrote:
>> Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com wrote:
>>>On 19 December 2014 at 05:18, Roopa Prabhu wrote:
On 12/18/14, 3:26 PM, Samudrala, Sridhar wrote:
>
>
>
> We
My ISP finally gave up on the old mail address, so I am moving things
over to bitmath.org instead. Also change the status fields to better
reflect reality.
Signed-off-by: Henrik Rydberg
---
MAINTAINERS | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/MAINTAINERS b
Fri, Dec 19, 2014 at 10:01:46AM CET, marichi...@gmail.com wrote:
>On 19 December 2014 at 13:57, Jiri Pirko wrote:
>> Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com wrote:
>>>On 19 December 2014 at 05:18, Roopa Prabhu wrote:
On 12/18/14, 3:26 PM, Samudrala, Sridhar wrote:
>
>
>
Also, rename bits to nbits. Both changes for consistency with other
bitmap_* functions.
Signed-off-by: Rasmus Villemoes
---
Notes:
v3: Hopefully complete and unambiguous commit log.
v2: Only do the signed->unsigned conversion. bitmap_remap only has a
single caller (via nodes_rem
Simplify the driver by removing board file support and letting
regulator core to parse DT.
The max77693 regulator driver is used only on Exynos based boards which
are DT-only. Board files are not supported.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/max77693.c | 93 +--
Hi,
Simplify the max77693 regulator driver by moving DT parse code out
to regulator core.
This removes also board file support. Exynos based boards are DT-only.
This removal allows bigger simplification of driver so overall diffstat
is nice: -95 deletions, 12 additions.
The patch 2/2 depends on
The max77693 regulator driver no longer supports board files. Remove the
left-overs. Additionally fix name of device in comment.
Signed-off-by: Krzysztof Kozlowski
---
include/linux/mfd/max77693.h | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/include/linux/mfd/
this patch drops duplicate dependency of HAS_DMA from
VIDEO_SH_VEU.
Signed-off-by: Lad, Prabhakar
---
drivers/media/platform/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
index dba29b8..dac316d 100644
--- a/drivers/medi
Fri, Dec 19, 2014 at 10:22:24AM CET, marichi...@gmail.com wrote:
>On 19 December 2014 at 14:31, B Viswanath wrote:
>> On 19 December 2014 at 13:57, Jiri Pirko wrote:
>>> Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com wrote:
On 19 December 2014 at 05:18, Roopa Prabhu
wrote:
>>
On 19 December 2014 at 14:53, Jiri Pirko wrote:
> Fri, Dec 19, 2014 at 10:01:46AM CET, marichi...@gmail.com wrote:
>>On 19 December 2014 at 13:57, Jiri Pirko wrote:
>>> Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com wrote:
On 19 December 2014 at 05:18, Roopa Prabhu
wrote:
>>>
This series implements a mechanism to detect if the chip is in its POR state
and reinitialize it if needed. It also extends the sysfs interface to make the
driver configurable at run-time.
The shunt_resistor attribute allows to change the shunt resistance value
at run-time in cases where ina2xx us
The shunt resistance can only be set via platform_data or device tree. This
isn't suitable for devices in which the shunt resistance can change/isn't
known at boot-time.
Add a sysfs attribute that allows to read and set the shunt resistance.
Signed-off-by: Bartosz Golaszewski
---
Documentation/
Chips from the ina family don't like to be uninitialized. In case the power
is cut-off and restored again the calibration register will be reset
to 0 and both the power and current registers will remain at 0.
Check the calibration register in ina2xx_update_device() and reinitialize
the chip if nee
The averaging rate of ina226 is hardcoded to 16 in the driver. Make it
modifiable at run-time via a new sysfs attribute.
While we're at it - add an additional variable to ina2xx_data, which holds
the current configuration settings - this way we'll be able to restore the
configuration in case of an
Signed-off-by: Bartosz Golaszewski
---
drivers/hwmon/ina2xx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/hwmon/ina2xx.c b/drivers/hwmon/ina2xx.c
index ffbd60f..39e017b 100644
--- a/drivers/hwmon/ina2xx.c
+++ b/drivers/hwmon/ina2xx.c
@@ -52,7 +52,6 @@
#define INA226_ALERT_LIMIT
Shunt resistance values greater than the chip's calibration factor make no
sense since the actual value written to the register equals:
/
Bail-out from ina2xx_probe() if the configured value is greater than the
calibration factor.
Signed-off-by: Bartosz Golaszewski
---
drivers/hwmon/
On 16/12/2014 13:00, Alexander Popov wrote:
02.12.2014 13:47, Matteo Facchinetti пишет:
On 26/11/2014 12:49, Alexander Popov wrote:
So starting Linux with clk_ignore_unused bootparam
or inserting dummy LPB reading to some initcall is a temporary fix.
In fact clk_ignore_unused bootparam helps
On Thu 2014-12-18 09:49:35, Josh Poimboeuf wrote:
> On Thu, Dec 18, 2014 at 08:55:21PM +0900, Masami Hiramatsu wrote:
> > (2014/12/17 2:58), Seth Jennings wrote:
> > > changes in v7:
> > > - TODO: set IPMODIFY (not a blocker to moving forward)
> >
> > Why don't you set this?
> > IPMODIFY series ar
drivers/staging/fpga/socfpga.c:647:5-11: inconsistent IS_ERR and PTR_ERR,
PTR_ERR on line 648
PTR_ERR should access the value just tested by IS_ERR
Semantic patch information:
There can be false positives in the patch case, where it is the call
IS_ERR that is wrong.
Generated by: scripts/coc
Hi!
> And you want to set the QUIRK_INVALID_BADDR. At least you want to do that in
> the final submission.
>
Ok, I found out that I can do it and result works, provided that I do
hciconfig hci0 up/down first.
I have trouble understanding... h4p_hci_open() seems to be called as
soon as I insmod
Fri, Dec 19, 2014 at 10:35:27AM CET, marichi...@gmail.com wrote:
>On 19 December 2014 at 14:53, Jiri Pirko wrote:
>> Fri, Dec 19, 2014 at 10:01:46AM CET, marichi...@gmail.com wrote:
>>>On 19 December 2014 at 13:57, Jiri Pirko wrote:
Fri, Dec 19, 2014 at 06:14:57AM CET, marichi...@gmail.com w
Define ci_get_revision API to know the controller revision
information according to chipidea 1.1a, 2.0a, 2.4 and 2.5a
spec. Besides, add one entry in struct ci_hdrc to indicate
revision information. This can be used for adding different
code for revisions, implementing erratas.
Signed-off-by: Sanc
Using hw_write_id_reg and hw_read_id_reg to write and read
identification registers contents. This can be used to get
controller information, change some system configurations
and so on.
Signed-off-by: Sanchayan Maity
---
drivers/usb/chipidea/ci.h | 53 +
At chipidea revision 2.40a, there is a below errata:
9000531823 B2-Medium Adding a dTD to a Primed Endpoint May Not Get Recognized
Title: Adding a dTD to a Primed Endpoint May Not Get Recognized
Impacted Configuration: All device mode configurations.
Description:
There is an issue with the ad
The first two patches add identification register API's. These can
be used to get controller's revision.
The third patch implements an errata for revision 2.40a. Not sure
which other SOCs implement this version of the Chipidea core but
this fixes the usb client issue observed on Vybrids. The patc
I am announcing the release of the Linux 3.16.7-ckt3 kernel.
The updated 3.16.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.16.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.16.y;a=shortlog
The diff from v3.16.7-c
Hi Pavel,
>> And you want to set the QUIRK_INVALID_BADDR. At least you want to do that in
>> the final submission.
>>
>
> Ok, I found out that I can do it and result works, provided that I do
> hciconfig hci0 up/down first.
that should not be the case. Actually hciconfig uses old ioctl. A full
On Fri, Dec 19, 2014 at 3:32 PM, Qin Chuanyu
wrote:
On 2014/12/1 18:17, Jason Wang wrote:
On newer hosts that support delayed tx interrupts,
we probably don't have much to gain from orphaning
packets early.
Note: this might degrade performance for
hosts without event idx support.
Should be
On Wed, 17 Dec 2014, Benjamin Tissoires wrote:
> > Devices speaking HID++ 2.0 report a different error code (0xff). Detect
> > these errors too to avoid 5 second delays when the device reports an
> > error. Caught by... well, a bug in the QEMU emulation of this receiver.
> >
> > Renamed fap to ra
Hello Linus,
Here are the target-pending updates for v3.19-rc1 code. Please go ahead
and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next
The highlights this merge window include:
- Allow target fabric drivers to function as built-in. (Roland)
- Fi
On Thu, Dec 18, 2014 at 06:04:45PM -0800, Fengguang Wu wrote:
>
> Hi Thierry,
>
> FYI, here is another bisect result.
Thanks. Looking at the cirrus driver more closely it already employs the
big hammer upon failure and ends up calling drm_fb_helper_fini() via the
cirrus_driver_unload() call in c
Hi Liu,
Am Freitag, den 19.12.2014, 13:53 +0800 schrieb Liu Ying:
[...]
> >> + mipi_dsi: mipi@021e {
> >> + #address-cells = <1>;
> >> + #size-cells = <0>;
> >> + compatible = "fsl,imx6q-mipi-dsi";
> >> + reg = <0x021e 0x4000>;
> >> + interrupt
On 3 December 2014 at 00:42, Doug Anderson wrote:
> Bing Zhao at Marvell found a problem with dw_mmc where interrupts
> weren't firing sometimes. He tracked it down to a read-modify-write
> problem with the INTMASK. These patches fix the problem.
>
> Note: I've picked up a > 1-year old series he
On Thu, 18 Dec 2014 14:06:29 -0800 Andrew Morton
wrote:
> On Thu, 18 Dec 2014 10:33:23 -0600 (CST) Christoph Lameter
> wrote:
>
> > This patch adds the basic infrastructure for alloc / free operations
> > on pointer arrays.
>
> Please provide the justification/reason for making this change.
Joe Perches writes:
> On Fri, 2014-12-19 at 01:43 +, Måns Rullgård wrote:
>> What exactly are you proposing to remove?
>
> Optionally compile out
> kernel/printk/printk.c:early_printk()
> even if CONFIG_EARLY_PRINTK is enabled.
>
>> I see no unused code related
>> to early printk (in any vari
On 5 December 2014 at 06:54, wrote:
> From: Micky Ching
>
> v4:
> split patch in more detailed patches. no code changes diff v3.
>
> v3:
> rtsx_pci_sdmmc.c:
> - dump_reg_range
> - remove unused pointer check
> - fix start index
> v2:
> rtsx_pci.h:
> - remove unused rtsx
On Thu, Dec 18, 2014 at 02:45:01PM -0800, Jeremiah Mahler wrote:
> Aapo,
>
> On Thu, Dec 18, 2014 at 05:32:52PM +0200, Aapo Vienamo wrote:
> > This patch fixes a coding style issue found by the checkpatch.pl tool in
> > amplc_dio200_common.c by removing the unnecessary parentheses around the
> > e
On Tue, 16 Dec 2014, Peter Wu wrote:
> Devices speaking HID++ 2.0 report a different error code (0xff). Detect
> these errors too to avoid 5 second delays when the device reports an
> error. Caught by... well, a bug in the QEMU emulation of this receiver.
>
> Renamed fap to rap for HID++ 1.0 erro
On Tue, 16 Dec 2014, Peter Wu wrote:
> Add a return to avoid a fall-through. Introduced in commit
> 57ac86cf52e903d9e3e0f12b34c814cce6b65550 ("HID: logitech-hidpp: add
> support of the first Logitech Wireless Touchpad").
>
> Signed-off-by: Peter Wu
Applied to for-3.19/upstream-fixes.
Thanks,
On Tue, 16 Dec 2014, Benjamin Tissoires wrote:
> This is my personal opinion and Jiri can say something different. I
> tend not to send big patches while there is a window opened. Sometimes
> Jiri has the time to get through them, sometime he does not.
> In this case, I think the patches you sent
Now f2fs have page-block mapping cache which can cache only one extent mapping
between contiguous logical address and physical address.
Normally, this design will work well because f2fs will expand coverage area of
the mapping extent when we write forward sequentially. But when we write data
random
On 19 December 2014 at 15:25, Jiri Pirko wrote:
> Fri, Dec 19, 2014 at 10:35:27AM CET, marichi...@gmail.com wrote:
>>On 19 December 2014 at 14:53, Jiri Pirko wrote:
>>> Fri, Dec 19, 2014 at 10:01:46AM CET, marichi...@gmail.com wrote:
On 19 December 2014 at 13:57, Jiri Pirko wrote:
> Fri,
On Wed, 17 Dec 2014, Benjamin Tissoires wrote:
> Thanks for applying most of the patches (2 are missing, I'll raise them
> in your inbox :-P )
>
> Regarding this one, I was wondering if we could not force it into 3.19,
> or at least add a stable@ tag. I had requested this in the first
> submissio
Am Donnerstag, den 18.12.2014, 18:00 -0800 schrieb Steve Longerbeam:
> Add conversion from drm_display_mode to videomode.
>
> Signed-off-by: Steve Longerbeam
> ---
> drivers/gpu/drm/drm_modes.c | 40
> include/drm/drm_modes.h |2 ++
> 2 files ch
Hi Steve,
Am Donnerstag, den 18.12.2014, 18:00 -0800 schrieb Steve Longerbeam:
> From: Jiada Wang
>
> On some monitors, high resolution modes are not working, exhibiting
> pixel column truncation problems (for example, 1280x1024 displays as
> 1280x1022).
>
> The function ipu_di_adjust_videomode
On Mon, 15 Dec 2014, Miroslav Benes wrote:
> On Fri, 12 Dec 2014, Paul E. McKenney wrote:
>
> > On Fri, Dec 12, 2014 at 03:06:20PM +0100, Miroslav Benes wrote:
> >
[...]
> > > One last thing. Is there a reason that there is not any similar INFO in
> > > the console for tiny implementation? I
The first patch merges two similar functions. Since the resulting
function is only called three times, it adds a parameter to differenciate
between the two behaviours.
The second patch proposes a simplification of the function code. The function
previously used a variable to skip through the rest
Hi Prabhakar,
I haven't seen any movement with Nikhil's patches, so it is probably better if
you just post a new version of this patch based on the latest media_tree.
This patch no longer applies cleanly.
Regards,
Hans
On 12/01/2014 12:23 PM, Hans Verkuil wrote:
> On 11/18/2014 02:00 P
mpt2sas_scsih_set_tm_flag and mpt2sas_scsih_clear_tm_flag
shared a lot of code. Therefore, they are merged into one
function whose behaviour is given by a new parameter
named action.
Signed-off-by: Quentin Lambert
---
drivers/scsi/mpt2sas/mpt2sas_scsih.c | 43 +++-
Since skip was only used to pass through the rest of the loop,
a break statment is called where skip was previously assigned 1.
Signed-off-by: Quentin Lambert
---
drivers/scsi/mpt2sas/mpt2sas_scsih.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/scsi/mpt2sas/mpt
Signed-off-by: Quentin Lambert
---
drivers/scsi/mpt2sas/mpt2sas_base.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/scsi/mpt2sas/mpt2sas_base.c
b/drivers/scsi/mpt2sas/mpt2sas_base.c
index 58e4521..c31de9d 100644
--- a/drivers/scsi/mpt2sas/mpt2sas_base.c
+++ b/
drivers/gpu/drm/cirrus/cirrus_fbdev.c:330:1-4: WARNING: end returns can be
simpified
Simplify a trivial if-return sequence. Possibly combine with a
preceding function call.
Generated by: scripts/coccinelle/misc/simple_return.cocci
CC: Thierry Reding
Signed-off-by: Fengguang Wu
---
cirrus_
On Fri, Dec 19, 2014 at 08:29:56AM +0800, Yuyang Du wrote:
> Subject: [PATCH] sched: Fix long and unsigned long multiplication error in
> effective_load
>
> In effective_load, we have (long w * unsigned long tg->shares) / long W,
> when w is negative, it is cast to unsigned long and hence the pro
1 - 100 of 433 matches
Mail list logo
