On 23/05/16 17:10, Crestez Dan Leonard wrote:
> On 05/21/2016 07:28 PM, Jonathan Cameron wrote:
>> On 20/05/16 16:55, Peter Meerwald-Stadler wrote:
>>>
This also drops all the code freeing string buffers at the end of main.
Memory is freed when the process exits anyway so there's no point
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/uaccess
commit 8829c7a53e1b4e44f6c24c6d165cf9d1cf8b1f14 ("[DEBUG] force
CONFIG_DEBUG_UACCESS")
on test machine: vm-lkp-wsx03-yocto-i386: 1 threads qemu-system-i386
-enable-kvm with 320M m
On 23/05/16 17:07, Crestez Dan Leonard wrote:
> This will clean (disable buffer/trigger/channels) when doing
> something like a CTRL-C. Otherwise restarting generic_buffer requires a
> manual echo 0 > buffer/enable
>
> This also cleanup up all the code freeing string buffers at
> the end of main.
On 29/05/16 20:14, Jonathan Cameron wrote:
> On 23/05/16 17:07, Crestez Dan Leonard wrote:
>> This will clean (disable buffer/trigger/channels) when doing
>> something like a CTRL-C. Otherwise restarting generic_buffer requires a
>> manual echo 0 > buffer/enable
>>
>> This also cleanup up all the c
On 23/05/16 17:07, Crestez Dan Leonard wrote:
> This makes it possible to distinguish between iio devices with the same
> name.
>
> Signed-off-by: Crestez Dan Leonard
I'm a cheapskate and never had more than one of a given part ;)
Hence clearly never thought this through properly.
Applied to the
On Sun, May 29, 2016 at 09:25:28AM -0700, Linus Torvalds wrote:
> On Sun, May 29, 2016 at 8:28 AM, kernel test robot
> wrote:
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
>
> This bisection seems unlikely.
>
> I *think* what is going on is that the previous k
On 24/05/16 22:54, Linus Walleij wrote:
> On Tue, May 24, 2016 at 2:33 PM, Crestez Dan Leonard
> wrote:
>> [Me]
>>> However I think my patch fixing the thread issue will collide
>>> by being close in context to this so it'd be great if you
>>> could resend it on top of
>>> "iio: st_sensors: switch
I have just tested removing i8k_get_fan_type() function from the
dell-smm-hwmon driver in the kernel on my Dell Inspiron 580 and the fan
speed problem goes away. My patch simply replaced fan_type with
fan_status in i8k_init_hwmon and used the index as the type in
i8k_hwmon_show_fan_label since
On 24/05/16 12:28, Linus Walleij wrote:
> On Fri, May 13, 2016 at 8:43 PM, Crestez Dan Leonard
> wrote:
>
>> This fixes odd behavior after reboot.
>>
>> The fact that we set the device to powerdown mode is not sufficient to
>> prevent DRDY being active because we might still have an unread sample
On 24/05/16 13:35, Crestez Dan Leonard wrote:
> On 05/24/2016 02:40 PM, Linus Walleij wrote:
>> On Fri, May 13, 2016 at 8:43 PM, Crestez Dan Leonard
>> wrote:
>>
>>> As far as I can tell DRDY for ST sensors behaves as a level rather than
>>> edge interrupt. Registering for IRQF_TRIGGER_RISING inst
On 23/05/16 19:39, Crestez Dan Leonard wrote:
> This will clean (disable buffer/trigger/channels) when doing
> something like a CTRL-C. Otherwise restarting generic_buffer requires a
> manual echo 0 > buffer/enable
>
> This also cleanup up all the code freeing string buffers at
> the end of main.
On 23/05/16 19:39, Crestez Dan Leonard wrote:
> This makes it possible to distinguish between iio devices with the same
> name.
>
> Signed-off-by: Crestez Dan Leonard
Applied.
> ---
> tools/iio/generic_buffer.c | 69
> ++
> 1 file changed, 51 insertio
On 23/05/16 19:39, Crestez Dan Leonard wrote:
> Signed-off-by: Crestez Dan Leonard
Again, sensible and straight forward.
Thanks,
Jonathan
> ---
> tools/iio/generic_buffer.c | 34 +-
> 1 file changed, 29 insertions(+), 5 deletions(-)
>
> diff --git a/tools/iio/ge
On 23/05/16 19:39, Crestez Dan Leonard wrote:
> IIO documents that trigger names are unique but does not actually guarantee
> this. You can easily create a software trigger with a duplicate name if you
> enable CONFIG_IIO_HRTIMER_TRIGGER:
>
> mkdir /sys/kernel/config/iio/triggers/hrtimer/\
>
On 23/05/16 19:40, Crestez Dan Leonard wrote:
> The trigger name is documented as unique but drivers are currently
> allowed to register triggers with duplicate names. This should be
> considered a bug since it makes the 'current_trigger' interface
> unusable.
>
> Signed-off-by: Crestez Dan Leonar
> + if (of_property_read_u32(node, "fsl,settling", &adapt)) {
> + ts->settling_delay = 10;
> + } else {
> + if (adapt < 1 || adapt > LRADC_DELAY_DELAY_MASK) {
> + dev_err(ts->dev, "Invalid settling delay (%u)\n",
> +
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/uaccess
commit 396426274682b471f3fb5ed2f4c3295c8e360d63 ("x86/uaccess: OOPS or warn on
a fault with KERNEL_DS and !pagefault_disabled()")
on test machine: vm-intel12-openwrt-i386: 1 thread
Andy?
Looking at that commit, it does look like what wmi_parse_guid +
wmi_swap_bytes did was to implement a LE uuid. So the conversion looks
correct, but the fact that it breaks something obviously means that
there's something missing. What's going on?
And dammit, how I hate uuid's and the idioti
On Fri, 20 May 2016, Jani Nikula wrote:
> At this time I've put most effort into the configuration and build side
> of things, solving the problems described above, and handling missing
> tools and packages gracefully. There are still issues to be ironed out
> in a) the kernel-doc script rst outpu
On Wed, May 25, 2016 at 11:06:35AM +0100, Harvey Hunt wrote:
> On certain MIPS32 devices, the ftrace tracer "function_graph" uses
> __lshrdi3() during the capturing of trace data. ftrace then attempts to
> trace __lshrdi3() which leads to infinite recursion and a stack overflow.
> Fix this by mark
sorry for delay,
On 05/25, Michal Hocko wrote:
>
> On Wed 25-05-16 00:43:41, Oleg Nesterov wrote:
> >
> > But. It _seems to me_ that the kernel "leaks" some pages in
> > LRU_INACTIVE_FILE
> > list because inactive_file_is_low() returns the wrong value. And do not even
> > ask me why I think so, u
There are two firmware events we handle similarly in brcmfmac:
BRCMF_E_LINK and BRCMF_E_IF. The difference from firmware point of view
is that the first one means BSS remains present in the firmware. Trying
to (re)create it (e.g. when adding new virtual interface) will result in
an error.
Current
Chips from the at24cs EEPROM series have an additional read-only
memory area containing a factory pre-programmed serial number. In
order to access it, a dummy write must be executed before reading
the serial number bytes.
Chips from the at24mac familiy, apart from the serial number, have
a second
Split at24_eeprom_read() into two smaller functions - one for the
i2c operations and one for the smbus extensions. Assign them in
at24_probe() depending on the bus capabilities.
Also: in order to avoid duplications move the comments related to
offset calculations above the at24_translate_offset()
In preparation for splitting at24_eeprom_write() & at24_eeprom_read()
into smaller, specialized routines move at24_read() below, so that it
won't be intertwined with the low-level EEPROM accessors.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 64 +++
Now with the infrastructure for reading the factory-programmed mac
address in place, add the two available chips from the at24mac
family: at24mac402 and at24mac602 to the device ID list.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 4
1 file changed, 4 insertions(+)
Before splitting the read/write routines into smaller, more
specialized functions, unduplicate some code in advance.
Use a 'for' loop instead of 'do while' when waiting for the previous
write to complete and hide it behind a macro.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24
The infrastructure for reading of the factory-programmed serial number
for at24cs EEPROM series is now in place. Add the chips that are actually
equipped with the serial number memory area to the list of supported
devices.
The chips from the at24cs family have two memory areas - a regular
read-wri
Add a new read function to the at24 driver allowing to retrieve the
factory-programmed mac address embedded in chips from the at24mac
family.
These chips can be instantiated similarily to the at24cs family,
except that there's no way of having access to both the serial number
and the mac address a
As part of supporting the at24mac series add a new flag to the at24
platform data. When set, it indicates that this chip exposes the
factory-programmed EUI-48 or EUI-64 address.
Signed-off-by: Bartosz Golaszewski
---
include/linux/platform_data/at24.h | 1 +
1 file changed, 1 insertion(+)
diff
Align the arguments in broken lines with the arguments list's opening
brackets and make checkpatch.pl happy by converting 'unsigned' into
'unsigned int'.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
Split at24_eeprom_write() into three smaller functions - one for the
i2c operations and two for the smbus extensions (separate routines for
block and byte transfers). Assign them in at24_probe() depending on
the bus capabilities.
Also: in order to avoid duplications move code adjusting the count
a
As part of the preparation for introducing support for more chips,
improve the readability of the device table by separating columns
with tabs.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
In preparation for supporting the at24cs EEPROM series add a new flag
to the at24 platform data. When set, it should tell the driver that
the chip has an additional read-only memory area that holds a factory
pre-programmed serial number.
Signed-off-by: Bartosz Golaszewski
---
include/linux/platf
The at24cs series EEPROM chips have an additional read-only memory area
containing a factory pre-programmed serial number. In order to access
it, one has to perform a dummy write before reading the serial number
bytes.
Add a function that allows to access the serial number and assign it
to at24->r
Use BIT() macro to replace the 0xXX constants in platform_data flags
definitions.
Signed-off-by: Bartosz Golaszewski
---
include/linux/platform_data/at24.h | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/include/linux/platform_data/at24.h
b/include/linux/platform_da
The first step in simplifying the read and write functions is to call
them via function pointers stored in at24_data. When we eventually
split the routines into smaller ones (depending on whether they use
smbus or i2c operations) we'll simply assign them to said pointers
instead of checking the fla
Hi,
[auto build test WARNING on next-20160527]
url:
https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/brcmfmac-don-t-remove-interface-on-link-down-firmware-event/20160530-054251
config: sparc64-allyesconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160
Hi Shawn,
Applied on my repository.
Thanks!
Best Regards,
Jaehoon Chung
On 05/27/2016 03:36 PM, Shawn Lin wrote:
> dw_mci_get_cd have already dealt with these for
> both of internal card-detect and gpio card-detect.
>
> Signed-off-by: Shawn Lin
>
> ---
>
> Changes in v2: None
>
> drivers/m
Hi Shawn,
On 05/27/2016 03:37 PM, Shawn Lin wrote:
> The main reason to add this check is to avoid unnecessary
> mmc_request like the on-going cmd and the corresponding sbc
> if the card is removed. Although we have already checked this in
> dw_mci_handle_cd for runtime usage of sd card and dw_mci
Hi,
On 03/05/2016 at 12:05:34 +0200, Arnd Bergmann wrote :
> On Tuesday 03 May 2016 09:24:18 Alexandre Belloni wrote:
> > Hi Arnd,
> >
> > I see you didn't copy Greg on that series (that may explain his
> > confusion on the previous patch), do you expect me to take it
> > through the RTC tree? Th
On 22/05/2016 at 11:06:16 +0200, Geert Uytterhoeven wrote :
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Alessandro Zummo
> Cc: Alexandre Belloni
> Cc: rtc-li...@googlegroups.com
> -
On Fri, 27 May 2016 14:54:59 +0200, Boris Brezillon said:
> From: Hans de Goede
>
> On some nand controllers with hw-ecc the controller code wants to know
> the ecc strength and size and having these as 0, 0 is not accepted.
>
> Specifying these in devicetree is possible but undesirable as the nan
[bringing back an old tangent from a thread back in February]
There is a lot of duplication between dentry_unlink_inode() and dentry_iput().
The only real difference is that dentry_unlink_inode() bumps ->d_seq and
dentry_iput() doesn't. The argument of the latter is known to have been
unhashed, s
Hi Vinod
> > > > Current rcar_dmac_desc_put() is using list_add_tail() in order to
> > > > push used descriptor to list of free descriptors, and next DMA transfer
> > > > try to reuse it from this list. But because it is using *_tail(),
> > > > this reuse effect can't be obtained without using al
off in befs_bt_read_node() will be written by befs_read_datastream(), with
the value that node->od_node needs.
node_off in befs_btree_read() isn't read before set to root_node_ptr.
Removing these two unneeded initializations.
Signed-off-by: Luis de Bethencourt
---
Hi,
Also saw these while rea
From: Kuninori Morimoto
For each descriptor, in addition to the memory used by the descriptors
structure itself, the driver allocates a list of chunks as well as a
buffer for hardware descriptors. Descriptors themselves are preallocated,
and allocation of the chunks and buffer is performed the f
Hi all,
I have been a bit remiss in publishing these stats and maybe that has
lead to the current lower result for commits in linux-next before the
merge window opened ...
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-201
From: Corey Minyard
When doing byte-by-byte mode, the code was writing the host
control register on every byte. However, this is only necessary
on the first byte and for read transactions the last byte.
So only do it those times.
Signed-off-by: Corey Minyard
---
drivers/i2c/busses/i2c-i801.c
From: Corey Minyard
Since hwpec is only used for block transactions, move it out of
i801_access() and into i801_block_transaction().
Signed-off-by: Corey Minyard
---
drivers/i2c/busses/i2c-i801.c | 47 +++
1 file changed, 25 insertions(+), 22 deletions(-
From: Corey Minyard
The priv->cmd is called subcmd elsewhere, and that's a more
appropriate name for it, so rename it.
The "size" parameter passed in to i801_access is passed to other
functions and those name is "command". This is confusing with the
"command" parameter passed in to i801_access.
From: Corey Minyard
If a bad number of bytes is read on a transaction, have it
report an error and return -EPROTO for the transaction.
Signed-off-by: Corey Minyard
---
drivers/i2c/busses/i2c-i801.c | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git
From: Corey Minyard
Don't leave a pointer to some external buffer lying around.
Signed-off-by: Corey Minyard
---
drivers/i2c/busses/i2c-i801.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
index 70da60a..bb15356 100644
--- a/d
From: Corey Minyard
It was always done before starting the transaction, so do it
in common code before the transaction start.
Signed-off-by: Corey Minyard
---
drivers/i2c/busses/i2c-i801.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/i2c/busses/i2c-i
From: Corey Minyard
The HSTCFG register save/restore was done in i2c_block_transaction,
but all the checks were already done in i801_access, so move it into
those checks.
This results in a small savings of code, and moves some special
handing for I2C transactions into code that is already handli
From: Corey Minyard
The code was passing around read_write, which required comparison
with a constant, but was effectively a bool. Pass around an
is_read bool instead. This also makes it consistent with the
priv->is_read used for interrupt handling.
Signed-off-by: Corey Minyard
---
drivers/i
From: Corey Minyard
This was almost always called at the end of the transaction. The
only time it wasn't called was when a protocol violation occurred,
and the error reporting was inconsistent there.
So have the transaction functions return positive status or a
negative error if they detect an
From: Corey Minyard
It's not used in the function, so get rid of it.
Signed-off-by: Corey Minyard
---
drivers/i2c/busses/i2c-i801.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
index 64b1208b..818c0c8 100
This is a new set that is fairly different than the old set, though it
fixes a lot of the same issues, and some new ones I noticed.
I did not do the consolidation of the isr and non-isr byte-by-byte
handling, based on Jean's comments.
I tested this on qemu (including returning a bad number of byt
On Fri, May 27, 2016 at 04:26:21PM +0200, Vlastimil Babka wrote:
> On 05/20/2016 04:23 PM, Minchan Kim wrote:
> >We have allowed migration for only LRU pages until now and it was
> >enough to make high-order pages. But recently, embedded system(e.g.,
> >webOS, android) uses lots of non-movable page
Per Vlastimil's review comment,
Vlastimil, I updated based on your comment. Please review this.
If everything is done, I will send v7 rebased on recent mmotm.
Thanks for the review!
>From ad4157e98651a2d18fd0a4ae90d1d9f609aab314 Mon Sep 17 00:00:00 2001
From: Minchan Kim
Date: Fri, 8 Apr 2016 1
Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@gmail.com]
> Subject: Re: [RFC PATCH 1/2] ACPI / button: Send "open" state after
> boot/resume
>
> [Jumping in the discussion at Bastien's request]
>
> On Thu, May 19, 2016 at 3:21 PM, Rafael J. Wysocki
> wrote:
> > On Thu, May 19, 2016
Hello,
On 2016년 05월 28일 07:44, Casey Schaufler wrote:
> On 5/27/2016 1:24 PM, Al Viro wrote:
>> On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
>>> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
Amended and force-pushed...
>>> Ok, I'll ignore that branch for now, in the hop
acpi_dev_found() will be used to detect if a given ACPI device is in the
system. It will be compiled in non-ACPI case, but the function is in
acpi_bus.h and acpi_bus.h can only be used in ACPI case, so this patch add
the stub function to linux/acpi.h to make compiled successfully in
non-ACPI cases.
acpi_evaluate_dsm() will be used to handle the _DSM method in ACPI case.
It will be compiled in non-ACPI case, but the function is in acpi_bus.h
and acpi_bus.h can only be used in ACPI case, so this patch add the stub
function to linux/acpi.h to make compiled successfully in non-ACPI cases.
Cc: Ra
In ACPI case, there is no interface to register phy device to mdio-bus.
Phy device has to be registered itself to mdio-bus, and then enet can
get the phy device's info so that it can config the phy-device to help
to trasmit and receive data.
HNS hardware topology is as below. The MDIO controller ma
OF series functions can be used only for DT case. Use unified
device property function instead to support both DT and ACPI.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c | 9 +
drivers/net/ethernet/hisilicon/hns/hns_enet.c
Dsaf needs to get configuration parameter by ACPI, so this patch add
support of ACPI.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
v2:
1. use dev_of_node() instead of IS_ENABLED() to check if it is in
DT case,
2. split a new patch to implement misc operation method,
As device_node is only used by DT case, it is expected to find uniform
ways. So fwnode_handle is the suitable method.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
v2: remove the redundant line
v1: first submit
link: https://lkml.org/lkml/2016/5/13/98
---
drivers/net
As device_node is only used by DT case, HNS needs to treat the other
cases including ACPI. It needs to use uniform ways to handle both of
DT and ACPI. This patch chooses phy_device, and of_phy_connect and
of_phy_attach are only used by DT case. It needs to use uniform interface
to handle that seque
As irq_of_parse_and_map is only used by DT case, it is excepted to use
a uniform interface. So it is used platform_get_irq() instead.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hns/hns_dsaf_rcb.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletio
Hns-mdio only supports DT case now. do some cleanup to prepare
for introducing other cases later, no functional change.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hns_mdio.c | 46 +++
1 file changed, 23 insertions(+), 23
Commit 3939f3345050 ("ARM: 8418/1: add boot image dependencies to
not generate invalid images") fixed bad image generation for the
parallel building, but as its side effect, Kbuild now descends into
arch/arm/boot/ again and again, duplicating the log messages.
It looks clumsy, so let's display the
The misc operation for different hw platform may be different, if using
current implementation, it will add a new branch on each function for
every new hw platform, so we add a method for this operation.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hn
Enet needs to get configration parameter by acpi. This patch
adds support of ACPI for enet. The configuration parameter will
be configed in BIOS.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
v2:
1. use acpi_dev_found() instead of acpi_match_device_ids()
2. use
hns-mdio needs to register itself to mii-bus. The info of the device can
be read by both DT and ACPI.
HNS tries to call Linux PHY driver to help access PHY-devices, the HNS
hardware topology is as below. The MDIO controller may control several
PHY-devices, and each PHY-device connects to a MAC devi
The miscellaneous operation is implemented in BIOS, the kernel can call
_DSM method help to call the implementation in ACPI case. Here is a patch
to do that.
Signed-off-by: Kejian Yan
Signed-off-by: Yisen Zhuang
---
change log:
v2: use a serial function to implement the reset sequence
v1: fir
This series adds HNS support of acpi. The routine will call some ACPI
helper functions, like acpi_dev_found() and acpi_evaluate_dsm(), which
are not included in other cases. In order to make system compile
successfully in other cases except ACPI, it needs to add relative stub
functions to linux/acp
Tree-wide replacement was done by commit 2ef7d5f342c1 (ARM, ARM64:
dts: drop "arm,amba-bus" in favor of "simple-bus"), but we have some
new users of "arm,amba-bus" at Linux 4.7-rc1. Eliminate them now.
Signed-off-by: Masahiro Yamada
---
In order to not leave these compatible strings for the rel
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
chrdev-warn
commit 65e5b1e9eb3f777ab7535b74b490e882eeec79d7 ("chrdev: allocate dynamic
chardevs in all unused holes")
on test machine: vm-lkp-wsx03-2G: 2 threads qemu-system-x86_64 -enab
From: Sam Ravnborg
Date: Sun, 29 May 2016 19:30:38 +0200
> It would be nice to include the explanation from the mail in the changelog.
> It gives a good background information and it is more accessible in the
> commit log rather than mails only.
Yep, will supplement the commit message as well as
On Sun, May 29, 2016 at 10:59 AM, Hector Martin wrote:
> On Mon, May 23, 2016 at 3:15 PM, Emese Revfy wrote:
>> +/*
>> + * Copyright 2012-2016 by the PaX Team
>> + * Copyright 2016 by Emese Revfy
>> + * Licensed under the GPL v2
>> + *
>> + * Note: the choice of the license means that the compi
This patch fixes the checkpatch.pl WARNINGs to ptrace.c:
WARNING: sizeof siginfo should be sizeof(siginfo)
Signed-off-by: Wei Tang
---
kernel/ptrace.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/ptrace.c b/kernel/ptrace.c
index d49bfa1..76fa875 100644
--- a/ke
Hi,
can we work together ? if yes email back to me at ( andris...@aim.com )
Regards,
Andris
--
Este mensaje ha sido analizado por MailScanner
en busca de virus y otros contenidos peligrosos,
y se considera que está limpio.
FYI, we noticed boot-slabinfo.num_objs +31.9% increasement due to commit:
commit 55834c59098d0c5a97b0f3247e55832b67facdcf ("mm: kasan: initial memory
quarantine implementation")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: vm-lkp-w
On 18 May 2016 at 17:21, LABBE Corentin wrote:
> Since the crypto engine has been converted to use crypto_async_request
> instead of ablkcipher_request, minor changes are needed to use it.
I think you missed the conversion for omap des driver, please rebase
your patch. Beyond that I think you did
FYI, we noticed the following commit:
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2016.05.17a
commit ac3c30e8911d244986e3bb2c56f7d3ca84405d98 ("rcu: Correctly handle sparse
possible CPUs")
on test machine: vm-kbuild-yocto-ia32: 1 threads qemu-system-x86_64 -enable
On 29 May 2016 at 17:40, Rongrong Zou wrote:
> Signed-off-by: Rongrong Zou
> Signed-off-by: Jianhua Li
> ---
> MAINTAINERS | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f466673..a8a62e0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3957
Hi Chao,
On Sat, May 21, 2016 at 01:19:11PM +0800, Chao Yu wrote:
> From: Chao Yu
>
> If we fail to move data page during foreground GC, we should give another
> chance to writeback that page which was set dirty previously by writer.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/gc.c | 5 -
>
On Fri, May 27, 2016 at 12:48:48PM +0800, He YunLei wrote:
> On 2016/5/27 8:25, Jaegeuk Kim wrote:
> >If we get ENOMEM or EIO in f2fs_find_entry, we should stop right away.
> >Otherwise, for example, we can get duplicate directory entry by ->chash and
> >->clevel.
> >
> >Signed-off-by: Jaegeuk Kim
This patch adds the hardirq flags trace code for irq macros.
Signed-off-by: Huang Shijie
---
arch/arm64/include/asm/assembler.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/include/asm/assembler.h
b/arch/arm64/include/asm/assembler.h
index 10b017c..0be1d29 100644
---
In the current arm64 code, we trace the hardirq flags change occasionally.
Sometimes, the trace code is buggy, such as the el0_irq.
This patch sets
0.) in order to avoid the save/restore registers, add patches to adjust
the code.
1.) add the trace code at the entry/exit,
2.) add
To implement the hardirq flag tracing properly on arm64,
the trace_hardirqs_on() should be called before interrupts are turned on.
But the trace_hardirqs_on() may clobber the registers, such as x0 ~ 18.
Just as the el0_sync does, this patch uses the callee-saved registers:
1.) uses x25 to save
We have added the trace code to the interrupt enable/disable macros,
so the trace code in work_pending and do_notify_resume are
duplicated, just remove them.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 3 ---
arch/arm64/kernel/signal.c | 6 --
2 files changed, 9 deletions(-)
This patch uses the callee-saved registers x19/x20/scno to save the
x0/x7/x8 which will be used in the syscall path.
This patch makes preparation for the trace code.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
Just as the arm32 code does, record the hardirq changes at the entry/exit
code.
The trace code may changes some registers, but the syscall path
needs the x0 ~ x7, we restore them in the el0_svc_naked.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 15 +++
1 file changed
This patch adds restore_syscall_regs to restore the x0~x7 arguments from
the stack.
And this patch also uses this macro to simplify the code.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/
We record the hardirq flags changes in the entry/exit code now,
So the code becomes duplicated, just remove it.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 12
arch/arm64/mm/fault.c | 10 --
2 files changed, 22 deletions(-)
diff --git a/arch/arm64/kernel
There are two pachs which will restore the syscall registers (x0 - x7)
separately: the hardirq trace code and the context tracking code.
This patch makes the code to restore the syscall registers only once.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 13 +
1 file cha
We will add the hardirq flags trace code in the disable_irq, the trace
code may changes the x0, so save the x0 back into the stack before
disabling the interrupt,
This patch makes preparation for the later patch.
Signed-off-by: Huang Shijie
---
arch/arm64/kernel/entry.S | 2 +-
1 file changed,
101 - 200 of 277 matches
Mail list logo
