This patch adds Comedi driver for Humusoft MF634 (PCIe) and
MF624 (PCI) data acquisition cards. The legacy card Humusoft
MF614 is not supported. More info about the cards may be found
at http://humusoft.cz/produkty/datacq/
The driver was tested with both cards. Everything seems to work
properly.
Changes since v1:
* Implemented all the small and big remarks pointed out by
Hartley Sweeten, Dan Carpenter and Ian Abbott
Rostislav Lisovy (1):
comedi: Humusoft MF634 and MF624 DAQ cards driver
drivers/staging/comedi/Kconfig | 6 +
drivers/staging/comedi/comedidev.h | 1 +
I am realizing that Linux-brats are vere very much like abusive mushroom
users aren´t they. I did ressearch on this, and that is where I have
seen that behaviour before. Obviously only having them in the
environment is influental, as I doubt they all do mushrooms.
This will be included on my
From: Andi Kleen
The --delay option was documented as --initial-delay in the perf
stat manpage. Fix this.
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/perf-stat.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/Documentation/perf-stat.txt
From: Andi Kleen
perf stat has a --delay option to delay measuring the workload.
This is useful to skip measuring the startup phase of the program, which
is often very different from the main workload.
The same is useful for perf record when sampling. Add --delay to perf record
too.
-D was
On Tue, Jan 07, 2014 at 01:58:17PM -0800, Andrew Morton wrote:
> On Mon, 6 Jan 2014 16:08:46 -0800 Andi Kleen wrote:
>
> > From: Andi Kleen
> >
> > [It turns out the documentation patch was already merged
> > earlier. So just resending without documentation.]
>
> Confused. How could we have
On 01/07/2014 12:16 PM, Greg Kroah-Hartman wrote:
On Tue, Jan 07, 2014 at 12:07:14PM -0700, Shuah Khan wrote:
On 01/06/2014 03:36 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.7 release.
There are 144 patches in this series, all will be posted as a
On Tue, 2014-01-07 at 14:02 -0800, Darrick J. Wong wrote:
> On Tue, Jan 07, 2014 at 07:59:15PM +, Chris Mason wrote:
> > On Tue, 2014-01-07 at 11:43 -0800, Darrick J. Wong wrote:
> > > On Tue, Jan 07, 2014 at 12:04:30PM -0500, Theodore Ts'o wrote:
> > > > On Tue, Jan 07, 2014 at 07:49:35AM
This is a(nother) proof of concept interface for replacing the
contentious FS_IOC_[GS]ETFLAGS interface with a new ioctl that allows
for a dramatic increase in the size of the flag-space.
In this new interface, the new [GS]ETFLAGS functions take a flag
number and either return or set the flag
On Tue, Jan 07, 2014 at 07:59:15PM +, Chris Mason wrote:
> On Tue, 2014-01-07 at 11:43 -0800, Darrick J. Wong wrote:
> > On Tue, Jan 07, 2014 at 12:04:30PM -0500, Theodore Ts'o wrote:
> > > On Tue, Jan 07, 2014 at 07:49:35AM -0800, Christoph Hellwig wrote:
> > > > On Tue, Jan 07, 2014 at
[cc: some more people]
On Wed, Dec 18, 2013 at 6:02 PM, Andy Lutomirski wrote:
> I have a box running 3.9.4. For a few hundred ms, all packages and
> cores* exceeded their power limits, and then they all came back to
> normal.
>
> Since then, turbo boost went away.
>
> The first thing I tried
On Mon, Jan 06, 2014 at 09:04:25PM -0500, Mike Snitzer wrote:
> On Wed, Dec 18, 2013 at 8:12 PM, Kent Overstreet wrote:
> > Now that we've got code for raid5/6 stripe awareness, bcache just needs
> > to know about the stripes and when writing partial stripes is expensive
> > - we probably don't
On Mon, 6 Jan 2014 16:08:46 -0800 Andi Kleen wrote:
> From: Andi Kleen
>
> [It turns out the documentation patch was already merged
> earlier. So just resending without documentation.]
Confused. How could we have merged the documentation for this feature
but not the feature itself?
> As
On Tue, Jan 07, 2014 at 09:46:57PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, January 07, 2014 10:48:05 AM David E. Box wrote:
> > On Tue, Jan 07, 2014 at 10:15:03AM -0800, Randy Dunlap wrote:
> > > On 01/07/14 10:03, David E. Box wrote:
> > > > From: "David E. Box"
> > > >
> > > > diff --git
> "Hannes" == Hannes Reinecke writes:
Hannes> Plus (as hch rightly pointed out) as there is no defined
Hannes> userland interface the question is why we bother with all the
Hannes> DIX stuff in the block layer.
Because it catches problems in the path between block layer and HBA
ASIC?
On Tue, Jan 07, 2014 at 12:59:38PM -0500, Tejun Heo wrote:
> This patchset improves kernfs removal path and implements
> kernfs_remove_self() which is to be called from an on-going kernfs
> operation and removes the self node. The function can be called
> concurrently and only one will return
This update also fixes a bug when deprecated pci_enable_msix()
and pci_enable_msi_block() functions return a positive return
value which indicats the number of interrupts that could have
been allocated rather than a successful allocation. The driver
misinterpreted this value and assumed MSI-X/MSIs
As result of recent deprecation of MSI-X/MSI enablement
interfaces pci_enable_msi_block(), pci_enable_msi() and
pci_enable_msix() all drivers need to be updated to use
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
This is the first in a series of updates, to phase out
Signed-off-by: Alexander Gordeev
---
drivers/net/wireless/ath/wil6210/pcie_bus.c | 36 ++
1 files changed, 19 insertions(+), 17 deletions(-)
diff --git a/drivers/net/wireless/ath/wil6210/pcie_bus.c
b/drivers/net/wireless/ath/wil6210/pcie_bus.c
index eeceab3..022dfe4
This update also fixes a stylistic (naming and messaging only)
confusion of MSI-X vs multiple MSIs which are not the same.
Signed-off-by: Alexander Gordeev
---
drivers/net/wireless/ath/ath10k/pci.c | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git
Signed-off-by: Alexander Gordeev
---
drivers/ata/ahci.c | 15 ++-
1 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 8516f4d..cfdb079 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -1098,13 +1098,13 @@ static
Signed-off-by: Alexander Gordeev
---
drivers/scsi/ipr.c |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
index 36ac1c3..fb57e21 100644
--- a/drivers/scsi/ipr.c
+++ b/drivers/scsi/ipr.c
@@ -9255,10 +9255,8 @@ static int
Signed-off-by: Alexander Gordeev
---
drivers/block/nvme-core.c | 33 -
1 files changed, 8 insertions(+), 25 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 26d03fa..adf26c2 100644
--- a/drivers/block/nvme-core.c
+++
Signed-off-by: Alexander Gordeev
---
drivers/scsi/ipr.c | 47 ++-
1 files changed, 18 insertions(+), 29 deletions(-)
diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
index fb57e21..3841298 100644
--- a/drivers/scsi/ipr.c
+++ b/drivers/scsi/ipr.c
On Tue, Jan 7, 2014 at 7:09 AM, Catalin Marinas wrote:
> On Fri, Dec 27, 2013 at 04:58:48AM +, Mark Zhang wrote:
>> From: Colin Cross
>>
>> For streaming-style operations (e.g., software rendering of graphics
>> surfaces shared with non-coherent DMA devices), the cost of performing
>> L2
Hi!
> Ok, after looking at what both N900 and N9 Nokia kernels do, I came
> up with the patch bellow. If you are ok with the changes, I'll
> submit the patch as it should. With that patch I tried more than 20
> videos of different resolutions(including 720p), not a single
> failure :) . Basically
And.. actually in commercial constructs one is also abused, but atleast
one gets money. In open-source, or particulary Stallman idolaters, one
is only abused.
No limiter-awards, where technical excellence is recognized, because
"the algorithm does this and that, and this is optimal". None of
On Tue, Jan 07, 2014 at 01:58:32PM +, David Laight wrote:
> The dmesg contains:
>
> [ 538.728064] EXT4-fs warning (device dm-0): ext4_end_bio:316: I/O error
> writing to inode 23330865 (offset 0 size 8388608 starting block 812628)
>
> An 8MB transfer will need at least 128 ring entries
Chris,
This is based off of Jens block tree, for-3.14/core branch...
Regards,
Muthu
On Tue, Jan 7, 2014 at 12:29 PM, Chris Mason wrote:
> On Tue, 2014-01-07 at 12:15 -0800, Muthu Kumar wrote:
>> Thanks Fengguang. Final patch with added comment. BTW, fengguang
>> mentioned that git-am has
On Tue, Jan 07, 2014 at 05:29:48AM -0800, walt wrote:
> On 01/06/2014 04:31 PM, Sarah Sharp wrote:
> > Hi Walt,
> >
> > I have a couple of patches for you to test.
>
> > Please only apply the first patch (which is diagnostic only), trigger
> > your issue, and send me the resulting dmesg. Then
From: Benjamin Poirier
Date: Tue, 7 Jan 2014 10:11:10 -0500
> There are many cases where this feature does not improve performance or even
> reduces it.
>
> For example, here are the results from tests that I've run using 3.12.6 on one
> Intel Xeon W3565 and one i7 920 connected by ixgbe
Just to be clear, no idolatry. At all.
Anyways I am just going to use windows here, and maybe even get an E5
mac. It has logic audio, which I think is perfectly fine.
I am almost nervous to contribute to this, seeing as much obscurity as
it is. People will have to choose a solution good for
On Tue, Jan 07, 2014 at 03:15:52PM +, Waskiewicz Jr, Peter P wrote:
> > Still confused here. So what you're saying is that cachelines get tagged
> > with {CR3,RMID} and when they observe the same CR3 with a different RMID
> > the hardware will iterate the entire cache and update all tuples?
>
On 1/7/2014 9:52 PM, Richard Dunn wrote:
In case you missed it, Phoronix covered your original email.
http://www.phoronix.com/scan.php?page=news_item=MTU1MTI
Phoronix is not a serious newsplace.
I did think about the problem some more.
Maybe the whole Microkernel debate is an ego-issue too,
In case you missed it, Phoronix covered your original email.
http://www.phoronix.com/scan.php?page=news_item=MTU1MTI
On 1/7/14, Liam Lindholm wrote:
> Mr. Karlsen,
>
> I find your response to my initial email quite interesting, but do not
> quite understand it. My mind is very sluggish here in
On Tue, Jan 07, 2014 at 04:42:55PM +0100, Andi Kleen wrote:
> > Yes; go read this:
> >
> > lkml.kernel.org/r/20131219125205.gt3...@twins.programming.kicks-ass.net
>
> Hmm, but AFAIK we're not using freeze counters on PMI today.
> We just rely on the explicit disabling in the counters through
On Tue, Jan 07, 2014 at 03:41:54PM +, Morten Rasmussen wrote:
> I think that could work if we sort of the priority scaling issue that I
> mentioned before.
We talked a bit about this on IRC a month or so ago, right? My memories
from that are that your main complaint is that we don't detect
On 01/07/2014 07:10 AM, Peter De Schrijver wrote:
> On Mon, Jan 06, 2014 at 09:50:42PM +0100, Stephen Warren wrote:
>> On 12/24/2013 06:32 AM, Peter De Schrijver wrote:
>>> Reduce fuse.c to the minimum functionality required for the early
>>> bootstages.
>>>
>>> Also export tegra_read_straps()
On 14-01-07 09:15 AM, Linus Walleij wrote:
On Sat, Dec 21, 2013 at 3:13 AM, Sherman Yin wrote:
+Optional Properties (for standard pins):
+
+- function:String. Specifies the pin mux selection. Values
+ must be one of: "alt1", "alt2", "alt3",
Hi!
There's some locking weirdness, and few missing comments in lp5523
driver.
Now, this is untested patch from my reverse-engineering. I hope I
understood things right...
In particular, there's unbalanced unlock in
lp5523_update_program_memory, and lp5523_update_program_memory needs
to be
On 01/07/2014 07:05 AM, Peter De Schrijver wrote:
> On Mon, Jan 06, 2014 at 09:32:24PM +0100, Stephen Warren wrote:
>> On 12/24/2013 06:32 AM, Peter De Schrijver wrote:
>>> Implement fuse driver for Tegra20, Tegra30, Tegra114 and Tegra124.
>>> diff --git a/drivers/misc/fuse/tegra/fuse-tegra20.c
On Tue, Jan 07, 2014 at 03:16:32PM +, Morten Rasmussen wrote:
> From a load perspective wouldn't it be better to pick the least loaded
> cpu in the group? It is not cheap to implement, but in theory it should
> give less balancing within the group later an less unfairness until it
> happens.
On Tuesday, January 07, 2014 10:48:05 AM David E. Box wrote:
> On Tue, Jan 07, 2014 at 10:15:03AM -0800, Randy Dunlap wrote:
> > On 01/07/14 10:03, David E. Box wrote:
> > > From: "David E. Box"
> > >
> > > diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> > > index
On Tue, 2014-01-07 at 12:15 -0800, Muthu Kumar wrote:
> Thanks Fengguang. Final patch with added comment. BTW, fengguang
> mentioned that git-am has trouble with the inline patch and "quilt
> import" worked fine for him...
>
>
> In btrfs_end_bio(), we increment bi_remaining if
On 07.01.2014 14:35, Tomi Valkeinen wrote:
On 2014-01-06 11:43, Ivaylo Dimitrov wrote:
Hi,
commit 7faa92339bbb1e6b9a80983b206642517327eb75 "OMAPDSS: DISPC: Handle
synclost errors in OMAP3" introduces some limits check to prevent
SYNCLOST errors on OMAP3 in a specific usecase. The problem I see
On Tue, 7 Jan 2014, Mike Snitzer wrote:
> On Tue, Jan 07 2014 at 1:00pm -0500,
> Mikulas Patocka wrote:
>
> >
> >
> > On Tue, 7 Jan 2014, Linus Torvalds wrote:
> >
> > > This looks completely broken to me. You do a "kobject_put()" and then
> > > after you've dropped that last use, you
Thanks Fengguang. Final patch with added comment. BTW, fengguang
mentioned that git-am has trouble with the inline patch and "quilt
import" worked fine for him...
In btrfs_end_bio(), we increment bi_remaining if is_orig_bio. If not,
we restore the orig_bio but failed to increment
On 01/07, Lorenzo Pieralisi wrote:
>
> Not sure this binding (cache node) belongs in cpus.txt
>
> I am working on defining cache bindings for ARM within the C-state
> standardization effort:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-December/215543.html
Thanks I'll take a
On Tue, Jan 7, 2014 at 7:50 PM, Alan Stern wrote:
> After all, it's not like there's anything I can do to fix the hardware,
> is there? And it doesn't look like the pipe state mismatch is going to
> go away by itself. Or is this a genuine, fixable, software bug?
These are genuine software bugs
When patching gathers, we don't need to check against
gathers with lower indices than the current one, as
they are guaranteed to already have been handled.
Signed-off-by: Erik Faye-Lund
---
Here's a trivial optimization I have been running with for a while.
drivers/gpu/host1x/job.c | 2 +-
1
Okay, I used log_buf_len to make dmesg bigger and now I think I have
the whole thing. It's attached.
dmesg2.gz
Description: application/gzip
On Tue, 2014-01-07 at 11:43 -0800, Darrick J. Wong wrote:
> On Tue, Jan 07, 2014 at 12:04:30PM -0500, Theodore Ts'o wrote:
> > On Tue, Jan 07, 2014 at 07:49:35AM -0800, Christoph Hellwig wrote:
> > > On Tue, Jan 07, 2014 at 01:48:31PM +0100, Jan Kara wrote:
> > > > I have to say I'm not thrilled
On 01/07, Lee Jones wrote:
> > >> +return of_platform_populate(pdev->dev.of_node, NULL, NULL,
> > >> >dev);
> > >> +}
> > > Can't you use the MFD core instead?
> > >
> >
> > Are you suggesting using mfd_add_devices()? At first glance it looks
> > like that would require an array of
From: Ville Syrjälä
The casts in __copy_{from,to}_user_inatomic lead to sparse warnings.
Drop the casts to get rid of the warnings.
Example:
CHECK drivers/gpu/drm/i915/i915_gem.c
arch/x86/include/asm/uaccess_64.h:213:40: warning: incorrect type in argument 1
(different address spaces)
On Tue, Jan 07, 2014 at 12:04:30PM -0500, Theodore Ts'o wrote:
> On Tue, Jan 07, 2014 at 07:49:35AM -0800, Christoph Hellwig wrote:
> > On Tue, Jan 07, 2014 at 01:48:31PM +0100, Jan Kara wrote:
> > > I have to say I'm not thrilled by the idea of juggling strings in
> > > userspace and in kernel
On Mon, Jan 06, 2014 at 05:32:56PM -0500, faibish, sorin wrote:
> Speaking of persistent memory I would like to discuss the PMFS as well as
> RDMA aspects of the persistent memory model. Also I would like to discuss KV
> stores and object stores on persistent memory. I was involved in the PMFS
Mr. Karlsen,
I find your response to my initial email quite interesting, but do not
quite understand it. My mind is very sluggish here in Sweden where it
is very, very cold. Sluggish like a cluster of 386s running Linux on a
kitchen table in someone's backwoods shack.
In case you didn't see it,
On Sat, Dec 14, 2013 at 12:14 AM, Christian Daudt wrote:
> On Thu, Dec 5, 2013 at 11:20 AM, Tim Kryger wrote:
>> Enable the external clock needed by the host controller during the
>> probe and disable it during the remove.
>>
>> Signed-off-by: Tim Kryger
>> Reviewed-by: Markus Mayer
>>
On Tue, Jan 07, 2014 at 07:21:05PM +0800, Jeff Liu wrote:
> Hi Chuansheng,
>
> On 01/07 2014 16:53 PM, Chuansheng Liu wrote:
> >
> > In case CONFIG_DEBUG_OBJECTS_WORK is defined, it is needed to
> > call destroy_work_on_stack() which frees the debug object to pair
> > with INIT_WORK_ONSTACK().
>
On 01/07/14 10:48, David E. Box wrote:
> On Tue, Jan 07, 2014 at 10:15:03AM -0800, Randy Dunlap wrote:
>> On 01/07/14 10:03, David E. Box wrote:
>>> From: "David E. Box"
>>>
>>> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
>>> index b51a746..6e199a5 100644
>>> ---
After thp split in hwpoison_user_mappings(), we hold page lock on the raw
error page only between try_to_unmap, hence we are in danger of race condition.
I found in the RHEL7 MCE-relay testing that we have "bad page" error
when a memory error happens on a thp tail page used by qemu-kvm:
On Tue, Jan 07, 2014 at 12:07:14PM -0700, Shuah Khan wrote:
> On 01/06/2014 03:36 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.12.7 release.
> >There are 144 patches in this series, all will be posted as a response
> >to this one. If anyone has any
On Tue, Jan 07 2014 at 1:00pm -0500,
Mikulas Patocka wrote:
>
>
> On Tue, 7 Jan 2014, Linus Torvalds wrote:
>
> > This looks completely broken to me. You do a "kobject_put()" and then
> > after you've dropped that last use, you wait for the completion of
> > something that may already have
On 01/07/2014 05:58 AM, David Laight wrote:
> The dmesg contains:
>
> [ 538.728064] EXT4-fs warning (device dm-0): ext4_end_bio:316: I/O error
> writing to inode 23330865 (offset 0 size 8388608 starting block 812628)
>
> An 8MB transfer will need at least 128 ring entries (TRB) even if the
Sorry, haven't had the chance yet. I'll try to do this and hopefully
send v3 of the patch by the end of this week
On Mon, Jan 6, 2014 at 11:14 PM, Dmitry Torokhov
wrote:
> On Fri, Jan 03, 2014 at 09:41:33PM -0800, Dmitry Torokhov wrote:
>> On Fri, Jan 03, 2014 at 09:03:11PM -0800, Andrey Smirnov
On 01/06/2014 03:39 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.76 release.
There are 43 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 01/07, Sergio Durigan Junior wrote:
>
> On Tuesday, January 07 2014, Oleg Nesterov wrote:
>
> > Finally. If we add this feature, we should probably also report
> > is_compat_task() somehow. Currently the debugger can't know if, say,
> > a 64bit tracee does int80.
>
> OK, I will look into it,
On 01/06/2014 03:37 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.26 release.
There are 129 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
From: Ethan Zhao
Date: Tue, 7 Jan 2014 17:31:17 +0800
> Has kmalloc() failure checking there, so it is unnecessary to allocate with
> __GFP_NOFAIL flag that might block forever.
>
> Signed-off-by: Ethan Zhao
This allocation failing borders on catastrophic. The allocation failure
handling is
On 01/06/2014 03:36 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.7 release.
There are 144 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
As of Matt Mooney's major refactoring in 2011, usbip port
option was left out. Add support for this option in
a manner similar to the old implementation.
Sample output:
Imported USB devices
Port 00: at Full Speed(12Mbps)
unknown vendor : unknown product (1687:6211)
3.10.26-rc1 also had some issues, so here's a -rc2 release.
Chances from -rc1 were the removal of a mm patch that shouldn't have
been there, addition of an ext4 fix, sh export symbol fix, and some ARM
clocksource fixes.
Full release announcement follows:
--
This
On Tue, Jan 07, 2014 at 11:02:30AM -0800, Greg Kroah-Hartman wrote:
> As there were lots of changes to the -rc1 release, I've now done a -rc2.
>
> Changes were with the mm NUMA patches (lots more added and reordered to
> fix potential build issues), some ARM clock fixes added, and a SH patch.
On Tue, 2014-01-07 at 09:24 -0800, Joe Perches wrote:
> On Tue, 2014-01-07 at 09:12 -0800, Davidlohr Bueso wrote:
> > On Tue, 2013-12-24 at 16:02 +0100, Manfred Spraul wrote:
> > > The ipc code does not adhere the typical linux coding style.
> > > This patch fixes lots of simple whitespace errors.
As there were lots of changes to the -rc1 release, I've now done a -rc2.
Changes were with the mm NUMA patches (lots more added and reordered to
fix potential build issues), some ARM clock fixes added, and a SH patch.
Full announcement follows:
---
On Thu, Dec 26, 2013 at 5:56 AM, 曹荣荣 wrote:
> I have read the latest Documentation/pinctrl.txt, and there is two examples
> about muxing logic in "GPIO mode pitfalls" section, let me take example A
> for instance:
>
>pin config
>logic regs
>
On Wed, 13 Nov 2013 13:06:33 -0800
"H. Peter Anvin" wrote:
> On 11/13/2013 12:20 PM, Steven Rostedt wrote:
> >
> > Function tracing callbacks expect to have the ftrace_ops that registered it
> > passed to them, not the address of the variable that holds the ftrace_ops
> > that registered it.
>
The board schematic states that the "SD_CARD_DET_N gets pulled to GND
when card is inserted" so the polarity has been updated to active low.
Polarity is now specified with a GPIO define instead of a magic number.
Signed-off-by: Tim Kryger
Reviewed-by: Matt Porter
---
On Tue, Jan 7, 2014 at 3:05 PM, Lars Poeschel wrote:
> From: Lars Poeschel
>
> This adds interrupt functionality for i2c chips to the driver.
> They can act as a interrupt-controller and generate interrupts, if
> the inputs change.
> This is tested on a mcp23017 chip.
>
> Signed-off-by: Lars
On Mon, Jan 06, 2014 at 09:05:17PM -0800, Guenter Roeck wrote:
> On 01/06/2014 02:36 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.12.7 release.
> >There are 144 patches in this series, all will be posted as a response
> >to this one. If anyone has any
Hello,
The check_crtc_state() routine in drivers/gpu/drm/i915/intel_display.c
contains a whole bunch of WARN() statements (and so do other routines
in this source file, but this is the one I'm presently concerned
about). Is it really necessary for these to be WARN?
I don't see how it does any
On Tue, Jan 07, 2014 at 10:09:50AM +, Mark Rutland wrote:
> Hi Greg,
>
> On Mon, Jan 06, 2014 at 10:39:15PM +, Greg Kroah-Hartman wrote:
> > 3.10-stable review patch. If anyone has any objections, please let me know.
>
> This patch alone may break ARM systems booted at hyp mode or when
On Tue, Jan 07, 2014 at 10:15:03AM -0800, Randy Dunlap wrote:
> On 01/07/14 10:03, David E. Box wrote:
> > From: "David E. Box"
> >
> > diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> > index b51a746..6e199a5 100644
> > --- a/drivers/platform/x86/Kconfig
> > +++
On Tue, Jan 07, 2014 at 05:26:59PM +, Luis Henriques wrote:
> On Mon, Jan 06, 2014 at 02:38:24PM -0800, Greg Kroah-Hartman wrote:
> > 3.10-stable review patch. If anyone has any objections, please let me know.
>
> This commit was tagged for 3.12 stable only, so you may want to drop it.
On 01/07/2014 12:54 PM, Luck, Tony wrote:
> + for (vector = FIRST_EXTERNAL_VECTOR; vector < NR_VECTORS; vector++) {
> + irq = __this_cpu_read(vector_irq[vector]);
> + if (irq >= 0) {
> + desc = irq_to_desc(irq);
> + data =
On Tue, Jan 7, 2014 at 3:46 AM, Daniel Vetter wrote:
> On Mon, Jan 06, 2014 at 05:55:12PM -0700, Bjorn Helgaas wrote:
>> This is basically v7 of Yinghai's patch series:
>> http://lkml.kernel.org/r/1387485843-17403-1-git-send-email-ying...@kernel.org
>>
>> The goal is to try to put 64-bit BARs
On Tue, 2014-01-07 at 19:05 +0100, Alexander Gordeev wrote:
> This update also fixes a bug when deprecated pci_enable_msix()
> and pci_enable_msi_block() functions return a positive return
> value which indicats the number of interrupts that could have
> been allocated rather than a successful
Hi Christoph,
On 7 January 2014 17:58, Christoph Hellwig wrote:
> On Mon, Jan 06, 2014 at 09:10:32PM +0100, Jan Kara wrote:
>> This is likely a problem of Linux direct IO implementation. The thing is
>> that in Linux when you are doing appending direct IO (i.e., direct IO which
>> changes file
Oops, fixed build error for !CONFIG_SYSFS due to broken missing /
wrong dummy functions. No other changes. I really should wait for
kbuild bot before sending out patches. git tree has been updated
accordingly.
Thanks.
- 8< -
>From cd468f7b831d8231d4da9c2b9d631a5eb364300b Mon Sep 17
On Tue, 7 Jan 2014 16:36:29 +
Dave Martin wrote:
> My other concern was that we might end up in a recursive trace due to
> the use of non-notrace core functions in the unwinder. But I seem to
> remember Steve Rostedt saying the the tracer guards against recursive
> invocation nowadays -- if
On Tue, Jan 07, 2014 at 04:35:01PM +0100, Arnd Bergmann wrote:
> > >> + 0x 0x0 0xd000 0xe0 0xd000 0x0
> > >> 0x0020 /* cfg */
> > >
> > > config space is not normally in the ranges property, and I think you will
> > > need
> > > it in the pcie node
On 07.01.2014 20:05, Pavel Machek wrote:
On Tue 2014-01-07 14:35:02, Tomi Valkeinen wrote:
On 2014-01-06 11:43, Ivaylo Dimitrov wrote:
Hi,
commit 7faa92339bbb1e6b9a80983b206642517327eb75 "OMAPDSS: DISPC: Handle
synclost errors in OMAP3" introduces some limits check to prevent
SYNCLOST errors
On Tue, Jan 7, 2014 at 6:56 PM, Pavel Machek wrote:
>> The additional cost of using current vs NULL is ~zero.
>
> The additional cost of current vs NULL is cca 8 bytes per caller. Test
> for NULL is cca 4 bytes, maybe 20 bytes total. I believe it is worth
> it.
It depends (typical answer ;-)
On
A locking dependency problem has been reported for b43 at
https://bugzilla.kernel.org/show_bug.cgi?id=67561. I was able to duplicate with
the following:
1. Set network under manual, not NetworkManager, control.
2. Start hostapd
3. Use 'rfkill block all' to disable the access point
As my
On Tue, Jan 07, 2014 at 06:16:22AM -0800, Greg Kroah-Hartman wrote:
> On Mon, Jan 06, 2014 at 11:01:22PM -0500, Mikulas Patocka wrote:
> >
> >
> > On Mon, 6 Jan 2014, Mike Snitzer wrote:
> >
> > > On Mon, Jan 06 2014 at 1:55pm -0500,
> > > Mikulas Patocka wrote:
> > >
> > > >
> > > >
> > >
Hello Bjorn / Yinghai,
> -Original Message-
> From: Bjorn Helgaas [mailto:bhelg...@google.com]
> Sent: Monday, January 06, 2014 4:04 PM
> To: Rajat Jain
> Cc: Rajat Jain; Kenji Kaneshige; Alex Williamson; Yijing Wang; linux-
> p...@vger.kernel.org; linux-kernel@vger.kernel.org; Yinghai
rcu_dereference_check_fdtable() looks very wrong,
1. rcu_my_thread_group_empty() was added by 844b9a8707f1 "vfs: fix
RCU-lockdep false positive due to /proc" but it doesn't really
fix the problem. A CLONE_THREAD (without CLONE_FILES) task can
hit the same race with get_files_struct().
On 01/07/14 10:03, David E. Box wrote:
> From: "David E. Box"
>
> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> index b51a746..6e199a5 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -819,4 +819,14 @@ config PVPANIC
> a
On 01/07/14 06:21, Jean Delvare wrote:
> Hi Eduardo,
>
> I suppose this works, however I believe there is value in allowing for
> modular building of as much code as possible.
ack, yes, please.
> I have an alternative proposal, which lets thermal be built as module,
> and hopefully also
On Tue, 7 Jan 2014, Greg Kroah-Hartman wrote:
> > Index: linux-3.13-rc7/drivers/md/dm-sysfs.c
> > ===
> > --- linux-3.13-rc7.orig/drivers/md/dm-sysfs.c 2014-01-07
> > 02:06:08.0 +0100
> > +++
201 - 300 of 1472 matches
Mail list logo
