From: dcashman
ASLR only uses as few as 8 bits to generate the random offset for the
mmap base address on 32 bit architectures. This value was chosen to
prevent a poorly chosen value from dividing the address space in such
a way as to prevent large allocations. This may not be an issue on all
pl
From: dcashman
arm: arch_mmap_rnd() uses a hard-code value of 8 to generate the
random offset for the mmap base address. This value represents a
compromise between increased ASLR effectiveness and avoiding
address-space fragmentation. Replace it with a Kconfig option, which
is sensibly bounded,
On 12/21/2015 06:10 AM, Arnd Bergmann wrote:
On Monday 21 December 2015, Gabriele Paoloni wrote:
-Original Message-
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Tomasz Nowicki
Some platforms may not be fully compliant with generic
On Sun, Dec 20, 2015 at 01:04:59PM -0800, Guenter Roeck wrote:
> The watchdog character device is currently created in watchdog_dev.c,
> and the watchdog device in watchdog_core.c. This results in
> cross-dependencies, since device creation needs to know the watchdog
> character device number as we
On Fri 18-12-15 22:22:18, Ross Zwisler wrote:
> To properly support the new DAX fsync/msync infrastructure filesystems
> need to call dax_pfn_mkwrite() so that DAX can track when user pages are
> dirtied.
The patch looks good to me. You can add:
Reviewed-by: Jan Kara
On Fri 18-12-15 22:22:19, Ross Zwisler wrote:
> To properly support the new DAX fsync/msync infrastructure filesystems
> need to call dax_pfn_mkwrite() so that DAX can track when user pages are
> dirtied.
The patch looks good to me. You can add:
Reviewed-by: Jan Kara
On Tue, Dec 15, 2015 at 08:25:37PM +, Elliott, Robert (Persistent Memory)
wrote:
> This isn't exactly what you're looking for, but here is
> an example of fio doing reads from pmem devices (reading
> from NVDIMMs, writing to DIMMs) with various transfer
> sizes.
... and "fio" is?
> At 256 K
On Sun, Dec 20, 2015 at 01:05:00PM -0800, Guenter Roeck wrote:
> All variables required by the watchdog core to manage a watchdog are
> currently stored in struct watchdog_device. The lifetime of those
> variables is determined by the watchdog driver. However, the lifetime
> of variables used by th
On 12/21/15 00:05, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151218:
>
on i386 or x86_64:
when CONFIG_MTD=m and CONFIG_LOGFS=y:
fs/built-in.o: In function `logfs_mount':
super.c:(.text+0xb695e): undefined reference to `logfs_get_sb_mtd'
fs/built-in.o: In function `logfs_get_sb_bdev
On Mon, Dec 21, 2015 at 05:04:11PM +, Bryan O'Donoghue wrote:
> > This patch also export efi_capsule_supported() function symbol for
> > verifying the submitted capsule header in this kernel module.
>
> 1. Should be a separate patch
> 2. Suggested, rewording for that patch log
>
> 2/2 Title
Since early in the 4.3-rcx series, my Dell Latitude D600 with a 32-bit kernel
fails to boot. Unfortunately, I did not discover this until late in the 4.4-rcX
cycle. The symptom is that the kernel echos the "Loading initial ramdisk ..."
message and then hangs.
The problem was bisected to commit
On Fri, Dec 18, 2015 at 05:44:37PM +0300, Yury Norov wrote:
> On Fri, Dec 18, 2015 at 05:11:12PM +0300, Yury Norov wrote:
> > On Thu, Dec 17, 2015 at 11:41:53AM +, Catalin Marinas wrote:
> > > On Wed, Dec 16, 2015 at 12:42:34AM +0300, Yury Norov wrote:
> > > > Reviewed-by: David Daney
> > > >
On Sat, 19 Dec 2015, Darren Hart wrote:
On Sat, Dec 19, 2015 at 07:24:38PM +0100, Thomas Gleixner wrote:
- Why are the reviews so sloppy and useless?
The one I'm answering to is just hillarious and the other one picks
a random commit, claims that it inadvertantly introduced the issue
Dear User
We recently detected an unusual activity from your email account, hence your
mailbox has been temporally suspended by the system administrator, please
recover your account by clicking on the following link OR copy to your browser:
http://adnimtoscpenalfaqaotiveuqdeta.2fh.co/BE3/ITupda
From: Liu Jiang
Previously msi_domain_alloc() assumes MSI irqdomains always have parent
irqdomains, but that's not true for the new Intel VMD devices. So relax
msi_domain_alloc() to support parentless MSI irqdomains.
Signed-off-by: Jiang Liu
Signed-off-by: Keith Busch
---
kernel/irq/msi.c | 8
Now on version 7, mostly cosmetic.
v6->v7:
Removed PCI resource window patch rejecting child bus that doesn't fit in
parent's window. There are additional caveats the maintainer brought up
that need more consideration. Since we are not dependent on that patch,
it is removed from the series.
On Mon, 2015-12-21 at 18:37 +0100, Borislav Petkov wrote:
> On Mon, Dec 21, 2015 at 05:04:11PM +, Bryan O'Donoghue wrote:
> > > This patch also export efi_capsule_supported() function symbol
> > > for
> > > verifying the submitted capsule header in this kernel module.
> >
> > 1. Should be a se
Signed-off-by: Keith Busch
---
drivers/pci/msi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index 7eaa4c8..fb7506f 100644
--- a/drivers/pci/msi.c
+++ b/drivers/pci/msi.c
@@ -1126,6 +1126,7 @@ struct pci_dev *msi_desc_to_pci_dev(struct msi_desc *des
The Intel Volume Management Device (VMD) is an integrated endpoint on the
platform's PCIe root complex that acts as a host bridge to a secondary
PCIe domain. BIOS can reassign one or more root ports to appear within
a VMD domain instead of the primary domain. The immediate benefit is
that additiona
On Fri, 18 Dec 2015 14:39:19 -0500
Damien Riegel wrote:
> This commit adds support for the TS-4800 interrupt controller. This
> controller is instantiated in a companion FPGA, and multiplex interrupts
> for other FPGA IPs.
>
> As this component is external to the SoC, the SoC might need to reser
New x86 pci h/w will require dma operations specific to that domain. This
patch allows those domains to register their operations, and sets devices
as they are discovered in that domain to use them.
Signed-off-by: Keith Busch
---
arch/x86/include/asm/device.h | 10 ++
arch/x86/pci/common
On Mon, Dec 21, 2015 at 06:15:12PM +0100, Jan Kara wrote:
> On Fri 18-12-15 22:22:15, Ross Zwisler wrote:
> > Add support for tracking dirty DAX entries in the struct address_space
> > radix tree. This tree is already used for dirty page writeback, and it
> > already supports the use of exceptiona
Signed-off-by: Keith Busch
---
kernel/irq/irqdomain.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index 22aa961..ca05cc8 100644
--- a/kernel/irq/irqdomain.c
+++ b/kernel/irq/irqdomain.c
@@ -1058,6 +1058,7 @@ void irq_domain_set_info(struct i
New pci device provides additional pci domains that start above what 16
bits can address.
Signed-off-by: Keith Busch
---
drivers/pci/pcie/aer/aer_inject.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/pci/pcie/aer/aer_inject.c
b/drivers/pci/pcie/ae
On Mon, Dec 21, 2015 at 9:05 AM, Ross Zwisler
wrote:
> On Sat, Dec 19, 2015 at 10:37:46AM -0800, Dan Williams wrote:
>> On Fri, Dec 18, 2015 at 9:22 PM, Ross Zwisler
>> wrote:
[..]
>> Hi Ross, I should have realized this sooner, but what guarantees that
>> the address returned by RADIX_DAX_ADDR(e
Remove the WARN() from the beN_to_cpu macro, which is used as a param to a
pr_debug() call. With a certain kernel config, this printk-in-printk
results in the no_printk() macro trying to recursively call the
no_printk() macro, and since macros can't recursively call themselves
a build error result
On 12/20/2015 04:20 AM, Andy Lutomirski wrote:
I hit this warning fairly frequently when resuming 4.4-rc5:
ret = usermodehelper_read_trylock();
if (WARN_ON(ret)) {
dev_err(device, "firmware: %s will not be loaded\n",
name);
goto out;
On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
> On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
>>
>> On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote:
>>>
>>> On Sun, Dec 20, 2015 at 10:17 PM, Andy Shevchenko
>>> wrote:
On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård
The Shared Memory accounting support is present in Kernel since
commit 4b02108ac1b3 ("mm: oom analysis: add shmem vmstat") and in
userland free(1) since 2014. This patch updates the Documentation to
reflect this change.
Signed-off-by: Rodrigo Freire
---
V2: Better wording as per Vlastimil Babka'
On Mon, Dec 21, 2015 at 4:49 PM, Aleksey Makarov
wrote:
> From: Graeme Gregory
>
> In ACPI this device is only defined in SBSA mode so
> if we are coming from ACPI use this mode.
>
> Signed-off-by: Graeme Gregory
> Signed-off-by: Aleksey Makarov
> ---
> drivers/tty/serial/amba-pl011.c | 37 +++
On Wed, 16 Dec 2015, Tomasz Nowicki wrote:
> In drivers/xen/pci.c, there are arch x86 dependent codes when
> CONFIG_PCI_MMCONFIG is enabled, since CONFIG_PCI_MMCONFIG
> depends on ACPI, so this will prevent XEN PCI running on other
> architectures using ACPI with PCI_MMCONFIG enabled (such as ARM64
Andy Shevchenko writes:
> On Mon, Dec 21, 2015 at 2:15 PM, Måns Rullgård wrote:
>> Andy Shevchenko writes:
>>
>>> +Viresh
>>>
>>> On Mon, Dec 21, 2015 at 2:58 AM, Måns Rullgård wrote:
Andy Shevchenko writes:
> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote:
>> Julian
This lock is already taken in ata_scsi_queuecmd() a few levels up the
call stack so attempting to take it here is an error. Moreover, it is
pointless in the first place since it only protects a single, atomic
assignment.
Enabling lock debugging gives the following output:
===
Andy Shevchenko writes:
> On Mon, 2015-12-21 at 15:24 +, Måns Rullgård wrote:
>> Julian Margetson writes:
>>
>>
>> Oh, that one again. My patch still applies. Here it is as applied
>> to
>> that revision of the file.
>>
>> From what I can tell, that bug has always been there. Probably
On Tue, Dec 15, 2015 at 05:29:30PM -0800, Tony Luck wrote:
> Copy the existing page fault fixup mechanisms to create a new table
> to be used when fixing machine checks. Note:
> 1) At this time we only provide a macro to annotate assembly code
> 2) We assume all fixups will in code builtin to the k
On Mon, Dec 21, 2015 at 6:41 PM, Aleksey Makarov
wrote:
> From: Graeme Gregory
>
> On ARM64 some devices use the AMBA device and not the platform bus for
> probing so add support for this. Uses a dummy clock for apb_pclk as ACPI
> does not have a suitable clock representation and to keep the core
Hello.
On 12/21/2015 03:46 PM, Vikas Bansal wrote:
From: Sumit Batra
Pre-Condition
URB with Scatter Gather list is queued to bulk OUT endpoint.
Every buffer in scatter gather list is not a multiple of maximum packet
size for that endpoint(short packet).
CHAIN bit is set for all TRBs in a TD s
On 12/21/2015 1:55 PM, Andy Shevchenko wrote:
On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote:
On Sun, Dec 20, 2015 at 10:17 PM, Andy Shevchenko
wrote:
On Sun, Dec 20, 2015 at 8:
Andy Shevchenko writes:
> On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
>> On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
>>>
>>> On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote:
On Sun, Dec 20, 2015 at 10:17 PM, Andy Shevchenko
wrote:
>
> On Sun, Dec
Changes from v5:
- rs485_emul variable has been renamed to em485 to follow function names
convention
Changes from v4:
- Add commit message to 1/3
Changes from v3:
- Completely redesigned.
Changes from v2:
- Introduced SER_RS485_SOFTWARE to show that software implementation is being
used
- se
Implementation of software emulation of RS485 direction handling is based
on omap_serial driver.
Before and after transmission RTS is set to the appropriate value.
Note that before calling serial8250_em485_init the caller has to
ensure that UART will interrupt when shift register empty. Otherwise,
The omapfb is failing to build in -next due missing declarations for
dss_feat_get_supported_displays() and dss_feat_get_supported_outputs():
CC [M] drivers/video/fbdev/omap2//omapfb/dss/dss.o
drivers/video/fbdev/omap2//omapfb/dss/dss.c: In function 'dss_save_context':
drivers/video/fbdev/omap2//
Use software emulated RS485 direction control to provide RS485 API existed in
omap_serial driver. Note that 8250_omap issues interrupt on shift register
empty which is single prerequesite for using software emulated RS485.
Signed-off-by: Matwey V. Kornilov
---
drivers/tty/serial/8250/8250_omap.c
Software RS485 emultaion is to be added in the following commit.
serial8250_start_tx will need to refer serial8250_stop_rx.
Move serial8250_stop_rx in front of serial8250_start_tx in order
to avoid function forward declaration.
Signed-off-by: Matwey V. Kornilov
---
drivers/tty/serial/8250/8250_p
Julian Margetson writes:
> On 12/21/2015 1:55 PM, Andy Shevchenko wrote:
>> On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
>>> On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote:
> On Sun, Dec 20, 2015 at 10:17 PM, Andy Shev
On Mon, Dec 21, 2015 at 5:19 PM, Sudip Mukherjee
wrote:
> diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig
> index 6412f14..ec3d287 100644
> --- a/drivers/tty/serial/8250/Kconfig
> +++ b/drivers/tty/serial/8250/Kconfig
> @@ -378,3 +378,11 @@ config SERIAL_8250_MID
>
On Fri, Dec 18, 2015 at 01:47:55PM +0100, Arnd Bergmann wrote:
> On Friday 18 December 2015 11:42:19 Catalin Marinas wrote:
> > On Thu, Dec 17, 2015 at 12:14:20PM -0800, Andrew Pinski wrote:
> > > Well (just like LP64 on AARCH64), when passing a 32bit value to a
> > > function, the upper 32bits are
> On 18 Dec 2015, at 13:47, Arnd Bergmann wrote:
>
>> 3. Follow the PCS up to glibc but always pass syscall arguments in W
>> registers, like AArch32 compat support (the least preferred option,
>> the only advantage is a single wrapper for all syscalls but it would
>> be doing unnecessary
On Mon, Dec 21, 2015 at 09:35:19PM +0800, Shawn Guo wrote:
> On Fri, Dec 18, 2015 at 12:00:32PM -0500, Damien Riegel wrote:
> > This commit adds LCD support for the TS-4800. The panel is an Okaya
> > RS800480T-7X0WQ and the timings have been extracted from Technologic
> > Systems' tree.
> >
> > Si
Removed braces from single statement if condition.Fixed checkpatch.pl
warning.
Signed-off-by: Bhumika Goyal
---
Changes in v2:
-Correct the subject and also send to a public mailing list.
---
drivers/char/raw.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/driver
Hi Maxime,
On Fri, 18 Dec 2015 11:19:43 +0100
Maxime Ripard wrote:
> It would also be a good idea to open a github issue on allwinner's
> documentation repo to make them know that the register name doesn't
> match between the register list and the register documentations.
I did that now. the
From: Dexuan Cui
With the recent change af3ff643ea91ba64dd8d0b1cbed54d44512f96cd
(Drivers: hv: vmbus: Use uuid_le type consistently), we always get this
warning:
CC [M] drivers/input/serio/hyperv-keyboard.o
drivers/input/serio/hyperv-keyboard.c:427:2: warning: missing braces around
in
From: Borislav Petkov
gcc complains on 32-bit like this:
drivers/gpu/drm/i915/intel_display.c: In function ‘intel_plane_obj_offset’:
drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer from \
integer of different size [-Wint-to-pointer-cast]
offset = (unsigne
I can only assume from lack of criticism that either:
1) This is a completely great idea with no cons and thus worthy of
time to implement
or
2) The topic has been ignored
Is it reasonable to allocate a 8KiB buffer for a bit vector covering
2*16 ports? Should I instead just focus on a list/co
From: Markus Elfring
Date: Mon, 21 Dec 2015 20:00:02 +0100
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Delete unnecessary goto statements in six functions
Delete an unnecessary variable initialisation in mgc_process_recover_log()
On Wed, Dec 09, 2015 at 02:50:28PM -0800, Brian Norris wrote:
> The kerneldoc for request_firmware_nowait() says that it may call the
> provided cont() callback with @fw == NULL, if the firmware request
> fails. However, this is not the case when called with an empty string
> (""). This case is sho
On Mon, 2015-12-21 at 01:19 +, Måns Rullgård wrote:
> Andy Shevchenko writes:
>
> > P.S. I also noticed that original driver enables interrupt per each
> > block
>
> And then ignores all but the transfer complete interrupt.
>
> > and sets protection control bits.
>
> With no indication wha
From: Markus Elfring
Date: Mon, 21 Dec 2015 18:15:45 +0100
Six goto statements referred to a source code position
directly behind them.
Thus omit such unnecessary jumps.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/staging/lustre/lustre/l
On 12/21/2015 2:27 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/21/2015 1:55 PM, Andy Shevchenko wrote:
On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote:
On Sun, Dec
The datasheet requires that the LLP_[SD]_EN bits be cleared whenever
LLP.LOC is zero, i.e. in the last descriptor of a multi-block chain.
Make the driver do this.
Signed-off-by: Mans Rullgard
---
drivers/dma/dw/core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/dma/dw/core.c b/
From: Markus Elfring
Date: Mon, 21 Dec 2015 18:24:45 +0100
The variable "mne_swab" will eventually be set to an appropriate value
from a call of the ptlrpc_rep_need_swab() function.
Thus let us omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
drivers/staging
From: Markus Elfring
Date: Mon, 21 Dec 2015 18:58:51 +0100
A few checks would be performed by the mgc_process_recover_log() function
even though it was determined that the passed variable "pages" contained
a null pointer or a call of the alloc_page() function failed.
1. Let us return directly if
From: Markus Elfring
Date: Mon, 21 Dec 2015 19:30:42 +0100
The script "checkpatch.pl" pointed out that labels should not be indented.
Thus delete a horizontal tab before the jump label "out"
in the function "osc_get_info".
Signed-off-by: Markus Elfring
---
drivers/staging/lustre/lustre/osc/osc
On Mon, Dec 21, 2015 at 10:18 AM, Borislav Petkov wrote:
> On Tue, Dec 15, 2015 at 05:29:30PM -0800, Tony Luck wrote:
>> Copy the existing page fault fixup mechanisms to create a new table
>> to be used when fixing machine checks. Note:
>> 1) At this time we only provide a macro to annotate assemb
On Mon, Dec 21, 2015 at 07:53:59PM +0100, Borislav Petkov wrote:
> From: Borislav Petkov
>
> gcc complains on 32-bit like this:
>
> drivers/gpu/drm/i915/intel_display.c: In function ‘intel_plane_obj_offset’:
> drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer from
> \
>
On 12/21/2015 2:27 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/21/2015 1:55 PM, Andy Shevchenko wrote:
On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote:
On Sun, Dec
Let me know if I need to do anything else with this patch. I am using
git/mutt to send patches from now on and I have my smtp gateway with
gmail properly setup and tested so there won't be any more fritzed
patches.It looks like this is relatively easy to do if you ge the
tools setup correctly.
Hi Brent,
On Tue, Dec 1, 2015 at 11:11 AM, Brent Taylor wrote:
> Since commit 8437754c83351d6213c1a47ff029c1126d6042a7, ar->fw is expected to
> be pointing to memory allocated by vmalloc. If the api1 method (via
> ath6kl_fetch_fw_api1) is used to allocate memory for ar->fw, then kmemdup is
>
On Mon, 2015-12-21 at 18:16 +, Måns Rullgård wrote:
> Andy Shevchenko writes:
>
> > On Mon, Dec 21, 2015 at 2:15 PM, Måns Rullgård
> > wrote:
> > > Andy Shevchenko writes:
> > >
> > I used to have a patch to implement this in dw_dmac driver.
> > However, I
> > dropped it at some point. See
Andy Shevchenko writes:
> On Mon, 2015-12-21 at 01:19 +, Måns Rullgård wrote:
>> Andy Shevchenko writes:
>>
>> > P.S. I also noticed that original driver enables interrupt per each
>> > block
>>
>> And then ignores all but the transfer complete interrupt.
>>
>> > and sets protection contr
On Mon, Dec 21, 2015 at 9:05 AM, Ross Zwisler
wrote:
> On Sat, Dec 19, 2015 at 10:37:46AM -0800, Dan Williams wrote:
>> On Fri, Dec 18, 2015 at 9:22 PM, Ross Zwisler
>> wrote:
>> > To properly handle fsync/msync in an efficient way DAX needs to track dirty
>> > pages so it is able to flush them d
Julian Margetson writes:
> On 12/21/2015 2:27 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>
>>> On 12/21/2015 1:55 PM, Andy Shevchenko wrote:
On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
> On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
>> On Sun, 2015-12-20 at
This series add seccomp support to User-mode Linux (i386 and x86_64
subarchitectures) and fix ptrace issues. This apply on v4.4-rc4 and pass all
the 48 tests from selftest/seccomp plus the UML ptsc test.
Changes since v1; addressed Richard Weinberger's comments:
* fix a new PTRACE_SETREGS bug on x
Hello, Artem.
On Mon, Dec 21, 2015 at 12:25:06PM +0500, Artem S. Tashkinov wrote:
> I've applied this patch on top of vanilla 4.3.3 kernel (without Linus'es
> revert). Hopefully it's how you intended it to be.
>
> Here's the result (I skipped the beginning of dmesg - it's the same as
> always - s
On Mon, 2015-12-21 at 19:10 +, Mans Rullgard wrote:
> The datasheet requires that the LLP_[SD]_EN bits be cleared whenever
> LLP.LOC is zero, i.e. in the last descriptor of a multi-block chain.
> Make the driver do this.
Acked-by: Andy Shevchenko
>
> Signed-off-by: Mans Rullgard
> ---
> d
On Mon, Dec 21, 2015 at 1:54 AM, Andrey Ryabinin
wrote:
> ip6addrlbl_get() has never worked. If ip6addrlbl_hold() succeeded,
> ip6addrlbl_get() will exit with '-ESRCH'. If ip6addrlbl_hold() failed,
> ip6addrlbl_get() will use about to be free ip6addrlbl_entry pointer.
>
> Fix this by inverting ip6
Some architectures do not implement PTRACE_GETREGSET nor
PTRACE_SETREGSET (required by HAVE_ARCH_TRACEHOOK) but only implement
PTRACE_GETREGS and PTRACE_SETREGS (e.g. User-mode Linux).
This improve seccomp selftest portability for architectures without
HAVE_ARCH_TRACEHOOK support by defining a new
Hello.
On 12/21/2015 02:01 PM, Sergei Shtylyov wrote:
This patch depend on GPIOLIB configuration as following:
I modified it with following diff and applied it.
diff --git a/drivers/extcon/Kconfig b/drivers/extcon/Kconfig
index ba4db7d..3d89e60 100644
--- a/drivers/extcon/Kconfig
+++ b/drivers
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Monday, December 21, 2015 8:28 AM
> To: KY Srinivasan ; Hannes Reinecke ;
> gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; oher...@suse.com;
> jbo
This fix two related bugs:
* PTRACE_GETREGS doesn't get the right orig_ax (syscall) value
* PTRACE_SETREGS can't set the orig_ax value (erased by initial value)
Remove the now useless and error-prone get_syscall().
Fix inconsistent behavior in the ptrace implementation for i386 when
updating orig
Hi Joao,
[auto build test ERROR on arc/for-next]
[also build test ERROR on v4.4-rc6 next-20151221]
url:
https://github.com/0day-ci/linux/commits/Joao-Pinto/adding-PCI-support-to-AXS10x/20151221-234734
base: https://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc for-next
config: i386
On 12/21/2015 3:27 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/21/2015 2:27 PM, Måns Rullgård wrote:
Julian Margetson writes:
On 12/21/2015 1:55 PM, Andy Shevchenko wrote:
On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson wrote:
On 12/21/2015 12:48 PM, Andy Shevchenko wrote:
Andy Shevchenko writes:
> On Mon, 2015-12-21 at 18:16 +, Måns Rullgård wrote:
>> Andy Shevchenko writes:
>>
>> > On Mon, Dec 21, 2015 at 2:15 PM, Måns Rullgård
>> > wrote:
>> > > Andy Shevchenko writes:
>> > >
>> > I used to have a patch to implement this in dw_dmac driver.
>> > However,
On 21/12/2015 11:13, Richard Weinberger wrote:
> Am 21.12.2015 um 10:23 schrieb Mickaël Salaün:
> Doesn't this break the support for changing syscall numbers using
> PTRACE_SETREGS?
The logic is unchanged except updating the UPT_SYSCALL_NR before
syscall_trace_enter(). I d
Kishon & Heiko,
On Tue, Dec 15, 2015 at 2:53 AM, Kishon Vijay Abraham I wrote:
> Hi Mike,
>
> On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote:
>> The USB phys on Rockchip SoCs contain their own internal PLLs to create
>> the 480MHz needed. Additionally this PLL output is also fed back i
ioremapping multiple BARs produces a warning with a message "Your kernel is
fine". This message mostly serves to comfort kernel developers. Users do
not read the message, they only see the big scary warning which means
something must be horribly broken with their system. Less dramatically, the
warn
On Sun, Dec 20, 2015 at 12:15:33AM +0530, Rahul Pathak wrote:
> Fixing coccicheck warning which recommends to use memdup_user instead
> to reimplement its code, using memdup_user simplifies the code
>
> ./drivers/tty/vt/keyboard.c:1709:9-16: WARNING opportunity for memdup_user
> ./drivers/tty/vt/k
On Sun, Dec 20, 2015 at 01:49:25PM +0100, Pavel Rojtberg wrote:
> 2015-12-20 8:55 GMT+01:00 Dmitry Torokhov :
> > On Sat, Dec 19, 2015 at 10:17:09PM +0100, Clement Calmels wrote:
> >> On Wed, 16 Dec 2015 14:44:08 -0800
> >> Dmitry Torokhov wrote:
> >>
> >> > When lighting up the segment identifyin
Hello, Artem.
Can you please apply the following patch on top and see whether
anything changes? If it does make the issue go away, can you please
revert the ".can_queue" part and test again?
Thanks.
---
drivers/ata/ahci.h|2 +-
drivers/ata/libahci.c |2 +-
2 files changed, 2 insert
On Mon, Dec 21, 2015 at 02:12:52PM +, Matt Fleming wrote:
> Môshe reported the following warning triggered on his machine since
> commit 50a0cb565246 ("x86/efi-bgrt: Fix kernel panic when mapping BGRT
> data"),
>
> [0.026936] [ cut here ]
> [0.026941] WARNIN
On Mon, Dec 21, 2015 at 11:16:44AM -0800, Dan Williams wrote:
> I suggested we reverse the dependency and have the driver optionally
> "select MCE_KERNEL_RECOVERY". There may be other drivers outside of
> LIBNVDIMM that want this functionality enabled.
Ah ok, makes sense.
--
Regards/Gruss,
On Tue, Oct 27, 2015 at 10:20 AM, Peter Hurley wrote:
> On 10/23/2015 09:31 AM, Masahiro Yamada wrote:
>> This UART driver should not depend on the console. They should be
>> orthogonal.
>>
>> Surround the earlycon code with CONFIG_SERIAL_EARLYCON conditional
>> and rip off "depends on SERIAL_825
On 12/21/2015 03:24 AM, Bijosh Thykkoottathil wrote:
From: Bijosh Thykkoottathil
This patch fixes following sparse warnings:
drivers/staging/android/ion/ion.c:1475:21: warning: incorrect type in
assignment (different base types)
drivers/staging/android/ion/ion.c:1475:21:expected restricte
This commit adds support for the TS-4800 interrupt controller. This
controller is instantiated in a companion FPGA, and multiplex interrupts
for other FPGA IPs.
As this component is external to the SoC, the SoC might need to reserve
pins, so this controller is implemented as a platform driver and
Please pull an nfsd change for 4.4:
git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.4-1
Just one fix for a NFSv4 callback bug introduced in 4.4.
Jeff Layton (1):
nfsd: don't hold ls_mutex across a layout recall
fs/nfsd
This is an interrupt-controller implemented in an FPGA, to multiplex
interrupts generated from other IPs. The FPGA usually uses a GPIO as a
parent interrupt controller to notify that one of the multiplexed
interrupts has triggered.
Signed-off-by: Damien Riegel
Acked-by: Rob Herring
---
Changes i
On Mon, 2015-12-21 at 15:19 -0400, Julian Margetson wrote:
> On 12/21/2015 2:27 PM, Måns Rullgård wrote:
> > The hard drive is recognized .
> > > These system gets unresponsive with USB devices like the mouse
> > > and
> > > keyboard not responding when I start Gparted.
> > Did you disable the SAT
> Does this patch fix it?
It didn't. With the patch I'm still seeing:
[ 1997.674112] kernel BUG at mm/vmstat.c:1408!
[ 1997.674930] invalid opcode: [#1] PREEMPT SMP KASAN
[ 1997.676252] Modules linked in:
[ 1997.676880] CPU: 4 PID: 14713 Comm: kworker/4:0 Not tainted
4.4.0-rc5-nex
On 12/21/2015 4:25 PM, Andy Shevchenko wrote:
On Mon, 2015-12-21 at 15:19 -0400, Julian Margetson wrote:
On 12/21/2015 2:27 PM, Måns Rullgård wrote:
The hard drive is recognized .
These system gets unresponsive with USB devices like the mouse
and
keyboard not responding when I start Gparted.
Add subarchitecture-independent implementation of asm-generic/syscall.h
allowing access to user system call parameters and results:
* syscall_get_nr()
* syscall_rollback()
* syscall_get_error()
* syscall_get_return_value()
* syscall_set_return_value()
* syscall_get_arguments()
* syscall_set_argumen
301 - 400 of 854 matches
Mail list logo
