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
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 =
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
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
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
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.
> >
> >
> 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 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
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
>
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
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
---
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
---
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':
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.
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
-
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
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
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
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
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
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
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, 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
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
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
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
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
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;
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
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
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
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
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
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
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
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 ++
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
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
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 |
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.
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:
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
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
> > > >
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
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
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
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
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
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 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 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
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
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,
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
From: dcashman
x86: arch_mmap_rnd() uses hard-coded values, 8 for 32-bit and 28 for
64-bit, 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,
From: dcashman
arm64: arch_mmap_rnd() uses STACK_RND_MASK 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, so
Address Space Layout Randomization (ASLR) provides a barrier to exploitation of
user-space processes in the presence of security vulnerabilities by making it
more difficult to find desired code/data which could help an attack. This is
done by adding a random offset to the location of regions in
On 12/21/2015 9:00 AM, Will Deacon wrote:
On Mon, Dec 21, 2015 at 05:51:22PM +0100, Thomas Gleixner wrote:
On Mon, 21 Dec 2015, Will Deacon wrote:
+static void send_user_sigtrap(int si_code)
+{
+ struct pt_regs *regs = current_pt_regs();
+ siginfo_t info = {
+
On 12/19/2015 05:57 AM, Sumit Gupta wrote:
Hi All,
For ARM Linux, during booting first memblock reserves memory regions
then bootmem allocator create node, mem_map, page bitmap data and then
hands over to buddy.
I have been thinking from some time about why we need two different
allocators for
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 Margetson writes:
>> On
On Tue, Dec 15, 2015 at 1:23 AM, Thomas Gleixner wrote:
> On Tue, 15 Dec 2015, Aniroop Mathur wrote:
>> On Sun, Dec 13, 2015 at 3:17 PM, Clemens Ladisch wrote:
>> > Aniroop Mathur wrote:
>> >>> 2. If we use msleep(40), is it possible that process could wake up after
>> >>> 60 ms or 70 ms or 100
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
wrote:
I noticed thanks to DWC_PARAMS that burst size is hardcoded to 32
items on
Hi,
On Mon, Dec 21, 2015 at 2:24 AM, Afzal Mohammed wrote:
> Hi Olof,
>
> On Sun, Dec 20, 2015 at 10:44:53AM -0800, Olof Johansson wrote:
>> On Wed, Nov 11, 2015 at 12:39:13PM +0530, Afzal Mohammed wrote:
>
>> > Enable TPS65217 regulator to have rootfs in MMC for Beagle Bone's.
>> >
>> >
In 7675104990ed ("sched: Implement lockless wake-queues") we gained
lockless wake-queues. -RT managed to lockup itself with those. There
could be multiple attempts for task X to enqueue it for a wakeup
_even_ if task X is already running.
The reason is that task X could be runnable but not yet on
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 exceptional (non struct page*) entries.
>
> In order to properly track
On Fri, Dec 18, 2015 at 11:08 AM, Randy Dunlap wrote:
> On 12/18/15 06:32, Dan Streetman wrote:
>> On Wed, Dec 16, 2015 at 3:23 PM, Randy Dunlap wrote:
>>> On 12/15/15 21:43, Stephen Rothwell wrote:
Hi all,
Changes since 20151215:
The drm-misc tree gained a conflict
On Mon, Dec 21, 2015 at 07:44:10AM +0300, Yury Norov wrote:
> Kernel option COMPAT defines the ability of executing aarch32 binaries.
> Some platforms does not support aarch32 mode, and so cannot execute that
> binaries. But we cannot just disable COMPAT for them because the same
> kernel binary
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 durably to media on demand.
> >
> > The tracking of dirty
On 12/18/2015 03:16 PM, Andy Lutomirski wrote:
> Hrm. We might also want an option to change pkru and/or baseline_pkru
> in all threads in the current mm. That's optional but it could be
> handy. Maybe it would be as simple as having the allocate-a-pkey call
> have an option to set an initial
Small nit.
On Fri, 2015-12-18 at 20:13 +0800, Kweh, Hock Leong wrote:
> From: "Kweh, Hock Leong"
>
> Introducing a kernel module to expose capsule loader interface
> (misc char device file note) for user to upload capsule binaries.
This patch ? introduces a kernel module to expose a capsule
On Mon, Dec 21, 2015 at 05:51:22PM +0100, Thomas Gleixner wrote:
> On Mon, 21 Dec 2015, Will Deacon wrote:
> > +static void send_user_sigtrap(int si_code)
> > +{
> > + struct pt_regs *regs = current_pt_regs();
> > + siginfo_t info = {
> > + .si_signo = SIGTRAP,
> > +
for_each_child_of_node performs an of_node_get on each iteration, so a
return from the loop requires an of_node_put.
A simplified version of the semantic patch that fixes this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
local idexpression n;
expression e,e1;
@@
for_each_child_of_node performs an of_node_get on each iteration, so a
return from the loop requires an of_node_put.
A simplified version of the semantic patch that fixes this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
local idexpression n;
expression e,e1;
@@
for_each_child_of_node performs an of_node_get on each iteration, so a
goto out of the loop requires an of_node_put.
A simplified version of the semantic patch that fixes this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
local idexpression n;
expression e,e1;
identifier l;
@@
for_each_child_of_node performs an of_node_get on each iteration, so a
return from the loop requires an of_node_put.
A simplified version of the semantic patch that fixes this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
local idexpression n;
expression e,e1;
@@
On Mon, 21 Dec 2015, Will Deacon wrote:
> +static void send_user_sigtrap(int si_code)
> +{
> + struct pt_regs *regs = current_pt_regs();
> + siginfo_t info = {
> + .si_signo = SIGTRAP,
> + .si_errno = 0,
> + .si_code= si_code,
> +
The various for_each device_node iterators performs an of_node_get on each
iteration, so a break out of the loop requires an of_node_put.
The complete semantic patch that fixes this problem is
(http://coccinelle.lip6.fr):
//
@r@
local idexpression n;
expression e1,e2;
iterator name
for_each_child_of_node performs an of_node_get on each iteration, so a
return from the loop requires an of_node_put.
A simplified version of the semantic patch that fixes this problem is as
follows (http://coccinelle.lip6.fr):
//
@@
local idexpression n;
expression e,e1;
@@
(implies CONFIG_WLCORE=m)
Patch is against linux-next (localversion-next is -next-20151221)
drivers/net/wireless/ti/wlcore/main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ti/wlcore/main.c
b/drivers/net/wireless/ti/wlcore/main.c
index ec7f6af
Hi Peter,
On 12/18/2015 04:03 PM, Peter Hurley wrote:
I totally understand, we have the same constraints with our SDK's APIs but with
major versions we drop old APIs that have been superseded.
I would have thought that the switch to DT would have been a good opportunity
to clean all that up,
Hi Geert,
On lun., déc. 21 2015, Geert Uytterhoeven wrote:
> As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
> property to "partitions" node"), the "partitions" subnode of an SPI
> FLASH device node must have a compatible property. The partitions are no
> longer
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
> > wrote:
> > I noticed thanks to DWC_PARAMS that burst size is hardcoded to 32
> > items on this board, however registers
Hi Geert,
On lun., déc. 21 2015, Geert Uytterhoeven wrote:
> As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
> property to "partitions" node"), the "partitions" subnode of an SPI
> FLASH device node must have a compatible property. The partitions are no
> longer
From: Graeme Gregory
Add a new ACPI scan handler for AMBA devices.
Signed-off-by: Graeme Gregory
Signed-off-by: Aleksey Makarov
---
drivers/acpi/scan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 78d5f02..20c8cba 100644
---
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 ++---
1 file changed, 26 insertions(+), 11
> -Original Message-
> From: Matt Fleming [mailto:m...@codeblueprint.co.uk]
> Sent: Monday, December 21, 2015 9:51 AM
> To: Elliott, Robert (Persistent Memory)
> Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
> linux-...@vger.kernel.org;
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
AMBA bus code unchanged between probing methods.
Signed-off-by:
As discussed when Shannon Zhao sent a patch to add platform_device support
to pl061 driver. Russel and other maintainers prefered that ACPI learned
how to create AMBA devices rather than converting/adding platform_device
support to AMBA drivers.
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
> nobody
> ever tested the driver
On 12/21/2015 7:56 AM, Jon Hunter wrote:
> The definition, PLLU_BASE_OVERRIDE, for the pll_u OVERRIDE bit is defined
> but not used and when the OVERRIDE bit is cleared in tegra210_pll_init()
> the code directly uses the bit number. Therefore, use the definition,
> PLLU_BASE_OVERRIDE when clearing
On 12/21/2015 7:56 AM, Jon Hunter wrote:
> If the pll_u is not configured by the bootloader, then on kernel boot the
> following warning is seen:
>
> clk_pll_wait_for_lock: Timed out waiting for pll pll_u_vco lock
> tegra_init_from_table: Failed to enable pll_u_out1
> [ cut here
Thomas,
While I was really thinking that the GIC stuff was over and done with
for this release, people have been busy Acking patches. Who wants
another helping of GIC for Christmas? ;-)
So here is the next batch of ACPI-related changes for the GIC family,
this time affecting the GICv2m MSI
On Tue, Dec 15, 2015 at 04:54:18PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> When an event alias is used that the kernel marked as .agg-per-core, force
> --per-core mode (and also require -a and forbid cgroups or per thread mode).
> This in term means, --topdown forces --per-core mode.
>
On Sat, 2015-12-19 at 02:28 +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: James Bottomley [mailto:james.bottom...@hansenpartnership.com
> > ]
> > Sent: Friday, December 18, 2015 8:48 AM
> > To: KY Srinivasan ; Hannes Reinecke <
> > h...@suse.de>;
> >
Hi Graeme,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.4-rc6 next-20151221]
url:
https://github.com/0day-ci/linux/commits/Aleksey-Makarov/ACPI-amba-bus-probing-support/20151221-225448
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux
On Thu, 17 Dec, at 07:28:34PM, Robert Elliott wrote:
> Print the base address for each range in decimal alongside the size.
> Use a "(size @ base)" format similar to the fake_memmap kernel parameter.
>
> Print the range and base in the best-fit B, KiB, MiB, etc. units rather
> than always MiB.
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Friday, December 18, 2015 9:14 AM
> To: Hannes Reinecke ; KY Srinivasan ;
> gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; oher...@suse.com;
>
On Tue, Dec 15, 2015 at 04:54:18PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> When an event alias is used that the kernel marked as .agg-per-core, force
> --per-core mode (and also require -a and forbid cgroups or per thread mode).
> This in term means, --topdown forces --per-core mode.
>
On 21/12/2015:07:52:59 AM, Guenter Roeck wrote:
> On 12/18/2015 08:22 PM, Pratyush Anand wrote:
> >On 17/12/2015:06:56:27 AM, Guenter Roeck wrote:
> >>On 12/17/2015 04:23 AM, Pratyush Anand wrote:
> >>>We need few sysfs attributes to know different status of a watchdog device.
> >>>To do that, we
On Tue, Dec 15, 2015 at 04:54:17PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> When an error happens during alias parsing currently the complete
> parsing of all attributes of the PMU is stopped. This is breaks
> old perf on a newer kernel that may have not-yet-know
> alias attributes (such
501 - 600 of 1708 matches
Mail list logo
