On Wed, Jan 7, 2015 at 11:50 PM, Hanjun Guo wrote:
> Hi Feng Kan,
>
> I have some comments below.
>
>
> On 2015年01月08日 01:32, Feng Kan wrote:
>>
>> Just want to ping this again.
>>
>> Happy new year
>>
>> On Thu, Dec 11, 2014 at 2:31 PM, Feng Kan wrote:
>>>
>>> This adds ACPI support for the APM
On Thursday 08 January 2015 10:33 PM, Will Deacon wrote:
On Wed, Dec 31, 2014 at 03:21:24PM +, Pratyush Anand wrote:
This patch adds support for uprobe on ARM64 architecture.
Unit test for following has been done so far and they have been found
working
1. Normal instruction, which can be
During UDS connection check, both sides are checked for write access to
the other side. But only the first check is performed with audit support.
The second one didn't produce any audit logs. This simple patch fixes that.
Signed-off-by: Rafal Krypa
---
security/smack/smack_lsm.c | 2 +-
1 file c
On Thu, Jan 8, 2015 at 1:16 AM, Fam Zheng wrote:
> + if (!timeout || (timeout->tv_nsec == 0 && timeout->tv_sec == 0)) {
..
> + } else if (timeout->tv_nsec >= 0 && timeout->tv_sec >= 0) {
the check for tv_nsec is not enough, which points
to the fragility of passing user timespec around
On Thursday 08 January 2015 10:31 PM, Will Deacon wrote:
On Fri, Jan 02, 2015 at 06:05:23PM +, Oleg Nesterov wrote:
Let me repeat once again that I know absolutely nothing about arm* ;)
On 12/31, Pratyush Anand wrote:
uprobe registers a handler at step_hook. So, single_step_handler now
On 08/01/15 17:20, Johannes Weiner wrote:
> On Thu, Jan 08, 2015 at 03:28:43PM +, David Vrabel wrote:
>> Add an optional array of pages to struct vm_area_struct that can be
>> used find the page backing a VMA. This is useful in cases where the
>> normal mechanisms for finding the page don't wo
On 07 Jan 2015, at 21:33, Eric Dumazet wrote:
> On Wed, 2015-01-07 at 20:37 +, Erik Grinaker wrote:
> I agree. I have contacted Amazon about this, but am not too hopeful
>> for a quick fix; they have been promising SACK-support on their
>> loadbalancers since 2006, for example.
>>
>> That sai
> -Original Message-
> From: Joseph Salisbury [mailto:joseph.salisb...@canonical.com]
> Sent: Thursday, January 08, 2015 11:26 AM
> To: Deucher, Alexander
> Cc: sta...@vger.kernel.org; LKML; Koenig, Christian; David Airlie; dri-devel
> Subject: Re: [Regression][v3.17][3.18][3.19-rc3] drm/ra
On 01/08/2015 12:49 PM, Vladimir Zapolskiy wrote:
> Hi Ezequiel,
>
> On 07.01.2015 19:20, Ezequiel Garcia wrote:
>> From: Naidu Tellapati
>>
>> The Pistachio SOC from Imagination Technologies includes a Pulse Width
>> Modulation DAC which produces 1 to 4 digital bit-outputs which represent
>> d
On Thu, Jan 08, 2015 at 11:28:40AM -0500, Milosz Tanski wrote:
> >
>
> Andrew I got busier with my other job related things between the
> Thanksgiving & Christmas then anticipated. However, I have updated and
> taken apart the patchset into two pieces (preadv2 and pwritev2). That
> should make ev
On Wed, Jan 7, 2015 at 6:42 AM, Geert Uytterhoeven wrote:
> On Wed, Jan 7, 2015 at 3:58 AM, Walter Lozano
> wrote:
>> diff --git a/Documentation/devicetree/bindings/input/adxl34x.txt
>> b/Documentation/devicetree/bindings/input/adxl34x.txt
>> new file mode 100644
>> index 000..0774f7e
>> ---
On Thursday 08 January 2015 11:06 PM, Will Deacon wrote:
On Thu, Jan 08, 2015 at 05:33:08PM +, Pratyush Anand wrote:
On Thursday 08 January 2015 10:25 PM, Will Deacon wrote:
On Wed, Dec 31, 2014 at 03:21:18PM +, Pratyush Anand wrote:
Most of the stuff of kprobes-arm64.c can also be u
On Thu, 8 Jan 2015, Catalin Marinas wrote:
> On Thu, Jan 08, 2015 at 04:57:05PM +, Russell King - ARM Linux wrote:
> > On Thu, Jan 08, 2015 at 04:41:12PM +, Catalin Marinas wrote:
> > > On Thu, Jan 08, 2015 at 04:34:50PM +, Russell King - ARM Linux wrote:
> > > > On Thu, Jan 08, 2015 a
On Thu, Jan 08, 2015 at 05:33:08PM +, Pratyush Anand wrote:
> On Thursday 08 January 2015 10:25 PM, Will Deacon wrote:
> > On Wed, Dec 31, 2014 at 03:21:18PM +, Pratyush Anand wrote:
> >> Most of the stuff of kprobes-arm64.c can also be used by uprobes.c. So
> >> move all those part to comm
On Thu, Jan 08, 2015 at 05:29:40PM +, Mark Langsdorf wrote:
> On 01/08/2015 07:45 AM, Catalin Marinas wrote:
> > On Thu, Jan 08, 2015 at 12:51:31PM +, Mark Langsdorf wrote:
> >> On 01/05/2015 07:46 PM, Linus Torvalds wrote:
> >>> It's a day delayed - not because of any particular developmen
On Thursday 08 January 2015 10:25 PM, Will Deacon wrote:
On Wed, Dec 31, 2014 at 03:21:18PM +, Pratyush Anand wrote:
Most of the stuff of kprobes-arm64.c can also be used by uprobes.c. So
move all those part to common code area. In the process rename kprobe to
probe whereever possible.
No
In order to safely migrate to a cumulative set of flags, start by
abstracting the way we look at these flags. There is otherwise no
change in semantics here.
Signed-off-by: Marc Zyngier
---
include/linux/irqdesc.h | 5 +
kernel/irq/chip.c | 10 +-
kernel/irq/manage.c | 6
The current infrastructure for stacked domains doesn't propagate
irq_chip flags, and as we only look at the top-level irq_chip,
we may miss a number of critical flags.
This patch accumulates the flags into a new set, stored at the
irq_desc level, with an additional flag to indicate that this is
a
With the landing of stacked irq domains in 3.19, we have ended up in a
situation where we have a stack of IRQ controllers, each with their
set of flags, but the core code is only able to look at the top-most,
which is not very helpful. This small series is trying to fix this.
The first patch conve
On Thursday 08 January 2015 10:25 PM, Will Deacon wrote:
On Wed, Dec 31, 2014 at 03:21:17PM +, Pratyush Anand wrote:
Its better to keep all BRK opcodes used by kprobes and uprobes at one
place. Therefore move these defines to asm/insn.h.
Signed-off-by: Pratyush Anand
---
arch/arm64/inc
Hi Daniel,
Some minor comments below...
On Wed, Jan 07, 2015 at 12:28:18PM +, Daniel Thompson wrote:
> Some ARM platforms mux the PMU interrupt of every core into a single
> SPI. On such platforms if the PMU of any core except 0 raises an interrupt
> then it cannot be serviced and eventually,
On 01/08/2015 07:45 AM, Catalin Marinas wrote:
On Thu, Jan 08, 2015 at 12:51:31PM +, Mark Langsdorf wrote:
On 01/05/2015 07:46 PM, Linus Torvalds wrote:
It's a day delayed - not because of any particular development issues,
but simply because I was tiling a bathroom yesterday. But rc3 is ou
No code changes.
This is a preparatory patch for change in "struct pt_regs" handling.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Oleg Nesterov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Frederic Weisbecker
CC: X86 ML
CC: Alexei Starovoitov
CC: Will Drewry
CC: Kees Cook
CC: l
The values of these two constants are the same, the meaning is different.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Oleg Nesterov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Frederic Weisbecker
CC: X86 ML
CC: Alexei Starovoitov
CC: Will Drewry
CC: Kees Cook
CC: linux-kernel@v
On Thu, 8 Jan 2015, Russell King - ARM Linux wrote:
> On Thu, Jan 08, 2015 at 04:41:12PM +, Catalin Marinas wrote:
> > On Thu, Jan 08, 2015 at 04:34:50PM +, Russell King - ARM Linux wrote:
> > > On Thu, Jan 08, 2015 at 04:19:08PM +, Catalin Marinas wrote:
> > > > I really think we shou
Hi Masami,
First, I would like to wish you a Happy New Year :-)
OK, now back to business.
It has come to my attention that jprobes and function graph tracing do
not play nicely together. I think you once told me they have issues as
well.
A simple way to test this is to load the jprobe_example.
On Thu, Jan 08, 2015 at 03:28:43PM +, David Vrabel wrote:
> Add an optional array of pages to struct vm_area_struct that can be
> used find the page backing a VMA. This is useful in cases where the
> normal mechanisms for finding the page don't work. This array is only
> inspected if the PTE
On Thu, Jan 08, 2015 at 11:26:30AM -0500, Christopher Covington wrote:
> > +DMA clients must use the format descripted in the dma.txt file, using a two
> > cell specifier for each channel.
> >
> > Each dmas request consists of 3 cells:
>
> Now 2 cells?
Good catch. I'll fix in next rev. T
Hi,
On Tue, Dec 30, 2014 at 05:49:27PM +0800, Songjun Wu wrote:
> Executing the 'insmod g_hid.ko', then executing the
> 'rmmod g_hid.ko', the NULL pointer oops will be triggered.
>
> When unloading the module 'g_hid.ko', the urb request will be
> dequeued and the completion routine will be excute
In order to populate the PHB msi_domain, use the "msi-parent"
attribute to lookup a corresponding irq domain. If found,
this is our MSI domain.
This gets plugged into the core PCI code.
Signed-off-by: Marc Zyngier
---
drivers/pci/of.c| 15 +++
drivers/pci/probe.c | 1 +
include
As MSI-type features are creeping into non-PCI devices, it is
starting to make sense to give our struct device some form of
support for this, by allowing a pointer to an MSI irq domain to
be set/retrieved.
Signed-off-by: Marc Zyngier
---
include/linux/device.h | 20
1 file c
Hi,
On Mon, Dec 08, 2014 at 09:35:51PM +0800, Jisheng Zhang wrote:
> On platforms which has native usb hosts/phys and pci-dwc3 controller,
> the dwc3 core may get the wrong usb2_phy and usb3_phy by
> devm_usb_get_phy(). It depends on which usb phy driver is initialized
> firstly, the usb_phy_gener
A number of platforms do not need to use the msi-parent property,
as the host bridge itself provides the MSI controller.
Allow this configuration by performing an irq domain lookup based
on the PHB node if it doesn't have a valid msi-parent property.
Signed-off-by: Marc Zyngier
---
drivers/pci/
Now that we can easily find which MSI domain a PCI device is
using, use dev_get_msi_domain as a way to retrieve the information.
The original code is still used as a fallback.
Signed-off-by: Marc Zyngier
---
drivers/pci/msi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a
In order to be able to populate the device msi_domain field,
add the necesary hooks to propagate the PHB msi_domain across
secondary busses to devices.
So far, nobody populates the initial msi_domain.
Signed-off-by: Marc Zyngier
---
drivers/pci/probe.c | 30 ++
inclu
GICv2m only uses the msi_controller structure as a way to match
the PHB with its MSI HW, and thus the msi_domain. But now that
we can directly associate an msi_domain with a device, there is
no use keeping this msi_controller around.
Just remove all traces of msi_controller from the driver.
Signe
MSI-like interrupts are starting to creep out of the PCI world, and
can now be seen into a number of "platform"-type busses. The MSI
domain patches recognise that fact, and start providing a way to
implement this.
Another problem we have to solve is to identify which MSI domain a
device is "connec
The only two users of that field are not using the msi_controller
structure anymore, so drop it altogether.
Signed-off-by: Marc Zyngier
---
drivers/pci/msi.c | 2 --
include/linux/msi.h | 3 ---
2 files changed, 5 deletions(-)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index 003040b..
The GICv3 ITS only uses the msi_controller structure as a way
to match the PHB with its MSI HW, and thus the msi_domain.
But now that we can directly associate an msi_domain with a device,
there is no use keeping this msi_controller around.
Just remove all traces of msi_controller from the driver.
Loan Offer at 3%, Feel Free to REPLY back to us for more info.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.o
On Tue, Jan 06, 2015 at 06:44:56AM +, Paul Walmsley wrote:
>
> After commit ecc19d17868be9c9f8f00ed928791533c420f3e0 ("dmaengine: Add
> a warning for drivers not using the generic slave caps retrieval"),
> the Tegra APB DMA driver causes this warning during boot:
>
> WARNING: CPU: 0 PID: 1 at
On Thu, Jan 08, 2015 at 05:25:13PM +0100, Bartosz Golaszewski wrote:
> This attribute allows to configure the update interval of ina226. Although
> the bus and shunt voltage conversion times remain hardcoded to 1.1 ms, we can
> now modify said interval by changing the averaging rate.
>
> While we'
On Wed, Dec 31, 2014 at 03:21:24PM +, Pratyush Anand wrote:
> This patch adds support for uprobe on ARM64 architecture.
>
> Unit test for following has been done so far and they have been found
> working
> 1. Normal instruction, which can be probed like sub, ldr, add etc.
> 2. Instructions whi
On Thu, Jan 08, 2015 at 05:51:09PM +0300, Vladimir Davydov wrote:
> Since commit b2052564e66d ("mm: memcontrol: continue cache reclaim from
> offlined groups") pages charged to a memory cgroup are not reparented
> when the cgroup is removed. Instead, they are supposed to be reclaimed
> in a regular
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Thursday, January 8, 2015 8:02 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; de...@linuxdriverproject.org; Haiyang
> Zhang; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 0/5] Tools: hv: fix
This change clarifies the behavior of the PERF_FLAG_FD_OUTPUT and
PERF_FLAG_FD_NO_GROUP flags to perf_event_open(), and removes
the related FIXME comments.
While writing tests to validate the behavior of these flags I
discovered that PERF_FLAG_FD_OUTPUT has been broken since the
2.6.35 kernel rel
Hi,
On Wed, Dec 24, 2014 at 03:23:07PM +0100, Michal Nazarewicz wrote:
> On Wed, Dec 24 2014, Rohith Seelaboyina wrote:
> > This patch fixes the sparse error in functionfs
> > driver.
> >
> > drivers/usb/gadget/function/f_fs.c:400:44: error: bad
> > constant experssion.
> >
> > Dynamic memory allo
When converting a pfn to a physical address be sure to use 64 bit
wide types.
Also avoid invalidating memory for zero sized non-aligned extra
memory regions.
Signed-off-by: Juergen Gross
Tested-by: Boris Ostrovsky
---
arch/x86/xen/setup.c | 6 --
1 file changed, 4 insertions(+), 2 deletion
On Fri, Jan 02, 2015 at 06:05:23PM +, Oleg Nesterov wrote:
> Let me repeat once again that I know absolutely nothing about arm* ;)
>
> On 12/31, Pratyush Anand wrote:
> >
> > uprobe registers a handler at step_hook. So, single_step_handler now
> > checks for user mode as well if there is a val
When allocating a new pmd for the linear mapped p2m list a check is
done for not introducing another pmd when this just happened on
another cpu. In this case the old pte pointer was returned which
points to the p2m_missing or p2m_identity page. The correct value
would be the pointer to the found ne
In xen_rebuild_p2m_list() for large areas of invalid or identity
mapped memory the pmd entries on 32 bit systems are initialized
wrong. Correct this error.
Suggested-by: Boris Ostrovsky
Signed-off-by: Juergen Gross
---
arch/x86/xen/p2m.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
On Thu, Jan 08, 2015 at 04:57:05PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 08, 2015 at 04:41:12PM +, Catalin Marinas wrote:
> > On Thu, Jan 08, 2015 at 04:34:50PM +, Russell King - ARM Linux wrote:
> > > On Thu, Jan 08, 2015 at 04:19:08PM +, Catalin Marinas wrote:
> > > > I
In the setup code of the linear mapped p2m list several bugs have
been found, especially for 32 bit dom0. These patches correct the
errors and make 32 bit dom0 bootable again.
Juergen Gross (3):
xen: correct error for building p2m list on 32 bits
xen: correct race in alloc_p2m_pmd()
xen: use
On Wed, Dec 31, 2014 at 03:21:20PM +, Pratyush Anand wrote:
> instruction_pointer_set is needed for uprobe implementation. Hence
> define it for ARM64.
>
> Signed-off-by: Pratyush Anand
> ---
> arch/arm64/include/asm/ptrace.h | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/ar
Hi,
On Tue, Jan 06, 2015 at 12:39:55PM +0530, sundeep subbaraya wrote:
> >> On Sun, Dec 14, 2014 at 08:39:18AM +0530, sundeep subbaraya wrote:
> >> > Hi Paul,
> >> >
> >> > As per my understanding, for BULK OUT we do queue a request with 512
> >> > bytes length since we do not
> >>
> >> sometimes
On 12/09/2014 11:07 PM, Paul Walmsley wrote:
Like several of the other files in drivers/clocksource,
tegra20_timer.c contains code that can only compile when CONFIG_ARM is
enabled. This causes obvious problems when trying to compile this
code for NVIDIA ARM64-based SoCs, such as Tegra132. The
On Thu, Jan 08, 2015 at 04:41:12PM +, Catalin Marinas wrote:
> On Thu, Jan 08, 2015 at 04:34:50PM +, Russell King - ARM Linux wrote:
> > On Thu, Jan 08, 2015 at 04:19:08PM +, Catalin Marinas wrote:
> > > I really think we should stop this thread. User ABI breakage fixed now.
> >
> > No
On Wed, Dec 31, 2014 at 03:21:18PM +, Pratyush Anand wrote:
> Most of the stuff of kprobes-arm64.c can also be used by uprobes.c. So
> move all those part to common code area. In the process rename kprobe to
> probe whereever possible.
>
> No functional change.
In which case, can you merge th
[PATCH] This patch fixes the bug which comes up when one tcp server
is already running on some ip and port with "test" as SMACK64IPIN label. And
we try to run the same server again with same port, same protocol, and same
ip but with different SMACK64IPIN label "server". Then this new server
pro
On Wed, Dec 31, 2014 at 03:21:17PM +, Pratyush Anand wrote:
> Its better to keep all BRK opcodes used by kprobes and uprobes at one
> place. Therefore move these defines to asm/insn.h.
>
> Signed-off-by: Pratyush Anand
> ---
> arch/arm64/include/asm/insn.h | 6 ++
> arch/arm64/kernel/kpr
On Thu 2015-01-08 13:03:25, One Thousand Gnomes wrote:
> On Mon, 5 Jan 2015 18:26:07 -0800
> Andy Lutomirski wrote:
> > > I don't know for sure, but it looks likely to me according to claim in the
> > > paper (8MB). But it still can be sombody else's data: 644 file on
> > > hugetlbfs mmap()ed r/o
On 01/08/2015 02:27 AM, Michael Kerrisk (man-pages) wrote:
> Thanks for the patch. Quite a number of queries below. Could you
> address those and resubmit?
Absolutely, thanks for the detailed review!
I'll address most of your comments in the new patch.
>> +The application must have allocated vir
There are several areas in the kernel that create temporary filename
objects using the following pattern:
int func(const char *name)
{
struct filename *file = { .name = name };
...
return 0;
}
... which for the most part work
Enable recording of filenames in getname_kernel() and remove the
kludgy workaround in __audit_inode() now that we have proper filename
logging for kernel users.
Signed-off-by: Paul Moore
---
fs/namei.c |1 +
kernel/auditsc.c | 40 +++-
2 files chan
In order to ensure that filenames are not released before the audit
subsystem is done with the strings there are a number of hacks built
into the fs and audit subsystems around getname() and putname(). To
say these hacks are "ugly" would be kind.
This patch removes the filename hackery in favor o
In all likelihood there were some subtle, and perhaps not so subtle,
bugs with filename matching in audit_inode() and audit_inode_child()
for some time, however, recent changes to the audit filename code have
definitely broken the filename matching code. The breakage could
result in duplicate file
There have been some patches added to v3.19-rcX to fix various
problems in the way audit handles filenames but they have been hacks
on top of hacks, not really something we want long term. This
patchset reworks the way audit handles filenames, removing a lot of
nasty hacks added recently, and fixi
In preparation for expanded use in the kernel, make getname_kernel()
more useful by allowing it to handle any legal filename length.
Signed-off-by: Paul Moore
---
fs/namei.c | 34 --
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/fs/namei.c b/fs
[PATCH] This patch fixes the issue when 2 servers uses same IP and
port but different protocols(Udp and tcp). And they are using different
SMACK64IPIN labels.Tcp server is using "test" and udp server is using
"test-in". Now when we try to run tcp client with SMACK64IPOUT label as
"test", then
[PATCH] This patch fixes the synchronization issue in IPv6
implementation. Previously there was no synchronization mechanism used while
accessing(adding/reading/deletion) smk_ipv6_port_list. It could be possible
that when one thread is reading the list, at the same time another thread is
addin
iio kfifo can be used without trigger support so there is no need to build it.
Signed-off-by: Karol Wrona
---
drivers/iio/Kconfig |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
index 50f6599..dfda2c3 100644
--- a/drivers/iio/Kconfig
+++ b/drivers/
On Thu, Jan 08, 2015 at 04:34:50PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 08, 2015 at 04:19:08PM +, Catalin Marinas wrote:
> > I really think we should stop this thread. User ABI breakage fixed now.
>
> No. Vince's email shows a more serious problem.
>
> The ABI breakage issue
Hello,
This small patchset introduces helpers for iio kfifo which are useful when
IIO_HARDWARE/SOFTWARE_BUFFER is used. I decided to do it similar to Lars'
industrialio-triggered-buffer as a separate module what can be considered
as overkill but there is some risk that this source file will grow
On Thu, 8 Jan 2015 16:53:41 +0200
Jyri Sarha wrote:
> > + - audio-ports: must contain one or two values selecting the source
> > + in the audio port.
> > + The source type is given by the corresponding entry in
> > + the audio-port-names property.
> > +
>
> This binding does not allow m
These ones helps to create and manage iio_kfifo buffer when
no-triggered buffer is used.
Signed-off-by: Karol Wrona
Suggested-by: Jonathan Cameron
---
drivers/iio/Kconfig |6 +++
drivers/iio/Makefile |1 +
drivers/iio/industrialio-notr
Linus,
Please pull the kgdb tree bug fixes.
These have been around since 3.17 and in kgdb-next for the last 9
weeks and some will go back to -stable.
Summary of changes:
KGDB/KDB fixes and cleanups
Cleanups
kdb: Remove unused command flags, repeat flags and KDB_REPEAT_NONE
Fixes
kgdb/k
On 01/08/2015 09:08 AM, Michal Hocko wrote:
[CCing linux-mm and CMA people]
[Full message here:
http://article.gmane.org/gmane.linux.ports.arm.kernel/383669]
[ 1054.095277] DMA: 109*64kB (UR) 53*128kB (R) 8*256kB (R) 0*512kB 0*1024kB
0*2048kB 1*4096kB (R) 0*8192kB 0*16384kB 1*32768kB (R) 0*655
Signed-off-by: Sakshi Bansal
---
drivers/staging/vt6655/baseband.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/vt6655/baseband.c
b/drivers/staging/vt6655/baseband.c
index 86c72ba..c138f9b 100644
--- a/drivers/staging/vt6655/baseband.c
+++ b/drivers/stagi
On Wed, Jan 7, 2015 at 6:57 PM, Fam Zheng wrote:
>
> There is a race condition in virtscsi_handle_event, when many device
> hotplug/unplug events flush in quickly.
>
> The scsi_remove_device in virtscsi_handle_transport_reset may trigger
> the BUG_ON in scsi_target_reap, because the state is alter
On Thu, Jan 08, 2015 at 04:19:08PM +, Catalin Marinas wrote:
> I really think we should stop this thread. User ABI breakage fixed now.
No. Vince's email shows a more serious problem.
The ABI breakage issue was reported before the patches were apparently
merged, but that information seems to
On Thu, Jan 08, 2015 at 07:20:43PM +0900, Satoru Takeuchi wrote:
> At Tue, 6 Jan 2015 17:49:03 -0800,
> Greg Kroah-Hartman wrote:
> >
> > This is the start of the stable review cycle for the 3.18.2 release.
> > There are 84 patches in this series, all will be posted as a response
> > to this one.
This attribute allows to configure the update interval of ina226. Although
the bus and shunt voltage conversion times remain hardcoded to 1.1 ms, we can
now modify said interval by changing the averaging rate.
While we're at it - add an additional variable to ina2xx_data, which holds
the current c
On Thu, Jan 08, 2015 at 10:44:53AM -0500, Vince Weaver wrote:
> On Thu, 8 Jan 2015, Russell King - ARM Linux wrote:
>
> > It's not a regression - yet. No one has shown that userspace has broken
> > according to the definition of the first quote above, and that's the
> > whole point.
>
> How much
On Tue, Jan 6, 2015 at 3:47 AM, Andrew Morton wrote:
> On Mon, 5 Jan 2015 10:41:43 -0800 Christoph Hellwig
> wrote:
>
>> On Wed, Dec 10, 2014 at 09:12:11AM -0500, Matthew Wilcox wrote:
>> > On Wed, Dec 10, 2014 at 06:03:47AM -0800, Christoph Hellwig wrote:
>> > > What is the status of this patch
On 01/07/2015 09:51 PM, Deucher, Alexander wrote:
>
>> -Original Message-
>> From: Joseph Salisbury [mailto:joseph.salisb...@canonical.com]
>> Sent: Wednesday, January 07, 2015 5:51 PM
>> To: Deucher, Alexander
>> Cc: sta...@vger.kernel.org; LKML; Koenig, Christian; David Airlie; dri-devel
This is a preparatory patch for change in "struct pt_regs"
handling in entry_64.S.
trace_hardirqs thunks were (ab)using a part of pt_regs
handling code, namely SAVE_ARGS/RESTORE_ARGS macros,
to save/restore registers across C function calls.
Since SAVE_ARGS is going to be changed, open-code
regis
Hi Andy,
On 01/07/2015 10:26 PM, Andy Gross wrote:
> This patch removes the crci information from the dma channel property. At
> least
> one client device requires using more than one CRCI value for a channel. This
> does not match the current binding and the crci information needs to be
> rem
A define, two macros and an unreferenced bit of assembly are gone.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Oleg Nesterov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Frederic Weisbecker
CC: X86 ML
CC: Alexei Starovoitov
CC: Will Drewry
CC: Kees Cook
CC: linux-kernel@vger.ker
This is the first part of a bigger patch set I posted last August,
then under title of "x86: entry.S optimizations".
I fully rebased that patch set to Linus tree, but currently
Linus and -next are diverging a bit in arch/x86/kernel/entry_64.S
To make it easier for mainteiners, I'm splitting the o
On 08/01/2015 15:59, Radim Krčmář wrote:
> Emulation does not utilize the feature.
Indeed... nice :)
Applied to kvm/queue, thanks.
Paolo
> Signed-off-by: Radim Krčmář
> ---
> arch/x86/kvm/x86.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b
On Thu, Jan 08, 2015 at 03:44:53PM +, Vince Weaver wrote:
> On Thu, 8 Jan 2015, Russell King - ARM Linux wrote:
>
> > It's not a regression - yet. No one has shown that userspace has broken
> > according to the definition of the first quote above, and that's the
> > whole point.
>
> How much
On Fri, Nov 21, 2014 at 03:08:27PM -0700, Alex Williamson wrote:
> I'd like to make vfio-pci capable of manipulating the device exposed
> to the user such that if the host can only support a single MSI
> vector then we hide the fact that the device itself may actually be
> able to support more. Wh
On 01/07/2015 09:51 PM, Deucher, Alexander wrote:
>
>> -Original Message-
>> From: Joseph Salisbury [mailto:joseph.salisb...@canonical.com]
>> Sent: Wednesday, January 07, 2015 5:51 PM
>> To: Deucher, Alexander
>> Cc: sta...@vger.kernel.org; LKML; Koenig, Christian; David Airlie; dri-devel
On 01/08/2015 08:10 AM, One Thousand Gnomes wrote:
> On Mon, 5 Jan 2015 22:09:45 -0500
> Peter Hurley wrote:
>
>> Some arches have no need to create unprobed 8250 ports; these phantom
>> ports are primarily required for ISA ports which have no probe
>> mechanism or to provide non-operational por
On Fri, Nov 21, 2014 at 11:24:27AM -0700, Alex Williamson wrote:
> Reports against the TL-WDN4800 card indicate that PCI bus reset of
> this Atheros device cause system lock-ups and resets. I've also
> been able to confirm this behavior on multiple systems. The device
> never returns from reset a
On Wed, Jan 07, 2015 at 06:49:53PM +, Murali Karicheri wrote:
> Add of_pci_dma_configure() to allow updating the dma configuration
> of the pci device using the configuration from DT of the parent of
> the root bridge device.
>
> Signed-off-by: Murali Karicheri
> ---
> drivers/of/of_pci.c
KY Srinivasan writes:
>> -Original Message-
>> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On
>> Behalf Of gre...@linuxfoundation.org
>> Sent: Wednesday, December 10, 2014 6:48 AM
>> To: Vitaly Kuznetsov
>> Cc: de...@linuxdriverproject.org; Haiyang Zhang; linux-
>>
> ---
>
> this was only compile tested with
> x86_64_defconfig + CONFIG_DMA_ENGINE=y + CONFIG_INTEL_IOATDMA=m
>
> patch is against linux-next 3.19.0-rc3 -next-20150108
>
> drivers/dma/ioat/dma_v3.c |9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2015 01:10 PM, Andrey Skvortsov wrote:
> On Wed, Jan 07, 2015 at 12:21:18PM -0700, Shuah Khan wrote:
>> On 01/07/2015 11:35 AM, Andrey Skvortsov wrote:
>>> add -lrt to fix undefined reference to `clock_gettime'
>>>
>>> Signed-off-by: Andrey S
On Thu, Jan 08, 2015 at 08:56:39AM +, Arnd Bergmann wrote:
> On Wednesday 07 January 2015 18:04:41 Murali Karicheri wrote:
> > On 01/07/2015 04:18 PM, Arnd Bergmann wrote:
> > > On Wednesday 07 January 2015 13:49:50 Murali Karicheri wrote:
> > >> PCI devices on Keystone doesn't have correct dma
301 - 400 of 672 matches
Mail list logo
