Hi, Davidlohr
On 01/21/15 at 11:46pm, Davidlohr Bueso wrote:
> On Thu, 2015-01-22 at 14:29 +0800, WANG Chao wrote:
> > Add a new kconfig option VMACACHE_SHIFT (as a power of 2) to specify the
> > number of slots vma cache has for each thread. Range is chosen 0-4 (1-16
> > slots) to consider both
On Wed, 21 Jan 2015, Jonathan Cameron wrote:
>
>
> On 21 January 2015 16:52:50 GMT+00:00, Sebastian Reichel
> wrote:
> >Hi,
> >
> >On Wed, Jan 21, 2015 at 03:46:25PM +, Adam Thomson wrote:
> >> This patch set adds initial support for the Dialog DA9150 Integrated
> >Charger &
> >>
On Thu, Jan 22, 2015 at 4:40 PM, Thierry Reding
wrote:
> On Tue, Jan 20, 2015 at 03:22:25PM +0300, Dmitry Osipenko wrote:
>> Support CPU BE mode by adding endianness conversion for memcpy interactions.
>>
>> Signed-off-by: Dmitry Osipenko
>> ---
>> drivers/i2c/busses/i2c-tegra.c | 3 +++
>> 1
On Wed, Jan 21, 2015 at 09:36:34PM -0800, Guenter Roeck wrote:
> On 01/21/2015 08:59 PM, Paul Moore wrote:
> >This patchset has some important changes from the previous revision,
> >namely a fix from Al Viro (included in 2/5) that resolves a boot panic
> >on some systems as well as some smaller,
On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang wrote:
> The address of __kuser_sigtramp is wrong by one word, due to padding
> __kuser_cmpxchg to fully 64 bytes. The version word at the start of the
> page displaces __kuser_sigtramp to 0x1044, instead of the intended 0x1040.
>
> Fixed by
On Thu, 22 Jan 2015, Stephen Rothwell wrote:
> Hi Lee,
>
> I noticed this commit in the mfd tree:
>
> f11b9265e6ca "[FIX/HACK] Disable DRM"
>
> Is that really appropriate here? Especially given it has no explanation.
>
> I guess it will make my builds slightly faster :-)
You're right, this
On Thu, 22 Jan 2015, Rickard Strandqvist wrote:
> Remove same unused functions and structs.
Repeating the subject line in the commit message is seldom
appropriate. Please elaborate.
> Signed-off-by: Rickard Strandqvist
> ---
> arch/arm/mach-ux500/board-mop500-regulators.c | 106
>
On Thu, 2015-01-22 at 14:29 +0800, WANG Chao wrote:
> Add a new kconfig option VMACACHE_SHIFT (as a power of 2) to specify the
> number of slots vma cache has for each thread. Range is chosen 0-4 (1-16
> slots) to consider both overhead and performance penalty. Default is 2
> (4 slots) as it
The subject line is not a good one. Please elaborate.
> Move struct ab8500_ext_regulator_cfg to the only file that is now used in.
Attention to detail --^
> Signed-off-by: Rickard Strandqvist
> ---
> drivers/regulator/ab8500-ext.c |6 ++
>
On Thu, 22 Jan 2015, Beomho Seo wrote:
> This patch device tree binding documentation for rt5033 multifunction device.
>
> Cc: Sebastian Reichel
> Cc: Lee Jones
> Cc: Mark Brown
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Mark Rutland
> Cc: Ian campbell
> Cc: Kumar Gala
> Signed-off-by:
On Thu, 2015-01-22 at 15:30 +0800, micky_ch...@realsil.com.cn wrote:
> update card drive settings, This setting can be used for rts5249
> rts524A and rts525A.
[]
> diff --git a/drivers/mfd/rts5249.c b/drivers/mfd/rts5249.c
> @@ -36,16 +36,16 @@ static u8 rts5249_get_ic_version(struct rtsx_pcr
On Tue, Jan 20, 2015 at 03:22:25PM +0300, Dmitry Osipenko wrote:
> Support CPU BE mode by adding endianness conversion for memcpy interactions.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/i2c/busses/i2c-tegra.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
From: Olliver Schinagl
When using a hrtimer for repeating periodic ticks, hrtimer_forward_now()
is often used. Quite possibly the timer loop is thus probably fully
controlled by hrtimer_forward_now() and we don't really care when the
timer is started. With hrtimer_start() we need to define
On Wed, Jan 21, 2015 at 04:16:05PM -0800, Stephen Boyd wrote:
> On 01/21/2015 08:13 AM, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > This new function is similar to clk_set_parent(), except that it doesn't
> > actually change the parent. It merely checks that the given parent clock
> >
On Thu, Jan 22, 2015 at 03:05:32PM +0800, Mark Yao wrote:
> drm dpms have many power modes: ON,OFF,SUSPEND,STANDBY, etc.
> but vop only have enable/disable mode, maybe case such bug:
> --> DRM_DPMS_ON: power on vop
> --> DRM_DPMS_SUSPEND: power off vop
> --> DRM_DPMS_OFF: already power off at
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
fs/ocfs2/aops.c: In function 'ocfs2_direct_IO_write':
fs/ocfs2/aops.c:784:9: error: too few arguments to function
'blkdev_issue_zeroout'
ret =
From: Micky Ching
resend:
- add lee jones ack for some patch.
v2:
- remove debug info when access failed.
- using macro list for phy register init.
- rename function for multi chip prefix with rtsx_base_
- save pcie_cap offset when init chip, not calling pci_find_capacity()
every time.
- add
From: Micky Ching
update phy register value and using direct value instead of macros.
It is much easier to debug using constant value than a lot of macros.
We usually need compare the value directly to check the configure.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c| 55
From: Micky Ching
update card drive settings, This setting can be used for rts5249
rts524A and rts525A.
Signed-off-by: Micky Ching
Acked-by: Lee Jones
---
drivers/mfd/rts5249.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/rts5249.c
From: Micky Ching
It is more readable to place register address and values define
togather. The values define add two leading space indicate belong
to the register address defined above.
Signed-off-by: Micky Ching
Acked-by: Lee Jones
---
include/linux/mfd/rtsx_pci.h | 836
From: Micky Ching
To enable/disable ASPM we should find LINK CONTROL register
in PCI config space. All old chip use 0x80 address, but new
chip may use another address, so we using pci_find_capability()
to get LINK CONTROL address.
rtsx_gops.c was removed, we consider to put some common
From: Micky Ching
add support for new chip rts525A.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c| 104 ++-
drivers/mfd/rtsx_pcr.c | 13 --
drivers/mfd/rtsx_pcr.h | 1 +
include/linux/mfd/rtsx_pci.h | 15 +++
4
From: Micky Ching
pcr_dbg is a wrapper of dev_dbg, which can save some code,
and help to enable/disable debug message static.
Signed-off-by: Micky Ching
Acked-by: Lee Jones
---
drivers/mfd/rtl8411.c | 11 +--
drivers/mfd/rts5209.c | 4 ++--
drivers/mfd/rts5227.c | 4 ++--
From: Micky Ching
add support for new chip rts524A.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c| 186 ---
drivers/mfd/rtsx_pcr.c | 25 +-
drivers/mfd/rtsx_pcr.h | 7 ++
include/linux/mfd/rtsx_pci.h | 125
From: Micky Ching
PETXCFG is defined at 0xFF03, the old 0xFE49 not used any more.
Signed-off-by: Micky Ching
Acked-by: Lee Jones
---
drivers/mfd/rts5227.c| 6 ++
drivers/mfd/rts5249.c| 6 ++
include/linux/mfd/rtsx_pci.h | 2 +-
3 files changed, 5 insertions(+), 9
From: Micky Ching
Re-format coding-style, using uniform SPC after "#define" keyword
instead of mixing using TAB and SPC.
Signed-off-by: Micky Ching
Acked-by: Lee Jones
---
include/linux/mfd/rtsx_pci.h | 254 +--
1 file changed, 127 insertions(+), 127
On Thu, Jan 22, 2015 at 11:59:37AM +0800, Robin Gong wrote:
> Below comments got from Page4724 of Reference Manual of i.mx6q:
> http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf
>
> --"Static context mode should be used for the first channel called
> after reset to ensure that
On Wed, Jan 21, 2015 at 6:31 PM, Xunlei Pang wrote:
> Currently, interface.c uses y2038 problematic rtc_tm_to_time()
> and rtc_time_to_tm(). So replace them with their corresponding
> y2038-safe versions: rtc_tm_to_time64() and rtc_time64_to_tm().
Ok, I've queued this set of 5 (with a few minor
Have you reworked all of these patches?
If not, why haven't my Acks been carried forward?
Please [RESEND] with the Acks applied.
> From: Micky Ching
>
> v2:
> - remove debug info when access failed.
> - using macro list for phy register init.
> - rename function for multi chip prefix with
16MB alignment for ioremap mappings was added by commit a069c896d0d6 ("[ARM]
3705/1: add supersection support to ioremap()") in order to support supersection
mappings. But __arm_ioremap_pfn_caller uses section and supersection mappings
only in !SMP && !LPAE case. There is no need for such big
On Wed, Jan 21, 2015 at 06:45:54PM -0800, Calvin Owens wrote:
> Currently, /proc//map_files/ is restricted to CAP_SYS_ADMIN, and
> is only exposed if CONFIG_CHECKPOINT_RESTORE is set. This interface
> is very useful for enumerating the files mapped into a process when
> the more verbose
The address of __kuser_sigtramp is wrong by one word, due to padding
__kuser_cmpxchg to fully 64 bytes. The version word at the start of the
page displaces __kuser_sigtramp to 0x1044, instead of the intended 0x1040.
Fixed by counting the 64-byte frame from the start of the page instead
of
On Mon, Nov 3, 2014 at 5:01 AM, Juergen Gross wrote:
> At the moment there are a lot of places that handle setting or getting
> the page cache mode by treating the pgprot bits equal to the cache mode.
> This is only true because there are a lot of assumptions about the setup
> of the PAT MSR.
there is a Bug that:
vop_enable()->drm_vblank_on, drm_vblank_on may call vop
enable vblank. if it happen, vblank enable would failed,
then cause irq status error. because is_enabled value is set
after drm_vblank_on.
after enable vop clocks and iommu regs, we can sure that
R/W vop regs and do
drm dpms have many power modes, ON,OFF,SUSPEND,STANDBY, etc.
but vop only have enable/disable mode, maybe case such bug:
--> DRM_DPMS_ON: power on vop
--> DRM_DPMS_SUSPEND: power off vop
--> DRM_DPMS_OFF: already power off at SUSPEND, crash
so use a bool val is more suitable.
another problem
drm dpms have many power modes: ON,OFF,SUSPEND,STANDBY, etc.
but vop only have enable/disable mode, maybe case such bug:
--> DRM_DPMS_ON: power on vop
--> DRM_DPMS_SUSPEND: power off vop
--> DRM_DPMS_OFF: already power off at SUSPEND, crash
so use a bool val is more suitable.
Signed-off-by:
From: Micky Ching
add support for new chip rts524A.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c| 186 ---
drivers/mfd/rtsx_pcr.c | 25 +-
drivers/mfd/rtsx_pcr.h | 7 ++
include/linux/mfd/rtsx_pci.h | 125
From: Micky Ching
To enable/disable ASPM we should find LINK CONTROL register
in PCI config space. All old chip use 0x80 address, but new
chip may use another address, so we using pci_find_capability()
to get LINK CONTROL address.
rtsx_gops.c was removed, we consider to put some common
From: Micky Ching
pcr_dbg is a wrapper of dev_dbg, which can save some code,
and help to enable/disable debug message static.
Signed-off-by: Micky Ching
---
drivers/mfd/rtl8411.c | 11 +--
drivers/mfd/rts5209.c | 4 ++--
drivers/mfd/rts5227.c | 4 ++--
drivers/mfd/rts5229.c | 4
From: Micky Ching
add support for new chip rts525A.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c| 104 ++-
drivers/mfd/rtsx_pcr.c | 13 --
drivers/mfd/rtsx_pcr.h | 1 +
include/linux/mfd/rtsx_pci.h | 15 +++
4
From: Micky Ching
It is more readable to place register address and values define
togather. The values define add two leading space indicate belong
to the register address defined above.
Signed-off-by: Micky Ching
---
include/linux/mfd/rtsx_pci.h | 836
Add register offset table entry for the newer (v1.7.0) version of the BAM IP
found on MSM8916. Update the DT bindings documentation.
Signed-off-by: Archit Taneja
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 1 +
drivers/dma/qcom_bam_dma.c | 30
From: Micky Ching
update card drive settings, This setting can be used for rts5249
rts524A and rts525A.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/rts5249.c b/drivers/mfd/rts5249.c
index
From: Micky Ching
update phy register value and using direct value instead of macros.
It is much easier to debug using constant value than a lot of macros.
We usually need compare the value directly to check the configure.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5249.c| 55
From: Micky Ching
PETXCFG is defined at 0xFF03, the old 0xFE49 not used any more.
Signed-off-by: Micky Ching
---
drivers/mfd/rts5227.c| 6 ++
drivers/mfd/rts5249.c| 6 ++
include/linux/mfd/rtsx_pci.h | 2 +-
3 files changed, 5 insertions(+), 9 deletions(-)
diff --git
From: Micky Ching
v2:
- remove debug info when access failed.
- using macro list for phy register init.
- rename function for multi chip prefix with rtsx_base_
- save pcie_cap offset when init chip, not calling pci_find_capacity()
every time.
- add pcr->ops: write_phy/read_phy for special
From: Micky Ching
Re-format coding-style, using uniform SPC after "#define" keyword
instead of mixing using TAB and SPC.
Signed-off-by: Micky Ching
---
include/linux/mfd/rtsx_pci.h | 254 +--
1 file changed, 127 insertions(+), 127 deletions(-)
diff
On Wed, 21 Jan 2015, Jiri Olsa wrote:
>
> However if we revert this code, we'll loose nice (and standard) way
> to check if the event is still valid.. not sure how to handle this.
there's likely no need to revert as my code wasn't really released and
I've already fixed it to work with the new
Fixes the sparse warning issue of the incorrect type in assignment which
found by the kbuild test robot.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 80
1 file changed, 41 insertions(+), 39 deletions(-)
diff --git
Fixes the warning issue of the variable dereferenced before check
'gen5_pip->resp_len' report by dan Carpenter.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/input/mouse/cyapa_gen5.c
Hi, Octavian
> From: Octavian Purdila [mailto:octavian.purd...@intel.com]
> Sent: Saturday, January 17, 2015 2:03 PM
>
> On Fri, Jan 16, 2015 at 11:44 AM, Zheng, Lv wrote:
> > Hi, Octavian
> >
>
> Hi Lv,
>
> > I noticed there are 2 patches you've sent to the community.
> > But unfortunately I
mp_query_drv_var() was only being used by
oid_rt_pro_query_dr_variable_hdl() but after commit
mp_query_drv_var() became
unused. so it is safe to remove it.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/rtl8712/rtl871x_mp_ioctl.c | 7 ---
1 file changed, 7 deletions(-)
diff --git
Hi,
On 01/21/2015 06:24 AM, Daniel Ehrenberg wrote:
On Fri, Jan 16, 2015 at 6:48 AM, Archit Taneja wrote:
+/*
+ * the bad block marker is readable only when we read the page with ECC
+ * disabled. all the read/write commands like NAND_CMD_READOOB, NAND_CMD_READ0
+ * and NAND_CMD_PAGEPROG are
Add a new kconfig option VMACACHE_SHIFT (as a power of 2) to specify the
number of slots vma cache has for each thread. Range is chosen 0-4 (1-16
slots) to consider both overhead and performance penalty. Default is 2
(4 slots) as it originally is, which provides good enough balance.
On Wed, Jan 21, 2015 at 09:44:10PM -0800, Nicolin Chen wrote:
> On Thu, Jan 22, 2015 at 12:55:35PM +0800, Zidan Wang wrote:
> > On Wed, Jan 21, 2015 at 10:08:03AM -0800, Nicolin Chen wrote:
> > > On Tue, Jan 20, 2015 at 08:21:19PM +0800, Zidan Wang wrote:
> > > > @@ -369,10 +380,25 @@ static int
On 01/21/2015 05:16 PM, Thomas Gleixner wrote:
> On Tue, 20 Jan 2015, Preeti U Murthy wrote:
>> diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
>> index 5544990..f3907c9 100644
>> --- a/kernel/time/clockevents.c
>> +++ b/kernel/time/clockevents.c
>> @@ -568,6 +568,7 @@ int
This was generated from 3.14 kernel, but since its so small it will likely
apply to newer
kernels without issue.
A lesser travelled code path specifically crafted for "tx interrupt buggy"
UARTs seems to be testing the wrong bit for whether or not to prime the
transmit pump. The result is that
Hi,
Since 3.18.2 I am getting the oops below during boot whilst running as a dom0
under xen 4.4.1 / 4.5.0. Is this a known issue or worth bisecting to identify
the exact commit which causes this?
Thanks,
James
[ 173.735541] BUG: unable to handle kernel NULL pointer dereference at
2015-01-22 8:34 GMT+03:00 Andrey Ryabinin :
> 2015-01-22 3:22 GMT+03:00 Sasha Levin :
>> On 01/21/2015 11:51 AM, Andrey Ryabinin wrote:
>>> Changes since v8:
>>> - Fixed unpoisoned redzones for not-allocated-yet object
>>> in newly allocated slab page. (from Dmitry C.)
>>>
>>>
On Thu, 22 Jan 2015 16:14:02 +1100 Stephen Rothwell
wrote:
> Hi Andrew,
>
> On Wed, 21 Jan 2015 19:34:11 -0800 Andrew Morton
> wrote:
> >
> > On Thu, 22 Jan 2015 10:51:23 +0900 Joonsoo Kim
> > wrote:
> >
> > > > The most recent -mmotm was a bit of a trainwreck. I'm scrambling to
> > > >
On Thu, Jan 22, 2015 at 01:13:46PM +0800, Zidan Wang wrote:
> On Wed, Jan 21, 2015 at 10:53:20AM -0800, Nicolin Chen wrote:
> > On Tue, Jan 20, 2015 at 08:21:20PM +0800, Zidan Wang wrote:
> > > Add Right-J mode and set TCR5 FBT bit to let data right justify.
> > >
> > > Signed-off-by: Zidan Wang
On Thu, Jan 22, 2015 at 12:55:35PM +0800, Zidan Wang wrote:
> On Wed, Jan 21, 2015 at 10:08:03AM -0800, Nicolin Chen wrote:
> > On Tue, Jan 20, 2015 at 08:21:19PM +0800, Zidan Wang wrote:
> > > @@ -369,10 +380,25 @@ static int fsl_sai_hw_params(struct
> > > snd_pcm_substream *substream,
> > >
(If Steven Rostedt accept the previous patch which introduce a priv
field to 'struct format_field', we can use a relative simple method
for name conversion. If not , perf must track name conversion by
itself.)
Some parameters of syscall tracepoints named as 'nr', 'event', etc.
When dealing
In https://lkml.org/lkml/2015/1/21/383 , Jiri Olsa gives a suggestion
about changing lib traceevent to solve a bug of perf-convert-to-ctf,
which is related to duplicated field names. I think his suggestion
should be something like this patch.
Signed-off-by: Wang Nan
---
Hi Jiri Olsa and Steven Rostedt (and others),
Here I post 2 patches. Patch 1 is for Steven Rostedt for his question:
https://lkml.org/lkml/2015/1/21/397
(Jiri, I hope you don't mind me posting this patch if you are working on
it. I just want to solve the problem.)
The second patch is for
On 01/21/2015 06:21 PM, Huang Ying wrote:
FYI, we noticed the below changes on
commit 34b48db66e08ca1c1bc07cf305d672ac940268dc ("block: remove artifical
max_hw_sectors cap")
testbox/testcase/testparams:
lkp-ws02/fileio/600s-100%-1HDD-btrfs-64G-1024f-seqrewr-sync
c2661b806092d8ea
On 01/21/2015 08:59 PM, Paul Moore wrote:
This patchset has some important changes from the previous revision,
namely a fix from Al Viro (included in 2/5) that resolves a boot panic
on some systems as well as some smaller, less noteworthy fixes found
in the linux-next announcement thread from
2015-01-22 3:22 GMT+03:00 Sasha Levin :
> On 01/21/2015 11:51 AM, Andrey Ryabinin wrote:
>> Changes since v8:
>> - Fixed unpoisoned redzones for not-allocated-yet object
>> in newly allocated slab page. (from Dmitry C.)
>>
>> - Some minor non-function cleanups in kasan
On 01/21/2015 09:22 PM, Jisheng Zhang wrote:
Dear Doug,
On Wed, 21 Jan 2015 15:17:22 -0800
Doug Anderson wrote:
On some dw_wdt implementations the "top" register may be initted to 0
at bootup. In such a case, each "pat" of the watchdog will reset the
timer to 0x. That's pretty short.
Dear Doug,
On Wed, 21 Jan 2015 15:17:22 -0800
Doug Anderson wrote:
> On some dw_wdt implementations the "top" register may be initted to 0
> at bootup. In such a case, each "pat" of the watchdog will reset the
> timer to 0x. That's pretty short.
+ Guenter Roeck
This should have been
As ARM ARM says, the bit 19-16 of ID_MMFR1 is always 0b because
ARMv7 requires a hierarchical cache implementation.
The line "mcrp15, 0, r10, c7, c14, 0" is not reachable.
Moreover, the v7_flush_dcache_all in arch/arm/mm/cache-v7.S does not
check the ID_MMFR1.
Signed-off-by: Masahiro
Below comments got from Page4724 of Reference Manual of i.mx6q:
http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf
--"Static context mode should be used for the first channel called
after reset to ensure that the all context RAM for that channel is
initialized during the context
On Wed, 2015-01-21 at 21:26 -0500, Pranith Kumar wrote:
> When CONFIG_PRINTK=n, log_buf_addr_get() returns NULL and log_buf_len_get()
> return 0. Check for these return values and skip registering the dump buffer.
>
> Signed-off-by: Pranith Kumar
> CC: Michael Ellerman
> ---
>
On Thu, Jan 22, 2015 at 11:08:11AM +0800, Zhang Zhen wrote:
> On 2015/1/22 4:06, Paul E. McKenney wrote:
> > On Wed, Jan 21, 2015 at 10:10:51AM -0500, Don Zickus wrote:
> >> On Wed, Jan 21, 2015 at 10:26:27AM +0800, Zhang Zhen wrote:
> This may not cause other problems but what happens if you
Hi Andrew,
On Wed, 21 Jan 2015 19:34:11 -0800 Andrew Morton
wrote:
>
> On Thu, 22 Jan 2015 10:51:23 +0900 Joonsoo Kim wrote:
>
> > > The most recent -mmotm was a bit of a trainwreck. I'm scrambling to
> > > get the holes plugged so I can get another mmotm out today.
> >
> > Another mmotm
On Wed, Jan 21, 2015 at 10:53:20AM -0800, Nicolin Chen wrote:
> On Tue, Jan 20, 2015 at 08:21:20PM +0800, Zidan Wang wrote:
> > Add Right-J mode and set TCR5 FBT bit to let data right justify.
> >
> > Signed-off-by: Zidan Wang
>
> > - if (sai->is_lsb_first)
> > + if (sai->is_lsb_first &&
Vince,
On Wed, Jan 21, 2015 at 10:55 AM, Vince Weaver wrote:
> Hello
>
> on my haswell system, running 3.19-rc5, and with
> echo "0" > /proc/sys/kernel/perf_event_paranoid
>
> I can easily crash my system with the attached test program that simply
> opens a RAPL event and then closes it.
Hi,
On Thu, Jan 22, 2015 at 01:06:38PM +0900, Beomho Seo wrote:
> This patchset adds driver for Richtek rt5033 chip The chip contains
> switching charge mode Li-Ion/Li-Polymer battery charger, fuelgauge.
> Additionally, This includes document for device tree of RT5033 device.
Thanks, applied.
On Wed, Jan 21, 2015 at 09:27:41PM -0500, Sasha Levin wrote:
> On 01/21/2015 08:59 PM, Joonsoo Kim wrote:
> > On Tue, Jan 20, 2015 at 11:31:43PM -0500, Sasha Levin wrote:
> >> > Commit "mm/slub: optimize alloc/free fastpath by removing preemption
> >> > on/off"
> >> > has added access to percpu
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in
arch/arm64/kvm/Kconfig between commit 83fe27ea5311 ("rcu: Make SRCU
optional by using CONFIG_SRCU") from the rcu tree and commit
7276030a082c ("KVM: arm/arm64: Enable Dirty Page logging for ARMv8")
from the kvm-arm tree.
I
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in
arch/arm64/include/asm/kvm_arm.h between commit 6e53031ed840 ("arm64:
kvm: remove ESR_EL2_* macros") from the arm64 tree and commit
0d97f8848104 ("arm/arm64: KVM: add tracing support for arm64 exit
handler") from the kvm-arm
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in
arch/arm64/kvm/handle_exit.c between commit c6d01a947a51 ("arm64: kvm:
move to ESR_ELx macros") from the arm64 tree and commit 0d97f8848104
("arm/arm64: KVM: add tracing support for arm64 exit handler") from the
kvm-arm tree.
Enable recording of filenames in getname_kernel() and remove the
kludgy workaround in __audit_inode() now that we have proper filename
logging for kernel users.
CC: v...@zeniv.linux.org.uk
CC: linux-fsde...@vger.kernel.org
Signed-off-by: Paul Moore
Reviewed-by: Richard Guy Briggs
---
This patchset has some important changes from the previous revision,
namely a fix from Al Viro (included in 2/5) that resolves a boot panic
on some systems as well as some smaller, less noteworthy fixes found
in the linux-next announcement thread from January 20th (refcount bump
in
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in
arch/arm/kvm/Kconfig between commit 83fe27ea5311 ("rcu: Make SRCU
optional by using CONFIG_SRCU") from the rcu tree and commit
53c810c364d7 ("KVM: arm: dirty logging write protect support") from the
kvm-arm tree.
I fixed it
In order to ensure that filenames are not released before the audit
subsystem is done with the strings there are a number of hacks built
into the fs and audit subsystems around getname() and putname(). To
say these hacks are "ugly" would be kind.
This patch removes the filename hackery in favor
In preparation for expanded use in the kernel, make getname_kernel()
more useful by allowing it to handle any legal filename length.
Thanks to Guenter Roeck for his suggestion to substitute memcpy() for
strlcpy().
CC: li...@roeck-us.net
CC: v...@zeniv.linux.org.uk
CC:
There are several areas in the kernel that create temporary filename
objects using the following pattern:
int func(const char *name)
{
struct filename *file = { .name = name };
...
return 0;
}
... which for the most part
在 2015年01月22日 12:25, Daniel Kurtz 写道:
On Thu, Jan 22, 2015 at 12:21 PM, Caesar Wang
wrote:
在 2015年01月22日 12:01, Daniel Kurtz 写道:
On Thu, Jan 22, 2015 at 1:29 AM, Caesar Wang wrote:
In general, the kernel should report temperature readings exactly as
reported by the hardware. The cpu / gpu
In all likelihood there were some subtle, and perhaps not so subtle,
bugs with filename matching in audit_inode() and audit_inode_child()
for some time, however, recent changes to the audit filename code have
definitely broken the filename matching code. The breakage could
result in duplicate
On Wed, Jan 21, 2015 at 10:08:03AM -0800, Nicolin Chen wrote:
> On Tue, Jan 20, 2015 at 08:21:19PM +0800, Zidan Wang wrote:
> > @@ -369,10 +380,25 @@ static int fsl_sai_hw_params(struct snd_pcm_substream
> > *substream,
> > u32 word_width = snd_pcm_format_width(params_format(params));
> >
Aarch64 ELF files use mapping symbols with special names $x, $d
to identify regions of Aarch64 code (see Aarch64 ELF ABI - "ARM
IHI 0056B", section "4.5.4 Mapping symbols").
The patch filters out these symbols at load time, similar to
"696b97a perf symbols: Ignore mapping symbols on ARM" changes
Both Arm and Aarch64 ELF ABI allow mapping symbols be in from
either "$d" or "$d.". But current code that handles mapping
symbols only deals with the first, dollar character and a single
letter, case.
The patch adds handling of the second case with period
followed by any characters.
Currently code that tries to read corresponding debug symbol
file from .gnu_debuglink section (DSO_BINARY_TYPE__DEBUGLINK)
does not take in account symfs option, so filename__read_debuglink
function cannot open ELF file, if symfs option is used.
Fix is to add proper handling of symfs as it is
Hi Folks,
Here is second version of mini-series that addresses couple issues
in perf symbols handling.
Changes since V1:
o 'perf symbols: Ignore mapping symbols on aarch64': based on feedback
from Will Deacon and Russell King [1] added code that handles ARM/Aarch64
mapping symbols like "$d.".
On Thursday, January 22, 2015 04:12:41 AM Al Viro wrote:
> On Wed, Jan 21, 2015 at 09:28:51PM -0500, Paul Moore wrote:
> > Al, do you mind if I fold your patch below into the existing patches?
>
> No problem, but I'd probably prefer to put this series through vfs.git.
> With the following as the
On Wed, 2015-01-21 at 22:39 -0600, Andy Gross wrote:
> Added myself as a co-maintainer. Updated the files to include the Qualcomm
> SoC
> directory. Added linux-soc mailing list.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -1284,9 +1284,12 @@ S: Maintained
> ARM/QUALCOMM SUPPORT
>
On Tue, Jan 13, 2015 at 8:20 PM, Marek Szyprowski
wrote:
> Hello,
>
> On 2015-01-13 09:45, Alexandre Courbot wrote:
>>
>> Ping? This patch still seems to be needed as of today...
>
>
> Arnd, could you take this patch together with your other pending
> dma-mapping.h changes?
Arnd, gentle ping on
Added myself as a co-maintainer. Updated the files to include the Qualcomm SoC
directory. Added linux-soc mailing list.
Signed-off-by: Andy Gross
---
MAINTAINERS |3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 93409ad..2af6e23 100644
--- a/MAINTAINERS
On Thu, 22 Jan 2015 04:23:30 +
Al Viro wrote:
> I would recommend against that - kernfs is overburdened by their need
> to accomodate cgroup weirdness. IMO it's not a good model for
> anything, other than an anti-hard-drugs poster ("don't shoot that
> shit, or you might end up hallucinating
1 - 100 of 1876 matches
Mail list logo
