Hi Linus,
I have been using the following patch as a merge resolution in the
merge of the usb tree for a while now. Greg seems to have missed it
when asking you to merge his tree ... It now applies cleanly to your
tree.
Fr
On pondělí 25. července 2016 8:41 Florian Westphal wrote:
> Michal Kubecek wrote:
> > On Thu, Jul 21, 2016 at 09:00:33PM +0200, Jiri Slaby wrote:
> > > On 07/21/2016, 08:56 PM, Greg KH wrote:
> > > > On Thu, Jul 21, 2016 at 08:36:18AM +0200, Jiri Slaby wrote:
> > > >> On 07/14/2016, 10:15 AM, Jiri
Hi, Bibby:
On Mon, 2016-07-25 at 14:24 +0800, Bibby Hsieh wrote:
> Hi, CK,
>
> Thanks for your comments.
>
> On Wed, 2016-07-20 at 15:57 +0800, CK Hu wrote:
> > Hi, Bibby:
> >
> > Some comments inline.
> >
> > On Wed, 2016-07-20 at 12:03 +0800, Bibby Hsieh wrote:
> > > From: Junzhi Zhao
> > >
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/ext4_for_linus
for you to fetch changes up to 7bc9491645118c9461b
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git
tags/random_for_linus
for you to fetch changes up to 86a574de4590ffe
Hi all,
Please do not add material destined for v4.9 to your linux-next included
branches until after v8.1-rc1 has been released.
--
Cheers,
Stephen Rothwell
On Mon, Jul 25, 2016 at 12:55:55AM +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on stable/master]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Borislav-Petkov/pri
* Andy Lutomirski wrote:
> On Mon, Jun 20, 2016 at 4:39 PM, Andy Lutomirski wrote:
> > Setting TS_COMPAT in ptrace is wrong: if we happen to do it during
> > syscall entry, then we'll confuse seccomp and audit. (The former
> > isn't a security problem: seccomp is currently entirely insecure if
* Paul Gortmaker wrote:
> These files were only including module.h for exception table
> related functions. We've now separated that content out into its
> own file "extable.h" so now move over to that and avoid all the
> extra header content in module.h that we don't really need to compile
> t
Hi all,
On Tue, 14 Jun 2016 15:07:37 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/lustre/lustre/llite/lloop.c
>
> between commit:
>
> 95fe6c1a209e ("block, fs, mm, drivers: use bio set/get op accessors")
>
> from th
Hi all,
On Mon, 20 Jun 2016 14:33:53 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/android/sync.h
>
> between commit:
>
> 76bf0db55439 ("dma-buf/fence: make fence context 64 bit v2")
>
> from the drm tree and commits
Hi, Philipp,
Thanks for your comment.
On Wed, 2016-07-20 at 11:41 +0200, Philipp Zabel wrote:
> Am Mittwoch, den 20.07.2016, 12:03 +0800 schrieb Bibby Hsieh:
> > From: Junzhi Zhao
> >
> > Pixel clock should be 297MHz when resolution is 4K.
> >
> > Signed-off-by: Junzhi Zhao
> > Signed-off-by:
Hi, CK,
Thanks for your comments.
On Wed, 2016-07-20 at 15:57 +0800, CK Hu wrote:
> Hi, Bibby:
>
> Some comments inline.
>
> On Wed, 2016-07-20 at 12:03 +0800, Bibby Hsieh wrote:
> > From: Junzhi Zhao
> >
> > Pixel clock should be 297MHz when resolution is 4K.
> >
> > Signed-off-by: Junzhi Z
On Sun, Jul 24, 2016 at 3:56 PM, Jonathan Cameron wrote:
> On 21/07/16 15:41, Pratik Prajapati wrote:
>> Signed-off-by: Pratik Prajapati
>> ---
>> drivers/iio/light/vcnl4000.c | 91
>> +---
>> 1 file changed, 78 insertions(+), 13 deletions(-)
>>
>> diff -
Hi all,
Changes since 20160724:
The powerpc tree still had its build failure for which I applied a fix patch.
The vfs tree gained conflicts against the f2fs and overlayfs trees.
The nvdimm tree gained a conflict against the kvm tree.
Non-merge commits (relative to Linus' tree): 11060
In dev_pm_opp_set_rate(), _find_opp_table() is called 4 times: once by
_get_opp_clk(), once by dev_pm_opp_set_rate() itself, and twice by
dev_pm_opp_find_freq_ceil(). If there are several opp_tables in the
system, three times of opp table finding is a big waste. This patch
reduced the call of _find
Hi, CK,
I'm appreciate your comment.
On Wed, 2016-07-20 at 15:15 +0800, CK Hu wrote:
> Hi, Bibby:
>
> One comment inline.
>
> On Wed, 2016-07-20 at 12:03 +0800, Bibby Hsieh wrote:
> > From: Junzhi Zhao
> >
> > In order to improve 4K resolution performance,
> > we have to enhance the HDMI driv
Provide support for PSU DPS-460, DPS-800 from Delta Electronics, INC and for
SGD009 from Acbel Polytech, INC.
These devices do not support the STATUS_CML register, and reports a
communication error in response to this command.
For this reason, the status register check is disabled for these control
modify get_qe_base function with of_address_to_resource
instead of of_get_property and of_translate_address.
Signed-off-by: Zhao Qiang
---
Changes for v2:
- na
Changes for v3:
- na
Changes for v4:
- na
Changes for v5:
- na
drivers/soc/fsl/qe/qe.c | 10 +-
On Mon, 25 Jul 2016 13:19:47 +0800 Jisheng Zhang wrote:
> Dear all,
>
> On Fri, 22 Jul 2016 22:30:53 +0800 kbuild test robot wrote:
>
> > Hi,
> >
> > [auto build test WARNING on pm/linux-next]
> > [also build test WARNING on v4.7-rc7 next-20160722]
> > [if your patch is applied to the wrong git
Hi,
[auto build test ERROR on stable/master]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Steve-Longerbeam/IPUv3-prep-for-i-MX5-6-v4l2-staging-drivers-v2/20160725-010817
base: https://git.ke
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the standard interface.
As I already mentioned[1] on previous mail, devfreq fwk support
the standard DEVFREQ_TRANSITION_NOTIFIER notifier which has the two
notifications.
- DEV
Ulf,
On Saturday 23 July 2016 03:09 PM, Ulf Hansson wrote:
> On 29 June 2016 at 17:18, Doug Anderson wrote:
>> Kishon,
>>
>> On Wed, Jun 29, 2016 at 6:49 AM, Kishon Vijay Abraham I
>> wrote:
>>> Hi,
>>>
>>> On Monday 27 June 2016 11:09 PM, Douglas Anderson wrote:
It's possible that there a
QE was supported on PowerPC, and dependent on PPC,
Now it is supported on other platforms. so remove PPCisms.
Signed-off-by: Zhao Qiang
---
Changes for v2:
- na
Changes for v3:
- add NO_IRQ
Changes for v4:
- modify spin_event_timeout to opencoded timeout loop
- rem
Hi
On Wed, Jul 20, 2016 at 12:23:22PM +0100, Lorenzo Pieralisi wrote:
> This RFC patch series is v3 of a previous posting:
>
> https://lkml.org/lkml/2016/6/7/523
>
> v2 -> v3
> - Rebased on top of dependencies series [1][2][3](v4.7-rc3)
> - Added back reliance on ACPI early probing in
On Thu, Jul 21, 2016 at 09:00:33PM +0200, Jiri Slaby wrote:
> On 07/21/2016, 08:56 PM, Greg KH wrote:
> > On Thu, Jul 21, 2016 at 08:36:18AM +0200, Jiri Slaby wrote:
> >> On 07/14/2016, 10:15 AM, Jiri Slaby wrote:
> >>> From: Florian Westphal
> >>>
> >>> 3.12-stable review patch. If anyone has an
> Subject: RE: Why does BIOS assign memory to 16 byte BAR
>
> > Subject: Re: Why does BIOS assign memory to 16 byte BAR
> >
> > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote:
> > > Hi Bharat,
> > >
> > > On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote:
> > > > H
Dear all,
On Fri, 22 Jul 2016 22:30:53 +0800 kbuild test robot wrote:
> Hi,
>
> [auto build test WARNING on pm/linux-next]
> [also build test WARNING on v4.7-rc7 next-20160722]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
>
Hi,
Chunhui He wrote:
> Hi,
>
> On Fri, 22 Jul 2016 10:20:01 +0300 (EEST), Julian Anastasov
> wrote:
>>
>> Hello,
>>
>> On Thu, 21 Jul 2016, Chunhui He wrote:
>>
>>> If neigh entry was CONNECTED and address is not changed, and if new state is
>>> STALE, entry state will not change. Because
In dev_pm_opp_set_rate(), _find_opp_table() is called 4 times: once by
_get_opp_clk(), once by dev_pm_opp_set_rate() itself, and twice by
dev_pm_opp_find_freq_ceil(). If there are several opp_tables in the
system, three times of opp table finding is a big waste. This patch
reduced the call of _find
Dear Viresh,
On Fri, 22 Jul 2016 09:21:51 -0700 Viresh Kumar wrote:
> On 22-07-16, 20:42, Jisheng Zhang wrote:
> > static int _set_opp_voltage(struct device *dev, struct regulator *reg,
> > unsigned long u_volt, unsigned long u_volt_min,
> > unsig
From: Kristian Evensen
Date: Thu, 21 Jul 2016 11:10:06 +0200
> The firmware in several ZTE devices (at least the MF823/831/910
> modems/mifis) use OS fingerprinting to determine which type of device to
> export. In addition, these devices export a REST API which can be used to
> control the type
cheng...@emindsoft.com.cn writes:
> From: Chen Gang
>
> For pure bool function's return value, bool is a little better more or
> less than int.
>
> Signed-off-by: Chen Gang
> ---
> arch/powerpc/include/asm/mman.h | 8
> include/linux/mman.h| 2 +-
> 2 files changed, 5 inser
On Sat, Jul 23, 2016 at 5:07 AM, Bjorn Helgaas wrote:
>
> On Tue, Jun 21, 2016 at 04:53:11PM +0800, Ley Foon Tan wrote:
> > This 2 patches fix the issue before and after retrain link.
> >
> > Ley Foon Tan (2):
> > PCI: altera: check link status before retrain link
> > PCI: altera: Polling for
On Tue, Jul 19, 2016 at 10:49:57AM -0700, Joe Perches wrote:
> On Tue, 2016-07-19 at 20:26 +0300, Leon Romanovsky wrote:
> > On Tue, Jul 19, 2016 at 02:09:25PM +0300, Netanel Belgazal wrote:
> > > This is the debugging message interface.
> > > https://www.kernel.org/doc/Documentation/networking/net
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
arch/x86/kvm/vmx.c
between commits:
64672c95ea4c ("kvm: vmx: hook preemption timer support")
37e4c997dadf ("KVM: VMX: validate individual bits of guest
MSR_IA32_FEATURE_CONTROL")
from the kvm tree and commit:
dfa1
Hello Arnd,
thanks for patch. it looks ok.
Acked-by: Abylay Ospan
2016-07-13 16:42 GMT-04:00 Arnd Bergmann :
> The addition of jump label support in dynamic_debug caused an unexpected
> warning in exactly one file in the kernel:
>
> drivers/media/dvb-frontends/cxd2841er.c: In function 'cxd2841e
On Sun, Jul 24, 2016 at 8:42 PM, Paul Gortmaker
wrote:
>
> While doing an audit looking for unnecessary instances of module.h
> inclusion across arch/x86/ I found a significant number of includes
> of module.h were for things like search_exception_table and friends.
>
> For historical reasons (i.e
Hi Rich,
On Sun, 24 Jul 2016 23:57:30 -0400 Rich Felker wrote:
>
> If it's acceptable I'll rebase this change into sh for-next and the
> patch I send to the subsystem maintainer.
Sure.
--
Cheers,
Stephen Rothwell
Hi Rich,
On Sun, 24 Jul 2016 23:55:03 -0400 Rich Felker wrote:
>
> On Sun, Jul 24, 2016 at 03:13:42PM +1000, Stephen Rothwell wrote:
> >
> > Today's linux-next merge of the tip tree got a conflict in:
> >
> > arch/sh/include/asm/spinlock.h
> >
> > between commit:
> >
> > 2da83dfce7df ("sh
From: Hiraku Toyooka
This enables pmsg to deal with multiple instances. One possible
use is content priority control on limited persistent store space. By
using different buffers, we can prevent important messages from being
overwritten by less important messages.
When pstore backend module spec
From: Hiraku Toyooka
To test multiple pmsg, we should check that /dev/pmsg[N] (N > 0) is
available. After reboot, we should check that pmsg-[backend]-[N] which
keeps content is detected even if pmsg-[backend]-[N-M] (0 < M <= N)
doesn't exist due to lack of contents.
So this adds the following te
From: Hiraku Toyooka
persistent_ram_zone(=prz) structures are allocated by persistent_ram_new(),
which includes vmap() or ioremap(). But they are currently freed by
kfree(). This uses persistent_ram_free() for correct this asymmetry usage.
Signed-off-by: Hiraku Toyooka
Signed-off-by: Nobuhiro I
From: Hiraku Toyooka
We modifies initialization and freeing code for prz for generic usage.
This change
* add generic function __ramoops_init_prz() to reduce redundancy
between ramoops_init_prz() and ramoops_init_przs().
* rename 'przs' member in struct ramoops_context to 'dprzs' so that
The following series implements multiple pmsg. This feature allows
userspace program to control individual content aging or priority.
If a pstore backend module(e.g. ramoops) requires the multiple pmsg
instances when registering itself to pstore, multiple /dev/pmsg[ID]
are created. Writes to each
From: Hiraku Toyooka
This enables ramoops to deal with multiple pmsg instances.
A User can configure the size of each buffers by its module parameter
as follows.
pmsg_size=0x1000,0x2000,...
Then, the ramoops allocates multiple buffers and tells the number
of buffers to pstore to create multip
On Sun, Jul 24, 2016 at 05:55:01PM +1000, Stephen Rothwell wrote:
> Hi Rich,
>
> After merging the sh tree, today's linux-next build (powerpc allyesconfig)
> failed like this:
>
> drivers/clocksource/jcore-pit.c:145:20: error: conflicting types for
> 'timer_interrupt'
> static irqreturn_t timer
On Sun, Jul 24, 2016 at 03:13:42PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> arch/sh/include/asm/spinlock.h
>
> between commit:
>
> 2da83dfce7df ("sh: add J2 atomics using the cas.l instruction")
>
> from the sh tree and co
On Sun, Jul 24, 2016 at 11:00:12AM +1000, Stephen Rothwell wrote:
> Hi Rich,
>
> After merging the sh tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-jcore.o
>
> Introduced by commit
>
> 8c7f438f06
With hopefully most/all users of module.h that were looking for
exception table functions moved over to the new extable.h header,
we can remove the back-compat include that let us transition
without introducing build regressions.
Cc: Rusty Russell
Cc: Andrew Morton
Cc: Linus Torvalds
Signed-off
[RFC: Not looking for detailed review given the merge window is open.
As long as nobody thinks the general idea is horrible, I'll expand into
more fringe arch and resend in 2wks and get it added then to linux-next.]
While doing an audit looking for unnecessary instances of module.h
inclusion acr
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Richard Henderson
C
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Chris Metcalf
Signe
This file was only including module.h for exception table related
functions. We've now separated that content out into its own file
"extable.h" so now move over to that and avoid all the extra header
content in module.h that we don't really need to compile this.
Cc: Geert Uytterhoeven
Cc: linux-
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Russell King
Cc: li
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Catalin Marinas
Cc:
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
The additions of uaccess
These files were including module.h for exception table related
functions. We've now separated that content out into its own file
"extable.h" so now move over to that and where possible, avoid all
the extra header content in module.h that we don't really need to
compile these non-modular files.
N
This file was only including module.h for exception table related
functions. We've now separated that content out into its own file
"extable.h" so now move over to that and avoid all the extra header
content in module.h that we don't really need to compile this file.
Cc: "James E.J. Bottomley"
C
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Thomas Gleixner
Cc:
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Benjamin Herrenschmi
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: Ralf Baechle
Cc: li
For historical reasons (i.e. pre-git) the exception table stuff was
buried in the middle of the module.h file. I noticed this while
doing an audit for needless includes of module.h and found core
kernel files (both arch specific and arch independent) were just
including module.h for this.
The con
These files were only including module.h for exception table
related functions. We've now separated that content out into its
own file "extable.h" so now move over to that and avoid all the
extra header content in module.h that we don't really need to compile
these files.
Cc: "David S. Miller"
C
Acked-by: Punit Agrawal
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
v2: No change
drivers/hwmon/hwmon.c | 16
include/linux/hwmon.h | 27 +++
2 files changed, 43 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/driver
Add basic pwm attribute support (no auto attributes) to new API.
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v2: No change
v2: Added patch
Documentation/hwmon/hwmon-kernel-api.txt | 2 ++
drivers/hwmon/hwmon.c| 9 +
include/linux/hwmon.h
Acked-by: Punit Agrawal
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
drivers/hwmon/hwmon.c | 20
include/linux/hwmon.h | 29 +
2 files changed, 49 insertions(+)
diff --git a/drivers/hwmon/hwmon.c b/drivers/hwmon/
Acked-by: Punit Agrawal
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
v2: No change
drivers/hwmon/hwmon.c | 30
include/linux/hwmon.h | 54 +++
2 files changed, 84 insertions(+)
diff --
Up to now, each hwmon driver has to implement its own sysfs attributes.
This requires a lot of template code, and distracts from the driver's core
function to read and write chip registers.
To be able to reduce driver complexity, move sensor attribute handling
and thermal zone registration into hw
Up to now, each hwmon driver has to implement its own sysfs attributes.
This requires a lot of template code, and distracts from the driver's
core function to read and write chip registers.
To be able to reduce driver complexity, move sensor attribute handling
and thermal zone registration into th
Acked-by: Punit Agrawal
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
v2: No change
drivers/hwmon/hwmon.c | 21 +
include/linux/hwmon.h | 36
2 files changed, 57 insertions(+)
diff --git a/drivers/hwmon/hw
Describe the new registration API function as well as the data
structures it requires.
Acked-by: Punit Agrawal
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
v2: Fixed typos
Documentation/hwmon/hwmon-kernel-api.txt | 229 ++-
1 file ch
Ordering include files alphabetically makes it easier to add new ones.
Stop including linux/spinlock.h and linux/kdev_t.h since both are not
needed.
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
v2: Added patch
drivers/hwmon/hwmon.c | 10 --
1 file change
Acked-by: Punit Agrawal
Reviewed-by: Jonathan Cameron
Signed-off-by: Guenter Roeck
---
v3: No change
v2: No change
drivers/hwmon/hwmon.c | 21 +
include/linux/hwmon.h | 35 +++
2 files changed, 56 insertions(+)
diff --git a/drivers/hwmon/hwm
Hi Linus,
Please pull hwmon updates for Linux v4.8 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v4.8
Thanks,
Guenter
--
The following changes since commit 4c2e07c6a29e0129e975727b9f57eede813eea85:
Linux 4.7-rc5 (2016-06-26 1
Hi He,
Thanks for your response firstly.
On Fri, 2016-07-22 at 18:40 +0800, Baoquan He wrote:
> Hi Jiangang,
>
> This is very nice, should be the stuff Eric and Ingo would like to see.
> But I have several questions:
>
> 1) Are you not going to clean up the old legacy irq mode setting code in
>
On 07/24/2016 12:08 PM, Jonathan Cameron wrote:
On 17/07/16 06:30, Guenter Roeck wrote:
Up to now, each hwmon driver has to implement its own sysfs attributes.
This requires a lot of template code, and distracts from the driver's core
function to read and write chip registers.
To be able to red
From: Geert Uytterhoeven
None of the code under drivers/sh/ is used anymore on Renesas ARM.
Signed-off-by: Geert Uytterhoeven
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7304d2e37a98..e6bf58769b49 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
From: Geert Uytterhoeven
Since commits 71d076ceb245f0d9 ("ARM: shmobile: Enable PM and
PM_GENERIC_DOMAINS for SoCs with PM Domains") and 2ee98234b88174f2
("arm64: renesas: Enable PM and PM_GENERIC_DOMAINS for SoCs with PM
Domains"), CONFIG_PM and CONFIG_PM_GENERIC_DOMAINS are enabled
unconditiona
Hi Linus,
Please consider these SH drivers updates for v4.8.
I expect this to be my last pull request for these drivers as
it removes usage of them from Renesas ARM Based SoCs and my
co-maintenance of them.
The drivers are still used by some SH SoCs and listed under SUPERH
in the MAINTAINERS fil
On 2016/7/22 21:27, Arnd Bergmann wrote:
> On Friday, July 22, 2016 11:56:49 AM CEST Mark Rutland wrote:
>> Hi,
>>
>> I understand that some SoC/socket level PMU is accessed via these
>> registers. It doesn't make sense to review either in isolation. Please
>> put together a unified series, with bo
On 2016/7/22 18:56, Mark Rutland wrote:
> Hi,
>
> I understand that some SoC/socket level PMU is accessed via these
> registers. It doesn't make sense to review either in isolation. Please
> put together a unified series, with both the djtag accessors and the
> PMU code.
>
> On it's own, it's *ve
On 2016/7/23 4:37, Paul Gortmaker wrote:
> On Fri, Jul 22, 2016 at 4:48 AM, Tan Xiaojun wrote:
>> The Hisilicon Djtag is an independent module which connects with some modules
>> in the SoC by Debug Bus. This module can be configured to access the
>> registers
>> of connecting modules (like L3 ca
On 2016/7/23 4:11, Andrew Morton wrote:
> On Fri, 22 Jul 2016 10:57:48 +0800 Xishi Qiu wrote:
>
>> Memory offline could happen on both movable zone and non-movable zone.
>> We can offline the whole node if the zone is movable zone, and if the
>> zone is non-movable zone, we cannot offline the wh
There are many AML tables reporting wrong initial lid state (Link 1), and
some of them never report lid open state (Link 2). Thus, the usage model of
the ACPI control method lid device is:
1. The initial lid state returned from _LID is not reliable;
2. The lid open event is not reliable;
3. The lid
On (07/22/16 20:02), SF Markus Elfring wrote:
> The iput() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
there is no issue; the change is just cosmetic.
> Sig
Hi, Bastien
> From: Bastien Nocera [mailto:had...@hadess.net]
> Subject: Re: [PATCH v4 2/2] ACPI / button: Add document for ACPI control
> method lid device restrictions
>
> On Fri, 2016-07-22 at 11:08 +0200, Benjamin Tissoires wrote:
> >
>
> > Then you just need to amend the documentation to sa
On Sun, 2016-07-24 at 16:36 -0500, Eric W. Biederman wrote:
> > A lot of drivers we care about are modular. But maybe the right
> > approach is to do something like remove() if it exist and
> shutdown() if
> > it doesn't ? Or a new callback for kexec ? quiesce() ?
>
> Perhaps remove if shutdown do
On Mon, Jul 25, 2016 at 10:24:53AM +1000, Stephen Rothwell wrote:
> Hi Al,
>
> Today's linux-next merge of the vfs tree got a conflict in:
>
> fs/overlayfs/super.c
>
> between commit:
>
> e2475b7276d0 ("ovl: check mounter creds on underlying lookup")
>
> from the overlayfs tree and commit:
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
fs/overlayfs/super.c
between commit:
e2475b7276d0 ("ovl: check mounter creds on underlying lookup")
from the overlayfs tree and commit:
b3ac9a85b31c ("qstr: constify instances in overlayfs")
from the vfs tree.
I fixed
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Saturday, July 23, 2016 8:37 PM
> Subject: Re: [PATCH v5 1/3] ACPI / button: Add missing event to keep
> SW_LID running without additional event loss
>
> On Friday, July 22, 2016 02:24:42 PM Lv Zheng wrote:
> > There are sev
Hi Al,
Today's linux-next merge of the vfs tree got conflicts in:
fs/f2fs/dir.c
fs/f2fs/f2fs.h
between commit:
91246c21b859 ("f2fs: fix to report error number of f2fs_find_entry")
from the f2fs tree and commit:
14bffd7c398a ("qstr: constify instances in f2fs")
from the vfs tree.
I f
On Sat, Jun 25, 2016 at 11:23:05AM +0200, Arnd Bergmann wrote:
> On Saturday, June 25, 2016 12:37:17 AM CEST Build bot for Mark Brown wrote:
> > Warnings Summary: 1
> > arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
> > 1 ../drivers/xen/balloon.c:155:13: warning:
>
On Sun, Jul 24, 2016 at 10:52:23PM +, Winkler, Tomas wrote:
> >
> > This patch series contains mostly fixes and enhancements of the rx path:
> > 1. Better handling of fixed address clients 2. Support for consecutive
> > reads 3.
> > Further amthif client diet
> >
> >
> Hi Greg, looks like th
On 07/24/16 01:20, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160722:
>
on x86_64:
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
# CONFIG_SECURITY_APPARMOR_HASH is not set
../security/apparmor/lsm.c:675:25: error:
'CONFIG_SECURITY_APPARMOR_HASH_DEFAULT' unde
>
> This patch series contains mostly fixes and enhancements of the rx path:
> 1. Better handling of fixed address clients 2. Support for consecutive reads
> 3.
> Further amthif client diet
>
>
Hi Greg, looks like the first 4 patches I've resent by mistake from the
previous patchset , not sure
On Thu, Jul 21, 2016 at 02:25:15AM +0200, Rafael J. Wysocki wrote:
> On Thursday, July 21, 2016 01:25:53 AM Lukas Wunner wrote:
> > On Thu, Jul 21, 2016 at 12:51:31AM +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, July 20, 2016 05:23:40 PM Lukas Wunner wrote:
> > > > On Wed, Jul 20, 2016 at 02
Hi,
[auto build test ERROR on stable/master]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Michael-S-Tsirkin/virtio-new-feature-to-detect-IOMMU-device-quirk/20160724-030032
base: https
On Sat, Jul 23, 2016 at 07:27:50PM +0100, Chris Wilson wrote:
> Due to the use of READ_ONCE() in list_empty() the compiler cannot
> optimise !list_empty() ? list_first_entry() : NULL very well. By
> manually expanding list_first_entry_or_null() we can take advantage of
> the READ_ONCE() to avoid th
On Mon, Jul 18, 2016 at 01:00:38PM +0300, Amir Levy wrote:
> + const unique_id_be proto_uuid = APPLE_THUNDERBOLT_IP_PROTOCOL_UUID;
> +
> + if (memcmp(proto_uuid, hdr->apple_tbt_ip_proto_uuid,
> +sizeof(proto_uuid)) != 0) {
You may want to use the uuid_be data type provided
1 - 100 of 237 matches
Mail list logo
