On 04/05, Rick Altherr wrote:
> On Wed, Apr 5, 2017 at 1:27 PM, Stephen Boyd wrote:
> > On 03/23, Rick Altherr wrote:
> >> +
> >> +static int aspeed_adc_probe(struct platform_device *pdev)
> >> +{
> >> + struct iio_dev *indio_dev;
> >> + struct aspeed_adc_data *data;
On Thu, 2017-04-06 at 09:16 +0800, jeffy wrote:
> maybe i should just send my ignore file upstream?
Probably a better idea.
On Wed, 2017-04-05 at 17:31 -0700, Stephen Hemminger wrote:
> On Sun, 02 Apr 2017 06:28:41 +0200
> Mike Galbraith wrote:
>
> > Livelock can be triggered by setting kworkers to SCHED_FIFO, then
> > suspend/resume.. you come back from sleepy-land with a spinning
> > kworker. For
On Wed, 5 Apr 2017 10:59:25 -0700
"Paul E. McKenney" wrote:
> > > Could you please let me know if tracing happens in NMI handlers?
> > > If so, a bit of additional code will be needed.
> > >
> > > Thanx, Paul
> > >
>
Clock on ls1088a chip takes primary clocking input from the external
SYSCLK signal. The SYSCLK input (frequency) is multiplied using
multiple phase locked loops (PLL) to create a variety of frequencies
which can then be passed to a variety of internal logic, including
cores and peripheral IP
Register each PLL and its division clocks to clock
lookup table to facilitate the clock look up for
clock consumer.
Signed-off-by: Tang Yuantian
---
drivers/clk/clk-qoriq.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/clk/clk-qoriq.c
FYI, we noticed the following commit:
commit: 19d436268dde95389c616bb3819da73f0a8b28a8 ("debug: Add _ONCE() logic to
report_bug()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 1G
Hi Sean,
On 04/06/2017 12:28 AM, Sean Paul wrote:
On Wed, Apr 05, 2017 at 04:29:26PM +0800, Jeffy Chen wrote:
After unbinding drm, the userspace may still has a chance to access
gem buf.
Add a sanity check for a NULL dev_private to prevent that from
happening.
I still don't understand how
On Wed 08 Mar 10:03 PST 2017, Avaneesh Kumar Dwivedi wrote:
> This patch add scm call support to make hypervisor call to enable access
> of fw regions in ddr to mss subsystem on arm-v8 arch soc's.
>
> Signed-off-by: Avaneesh Kumar Dwivedi
> ---
>
On 04/06/2017 12:57 AM, Andy Shevchenko wrote:
On Wed, Apr 5, 2017 at 11:20 PM, Aleksey Makarov
wrote:
If a console was specified by ACPI SPCR table _and_ command line
parameters like "console=ttyAMA0" _and_ "earlycon" were specified,
then log messages appear
On Thu, 2017-04-06 at 04:58 +, Song, Hongyan wrote:
> Hi Srinivas,
> I have checked the patch dose not meets my requirement for ISH.
> With this patch sensor properties still losing after resume from S3.
What is your test case? I want to try.
Thanks,
Srinivas
>
> BR
> Song Hongyan
>
Hi Punit,
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on v4.11-rc5 next-20170405]
[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/Punit-Agrawal/Support-swap-entries
I hadn't done this yet but I think a simple closest device in the tree
would solve the issue sufficiently. However, I originally had it so the
user has to pick the device and I prefer that approach. But if the user
picks the device, then why bother restricting what he picks?
Because the user
1) Reject invalid updates to netfilter expectation policies, from
Pablo Neira Ayuso.
2) Fix memory leak in nfnl_cthelper, from Jeffy Chen.
3) Don't do stupid things if we get a neigh_probe() on a neigh entry
whose ops lack a solicit method. From Eric Dumazet.
4) Don't transmit packets
Hi Thomas,
At 04/05/2017 07:46 PM, Thomas Gleixner wrote:
On Wed, 29 Mar 2017, Dou Liyang wrote:
Now, there are two ways to setup local apic and io-apic in X86 arch:
1. In an SMP-capable system, it will be done when preparing the
cpus in native_smp_prepare_boot_cpu().
2. If UP_LATE_INIT
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/firmware/efi/efi-pstore.c
between commit:
76cc9580e3fb ("pstore: Replace arguments for write() API")
from the pstore tree and commit:
fee929ba1c93 ("efi/pstore: Return error code (if any) from
On Thu, Apr 06, 2017 at 10:02:48AM +1000, NeilBrown wrote:
> If you are concerned about space in 'struct address_space', just prune
> some wastage.
I'm trying to (via wlists). still buggy though.
> The "host" field brings no value. It is only ever assigned in
> inode_init_always():
>
>
Symbol versioning, as in glibc, results in symbols being defined as:
@[@]
(Note that "@@" identifies a default symbol, if the symbol name
is repeated.)
perf is currently unable to deal with this, and is unable to create
user probes at such symbols:
--
$ nm
Implement a mechanism to check if a module's address is in
the rodata or ro_after_init sections. It mimics the existing functions
that test if an address is inside a module's text section.
Functions that take a module as an argument will be able to verify that the
module address is in a read-only
> -Original Message-
> From: Bart Van Assche [mailto:bart.vanass...@sandisk.com]
> Sent: Wednesday, April 5, 2017 5:32 PM
> To: linux-kernel@vger.kernel.org; linux-bl...@vger.kernel.org; Long Li
> ; ax...@kernel.dk
> Cc: Stephen Hemminger ;
Hi Shuah,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc5]
[cannot apply to next-20170405]
[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/Shuah-Khan/arm-dma-fix
Hi Alan,
first pass ... need to get back to it.
On Mon, Mar 13, 2017 at 04:53:33PM -0500, Alan Tull wrote:
> FPGA region is a layer above the FPGA manager and FPGA bridge
> frameworks. Currently, FPGA region is dependent on device tree.
> This commit separates the device tree specific code from
Hi all,
Changes since 20170405:
The input tree gained a conflict against the jc_docs tree.
The mfd tree still had its build failure for which I reverted a commit.
The tip tree lost its build failure but gained a conflict against the
pstore tree.
The staging tree gained conflicts against
> -Original Message-
> From: KY Srinivasan
> Sent: Wednesday, April 5, 2017 9:21 PM
> To: Bart Van Assche ; linux-
> ker...@vger.kernel.org; linux-bl...@vger.kernel.org; Long Li
> ; ax...@kernel.dk
> Cc: Stephen Hemminger
PHY transceiver driver for QUSB2 phy controller that provides
HighSpeed functionality for DWC3 controller present on
Qualcomm chipsets.
Signed-off-by: Vivek Gautam
Reviewed-by: Stephen Boyd
---
Changes since v7:
- Fixed 'checkpatch --strict'
Qualcomm SOCs have QMP phy controller that provides support
to a number of controller, viz. PCIe, UFS, and USB.
Add a new driver, based on generic phy framework, for this
phy controller.
Signed-off-by: Vivek Gautam
Tested-by: Srinivas Kandagatla
Qualcomm chipsets have QMP phy controller that provides
support to a number of controller, viz. PCIe, UFS, and USB.
Adding dt binding information for the same.
Signed-off-by: Vivek Gautam
Reviewed-by: Stephen Boyd
Acked-by: Rob Herring
Qualcomm chipsets have QUSB2 phy controller that provides
HighSpeed functionality for DWC3 controller.
Adding dt binding information for the same.
Signed-off-by: Vivek Gautam
Reviewed-by: Stephen Boyd
Acked-by: Rob Herring
---
On Wed, 05 Apr 2017 07:01:57 -0700 (PDT)
David Miller wrote:
> From: Nicholas Piggin
> Date: Tue, 4 Apr 2017 13:02:33 +1000
>
> > On Mon, 3 Apr 2017 17:43:05 -0700
> > Linus Torvalds wrote:
> >
> >> But that depends on
Hi Joe,
On 04/06/2017 12:06 AM, Joe Perches wrote:
On Wed, 2017-04-05 at 19:30 +0800, Jeffy Chen wrote:
Currently we are searching "./:$ENV{HOME}/:.scripts/" for ignore file,
but would always get "./.get_maintainer.ignore" only.
That's the point.
It allows you to have specific .ignore files
Hi Thomas,
Thank you very much!
At 04/05/2017 06:43 PM, Thomas Gleixner wrote:
On Wed, 29 Mar 2017, Dou Liyang wrote:
The init_bsp_APIC() setups the virtual wire mode through the local
APIC.
The function name is unsuitable which might imply that the BSP's
APIC will be initialized here,
On Wed, 5 Apr 2017 13:42:29 -0700
"Paul E. McKenney" wrote:
> > OK, do you want me to send you a patch, or should I take your patch
> > into my tree and add this?
>
> Given that I don't seem to have disable_stack_tracer() and
> enable_stack_tracer(), could you
Hi Thomas,
At 04/05/2017 06:50 PM, Thomas Gleixner wrote:
On Wed, 5 Apr 2017, Thomas Gleixner wrote:
On Wed, 29 Mar 2017, Dou Liyang wrote:
The init_bsp_APIC() setups the virtual wire mode through the local
APIC.
The function name is unsuitable which might imply that the BSP's
APIC will be
On Wed, Apr 05 2017, Michal Hocko wrote:
> On Wed 05-04-17 09:19:27, Michal Hocko wrote:
>> On Wed 05-04-17 14:33:50, NeilBrown wrote:
> [...]
>> > diff --git a/drivers/block/loop.c b/drivers/block/loop.c
>> > index 0ecb6461ed81..44b3506fd086 100644
>> > --- a/drivers/block/loop.c
>> > +++
Hi Daniel,
Daniel Borkmann writes:
> On 04/04/2017 08:33 PM, Aaron Conole wrote:
>> The eBPF framework is used for more than just socket level filtering. It
>> can also provide tracing, and even change the way packets coming into the
>> system look. Most of the eBPF
On Thu, Apr 06, 2017 at 10:15:14AM +0930, Jonathan Woithe wrote:
> Hi Michael
>
> On Wed, Apr 05, 2017 at 09:55:34PM +0200, Micha?? K??pie?? wrote:
> > > On Wed, Apr 05, 2017 at 08:48:59AM +0200, Micha?? K??pie?? wrote:
> > > > This series introduces further changes to the way LCD backlight is
>
Provide a mechanism to check if the address of a variable is
const or ro_after_init. It mimics the existing functions that test if an
address is inside the kernel's text section.
The idea is to prevent structures that are not read-only from being
passed to functions. Other functions inside the
mlinux.lds: add missing VMLINUX_SYMBOL macros")
The latest version of this series uses new symbols provided in these
fixes. The series now cross compiles on Blackfin without errors. I have
also test compiled this series on next-20170405 for x86.
I have dropped the third patch that uses the
On 04/04/2017 09:26 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Apr 04, 2017 at 11:18:02PM +0900, Masami Hiramatsu escreveu:
On Mon, 3 Apr 2017 11:46:58 -0300
Arnaldo Carvalho de Melo wrote:
> > > But apart from those problems, I think that one should be able to ask
> > > for
On Thu, 2017-04-06 at 03:38 +, Long Li wrote:
> > -Original Message-
> > From: Bart Van Assche [mailto:bart.vanass...@sandisk.com]
> >
> > Please drop this patch. I'm working on a better solution.
>
> Thank you. Looking forward to your patch.
Hello Long,
It would help if you could
Everything but the USER domain is the same with CONFIG_CPU_SW_DOMAIN_PAN
or not. This extracts the differences for a common DACR_INIT macro so it
is easier to make future changes (like adding the WR_RARE domain).
Signed-off-by: Kees Cook
---
arch/arm/include/asm/domain.h
Set current email address to replace previous employers email
addresses.
Signed-off-by: Jeffy Chen
---
.mailmap | 1 +
1 file changed, 1 insertion(+)
diff --git a/.mailmap b/.mailmap
index e775f79..de0fc5b 100644
--- a/.mailmap
+++ b/.mailmap
@@ -172,6 +172,7 @@
On Wed, Apr 5, 2017 at 3:35 PM, Mark Rutland wrote:
> On Wed, Apr 05, 2017 at 02:42:39PM +0530, Ganapatrao Kulkarni wrote:
>> On Tue, Apr 4, 2017 at 5:58 PM, Mark Rutland wrote:
>> > On Tue, Apr 04, 2017 at 01:06:43PM +0530, Ganapatrao Kulkarni wrote:
This patch moves the struct devfreq_governor from header file
to the devfreq directory because this structure is private data
and it have to be only accessed by the devfreq core.
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/governor.h | 29 +
On Sat, Apr 1, 2017 at 1:51 AM, Brian Norris wrote:
> This reverts commit 437322ea2a36d112e20aa7282c869bf924b3a836.
>
> This above-mentioned "fix" does not actually do anything to prevent a
> race condition. It simply papers over it so that the issue doesn't
> appear.
>
On Thu, Apr 06, 2017 at 11:22:12AM +0800, Figo.zhang wrote:
[...]
> > Heterogeneous Memory Management (HMM) (description and justification)
> >
> > Today device driver expose dedicated memory allocation API through their
> > device file, often relying on a combination of IOCTL and mmap calls.
On Wed, Apr 05 2017, Matthew Wilcox wrote:
> On Thu, Apr 06, 2017 at 10:02:48AM +1000, NeilBrown wrote:
>> If you are concerned about space in 'struct address_space', just prune
>> some wastage.
>
> I'm trying to (via wlists). still buggy though.
Cool.
(I wonder what a wlist is weighted
On Wed, Apr 05, 2017 at 06:43:03AM -0700, David Miller wrote:
> This patch does too many things at one time. Each entry in that list
> of changes above should be a separate change, all posted together as
> a group as a proper patch series.
And please start a new thread with the next posting.
On Wed, 2017-04-05 at 17:16 -0700, Long Li wrote:
> Under heavy I/O, one hardware queue may be unable to dispatch any I/O to the
> device layer. This poses a problem with restarting this hardware queue on I/O
> finish in blk_mq_sched_restart_queues(), becaue there is nothing pending that
> will
Hi Michael
On Wed, Apr 05, 2017 at 09:55:34PM +0200, Micha?? K??pie?? wrote:
> > On Wed, Apr 05, 2017 at 08:48:59AM +0200, Micha?? K??pie?? wrote:
> > > This series introduces further changes to the way LCD backlight is
> > > handled by fujitsu-laptop. These changes include fixing a bug in code
Rik van Riel writes:
> On Wed, 2017-04-05 at 15:10 +0800, Huang, Ying wrote:
>> To solve the issue, the per-CPU buffer is sorted according to the
>> swap
>> device before freeing the swap entries. Test shows that the time
>> spent by swapcache_free_entries() could be reduced
Hi all,
Today's linux-next merge of the input tree got a conflict in:
Documentation/input/ff.rst
between commit:
1e4390ae1015 ("Documentation: input: fix path to struct ff_effect's
definition")
from the jc_docs tree and commit:
deeb1e902fbc ("Input: use svg files instead of xfig in
On Wed, Apr 05 2017, Jan Kara wrote:
> On Wed 05-04-17 11:43:32, NeilBrown wrote:
>> On Tue, Apr 04 2017, J. Bruce Fields wrote:
>>
>> > On Thu, Mar 30, 2017 at 02:35:32PM -0400, Jeff Layton wrote:
>> >> On Thu, 2017-03-30 at 12:12 -0400, J. Bruce Fields wrote:
>> >> > On Thu, Mar 30, 2017 at
On Thu, 2017-04-06 at 10:01 +0800, Jeffy Chen wrote:
> The mail account "Yakir Yang " is no longer
> valid.
Does this person still want to be involved with the kernel?
If so, perhaps a .mailmap entry would be more appropriate.
> diff --git a/.get_maintainer.ignore
Hi Joe,
On 04/06/2017 10:39 AM, Joe Perches wrote:
On Thu, 2017-04-06 at 10:01 +0800, Jeffy Chen wrote:
The mail account "Yakir Yang " is no longer
valid.
Does this person still want to be involved with the kernel?
If so, perhaps a .mailmap entry would be more
Hi James,
After merging the scsi tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from include/linux/list.h:8:0,
from include/linux/module.h:9,
from drivers/scsi/sd.c:35:
drivers/scsi/sd.c: In function
On Wed, Apr 05, 2017 at 10:12:24PM -0400, Steven Rostedt wrote:
> On Wed, 5 Apr 2017 10:59:25 -0700
> "Paul E. McKenney" wrote:
>
> > > > Could you please let me know if tracing happens in NMI handlers?
> > > > If so, a bit of additional code will be needed.
> > > >
> -Original Message-
> From: Bart Van Assche [mailto:bart.vanass...@sandisk.com]
> Sent: Wednesday, April 5, 2017 8:46 PM
> To: linux-kernel@vger.kernel.org; linux-bl...@vger.kernel.org; Long Li
> ; ax...@kernel.dk
> Cc: Stephen Hemminger ;
2017년 04월 05일 00:38에 Krzysztof Kozlowski 이(가) 쓴 글:
> On Tue, Mar 28, 2017 at 11:38 AM, Krzysztof Kozlowski wrote:
>> On Tue, Mar 28, 2017 at 11:26 AM, Inki Dae wrote:
>>> Merged.
>>
>> Hi,
>>
>> I do not see the tag (with DT patches) merged by you which I
On Tue, 4 Apr 2017, Jarkko Sakkinen wrote:
> Hi James,
>
> Here is the pull request for 4.12.
>
> Major new features have been landed:
>
> 1. TPM resource manager. There's a new device called /dev/tpmrm0. When this
> device is opened, a new session is created that is isolated from other users.
On Sun, 02 Apr 2017 06:28:41 +0200
Mike Galbraith wrote:
> Livelock can be triggered by setting kworkers to SCHED_FIFO, then
> suspend/resume.. you come back from sleepy-land with a spinning
> kworker. For whatever reason, I can only do that with an enterprise
> like config, my
On Wed, Apr 05 2017, Jeff Layton wrote:
>>
>> O_DIRECT write() can get an EIO from a previous write-back write to the
>> same file. Maybe non-O_DIRECT writes should too?
>>
>
> Some already do this for buffered writes.
>
> This is really a philosophical question, IMO...is it correct to return
The mail account "Yakir Yang " is no longer
valid.
Some mail server(for example 263) would refuse to send mails when
the address list contains this account.
Update .get_maintainer.ignore to prevent that.
Signed-off-by: Jeffy Chen
---
Hi all,
Today's linux-next merge of the staging tree got conflicts in:
drivers/staging/media/lirc/lirc_sasem.c
drivers/staging/media/lirc/lirc_sir.c
between commits:
e66267161971 ("[media] rc: promote lirc_sir out of staging")
51bb3fd788cb ("[media] staging: lirc_sasem: remove")
from
Brian Norris writes:
> nl80211 provides the NL80211_SCAN_FLAG_RANDOM_ADDR for every scan
> request that should be randomized; the absence of such a flag means we
> should not randomize. However, mwifiex was stashing the latest
> randomization request and *always* using
Hi Alan,
minor nits, inline
On Mon, Mar 13, 2017 at 04:53:32PM -0500, Alan Tull wrote:
> Add fpga_mgr_lock/unlock functions that get a mutex for
> exclusive use.
>
> of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put no longer lock
> the FPGA manager mutex.
>
> This makes it more straightforward
On Wed, Apr 05, 2017 at 09:31:45PM -0400, Steven Rostedt wrote:
> On Wed, 5 Apr 2017 13:42:29 -0700
> "Paul E. McKenney" wrote:
>
> > > OK, do you want me to send you a patch, or should I take your patch
> > > into my tree and add this?
> >
> > Given that I don't
Hi Srinivas,
I have checked the patch dose not meets my requirement for ISH.
With this patch sensor properties still losing after resume from S3.
BR
Song Hongyan
-Original Message-
From: Srinivas Pandruvada [mailto:srinivas.pandruv...@linux.intel.com]
Sent: Wednesday, April 5,
Hi Bjorn,
On Wednesday 05 April 2017 10:22 PM, Bjorn Helgaas wrote:
> On Wed, Apr 05, 2017 at 02:22:21PM +0530, Kishon Vijay Abraham I wrote:
>> Introduce a new EP core layer in order to support endpoint functions in
>> linux kernel. This comprises the EPC library (Endpoint Controller Library)
>>
Note that the nvme completion queues are still on the host memory, so
this means we have lost the ordering between data and completions as
they go to different pcie targets.
Hmm, in this simple up/down case with a switch, I think it might
actually be OK.
Transactions might not complete at
Hi Kishon,
Here's the series with fixed checkpatch warnings/checks.
Please pick it for phy/next.
This patch series adds couple of PHY drivers for Qualcomm chipsets.
a) qcom-qusb2 phy driver: that provides High Speed USB functionality.
b) qcom-qmp phy driver: that is a combo phy providing support
On 04/05/2017 09:50 AM, SF Markus Elfring wrote:
From: Markus Elfring
Date: Wed, 5 Apr 2017 15:34:32 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (5):
Use kcalloc() in qib_init_iba7322_funcs()
Use
On Wednesday 04/05 at 17:22 +0200, Petr Mladek wrote:
> On Wed 2017-04-05 11:16:28, Sergey Senozhatsky wrote:
> > On (04/05/17 11:08), Sergey Senozhatsky wrote:
> > [..]
> > > > stop_critical_timings();/* don't trace print
> > > > latency */
> > > > -
Hi, Nikolaus,
Could you add below debug message to hid-alps.c, and check it?
This device is "HID_DEVICE_ID_ALPS_T4_BTNLESS"(0x120C).
If the device is UNKNOWN, this device does not work completely.
And if the system does not call here, it has nothing to do with my patch.
static int alps_probe()
{
On Wed, 2017-04-05 at 16:55 -0700, Cong Wang wrote:
> On Tue, Apr 4, 2017 at 11:12 PM, Mike Galbraith wrote:
> > On Tue, 2017-04-04 at 22:25 -0700, Cong Wang wrote:
> > > On Tue, Apr 4, 2017 at 8:20 PM, Mike Galbraith wrote:
> > > > - while
Setting thp defrag mode of "defer+madvise" actually sets "defer" in the
kernel due to the name similarity and the out-of-order way the string is
checked in defrag_store().
Check the string in the correct order so that
TRANSPARENT_HUGEPAGE_DEFRAG_KSWAPD_OR_MADV_FLAG is set appropriately for
From: Jarod Wilson
Date: Tue, 4 Apr 2017 17:32:42 -0400
> People are using bonding over Infiniband IPoIB connections, and who knows
> what else. Infiniband has a hardware address length of 20 octets
> (INFINIBAND_ALEN), and the network core defines a MAX_ADDR_LEN of 32.
>
On Wed, Apr 05 2017, Michael Wang wrote:
> On 04/05/2017 12:17 AM, NeilBrown wrote:
> [snip]
>>> diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
>>> index 7d67235..0554110 100644
>>> --- a/drivers/md/raid1.c
>>> +++ b/drivers/md/raid1.c
>>> @@ -1986,11 +1986,13 @@ static int
Dear all,
I created the extcon immutable branch for v4.12. This branch
will be never changed before releasing the v4.12-rc1.
If there are some patches depending on the extcon core,
please pull this immutable branch.
Best Regards,
Chanwoo Choi
The following changes since commit
From: Huang Ying
In the original THP swapping out implementation, before splitting the
THP (Transparent Huage Page), the swap cluster will be allocated and
the THP will be added into the swap cache. But it is possible that
the THP cannot be split, and we must delete the
From: Huang Ying
In this patch, splitting huge page is delayed from almost the first
step of swapping out to after allocating the swap space for the
THP (Transparent Huge Page) and adding the THP into the swap cache.
This will batch the corresponding operation, thus improve
From: Huang Ying
This patchset is to optimize the performance of Transparent Huge Page
(THP) swap.
Hi, Andrew, could you help me to check whether the overall design is
reasonable?
Hi, Hugh, Shaohua, Minchan and Rik, could you help me to review the
swap part of the
From: Huang Ying
If there is no compound map for a THP (Transparent Huge Page), it is
possible that the map count of some sub-pages of the THP is 0. So it
is better to split the THP before swapping out. In this way, the
sub-pages not mapped will be freed, and we can avoid
> In fact "internet" label on the case is uppercase, would this matter
> for you for new bindings, or would you still use the lowercase version?
I would use lower case, just to fix with the general convention that
interface names are lower case.
> > I would say, this is now too late. Changing an
Argh, I sill have the typo in the title of this patch! :(
If you are going to apply it could you fix it, else it will be fixed in
the next version.
Sorry,
Gregory
On mer., avril 05 2017, Gregory CLEMENT
wrote:
> The Armada 37xx SoCs can handle
The driver is bound to the devices based on their PCI IDs.
There is no need to do an additional check.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_scu_ipc.c | 5 -
1 file changed, 5 deletions(-)
diff --git
Hi Andrew,
On Wed, 5 Apr 2017 17:50:32 +0200
Andrew Lunn wrote:
> > In fact "internet" label on the case is uppercase, would this matter
> > for you for new bindings, or would you still use the lowercase
> > version?
>
> I would use lower case, just to fix with the general
On Wed, 2017-04-05 at 19:30 +0800, Jeffy Chen wrote:
> Currently we are searching "./:$ENV{HOME}/:.scripts/" for ignore file,
> but would always get "./.get_maintainer.ignore" only.
That's the point.
It allows you to have specific .ignore files for various projects.
> This patch applies all
On 04/02, Eric W. Biederman wrote:
>
> Take advantage of the situation when sighand->count == 1 to only wait
> for threads to reach EXIT_ZOMBIE instead of EXIT_DEAD in de_thread.
Let me comment this patch first, it looks mostly fine to me.
And note that this is what my patch does too: exec()
On 04/04/17 19:06, Christopher Bostic wrote:
> From: Chris Bostic
>
> Implement a FSI master using GPIO. Will generate FSI protocol for
> read and write commands to particular addresses. Sends master command
> and waits for and decodes a slave response.
>
>
On 04/04/17 19:06, Christopher Bostic wrote:
> From: Chris Bostic
>
> Add an engine driver to expose a "hub" FSI master - which has a set of
> control registers in the engine address space, and uses a chunk of the
> slave address space for actual FSI communication.
>
On Wed, Apr 05, 2017 at 02:52:08PM +, Ghannam, Yazen wrote:
> Yes, BIOS does and should set this bit. If it doesn't for some reason
> then our handling in the Kernel will still be functional. We just
> won't find Deferred errors in MCA_STATUS.
Ok.
> I'd rather we keep as many checks as
JonathanOn 04/02/2017 02:19 PM, Jonathan Cameron wrote:
> On 31/03/17 12:45, Fabrice Gasnier wrote:
>> STM32 DAC has built-in noise or triangle waveform generator.
>> Waveform generator requires trigger to be configured.
>> - "wave" extended attribute selects noise or triangle.
>> - "mamp"
On 04/03, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > I meant that may_hang == 0 implies zap_other_threads(do_count => -1) which
> > should
> > return the number of threads which didn't pass exit_notify(). The returned
> > value
> > can be wrong unless you change
On Wed 05-04-17 20:52:15, Srikar Dronamraju wrote:
> * Michal Hocko [2017-04-05 14:57:43]:
>
> > On Tue 04-04-17 22:57:28, Srikar Dronamraju wrote:
> > [...]
> > > For example:
> > > perf bench numa mem --no-data_rand_walk -p 4 -t $THREADS -G 0 -P 3072 -T
> > > 0 -l 50 -c -s
On Wed, 5 Apr 2017 09:25:15 -0700
"Paul E. McKenney" wrote:
> > Thoughts?
>
> Ouch!!!
>
> I really blew it telling you that you can use rcu_irq_enter()!!!
>
> RCU's eqs code disables interrupts, but has a call to the trace code
> exactly where it cannot handle an
On 04/02/2017 02:21 PM, Jonathan Cameron wrote:
> On 02/04/17 12:45, Jonathan Cameron wrote:
>> On 31/03/17 12:45, Fabrice Gasnier wrote:
>>> STM32 DAC supports triggers to synchronize conversions. When trigger
>>> occurs, data is transferred from DHR (data holding register) to DOR
>>> (data
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
301 - 400 of 1922 matches
Mail list logo