Currently we already have two pin configuration related callbacks
available for GPIO chips .set_single_ended() and .set_debounce(). In
future we expect to have even more, which does not scale well if we need
to add yet another callback to the GPIO chip structure for each possible
configuration para
When a GPIO driver is backed by a pinctrl driver the GPIO driver
sometimes needs to call the pinctrl driver to configure certain things,
like whether the pin is used as input or output. In addition to this
there are other configurations applicable to GPIOs such as setting
debounce time of the GPIO.
The current pinconf packed format allows only 16-bit argument limiting
the maximum value 65535. For most types this is enough. However,
debounce time can be in range of hundreths of milliseconds in case of
mechanical switches so we cannot represent the worst case using the
current format.
In order
Hi!
It seems that battery driver stopped working on N900 between -rc4 and
-rc5.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horse
Hi Minchan,
Thanks for reviewing.
On 2017/1/23 13:14, Minchan Kim wrote:
> Hello,
>
> On Thu, Jan 19, 2017 at 10:59:03PM +0800, ys...@foxmail.com wrote:
>> From: Yisheng Xie
>>
>> @@ -1527,7 +1527,8 @@ static int get_any_page(struct page *page, unsigned
>> long pfn, int flags)
>> {
>> int
Hi Magnus,
On Mon, Jan 23, 2017 at 12:40 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Bump up the maximum numbers of micro-TLBS to 48.
>
> Each IPMMU device instance get micro-TLB assignment via
> the "iommus" property in DT. Older SoCs tend to use a
> maximum number of 32 micro-TLBs per IPMMU
On Monday 23 January 2017 13:40:58 Pavel Machek wrote:
> It seems that battery driver stopped working on N900 between -rc4 and
> -rc5.
Which one of those 4 drivers stopped working?
--
Pali Rohár
pali.ro...@gmail.com
On Sun, Jan 22, 2017 at 09:31:44AM +0800, Alex Shi wrote:
>
> >Yeah, that could be problematic. The code snippet gives the general idea but
> >it
> >could be changed by for example by a flag telling the cpus when they enter
> >idle
> >to update their state_count. Or something like that.
>
> Yes
On 01/23, Oleg Nesterov wrote:
>
> Btw task_is_descendant() looks wrong at first glance.
No, I missed the 2nd ->group_leader dereference. Still this function looks
overcomplicated and the usage of thread_group_leader/group_leader just add
the unnecessary confusion. It can be simplified a little bi
On Mon, Jan 23, 2017 at 04:01:51PM +0800, Xunlei Pang wrote:
> We met an issue for kdump: after kdump kernel boots up,
> and there comes a broadcasted mce in first kernel, the
How does that even happen?
Lemme try to understand this correctly: the first kernel gets an
MCE, kdump starts and boots a
Hi John,
On 01/23/2017 08:24 PM, John Keeping wrote:
> Hi,
>
> On Fri, 20 Jan 2017 15:08:57 +0900, Jaehoon Chung wrote:
>> On 01/17/2017 10:38 PM, Romain Perier wrote:
>>> In my case I can reproduce the issue on the rock2 and the firefly-rk3288. A
>>> workaround is to
>>>
>>> comment the line ".
On 01/23/2017 01:16 PM, Arnd Bergmann wrote:
The __alloc_pages_slowpath() has gotten rather complex and gcc
is no longer able to follow the gotos and prove that the
alloc_flags variable is initialized at the time it is used:
mm/page_alloc.c: In function '__alloc_pages_slowpath':
mm/page_alloc.c:
Em Mon, 23 Jan 2017 11:44:54 +0100
Geert Uytterhoeven escreveu:
> Hi Mauro,
>
> On Mon, Jan 23, 2017 at 11:34 AM, Mauro Carvalho Chehab
> wrote:
> > Em Fri, 13 Jan 2017 12:03:24 -0800
> > Joe Perches escreveu:
> >> On Fri, 2017-01-13 at 12:41 -0700, Jonathan Corbet wrote:
> >> > On Tue, 10
Hi Florian,
On Fri, Jan 20, 2017 at 12:58 AM, Florian Fainelli wrote:
> On 01/19/2017 02:44 AM, Raviteja Garimella wrote:
>> Hi,
>>
>> On Thu, Jan 19, 2017 at 12:15 AM, Florian Fainelli
>> wrote:
>>> On 01/17/2017 12:05 AM, Raviteja Garimella wrote:
This patch splits the amd5536udc driver
Hi Chris,
On Mon, 23 Jan 2017 09:38:54 +0800, Chris Zhong wrote:
> On 01/22/2017 12:31 AM, John Keeping wrote:
> > The multiplication ratio for the PLL is required to be even due to the
> > use of a "by 2 pre-scaler". Currently we are likely to end up with an
> > odd multiplier even though there
On Mon, 23 Jan 2017 08:36:28 +0100,
Arvind Yadav wrote:
>
> Here, If ioremap_nocache will fail. It will return NULL.
> Kernel can run into a NULL-pointer dereference.
> This error check will avoid NULL pointer dereference.
>
> Signed-off-by: Arvind Yadav
> ---
> sound/pci/ymfpci/ymfpci_main.c |
> You haven't yet tried to fix anything,
I have got an other impression.
> but you've definitely introduced bugs...
I am also stumbling on my own share of software development mistakes.
> We have had this discussion many times.
The usual challenges remain from different opinions about involv
On 01/23/2017 at 04:48 PM, Dave Young wrote:
> Hi, Xunlei
>
> On 01/23/17 at 02:48pm, Xunlei Pang wrote:
>> CRASH_KERNEL_ADDR_MAX has been missing for a long time,
>> update it with more detailed explanation.
>>
>> Cc: Robert LeBlanc
>> Cc: Baoquan He
>> Signed-off-by: Xunlei Pang
>> ---
>> arc
On Mon, 23 Jan 2017 21:53:02 +0900, Jaehoon Chung wrote:
> On 01/23/2017 08:24 PM, John Keeping wrote:
> > Hi,
> >
> > On Fri, 20 Jan 2017 15:08:57 +0900, Jaehoon Chung wrote:
> >> On 01/17/2017 10:38 PM, Romain Perier wrote:
> >>> In my case I can reproduce the issue on the rock2 and the fir
Hi Mauro,
On Mon, Jan 23, 2017 at 2:01 PM, Mauro Carvalho Chehab
wrote:
> Em Mon, 23 Jan 2017 11:44:54 +0100
> Geert Uytterhoeven escreveu:
>> On Mon, Jan 23, 2017 at 11:34 AM, Mauro Carvalho Chehab
>> wrote:
>> > Em Fri, 13 Jan 2017 12:03:24 -0800
>> > Joe Perches escreveu:
>> >> On Fri, 2017-
Em Sun, Jan 22, 2017 at 02:51:25PM -0800, Alexei Starovoitov escreveu:
> On Sat, Jan 21, 2017 at 07:51:43AM +0300, Dan Carpenter wrote:
> > max_key is a value in the 0-63 range, so on 32 bit systems the shift
> > could wrap.
> >
> > Signed-off-by: Dan Carpenter
>
> Looks fine. I think 'net-next'
Hello,
The following program triggers use-after-free in perf_event_for_each:
https://gist.githubusercontent.com/dvyukov/f1c354a8356e42f4d0b3d912e1bec956/raw/31d7ecdf6dc2c7327b80ef8581a39c823bbe405d/gistfile1.txt
BUG: KASAN: use-after-free in perf_event_for_each_child+0x15f/0x180
kernel/events/cor
On 01/23/2017 at 08:51 PM, Borislav Petkov wrote:
> On Mon, Jan 23, 2017 at 04:01:51PM +0800, Xunlei Pang wrote:
>> We met an issue for kdump: after kdump kernel boots up,
>> and there comes a broadcasted mce in first kernel, the
> How does that even happen?
>
> Lemme try to understand this correct
On 01/23/2017 12:08 PM, SF Markus Elfring wrote:
> Would you like to check run time consequences
> for the shown error code settings once more?
Sure, lets for now ignore the fact that the performance of an error path
does not matter most of the time.
Have you actually looked at your patch? After
On Mon, Jan 23, 2017 at 02:21:45PM +0100, SF Markus Elfring wrote:
> > You haven't yet tried to fix anything,
>
> I have got an other impression.
>
Name three bugs that you have fixed (not cleanups).
regards,
dan carpenter
Am 04.01.2017 um 23:06 schrieb Jonathan Corbet :
> On Mon, 2 Jan 2017 16:22:22 +0100
> Paolo Bonzini wrote:
>
>> these patches are the result of my experiments with using kernel-doc
>> for QEMU's documentation. Patches 1 and 2 should be relatively
>> straightforward, as they are simple bugfix
On Fri, Jan 20, 2017 at 09:25:02PM +0100, Richard Cochran wrote:
> On Fri, Jan 20, 2017 at 10:20:29AM -0200, Marcelo Tosatti wrote:
> > Emulate PTP_SYS_OFFSET by using an arithmetic mean of the
> > realtime samples from ->getcrosststamp callback.
>
> This change log is not very informative.
>
> Y
If the device-tree 'reg' node doesn't reserve enough
space for the DP, fail to bind.
Reviewed-by: Brian Starkey
Signed-off-by: Mihail Atanassov
---
drivers/gpu/drm/arm/malidp_drv.c | 20
drivers/gpu/drm/arm/malidp_regs.h | 2 ++
2 files changed, 22 insertions(+)
diff --g
Refuse to bind if the device-tree compatible string
lists a different hardware version.
Reviewed-by: Brian Starkey
Signed-off-by: Mihail Atanassov
---
A couple of small improvements to driver-to-hardware binding.
drivers/gpu/drm/arm/malidp_drv.c | 52 +++
On Tue, Jan 10, 2017 at 03:55:15PM +0800, Chen Feng wrote:
> + memory@0 {
> + device_type = "memory";
> + reg = <0x0 0x0040 0x0 0xbfe0>;
> + };
The unit-address here is incorrect. The base address of this memory is
not zero.
> + timer {
> +
On (01/23/17 13:17), Minchan Kim wrote:
> zram_reset_device waits ongoing writepage pages completed by
> zram->refcount logic. However, it's pointless because before
> the reset, we prevent further opening of zram by zram->claim
> and flush all of pending IO by fsync_bdev so there should be
> no pe
On 23/01/2017 14:42, Markus Heiser wrote:
>
> Am 04.01.2017 um 23:06 schrieb Jonathan Corbet :
>
>> On Mon, 2 Jan 2017 16:22:22 +0100
>> Paolo Bonzini wrote:
>>
>>> these patches are the result of my experiments with using kernel-doc
>>> for QEMU's documentation. Patches 1 and 2 should be re
On Wed, Jan 11, 2017 at 02:50:59PM +0100, David Engraf wrote:
> On newer boards the TC can be read as single 32 bit value without locking.
> Thus the clock can be used as reference for sched_clock which is much more
> accurate than the jiffies implementation.
>
> Tested on a Atmel SAMA5D2 board.
>
On Sat, Jan 21, 2017 at 7:49 PM, Chunfeng Yun wrote:
> Hi,
>
> On Sat, 2017-01-21 at 14:11 -0600, Rob Herring wrote:
>> On Wed, Jan 18, 2017 at 02:08:27PM +0800, Chunfeng Yun wrote:
>> > add a reference clock for compatibility
>>
>> Why? This block suddenly has 2 clocks instead of 1?
> In fact, th
On Mon, Jan 16, 2017 at 05:06:51PM +0100, Nicholas Mc Guire wrote:
> Add declarations for the camellia substitution box to allow a clean build.
>
> Signed-off-by: Nicholas Mc Guire
> ---
> Problem reported by sparse
> arch/x86/crypto/camellia_glue.c:65:21: warning: symbol 'camellia_sp1000'
>
On Sat, Jan 21, 2017 at 8:50 PM, Chunfeng Yun wrote:
> On Sat, 2017-01-21 at 14:08 -0600, Rob Herring wrote:
>> On Wed, Jan 18, 2017 at 02:00:14PM +0800, Chunfeng Yun wrote:
>> > add a new compatible string for "mt2712", and a new reference clock
>> > for SuperSpeed analog phy;
>> >
>> > Signed-of
Hi Mark,
On 2017/1/23 13:46, Mark Rutland wrote:
> On Tue, Jan 10, 2017 at 03:55:15PM +0800, Chen Feng wrote:
>> +memory@0 {
>> +device_type = "memory";
>> +reg = <0x0 0x0040 0x0 0xbfe0>;
>> +};
>
> The unit-address here is incorrect. The base address of th
On 23/01/2017 10:48, SF Markus Elfring wrote:
>> The others are useless churn or they make the result uselessly different
>> from the rest of KVM code.
>
> I got an other view about potential benefits around the suggested movements
> for error code settings.
I'll consider them when your emails s
KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
uninitialized memory in cfq_init_cfqq():
==
BUG: KMSAN: use of unitialized memory
...
Call Trace:
[< inline >] __dump_stack lib/dump_stack.c:15
[] dump
Big endian CPUs require SWAP_IO_SPACE enabled to swap accesses to little
endian peripherals.
Without this patch, big endian kernels fail to communicate with little
endian periperals, such as PCI devices, on QEMU and FPGA based
platforms.
Signed-off-by: Matt Redfearn
Fixes: eed0eabd12ef ("MIPS: g
On Sun, Jan 22, 2017 at 01:36:28PM -0800, James Bottomley wrote:
> On Sun, 2017-01-22 at 23:04 +0200, Jarkko Sakkinen wrote:
> > On Sun, Jan 22, 2017 at 11:01:07PM +0200, Jarkko Sakkinen wrote:
> > > On Sun, Jan 22, 2017 at 10:30:55PM +0200, Jarkko Sakkinen wrote:
> > > > On Sun, Jan 22, 2017 at 10
On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote:
> On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > Changes since 20170118:
> >
> > The audit tree gained a conflict against Linus' tree.
> >
> > The tip tree gained a conflict against the security tree.
On 20/01/2017 19:19, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 19 Jan 2017 22:45:56 +0100
>
> * A local variable was set to an error code in five cases
> before a concrete error situation was detected.
> Thus move the corresponding assignments into
> if branches to indi
On 10/01/17 07:55, Chen Feng wrote:
> Add initial dtsi file to support Hisilicon Hi3660 SoC with
> support of Octal core CPUs in two clusters(4 * A53 & 4 * A73).
>
> Also add dts file to support HiKey960 development board which
> based on Hi3660 SoC.
> The output console is earlycon "earlycon=pl
On 20/01/2017 19:21, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 20 Jan 2017 10:30:26 +0100
>
> A local variable was set to an error code in a few cases before a concrete
> error situation was detected. Thus move the corresponding assignments into
> if branches to indicate a so
On Thu, 5 Jan 2017, Benjamin Tissoires wrote:
> I don't know what to do about hiddev too. I don't know if we have actual
> users besides some debugging tools. And hidraw is much better than
> hiddev, so ideally, I'd like to remove it some way.
First, I'd love to get rid of HID_QUIRK_NO_INIT_REP
On Fri, Jan 20, 2017 at 06:12:38AM -0800, Vadim Lomovtsev wrote:
Please ignore this accordingly to mysypo
> Having kernel modules with debug sections consumes a lot of
> hdd space, increases size of kernel rpm, initrd image grows
> and in some cases kernel even can't be installed due to
> insuffici
Hi!
> It seems that battery driver stopped working on N900 between -rc4 and
> -rc5.
pavel@amd:/data/l/linux-n900$ git bisect log
# bad: [41f283973653dc44af47585fa79fb6da6ffdc2e2] Merge
/data//l/clean-cg into mini-v4.10
# good: [4f8d9925eb1de1ec1c4183164f1bc7b01f5ae185] It seems mainline
-rc4 did
Hello,
I've started seeing the following WARNING while running syzkaller fuzzer:
Out of memory: Kill process 30627 (syz-execprog) score 57 or sacrifice child
Killed process 30962 (syz-executor) total-vm:20996kB, anon-rss:64kB,
file-rss:0kB, shmem-rss:0kB
oom_reaper: reaped process 3916 (syz-execu
On Mon 2017-01-23 13:42:06, Pali Rohár wrote:
> On Monday 23 January 2017 13:40:58 Pavel Machek wrote:
> > It seems that battery driver stopped working on N900 between -rc4 and
> > -rc5.
>
> Which one of those 4 drivers stopped working?
n900-battery.
Good Day Dear,
My name is Ms. Joyes Dadi, I am glad you are reading this letter and I hope
we will start our communication and I know that this message will look strange,
surprising and probably unbelievable to you, but it is the reality. I want to
make a donation of money to you.
I contact you b
On Mon, 2017-01-23 at 15:34 +0300, Mika Westerberg wrote:
> This series makes it possible to configure pins from GPIO chip drivers
> by
> implementing a new callback .set_config(). This callback replaces the
> existing .set_single_ended() and .set_debounce() simply because adding
> new
> callbacks
On 01/23/2017 06:19 AM, Pavel Machek wrote:
Hi!
It seems that battery driver stopped working on N900 between -rc4 and
-rc5.
pavel@amd:/data/l/linux-n900$ git bisect log
# bad: [41f283973653dc44af47585fa79fb6da6ffdc2e2] Merge
/data//l/clean-cg into mini-v4.10
# good: [4f8d9925eb1de1ec1c4183164
Having kernel modules with debug sections consumes a lot of
hdd space, increases size of kernel rpm, initrd image grows
and in some cases kernel even can't be installed due to
insufficient hdd space for modules.
Set INSTALL_MOD_STRIP=1 to enable debug info strip at rpm modules
install phase.
Sign
On Tue, 2017-01-17 at 15:35 +0100, Benjamin Tissoires wrote:
> Hey guys,
>
> I tried to revive the in-kernel battery support for HID++ devices.
> I was thinking of doing just a few patches, but in the end I had to
> do
> cleanups and some more tweaks...
>
> So, the final result is that now hid-lo
On Sun, Jan 22, 2017 at 11:38:48PM -0800, Dmitry Torokhov wrote:
> When augmenting ACPI-enumerated devices with additional property data based
> on DMI info, a module has often several potential property sets, with only
> one being active on a given box. In order to save memory it should be
> possi
Am 23.01.2017 um 14:58 schrieb Paolo Bonzini :
>>
>> Hi Paolo !
>>
>> Sorry for my late reply, I'am testing patch 2:
>>
>> https://www.mail-archive.com/linux-doc@vger.kernel.org/msg08503.html
>>
>> but I can't find any changes in the reST output (even not in
>> include/linux/log2.h
>> you me
On Sun, Jan 22, 2017 at 11:38:49PM -0800, Dmitry Torokhov wrote:
> There is no reason why statically defined properties should be modifiable,
> so let's make device_add_properties() and the rest of pset_*() functions to
> take const pointers to properties.
>
> This will allow us to mark properties
On Mon 2017-01-23 06:31:31, Guenter Roeck wrote:
> On 01/23/2017 06:19 AM, Pavel Machek wrote:
> >Hi!
> >
> >>It seems that battery driver stopped working on N900 between -rc4 and
> >>-rc5.
> >
> >pavel@amd:/data/l/linux-n900$ git bisect log
> ># bad: [41f283973653dc44af47585fa79fb6da6ffdc2e2] Merg
mmap_init() is no longer associated with VMA slab. so fix it.
Signed-off-by: seokhoon.yoon
---
mm/mmap.c | 2 +-
mm/nommu.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/mmap.c b/mm/mmap.c
index dc4291d..3794ada 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -3433,7 +3433
From: Cristian Birsan
Update atmel udc driver with a new enpoint allocation scheme. The data
sheet requires that all endpoints are allocated in order.
Signed-off-by: Cristian Birsan
---
drivers/usb/gadget/udc/Kconfig | 14 ++
drivers/usb/gadget/udc/atmel_usba_udc.c | 236
From: Cristian Birsan
Hi,
This patch updates the usb endpoint allocation scheme for atmel usba
driver to make sure all endpoints are allocated in order. This requirement
comes from the datasheet of the controller.
The allocation scheme is decided by fifo_mode parameter. For fifo_mode = 0
the dr
On Thu, Jan 19, 2017 at 04:24:09PM +0100, Frieder Schrempf wrote:
> This patch adds the documentation for the devicetree bindings to set
> the volume levels.
>
> Signed-off-by: Frieder Schrempf
> ---
> Changes in v3:
> - change description of volume-levels to be used for linear levels
>
> ...
On Sat, 2017-01-21 at 10:12 +, Winkler, Tomas wrote:
> >
> > > -struct mei_device *mei_txe_dev_init(struct pci_dev *pdev)
> > > +struct mei_device *devm_mei_txe_init(struct pci_dev *pdev)
> >
> > Ditto.
> >
> > > end:
> > > + pci_set_drvdata(pdev, NULL);
> >
> > Not needed.
>
> Ple
On Wed, Dec 21, 2016 at 05:21:05PM +0300, Alexander Kochetkov wrote:
> Hello Heiko, Daniel!
>
> Are there any reasons why the patches [1][2] are not applied yet into kernel?
> How can I help in applying patches?
Hi Alexander,
sorry for the delay. Let me review them before taking the patchset.
H
Add to cc Lennart Poettering
On 01/23/2017 02:55 PM, Oleg Nesterov wrote:
On 01/22, Pavel Tikhomirov wrote:
Hmm. could you explain how this change helps CRIU? I mean, why
restorer can't do prctl(CHILD_SUBREAPER) before the first fork?
Imagine we have these tree in pidns:
1: has_child_sub
From: Yisheng Xie
This patch is to extends soft offlining framework to support
non-lru page, which already support migration after
commit bda807d44454 ("mm: migrate: support non-lru movable page
migration")
When memory corrected errors occur on a non-lru movable page,
we can choose to stop using
On Mon, Jan 23, 2017 at 09:35:53PM +0800, Xunlei Pang wrote:
> One possible timing sequence would be:
> 1st kernel running on multiple cpus panicked
> then the crash dump code starts
> the crash dump code stops the others cpus except the crashing one
> 2nd kernel boots up on the crash cpu with "nr_
On Thu, Jan 19, 2017 at 08:36:31AM -0800, Andrey Smirnov wrote:
> Add various bits of code needed to support i.MX7D variant of the IP.
>
> Cc: yurov...@gmail.com
> Cc: Richard Zhu
> Cc: Lucas Stach
> Cc: Bjorn Helgaas
> Cc: Fabio Estevam
> Cc: Shawn Guo
> Cc: Rob Herring
> Cc: Mark Rutland
On 01/23/2017 08:50 PM, Daniel Lezcano wrote:
> On Sun, Jan 22, 2017 at 09:31:44AM +0800, Alex Shi wrote:
>>
>>> Yeah, that could be problematic. The code snippet gives the general idea
>>> but it
>>> could be changed by for example by a flag telling the cpus when they enter
>>> idle
>>> to upd
On Sun, Jan 15, 2017 at 01:37:50PM +0100, Nicolas Iooss wrote:
> The fourth argument of dma_map_sg() and dma_unmap_sg() is an item of
> dma_data_direction enum. Function img_hash_xmit_dma() wrongly used
> DMA_MEM_TO_DEV, which is an item of dma_transfer_direction enum.
>
> Replace DMA_MEM_TO_DEV (
On Thu, Jan 19, 2017 at 11:15:07AM +0100, Greg KH wrote:
> On Wed, Jan 18, 2017 at 09:31:56AM -0800, Luis R. Rodriguez wrote:
> > If you modify the target asm we currently do not force the
> > recompilation of the firmware files. The target asm is in
> > the firmware/Makefile, peg this file as a de
On Thu, Jan 19, 2017 at 10:28:05PM +0100, Denys Vlasenko wrote:
> %progbits form is used on ARM (where @ is a comment char).
>
> x86 consistently uses @progbits everywhere else.
>
> Signed-off-by: Denys Vlasenko
Patch applied. Thanks.
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.a
On Fri, Jan 20, 2017 at 01:41:07PM +0800, Ryder Lee wrote:
> Hi,
>
> This series of patches is a global rework of the mtk driver.
> Fix bug - incomplete DMA data transfer when SG buffer dst.len != src.len
>
> It also updates some part of the code to make them more generic. For
> instance the cryp
On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote:
> When augmenting ACPI-enumerated devices with additional property data
> based
> on DMI info, a module has often several potential property sets, with
> only
> one being active on a given box. In order to save memory it should be
> possible
On Thu, Jan 19, 2017 at 10:33:04PM +0100, Denys Vlasenko wrote:
> A lot of asm-optimized routines in arch/x86/crypto/ keep its
> constants in .data. This is wrong, they should be on .rodata.
>
> Mnay of these constants are the same in different modules.
> For example, 128-bit shuffle mask 0x000102
On Mon, Jan 23, 2017 at 03:59:52PM +0100, Luis R. Rodriguez wrote:
> On Thu, Jan 19, 2017 at 11:15:07AM +0100, Greg KH wrote:
> > On Wed, Jan 18, 2017 at 09:31:56AM -0800, Luis R. Rodriguez wrote:
> > > If you modify the target asm we currently do not force the
> > > recompilation of the firmware f
On Mon, Jan 23, 2017 at 6:52 AM, Rob Herring wrote:
> On Thu, Jan 19, 2017 at 08:36:31AM -0800, Andrey Smirnov wrote:
>> Add various bits of code needed to support i.MX7D variant of the IP.
>>
>> Cc: yurov...@gmail.com
>> Cc: Richard Zhu
>> Cc: Lucas Stach
>> Cc: Bjorn Helgaas
>> Cc: Fabio Este
use dma_zalloc_coherent() instead of dma_alloc_coherent and memset().
Signed-off-by: Srinivas Kandagatla
---
drivers/net/wireless/ath/ath10k/ce.c | 9 +
drivers/net/wireless/ath/ath10k/pci.c | 3 +--
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/at
The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:
Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to 0db1dba5dfaf70fb3baf07973
DIAG_TRANSFER_LIMIT is redefined with same value and comments
just below this entry, remove this duplicate entry.
Signed-off-by: Srinivas Kandagatla
---
drivers/net/wireless/ath/ath10k/pci.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.h
b/drivers/
CORE_CTRL_ADDRESS is offset in register address space, it does not
make sense to OR it to derive the final address. It looks like its
a typo, so fix it.
Signed-off-by: Srinivas Kandagatla
---
drivers/net/wireless/ath/ath10k/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
On Mon, Jan 23, 2017 at 9:02 AM, Greg KH wrote:
> On Mon, Jan 23, 2017 at 03:59:52PM +0100, Luis R. Rodriguez wrote:
>> On Thu, Jan 19, 2017 at 11:15:07AM +0100, Greg KH wrote:
>> > On Wed, Jan 18, 2017 at 09:31:56AM -0800, Luis R. Rodriguez wrote:
>> > > If you modify the target asm we currently
If you modify the target asm we currently do not force the
recompilation of the firmware files. The target asm is in
the firmware/Makefile, peg this file as a dependency to
require re-compilation of firmware targets when the asm
changes.
Signed-off-by: Luis R. Rodriguez
---
Michal,
I had this p
Regularly, when a new header is created in include/uapi/, the developer
forgets to add it in the corresponding Kbuild file. This error is usually
detected after the release is out.
In fact, all headers under uapi directories should be exported, thus it's
useless to have an exhaustive list.
After
This header file is exported, thus move it to uapi.
Signed-off-by: Nicolas Dichtel
---
arch/h8300/include/asm/bitsperlong.h | 14 --
arch/h8300/include/uapi/asm/bitsperlong.h | 14 ++
2 files changed, 14 insertions(+), 14 deletions(-)
delete mode 100644 arch/h8300/i
This patch removes the need of subdir-y. Now all files/directories under
arch//include/uapi/ are exported.
The only change for userland is the layout of the command 'make
headers_install_all': directories asm- are replaced by arch-/.
Those new directories contains all files/directories of the spec
This header file is exported, thus move it to uapi.
Signed-off-by: Nicolas Dichtel
---
arch/x86/include/asm/msr-index.h | 698 --
arch/x86/include/uapi/asm/msr-index.h | 698 ++
2 files changed, 698 insertions(+), 698 deletions
This header file is exported, but from a userland pov, it's just a wrapper
to asm-generic/setup.h.
Signed-off-by: Nicolas Dichtel
Reviewed-by: Tobias Klauser
---
arch/nios2/include/uapi/asm/Kbuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/nios2/include/uapi/asm/Kbuild
b/arch/nio
This option was added in commit c7bb349e7c25 ("kbuild: introduce destination-y
for exported headers") but never used in-tree.
Signed-off-by: Nicolas Dichtel
---
Documentation/kbuild/makefiles.txt | 23 ---
scripts/Makefile.headersinst | 2 +-
2 files changed, 5 inserti
After the last four patches, all exported headers are under uapi/, thus
input-files2 are not needed anymore.
The side effect is that input-files1-name is exactly header-y.
Note also that input-files3-name is genhdr-y.
Signed-off-by: Nicolas Dichtel
---
scripts/Makefile.headersinst | 34
On Mon, Jan 23, 2017 at 02:26:25AM -0500, Nayna Jain wrote:
> The TPM device driver defines ascii and binary methods for
> displaying the TPM 1.2 event log via securityfs files, which are
> needed for validating a TPM quote. The device driver for TPM 2.0
> does not have similar support for displayi
On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote:
> There is no reason why statically defined properties should be
> modifiable,
> so let's make device_add_properties() and the rest of pset_*()
> functions to
> take const pointers to properties.
>
> This will allow us to mark properties as
Here is the v4 of this series. Seems there was too many people cc'ed, so I've
removed arch specific ml. Hope it's better now.
Patches #1 to #4 are just cleanup: some exported headers were still under
a non-uapi directory.
The patch #5 was spotted by code review: there is no in-tree user of this
fu
On Mon, Jan 23, 2017 at 02:26:27AM -0500, Nayna Jain wrote:
> Unlike the device driver support for TPM 1.2, the TPM 2.0 does
> not support the securityfs pseudo files for displaying the
> firmware event log.
>
> This patch enables support for providing the TPM 2.0 event log in
> binary form. TPM 2
On Mon, Jan 23, 2017 at 10:31:12AM +0100, Valentin Rothberg wrote:
> Hi Andrew,
>
> your commit cf1a56a4cf19 ("net: dsa: Remove hwmon support") has popped
> up in today's linux-next. The commit removes all references on
> NET_DSA_HWMON but the following:
>
> Documentation/networking/dsa/dsa.txt:
On 01/23/2017 02:20 AM, Johannes Thumshirn wrote:
> On Sun, Jan 22, 2017 at 09:33:08AM +0100, SF Markus Elfring wrote:
>> From: Markus Elfring
>> Date: Sat, 21 Jan 2017 22:15:33 +0100
>>
>> The script "checkpatch.pl" pointed information out like the following.
>>
>> ERROR: do not use assignment in
From: Patrick Bruenn
The pinmux configuration in device tree is different from manual
muxing in /board/freescale/mx53loco/mx53loco.c
It seems the device tree configuration is never used by any kernel
driver and the correct setting, preconfigured by u-boot, was never
overwritten. So this issue nev
From: Markus Heiser [mailto:markus.hei...@darmarit.de]
> Am 23.01.2017 um 09:18 schrieb Matthew Wilcox
> :
> Hi Matthew !
>
> short answer: Thanks a lot
> Acked-by: Markus Heiser
Excellent!
> to be more verbose:
>what I have tested and what I recommend ...
>
> I maintain my own stack
On 01/23/2017 05:06 AM, SF Markus Elfring wrote:
>>> We have got different preferences for the placement of error code settings.
>> Yes we do, so what's the point? Both are OK.
>
> Can a function implementation be executed a bit faster in the case
> that error codes will usually only matter if the
501 - 600 of 823 matches
Mail list logo
