On Mon, May 02, 2016 at 09:32:54AM +0200, Wolfram Sang wrote:
> On Sun, Apr 24, 2016 at 08:28:06PM +0100, Srinivas Kandagatla wrote:
> > This patch moves to nvmem support in the driver to use callback instead
> > of regmap.
> >
> > Signed-off-by: Srinivas Kandagatla
>
> Andrew, since you did the
"mac" is an array allocated in stack without being initialized,
and will be sent out via "nla_put". The dump_station() is supposed
to initialize the mac address; otherwise, sensitive data in kernel
stack will be leaked. To fix this, copy the mac address to it.
Signed-off-by: Kangjie Lu
---
drive
Hi Boris,
On Tue, Apr 19, 2016 at 3:34 PM, Boris Brezillon
wrote:
> Hi Peter,
>
> On Tue, 19 Apr 2016 08:40:40 +0800
> Peter Pan wrote:
>>
>> >
>> >> So it's true, it
>> >> should still be numchips in nand_bbt.c? I just came out this question
>> >> when
>> >> making v4. :)
>> >
>> > BTW, I hav
Ping? Did this change get accepted?
cheers,
grant
On Tue, Apr 5, 2016 at 12:07 PM, Grant Grundler wrote:
> On Mon, Apr 4, 2016 at 5:37 PM, Guenter Roeck wrote:
>> The Qualcom watchdog timer block reports if the system was reset by the
>> watchdog. Pass the information to user space.
>>
>> Cc: G
On Tue, May 03, 2016 at 06:30:04PM +, Rudoff, Andy wrote:
> >
> >And when the filesystem says no because the fs devs don't want to
> >have to deal with broken apps because app devs learn that "this is a
> >go fast knob" and data integrity be damned? It's "fsync is slow so I
> >won't use it" all
commit 61b914eb81f8 ("mmc: sdhci-of-arasan: add phy support for
sdhci-of-arasan") introduce phy support for arasan. According to
the vendor's databook, we should make sure the phy is in poweroff
status before we configure the clk stuff. Otherwise it may cause
some IO sample timing issues from the t
在 2016/4/28 18:38, Ulf Hansson 写道:
On 28 April 2016 at 10:38, Shawn Lin wrote:
commit 61b914eb81f8 ("mmc: sdhci-of-arasan: add phy support for
sdhci-of-arasan") introduce phy support for arasan. According to
the vendor's databook, we should make sure the phy is in poweroff
status before we conf
On Tue, May 03, 2016 at 06:44:46PM +0300, Roger Quadros wrote:
> Hi,
>
> On 03/05/16 10:06, Jun Li wrote:
> > Hi
> >
> > /**
> > + * usb_gadget_start - start the usb gadget controller and
> > +connect to bus
> > + * @gadget: the gadget device to start
> >
On 05/03/2016 06:36 PM, Grant Grundler wrote:
Ping? Did this change get accepted?
Hi Grant,
Should be. It is in my watchdog-next branch. I plan to send
a pull request to Wim early next week.
Guenter
cheers,
grant
On Tue, Apr 5, 2016 at 12:07 PM, Grant Grundler wrote:
On Mon, Apr 4, 2016
On Tue, May 3, 2016 at 7:01 PM, Guenter Roeck wrote:
> On 05/03/2016 06:36 PM, Grant Grundler wrote:
>>
>> Ping? Did this change get accepted?
>>
>
> Hi Grant,
>
> Should be. It is in my watchdog-next branch. I plan to send
> a pull request to Wim early next week.
Hi Guenter!
Excellent - I just h
On Tue, May 03, 2016 at 10:53:56AM +0200, Michal Hocko wrote:
> On Tue 03-05-16 14:23:04, Joonsoo Kim wrote:
> > From: Joonsoo Kim
> >
> > Currently, we store each page's allocation stacktrace on corresponding
> > page_ext structure and it requires a lot of memory. This causes the problem
> > tha
> > I think Greg is referring to commit 464ad8c43a9e ("usb: core : hub: Fix
> > BOS 'NULL pointer' kernel panic"), which has already been applied
> > upstream. It looks to me like that patch might have fixed the same
> > problem in a different way, in which case Changbin's patch is not
> > needed.
On Sun, May 01, 2016 at 02:18:37PM +0200, Christian Lamparter wrote:
> This patch adds the device tree bindings for the Western Digital's
> MyBook Live memory-mapped GPIO controllers.
>
> The gpios will be supported by gpio-mmio code of the
> GPIO generic library.
>
> Signed-off-by: Christian Lam
Some code waits for a metadata update by:
1. flagging that it is needed (MD_CHANGE_DEVS or MD_CHANGE_CLEAN)
2. setting MD_CHANGE_PENDING and waking the management thread
3. waiting for MD_CHANGE_PENDING to be cleared
If the first two are done without locking, the code in md_update_sb()
which chec
On 2016年05月03日 23:21, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Tue, May 03, 2016 at 05:09:37PM +0800, Wei Ni wrote:
>> This patch changes the compatible of Tegra132 fuse node
>> to "nvidia,tegra132-efuse", instead of "nvidia,tegra1124-efuse".
>> Because the CONFIG_ARCH_TEGRA
Tadeusz Struk wrote:
> Could you please check if this one fixes the problem for you:
> https://patchwork.kernel.org/patch/8766361/
That patch is already present by 4.6-rc5 and the problem still exists,
so no, it doesn't.
--
Jamie Heilman http://audible.transient.net/~jamie/
David Howells wrote:
> (cc'ing Tadeusz as he did the pkcs1 padding function)
>
> Jamie Heilman wrote:
>
> > > > Problem loading in-kernel X.509 certificate (-2)
> > >
> > > ENOENT? Hmmm... The only place that is generated is in the crypto layer.
> > > That suggests missing crypto of some sort
On 05/03/2016 11:21 AM, Greg Kroah-Hartman wrote:
On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote:
On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.5.3 release.
There are 200 patches in this series, all will be posted as a re
On Mon, May 02, 2016 at 12:35:04PM +0530, Sanchayan Maity wrote:
> Add device tree binding documentation for Vybrid SoC.
>
> Signed-off-by: Sanchayan Maity
> ---
> .../bindings/arm/freescale/fsl,vf610-soc.txt | 35
> ++
> 1 file changed, 35 insertions(+)
> create mode
On Tue, May 03, 2016 at 06:19:15AM -0400, Sowmini Varadhan wrote:
> On (05/03/16 16:12), Herbert Xu wrote:
> >
> > Sorry, but your patch doesn't apply against the current tree at all.
> > Please rebase it if it is still needed.
>
> Hello,
>
> I had based my patch off of net-next, which is where
On Mon, May 02, 2016 at 10:39:05AM +0100, Jose Abreu wrote:
> The ARC SDP I2S clock can be programmed using a
> specific PLL.
>
> This patch has the goal of adding a clock driver
> that programs this PLL.
>
> At this moment the rate values are hardcoded in
> a table but in the future it would be
On Wed, May 04, 2016 at 11:14:50AM +0900, Joonsoo Kim wrote:
> On Tue, May 03, 2016 at 10:53:56AM +0200, Michal Hocko wrote:
> > On Tue 03-05-16 14:23:04, Joonsoo Kim wrote:
> > > From: Joonsoo Kim
> > >
> > > Currently, we store each page's allocation stacktrace on corresponding
> > > page_ext s
On Wed, May 04, 2016 at 12:31:12AM +0200, Jiri Kosina wrote:
> On Tue, 3 May 2016, Josh Poimboeuf wrote:
>
> > > 1. Do we really need a completion? If I am not missing something
> > > kobject_del() always waits for sysfs callers to leave thanks to kernfs
> > > active protection.
> >
> > What do y
On 05/03/2016 10:15 AM, Lucas Stach wrote:
Commits 190aa4304de6 (Add AMD Mullins platform support) and
cca118fa2a0a94 (Add AMD Carrizo platform support) enabled the
driver on a lot more devices, but the following commit missed
a single location in the code when checking if the SB800 register
offs
Got it. Thanks Alex. I may have future queries as well on this. Will get back
to you.
Thanks,
Nitin
> On 04-May-2016, at 01:33, Alex Williamson wrote:
>
> Hi,
>
> On Tue, 3 May 2016 23:56:38 +0530
> Nitin Saxena wrote:
>
>> Hi,
>>
>> I am a newbie to VFIO framework and trying to use it for
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 5413d1babe8f10de13d72496c12b862eef8ba613 ("net: do not block BH while
processing socket backlog")
on test machine: vm-lkp-wsx03-1G: 1 threads qemu-system-x86_64 -enable-kvm -c
On Sun, May 01, 2016 at 02:08:27PM +0900, Yoshinori Sato wrote:
> Board specific code conflict on of-generic.
>
> Signed-off-by: Yoshinori Sato
> ---
> arch/sh/Makefile | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/sh/Makefile b/arch/sh/Makefile
> index bf5b3f5..8ff
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/irqchip/Kconfig
between commit:
df1a714d52c4 ("irqchip: add nps Internal and external irqchips")
from the arc tree and commit:
9e2c986cb460 ("irqchip: Add per-cpu interrupt partitioning library")
from the tip t
From: Dom Cote
Replace the addition (+) of 2 python 'memoryview' objects
with the addition of 2 'bytes' objects, convert the result
back to memoryview.
Tested with python 3.4 and 2.7
Tested with gdb 7.7
Signed-off-by: Dom Cote
---
scripts/gdb/linux/dmesg.py | 7 ---
1 file changed, 4 inse
From: Dom Cote
Change the read_u16 function so it accepts both 'str' and 'byte'
as type for the arguments.
When calling read_memory() from gdb API, depending on if
it was built with 2.7 or 3.X, the format used to return the
data will differ ( 'str' for 2.7, and 'byte' for 3.X ).
Add a function
On Sun, May 01, 2016 at 02:08:29PM +0900, Yoshinori Sato wrote:
> Changes bellow
> - FDT setup timing fix.
> - chosen/bootargs support.
> - zImage support.
> - DT binding helper macro.
>
> Signed-off-by: Yoshinori Sato
> ---
> arch/sh/boards/of-generic.c| 23
> ++
On Tue, May 3, 2016 at 7:47 PM, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 5413d1babe8f10de13d72496c12b862eef8ba613 ("net: do not block BH while
> processing socket backlog")
>
> on tes
From: Dom Cote
Change the read_u16 function so it accepts both 'str' and 'byte'
as type for the arguments.
When calling read_memory() from gdb API, depending on if
it was built with 2.7 or 3.X, the format used to return the
data will differ ( 'str' for 2.7, and 'byte' for 3.X ).
Add a function
From: Dom Cote
Replace the addition (+) of 2 python 'memoryview' objects
with the addition of 2 'bytes' objects, convert the result
back to memoryview.
Tested with python 3.4 and 2.7
Tested with gdb 7.7
Signed-off-by: Dom Cote
---
scripts/gdb/linux/dmesg.py | 7 ---
1 file changed, 4 inse
On Tue, May 03, 2016 at 10:28:15AM -0700, Dan Williams wrote:
> On Mon, May 2, 2016 at 6:51 PM, Dave Chinner wrote:
> > On Mon, May 02, 2016 at 04:25:51PM -0700, Dan Williams wrote:
> [..]
> > Yes, I know, and it doesn't answer any of the questions I just
> > asked. What you just told me is that t
Hi Leo and Scott,
> -Original Message-
> From: Leo Li [mailto:pku@gmail.com]
> Sent: Wednesday, May 04, 2016 4:06 AM
> To: Yangbo Lu
> Cc: Scott Wood; Yang-Leo Li; linux-...@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.k
On Sun, May 01, 2016 at 02:08:34PM +0900, Yoshinori Sato wrote:
> Signed-off-by: Yoshinori Sato
> ---
> arch/sh/boot/dts/landisk.dts | 150
> +++
> 1 file changed, 150 insertions(+)
> create mode 100644 arch/sh/boot/dts/landisk.dts
>
> diff --git a/arch/
Hi Mark
>> > +static const unsigned int wm831x_usb_limits[] = {
>> > + 0,
>> > + 2,
>> > + 100,
>> > + 500,
>> > + 900,
>> > + 1500,
>> > + 1800,
>> > + 550,
>> > +};
>
>> Just for curiosity, How these current limits are getting decided?
>> Can we ha
Hi Pramod
>>> @@ -715,10 +724,13 @@ static int bam_resume(struct dma_chan *chan)
>>> struct bam_device *bdev = bchan->bdev;
>>> unsigned long flag;
>>>
>>> + pm_runtime_get_sync(bdev->dev);
>>> spin_lock_irqsave(&bchan->vc.lock, flag);
>>> writel_relaxed(0, ba
Hi,
On 05/03/2016 08:13 PM, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> commit 13a7238eeab5718bf968e2a835205ba659a38a77 ("serial: core: Prevent
> unsafe uart port access, part 3")
This shoul
Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
since it's used by not only PowerPC but also ARM. And add a specification
for 'little-endian' property.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
Acked-by: Rob Herring
---
Changes for v4:
- Added this patch
Chang
The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version.
Acturally the right version numbers should be VVN=0x13 and SVN = 0x1.
This patch adds the GUTS driver support for eSDHC driver to get SVR(System
version register). And fix host version to avoid that incorrect version
number
On Tue, May 03, 2016 at 09:39:48PM -0500, Josh Poimboeuf wrote:
> On Wed, May 04, 2016 at 12:31:12AM +0200, Jiri Kosina wrote:
> > On Tue, 3 May 2016, Josh Poimboeuf wrote:
> >
> > > > 1. Do we really need a completion? If I am not missing something
> > > > kobject_del() always waits for sysfs cal
The global utilities block controls power management, I/O device
enabling, power-onreset(POR) configuration monitoring, alternate
function selection for multiplexed signals,and clock control.
This patch adds GUTS driver to manage and access global utilities
block.
Signed-off-by: Yangbo Lu
Acked-
On Tue, May 03, 2016 at 06:44:46PM +0300, Roger Quadros wrote:
> Hi,
>
> On 03/05/16 10:06, Jun Li wrote:
> > Hi
> >
> > /**
> > + * usb_gadget_start - start the usb gadget controller and
> > +connect to bus
> > + * @gadget: the gadget device to start
> >
Everybody has it. If code-size is not the problem, __accumulate_sum()
should have it too.
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 34ccaa3..a060ef2 100644
--- a/kernel/s
__compute_runnable_contrib() uses a loop to compute sum, whereas a
table lookup can do it faster in a constant time.
The program to generate the constants is located at:
Documentation/scheduler/sched-avg.txt
Signed-off-by: Yuyang Du
Reviewed-by: Morten Rasmussen
Acked-by: Vincent Guittot
---
Hi Peter,
This patch series combines the previous cleanup and optimization
series. And as you and Ingo suggested, the increased kernel load
scale is reinstated when on 64BIT and FAIR_GROUP_SCHED.
This patch series should have no perceivable changes to load
and util except that load's range is inc
The names of sched averages (including load_avg and util_avg) have
been changed and added in the past a couple of years, some of
the names are a bit confusing especially to people who first read them.
This patch attempts to make the names more self-explaining. And some
comments are updated too.
Si
After cleaning up the sched metrics, these two definitions that cause
ambiguity are not needed any more. Use NICE_0_LOAD_SHIFT and NICE_0_LOAD
instead (the names suggest clearly who they are).
Suggested-by: Ben Segall
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c |4 ++--
kernel/sched/s
These sched metrics have become complex enough. We introduce them
at their definitions.
Signed-off-by: Yuyang Du
---
include/linux/sched.h | 60 -
1 file changed, 49 insertions(+), 11 deletions(-)
diff --git a/include/linux/sched.h b/include/lin
Currently, load_avg = scale_load_down(load) * runnable%. The extra scaling
down of load does not make much sense, because load_avg is primarily THE
load and on top of that, we take runnable time into account.
We therefore remove scale_load_down() for load_avg. But we need to
carefully consider the
The increased scale or precision for kernel load has been disabled
since the commit e4c2fb0d5776 ("sched: Disable (revert) SCHED_LOAD_SCALE
increase"). But we do need it when we have task groups, especially on
bigger machines. Otherwise, we probably will run out of precision for
load distribution.
Rename scale_load() and scale_load_down() to user_to_kernel_load()
and kernel_to_user_load() respectively. This helps us tag them
clearly and avoid confusion.
[update calculate_imbalance]
Signed-off-by: Vincent Guittot
Signed-off-by: Yuyang Du
---
kernel/sched/core.c |8
kernel/sc
This doc file has the program to generate the constants to compute
sched averages.
Signed-off-by: Yuyang Du
---
Documentation/scheduler/sched-avg.txt | 94 +
1 file changed, 94 insertions(+)
create mode 100644 Documentation/scheduler/sched-avg.txt
diff --git a
Integer metric needs fixed point arithmetic. In sched/fair, a few
metrics, including weight, load, load_avg, util_avg, freq, and capacity,
may have different fixed point ranges.
In order to avoid errors relating to the fixed point range of these
metrics, we define a basic fixed point range, and th
__update_sched_avg() has these steps:
1. add the remainder of the last incomplete period
2. decay old sum
3. accumulate new sum in full periods since last_update_time
4. add the current incomplete period
5. update averages
Previously, we separately computed steps 1, 3, and 4, leading to
In sched average update, a period is about 1ms, so a 32-bit unsigned
integer can approximately hold a maximum of 49 (=2^32/1000/3600/24)
days.
For usual cases, 32bit is big enough and 64bit is needless. But if
a task sleeps longer than it, there can be two outcomes:
Consider a task sleeps whateve
Update Freescale DCFG compatible with 'fsl,-dcfg' instead
of 'fsl,ls1021a-dcfg' to include more chips such as ls1021a,
ls1043a, and ls2080a.
Signed-off-by: Yangbo Lu
---
Changes for v8:
- Added this patch
Changes for v9:
- Added a list for the possible compatibles
---
Documentati
Add maintainer entry for Freescale SoC driver including
the QE library and the GUTS driver now. Also add maintainer
for QE library.
Signed-off-by: Yangbo Lu
---
Changes for v8:
- Added this patch
Changes for v9:
- Added linux-arm mail list
- Removed GUTS driver entry
---
Add the dts node for device configuration unit that provides
general purpose configuration and status for the device.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
---
Changes for v5:
- Added this patch
Changes for v6:
- None
Changes for v7:
- None
Changes for v8:
Move mpc85xx.h to include/linux/fsl and rename it to svr.h as
a common header file. It has been used for mpc85xx and it will
be used for ARM-based SoC as well.
Signed-off-by: Yangbo Lu
Acked-by: Wolfram Sang
Acked-by: Stephen Boyd
Acked-by: Scott Wood
Acked-by: Joerg Roedel
---
Changes for v2
This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0
eSDHC controller. To get the SoC version and revision, it's needed to add the
GUTS driver to access the global utilities registers.
So, the first four patches are to add the GUTS driver.
The following patches except th
On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set
to be able to do DMA allocations, so use the of_dma_configure() helper
to populate the dma properties and assign an appropriate dma_ops.
Signed-off-by: Rajesh Bhagat
Reviewed-by: Yang-Leo Li
---
drivers/usb/dwc3/host.c | 4
On 05/03/2016 11:00 PM, Peter Ujfalusi wrote:
>>> @@ -1382,29 +1379,31 @@ static int mmc_omap_probe(struct platform_device
>>> *pdev)
>>> goto err_free_iclk;
>>> }
>>>
>>> - dma_cap_zero(mask);
>>> - dma_cap_set(DMA_SLAVE, mask);
>>> -
>>> host->dma_tx_b
Hi Emese,
2016-05-04 6:29 GMT+09:00 Emese Revfy :
> On Tue, 3 May 2016 11:00:56 +0900
> Masahiro Yamada wrote:
>
> Hi,
>
>> # Compile .c file, create position independent .o file
>> # host-cxxshobjs -> .o
>> quiet_cmd_host-cxxshobjs = HOSTCXX -fPIC $@
>> cmd_host-cxxshobjs = $(HOSTCXX) $(h
Muhammad Falak R Wani wrote:
> Never use sg++, always use sg = sg_next(sg). Scatterlist entries can
> be combined if the memory is contiguous but sg++ won't know about
> that. It sure would run on the slower side.
> But regardless, sg++ should never be used, only sg_next is safe.
>
> Signed-off-b
From: Benjamin Herrenschmidt
Date: Wed, 04 May 2016 10:37:40 +1000
> On Tue, 2016-05-03 at 15:52 -0700, Yinghai Lu wrote:
>> BenH and DavidM,
>> Are you ok to let /proc/bus/pci/devices to expose resource value
>> instead of
>> BAR value?
>> powerpc already expose MMIO as resource value, but still
On 05/03/2016 07:26 PM, Jamie Heilman wrote:
>>> Alrighty, presumably relevant bits:
>>> > >
>>> > > X.509: Cert Issuer: Build time autogenerated kernel key
>>> > > X.509: Cert Subject: Build time autogenerated kernel key
>>> > > X.509: Cert Key Algo: rsa
>>> > > X.509: Cert Valid period: 146182679
Hi
On 2016-05-03, Linus Torvalds wrote:
> On Tue, May 3, 2016 at 2:38 PM, Stefan Lippers-Hollmann wrote:
> > Hi
> > [...]
> >> Mauro Carvalho Chehab (95):
> > [...]
> >> [media] use v4l2_mc_usb_media_device_init() on most USB devices
> > [...]
> >
> > This change, as part of v4.6-rc
On Tuesday, May 03, 2016 09:22:10 PM Rob Herring wrote:
> On Sun, May 01, 2016 at 02:18:37PM +0200, Christian Lamparter wrote:
> > This patch adds the device tree bindings for the Western Digital's
> > MyBook Live memory-mapped GPIO controllers.
> >
> > The gpios will be supported by gpio-mmio cod
Tadeusz Struk wrote:
> On 05/03/2016 07:26 PM, Jamie Heilman wrote:
> >>> Alrighty, presumably relevant bits:
> >>> > >
> >>> > > X.509: Cert Issuer: Build time autogenerated kernel key
> >>> > > X.509: Cert Subject: Build time autogenerated kernel key
> >>> > > X.509: Cert Key Algo: rsa
> >>> > >
On Tue, May 3, 2016 at 8:18 PM, Dave Chinner wrote:
> On Tue, May 03, 2016 at 10:28:15AM -0700, Dan Williams wrote:
>> On Mon, May 2, 2016 at 6:51 PM, Dave Chinner wrote:
>> > On Mon, May 02, 2016 at 04:25:51PM -0700, Dan Williams wrote:
>> [..]
>> > Yes, I know, and it doesn't answer any of the
On Tue, May 3, 2016 at 6:25 PM, Bjorn Helgaas wrote:
> On Wed, May 04, 2016 at 10:37:40AM +1000, Benjamin Herrenschmidt wrote:
>>
>> The problem tends to be old Xserver expectations...
>>
>> That stuff has been a can of worms over the years and we did things in
>> the kernel to work around X limit
On Tue, 2016-05-03 at 17:52 +0200, Olliver Schinagl wrote:
> Hey all,
>
> On 03-05-16 17:02, christo.ra...@gmail.com wrote:
> > On Tuesday, May 3, 2016 at 4:14:41 PM UTC+3, Maxime Ripard wrote:
> > > Hi,
> > >
> > > On Tue, May 03, 2016 at 4:12:06 PM UTC+3, Christo Radev wrote:
> > > > Hi to All,
tty and ch are already checked for NULL
before calling dgnc_block_til_ready().
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_tty.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
index 2cec
On Tuesday 03 May 2016 10:20 PM, Bjorn Helgaas wrote:
> On Mon, May 02, 2016 at 04:09:33PM -0500, Bjorn Helgaas wrote:
>> On Mon, May 02, 2016 at 04:54:40PM +0200, Niklas Cassel wrote:
>>> From: Niklas Cassel
>>>
>>> commit 1488aefa37a4 ("PCI: designware: Move Root Complex
>>> setup code to dw_p
the "ch" in dgnc_get_modem_info() was already checked before calling
this function and also if "ch" is not NULL, dgnc_get_mstat() returns
valid value so it doesn't need to check an error.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_tty.c | 12 +---
1 file changed, 1 inserti
the result in dgnc_get_mstat() was initialized with -EIO but
there are no use of EIO as a result in this function.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_tty.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/stag
On 2016-05-04 05:12, buzdelab...@gmail.com wrote:
> From: Dom Cote
>
> Replace the addition (+) of 2 python 'memoryview' objects
> with the addition of 2 'bytes' objects, convert the result
> back to memoryview.
>
> Tested with python 3.4 and 2.7
> Tested with gdb 7.7
A word here on what setup
The error handling for print_drive after calling tty_alloc_driver()
was needed. But there was error handling but too late for this.
Error handling code moved after tty_alloc_driver() call.
Fixes: 60b3109e5e2d ("staging: dgnc: use tty_alloc_driver instead of kcalloc")
Reported-by: Dan Carpenter
Si
On Wed, Apr 20, 2016 at 03:47:13PM -0400, Michal Hocko wrote:
> Hi,
>
> This is v6 of the series. The previous version was posted [1]. The
> code hasn't changed much since then. I have found one old standing
> bug (patch 1) which just got much more severe and visible with this
> series. Other than
From: Bob Moore
ACPICA commit 599e9159f53565e4a3f3e67f6a03f81fcb10a4cf
Original patch from hanjun@linaro.org
ACPICA BZ 1072.
Link: https://github.com/acpica/acpica/commit/599e9159
Link: https://bugs.acpica.org/show_bug.cgi?id=1072
Original-by: Hanjun Guo
Signed-off-by: Bob Moore
Signed-of
The 20160422 ACPICA kernel-resident subsystem updates are linuxized based
on the linux-pm/linux-next branch.
NOTE:
1. Indentation improvement
The [PATCH 02] is a result of an ACPICA release process fix. It requires
much of human intervention, and many linuxized patches in my hand that are
not upst
ACPICA commit b2294cae776f5a66a7697414b21949d307e6856f
This patch removes unwanted spaces for typedef. This solution doesn't cover
function types.
Note that the linuxize result of this commit is very giant and should have
many conflicts against the current Linux upstream. Thus it is required to
m
The patch reduces source code differences between the Linux kernel and the
ACPICA upstream so that the linuxized ACPICA 20160422 release can be
applied with reduced human intervention.
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/aclocal.h |2 +-
drivers/acpi/acpica/acresrc.h |2 +-
From: Bob Moore
ACPICA commit de3ea7c322b9b6bdb09aa90c2e1d420cd4dce47c
Additional subspace structure was added.
Link: https://github.com/acpica/acpica/commit/de3ea7c3
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
include/acpi/actbl3.h | 23 ++-
1 file changed, 22
This patch introduces ACPI_IS_ALIGNED() macro. Lv Zheng.
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/acmacros.h |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/acpi/acpica/acmacros.h b/drivers/acpi/acpica/acmacros.h
index 73f6653..ecbaaba 100644
--- a/drivers
ACPICA commit c23034a3a09d5ed79f1827d51f43cfbccf68ab64
A regression was reported to the shift offset >= width of type.
This patch fixes this issue. BZ 1270.
This is a part of the fix because the order of the patches are modified for
Linux upstream, containing the cleanups for the old code. Lv Zhen
From: Bob Moore
ACPICA commit 3451e6d49d37919c13ec2c0019a31534b0dfc0c0
One integer was added at the end of the _BIX method, and the
version number was incremented.
Link: https://github.com/acpica/acpica/commit/3451e6d4
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/
ACPICA commit 48eea5e7993ccb7189bd63cd726e02adafee6057
This patch adds access_width/bit_offset support in acpi_hw_write().
Lv Zheng.
Link: https://github.com/acpica/acpica/commit/48eea5e7
Link: https://bugs.acpica.org/show_bug.cgi?id=1240
Signed-off-by: Lv Zheng
Signed-off-by: Bob Moore
---
dr
From: Prarit Bhargava
ACPICA commit 7a3bd2d962f221809f25ddb826c9e551b916eb25
Set the mutex owner thread ID.
Original patch from: Prarit Bhargava
Link: https://github.com/acpica/acpica/commit/7a3bd2d9
Signed-off-by: Prarit Bhargava
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
driver
ACPICA commit c49a751b4dae7baec1790748a2b4b6e8ab599f51
For Access Size = 0, it actually can use user expected access bit width.
This patch implements this.
Besides of the ACPICA upstream commit, this patch also includes a fix fixing
the issue reported by the FreeBSD community.
The old register de
From: Bob Moore
ACPICA commit 438905b205e64e742f9670a0970419c426264831
Expanded a couple of cryptic names.
Link: https://github.com/acpica/acpica/commit/438905b2
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/aclocal.h | 30 +++---
drivers/
From: Bob Moore
ACPICA commit a2327ba410e19c2aabaf34b711dbadf7d1dcf346
Version 20160422.
Link: https://github.com/acpica/acpica/commit/a2327ba4
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
include/acpi/acpixf.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/in
ACPICA commit 96ece052d4d073aae4f935f0ff0746646aea1174
ACPICA commit 3d8583a054e410f2ea4d73b48986facad9cfc0d4
This patch adds access_width/bit_offset support in acpi_hw_read().
This also enables GAS definition where bit_width is not a power of
two. Lv Zheng.
Link: https://github.com/acpica/acpica
From: Bob Moore
ACPICA commit ba60e4500053010bf775d58f6f61febbdb94d817
New file is utascii.c
Link: https://github.com/acpica/acpica/commit/ba60e450
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/Makefile |1 +
drivers/acpi/acpica/actables.h
On Tue, May 3, 2016 at 10:08 PM, Yinghai Lu wrote:
> On Tue, May 3, 2016 at 6:25 PM, Bjorn Helgaas wrote:
>> I did not propose changing any user-visible ABI. To recap what I did
>> propose:
>
> I want to avoid introduce one strange pci_user_to_resource.
>
>>
>> - The sysfs path uses offsets be
From: Bob Moore
ACPICA commit 5a0555ece4ba9917e5842b21d88469ae06b4e815
Adds full support for:
i2c_serial_bus_v2
spi_serial_bus_v2
uart_serial_bus_v2
Compiler, Disassembler, Resource Manager, acpi_help.
Link: https://github.com/acpica/acpica/commit/5a0555ec
Signed-off-by: Bob Moore
Signed-off-
Hi Matias,
After merging the lightnvm tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
In file included from include/linux/swab.h:4:0,
from include/uapi/linux/byteorder/big_endia
n.h:12,
from include/linux/byteorder/big_endian.h:4
,
801 - 900 of 953 matches
Mail list logo
