On Fri, Feb 21, 2014 at 7:14 PM, Jiang Liu wrote:
> Seems there is no such protection on IA64 side. I feel create_irq_nr()
> returns 0 for error is a little risky, 0 may be
> a valid IRQ number on other platforms(no sure about this).
> Thanks!
in [PATCH] ia64, irq: Add dummy
init_inodecache is only called by __init init_affs_fs
Signed-off-by: Fabian Frederick
---
fs/affs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/affs/super.c b/fs/affs/super.c
index d098731..41a7557 100644
--- a/fs/affs/super.c
+++ b/fs/affs/super.c
@@ -128,7
Hi
> Please use the real compatibles here. It's much easier to search
> for. Plus, your driver doesn't support all the SoCs you're mentionning here.
> [...]
> Please provide the real property name to use. No need for an example
> here, you have a full-fledged one in a few lines.
Fixed that.
>
- Remove old and currently wrong address of the FSF from license
parts of the code.
- Remove unused #include and sort remaining headers alphabetically.
- Remove unised definitions.
- Add definitions for bit-fields.
- Add missing module owner field.
Signed-off-by: Alexander Shiyan
---
Configuration for masters and slaves is included only if W1 symbol
enabled, so no reason to check it once more.
Signed-off-by: Alexander Shiyan
---
drivers/w1/masters/Kconfig | 3 +--
drivers/w1/slaves/Kconfig | 5 -
2 files changed, 1 insertion(+), 7 deletions(-)
diff --git
This helps increasing build testing coverage.
To do this, __raw_{read,write}b() functions was be replaced with
simple {read,write}b() variants.
Signed-off-by: Alexander Shiyan
---
drivers/w1/masters/Kconfig | 2 +-
drivers/w1/masters/mxc_w1.c | 12 ++--
2 files changed, 7
This patch fix mxc_w1_ds2_reset_bus() return value.
According to i.MX reference manual, "presence status" reflected
in the bit 6 of control register.
Signed-off-by: Alexander Shiyan
---
drivers/w1/masters/mxc_w1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hello
I am from GEA Groups Company Ltd, we are really interested in your product
being advertise in IM. We would like to have quotations for the following
products. Kindly log on to our website by clicking on the link below to view
the sample of the products we wish to buy.
On 02/21/2014 08:37 PM, Sebastian Capella wrote:
> Quoting Sebastian Capella (2014-02-21 15:59:11)
>> - Cyril Chemparathy as his email is bouncing back to me.
>>
>> Quoting Sebastian Capella (2014-02-21 10:39:56)
>>> Quoting Lorenzo Pieralisi (2014-02-20 08:27:55)
>>> +
Thomas,
This is a small round of changes intended for v3.15. Despite the commit
date these have been in -next for almost a week. I needed to rebase the
branch on v3.14-rc1 instead of merging it. When I originally added
these patches, the dove PMU hadn't been pulled from this branch yet.
At
On 02/21/2014 08:50 PM, Vince Weaver wrote:
So I changed the perf_fuzzer so when it randomly stomps all over the
perf_event_mmap_page, it uses a constant value of 0xdeadbeef rather
than a random value.
The result is below. The segfaults make a bit more sense now, it
almost looks like what is
This patch moves diagnostic messages used for debugging purposes
to dev_dbg().
Signed-off-by: Alexander Shiyan
---
drivers/mfd/syscon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
index 71841f9..2620056 100644
---
Those are segfaults in user space, though?
On February 21, 2014 8:50:38 PM PST, Vince Weaver
wrote:
>
>So I changed the perf_fuzzer so when it randomly stomps all over the
>perf_event_mmap_page, it uses a constant value of 0xdeadbeef rather
>than a random value.
>
>The result is below. The
On Fri, 2014-02-21 at 20:55 -0800, Davidlohr Bueso wrote:
> On Fri, 2014-02-21 at 13:24 -0800, Linus Torvalds wrote:
> > On Fri, Feb 21, 2014 at 12:57 PM, Davidlohr Bueso wrote:
> > >
> > > Btw, one concern I had is regarding seqnum overflows... if such
> > > scenarios should happen we'd end up
On Fri, 2014-02-21 at 13:24 -0800, Linus Torvalds wrote:
> On Fri, Feb 21, 2014 at 12:57 PM, Davidlohr Bueso wrote:
> >
> > Btw, one concern I had is regarding seqnum overflows... if such
> > scenarios should happen we'd end up potentially returning bogus vmas and
> > getting bus errors and other
Remove checking control_reg in [set|get]_voltage_sel and then convert to use
regulator_[set|get]_voltage_sel_regmap for [set|get]_voltage_sel callbacks.
The anatop-reg-offset property is a required property rather than optional
property. So the question is what is the meaning of setting
So I changed the perf_fuzzer so when it randomly stomps all over the
perf_event_mmap_page, it uses a constant value of 0xdeadbeef rather
than a random value.
The result is below. The segfaults make a bit more sense now, it
almost looks like what is happening is we are corrupting an address
On Sat, 22 Feb 2014 05:03:50 +0100 Andi Kleen wrote:
> > But I think it would be better if it made hugepages= and hugepagesz=
> > obsolete, so we can emit a printk if people use those, telling them
> > to migrate because the old options are going away.
>
> Not sure why everyone wants to break
On Sat, 2014-02-22 at 05:03 +0100, Andi Kleen wrote:
> > But I think it would be better if it made hugepages= and hugepagesz=
> > obsolete, so we can emit a printk if people use those, telling them
> > to migrate because the old options are going away.
>
> Not sure why everyone wants to break
> But I think it would be better if it made hugepages= and hugepagesz=
> obsolete, so we can emit a printk if people use those, telling them
> to migrate because the old options are going away.
Not sure why everyone wants to break existing systems. These options
have existed for many years, you
Hi Linus,
Please pull hwmon fixes for Linux 3.14-rc4 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus
Thanks,
Guenter
--
The following changes since commit 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2:
Linux 3.14-rc3 (2014-02-16
There are a couple of cases where a comment being on the same line as a
statement is causing the line to be over 80 characters long. This is an
easy fix; move these comments to the previous line.
Signed-off-by: Chase Southwood
---
drivers/staging/comedi/drivers/addi-data/hwdrv_apci035.c | 11
There were some conditional blocks that had an unneccesary level of
indentation in them. We can remove this to improve code clarity.
Signed-off-by: Chase Southwood
---
.../comedi/drivers/addi-data/hwdrv_apci035.c | 31 ++
1 file changed, 14 insertions(+), 17
This patch further cleans up the comments in hwdrv_apci035.c, converting
them to kernel style and removing some commented conditional statements
that are unused.
Signed-off-by: Chase Southwood
---
I decided to return to the first driver I touched. I found some more
things that could be cleaned
On 2014/2/22 7:18, Yinghai Lu wrote:
> On Thu, Feb 20, 2014 at 11:43 PM, Jiang Liu wrote:
>>
>>
>> On 2014/1/3 8:05, Yinghai Lu wrote:
>>> iommu irq's irq_desc should be on local node ram.
>>>
>>> Fix the return value checking problem.
>>> create_irq() will return -1 when fail to allocate.
On Fri, Feb 21, 2014 at 01:12:38PM +0100, Krzysztof Kozlowski wrote:
> This fixes bug introduced in 667a6b7a (regulator: max14577: Add missing
> of_node_put). The DTS parsing function returned number of matched
> regulators as success status which then was compared against 0 in probe.
Applied,
Hi John,
This is our first pull request for 3.15, the main feature here is the addition
of
the privacy feature for low energy devices. Other than that we have a bunch of
small
improvements, fixes, and clean ups all over the tree.
Please pull or let me know of any concerns you may have. Thanks.
On Fri, Feb 21, 2014 at 04:06:10PM +0800, Nenghua Cao wrote:
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
> @@ -2413,7 +2413,7 @@ struct snd_kcontrol *snd_soc_cnew(const struct
> snd_kcontrol_new *_template,
> struct snd_kcontrol *kcontrol;
> char *name = NULL;
>
> -
On Fri, Feb 21, 2014 at 04:05:45PM +0800, Nenghua Cao wrote:
> From: Nenghua Cao
>
>/drivers/base/regmap/regmap.c:717:6-33: WARNING:
> Comparison to bool.
Applied, thanks. Please use subject lines consistent with the
subsystem.
signature.asc
Description: Digital signature
On Fri, Feb 21, 2014 at 09:38:55AM +, Charles Keepax wrote:
> I guess there are two parts here applying the hardware patch and
> the manual application of the register patch. Applying the
> hardware patch restores registers once it is finished anyway, and
> the actual patch is applied by the
On Fri, Feb 21, 2014 at 07:37:10PM +, Charles Keepax wrote:
> Currently, we check the registers in the patch are aligned to the
> register stride everytime we sync the cache and the first time the patch
> is written out is unchecked.
Applied, thanks.
signature.asc
Description: Digital
On Fri, Feb 21, 2014 at 07:37:11PM +, Charles Keepax wrote:
> This patch provides a new regmap API call that allows a patch to be
> applied but not registered with the regmap core. Common code between
> this and the existing regmap_register_patch function is factored out to
> reduce
On 22/02/14 00:48, Mark Rutland wrote:
[Adding Tony Prisk to Cc]
On Fri, Feb 21, 2014 at 06:31:30AM +, Alistair Popple wrote:
Currently the ppc-of driver uses the compatibility string
"usb-ehci". This means platforms that use device-tree and implement an
EHCI compatible interface have to
On Fri, Feb 21, 2014 at 11:23:39AM -0600, Jay Cornwall wrote:
> Hi,
>
> I'm tracking a possible memory leak in iommu/amd. The driver uses this logic
> to fault a page in response to a PRI from a device:
>
> npages = get_user_pages(fault->state->task, fault->state->mm,
>
Reduce text a bit by using static const.
Fix a symmetric typo and neaten a dev_info call
to 80 columns.
$ size drivers/usb/misc/sisusbvga/sisusb.o*
textdata bss dec hex filename
3001648419180 44037ac05 drivers/usb/misc/sisusbvga/sisusb.o.new
300874841
On Sat, Feb 22, 2014 at 12:33 AM, Kumar Gala wrote:
>
> On Feb 11, 2014, at 2:22 PM, Kumar Gala wrote:
>
>> We've split Qualcomm MSM support into legacy and multiplatform. The gpio
>> msm-v2 driver is only relevant on the multiplatform supported SoCs so
>> switch the Kconfig depends to
At Thu, 20 Feb 2014 15:51:55 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.13.5 release.
> There are 99 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.
>
On 02/22/2014 12:43 AM, Sasha Levin wrote:
> On 02/19/2014 11:32 PM, Michael wang wrote:
>> On 02/20/2014 02:08 AM, Sasha Levin wrote:
>>> >Hi all,
>>> >
>>> >While fuzzing with trinity inside a KVM tools guest, running latest
>>> >-next kernel, I see to hit the following hang quite often.
>> Fix
On Fri, Feb 21, 2014 at 5:02 AM, Zoltan Kiss wrote:
> Check this how current Xen scripts does routed networking:
>
> http://wiki.xen.org/wiki/Xen_Networking#Associating_routes_with_virtual_devices
>
> Note, there are no bridges involved here! As the above page says, the
> backend has to have IP
On 02/21/2014 12:28 PM, Peter Zijlstra wrote:
On Mon, Feb 17, 2014 at 03:41:24PM -0500, Waiman Long wrote:
+ struct {
+ u8 lock; /* Lock bit */
+ u8 wait; /* Waiting bit */
+ u16 qcode; /* Queue code */
+ };
16 bit
On Fri, Feb 21, 2014 at 8:01 AM, Luis R. Rodriguez
wrote:
> On Fri, Feb 21, 2014 at 5:02 AM, Zoltan Kiss wrote:
>>> Agreed that's the best strategy and I'll work on sending patches to
>>> brctl to enable the root_block preference. This approach however also
>>
>> I don't think brctl should deal
On 02/21/2014 12:26 PM, Peter Zijlstra wrote:
On Fri, Feb 21, 2014 at 12:09:57PM -0500, Waiman Long wrote:
On 02/21/2014 12:08 PM, Waiman Long wrote:
On 02/21/2014 07:12 AM, Peter Zijlstra wrote:
Why is this x86 only code?
The code is making use of the fact that byte write is atomic which is
static const char* arrays create smaller text as each
function call does not have to populate the array.
Emit a warning when char *arrays aren't static const
and the array is not apparently global by being
declared in the first column.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 7
On 02/21/2014 06:51 PM, Kirill A. Shutemov wrote:
On Fri, Feb 21, 2014 at 05:46:36PM -0500, Sasha Levin wrote:
>Hi all,
>
>While fuzzing with trinity inside a KVM tools guest running latest -next
>kernel I've stumbled on the following (now with pretty line numbers!) spew:
>
>[ 746.125099]
On 21.02.2014 20:36, Juri Lelli wrote:
> On Fri, 21 Feb 2014 11:37:15 +0100
> Peter Zijlstra wrote:
>
>> On Thu, Feb 20, 2014 at 02:16:00AM +0400, Kirill Tkhai wrote:
>>> Since deadline tasks share rt bandwidth, we must care about
>>> bandwidth timer set. Otherwise rt_time may grow up to
Implement em28xx_ops: suspend/resume hooks. em28xx usb driver will
invoke em28xx_ops: suspend and resume hooks for all its extensions
from its suspend() and resume() interfaces.
Signed-off-by: Shuah Khan
---
drivers/media/usb/em28xx/em28xx-dvb.c | 57 +++
1 file
Implement em28xx_usb_driver suspend, resume, and reset_resume hooks.
These hooks will invoke em28xx core em28xx_suspend_extension() and
em28xx_resume_extension() to suspend and resume registered extensions.
Approach:
Add power management support to em28xx usb driver. This driver works in
Implement em28xx_ops: suspend/resume hooks. em28xx usb driver will
invoke em28xx_ops: suspend and resume hooks for all its extensions
from its suspend() and resume() interfaces.
Signed-off-by: Shuah Khan
---
drivers/media/usb/em28xx/em28xx-video.c | 28
1 file
Implement em28xx_ops: suspend/resume hooks. em28xx usb driver will
invoke em28xx_ops: suspend and resume hooks for all its extensions
from its suspend() and resume() interfaces.
Signed-off-by: Shuah Khan
---
drivers/media/usb/em28xx/em28xx-audio.c | 30 ++
1 file
Implement em28xx_ops: suspend/resume hooks. em28xx usb driver will
invoke em28xx_ops: suspend and resume hooks for all its extensions
from its suspend() and resume() interfaces.
Signed-off-by: Shuah Khan
---
drivers/media/usb/em28xx/em28xx-input.c | 35 +
1 file
em28xx usb driver will have to suspend and resume its extensions. Adding
suspend and resume to em28xx_ops gives extensions the ability to install
suspend and resume that can be invoked from em28xx_usb driver suspend()
and resume() interfaces.
Approach:
Add power management support to em28xx usb
Add power management support to em28xx usb driver. This driver works in
conjunction with extensions for each of the functions on the USB device
for video/audio/dvb/remote functionality that is present on media USB
devices it supports. During suspend and resume each of these extensions
will have to
On Sat, 2014-02-22 at 00:44 +, Ben Hutchings wrote:
> On Tue, 2014-02-18 at 11:11 +0100, Alexander Gordeev wrote:
> > As result of deprecation of MSI-X/MSI enablement functions
> > pci_enable_msix() and pci_enable_msi_block() all drivers
> > using these two interfaces need to be updated to use
On Fri, Feb 21, 2014 at 3:09 AM, Will Deacon wrote:
> On Fri, Feb 21, 2014 at 01:02:47AM +, Olof Johansson wrote:
>> On Thu, Feb 20, 2014 at 4:58 PM, Stephen Rothwell
>> wrote:
>> > Today's linux-next merge of the arm-soc tree got a conflict in
>> > arch/arm/boot/dts/qcom-msm8960-cdp.dts
On Tue, 2014-02-18 at 11:11 +0100, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
>
On Tue, 2014-02-18 at 11:07 +0100, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
>
/sys/devices/system/cpu/cpu*/smt-snooze-delay was converted into a NOP
in commit 3fa8cad82b94d0bed002571bd246f2299ffc876b, and now does
nothing. Add a pr_warn() to convince any users that they should stop
using it.
The commit message from the removing commit notes that this
functionality should
On Thu, 20 Feb 2014 11:22:04 +0400 Vladimir Davydov
wrote:
> This patch cleanups the memcg cache creation path as follows:
> - Move memcg cache name creation to a separate function to be called
>from kmem_cache_create_memcg(). This allows us to get rid of the
>mutex protecting the
From: Rafael J. Wysocki
Modify the SATA subsystem to add hotplug contexts to ACPI companions
of SATA devices and ports instead of registering special ACPI dock
operations using register_hotplug_dock_device().
That change will allow the entire code handling those special ACPI
dock operations to
On 21.02.2014 [14:07:35 -0800], Andrew Morton wrote:
> On Thu, 20 Feb 2014 10:51:44 +0100 Michal Hocko wrote:
>
> > We had a report about strange OOM killer strikes on a PPC machine
> > although there was a lot of swap free and a tons of anonymous memory
> > which could be swapped out. In the
I got this while perf_fuzzing, same core2 machine, this
is 3.14-rc3 *with* Peter's patch to fix the other WARNING applied.
I can try to isolate a test case, though not until after the weekend.
Vince
if (__test_and_clear_bit(hwc->idx, cpuc->active_mask)) {
On Mon, 17 Feb 2014 21:47:36 -0800 Davidlohr Bueso wrote:
> > How is that difficult? hugepages= is the "noun", hugepagesz= is the
> > "adjective". hugepages=100 hugepagesz=1G hugepages=4 makes perfect sense
> > to me, and I actually don't allocate hugepages on the command line, nor
> > have
d in:
> [ 746.128358] CPU: 2 PID: 19816 Comm: trinity-c127 Tainted: GW
> 3.14.0-rc3-next-20140221-sasha-8-g0e660cf-dirty #114
> [ 746.130196] task: 8803a7cc3000 ti: 8803a7f1c000 task.ti:
> 8803a7f1c000
> [ 746.130317] RIP: 0010:[] []
> zap_huge_pmd+0x17a
21.02.2014, 20:52, "Juri Lelli" :
> On Fri, 21 Feb 2014 17:36:41 +0100
> Juri Lelli wrote:
>
>> On Fri, 21 Feb 2014 11:37:15 +0100
>> Peter Zijlstra wrote:
>>> On Thu, Feb 20, 2014 at 02:16:00AM +0400, Kirill Tkhai wrote:
Since deadline tasks share rt bandwidth, we must care about
On Wed, Feb 19 2014, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
> interfaces.
On 02/21/2014 06:18 PM, Tejun Heo wrote:
On Fri, Feb 21, 2014 at 06:01:29PM -0500, Peter Hurley wrote:
smp_mb__after_unlock_lock() is only for ordering memory operations
between two spin-locked sections on either the same lock or by
the same task/cpu. Like:
i = 1
spin_unlock(lock1)
On 02/20/2014 04:51 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.13.5 release.
There are 99 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 Wed, Feb 19 2014, Philipp Reisner wrote:
> From: Andreas Gruenbacher
>
> Right now every resource has exactly one connection. But we are preparing
> for dynamic connections. I.e. in the future thre can be resources without
> connections.
>
> However smatch points this out as 'variable
On 02/20/2014 04:51 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.13 release.
There are 82 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 02/20/2014 04:51 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.82 release.
There are 25 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 02/20/2014 04:50 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.32 release.
There are 66 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 Fri, Feb 21, 2014 at 04:49:29PM +0100, Alexander Gordeev wrote:
> Signed-off-by: Alexander Gordeev
> Cc: Jon Mason
> Cc: linux-...@vger.kernel.org
Good catch. Applied.
> ---
> drivers/ntb/ntb_hw.c |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git
On 14/02/19, Richard Guy Briggs wrote:
> On 14/02/18, Richard Guy Briggs wrote:
> > On 14/02/18, Steve Grubb wrote:
> > > On Tuesday, February 18, 2014 03:50:44 PM Richard Guy Briggs wrote:
> > > > > missing '=' but this isn't what audit_get_context() does... it's
> > > > > crappy naming...
On Thu, 20 Feb 2014, Dan Williams wrote:
> On Thu, Feb 20, 2014 at 2:30 AM, Thomas Gleixner wrote:
> > That's 18 of 30 usage sites. Impressive
> >
> > We need to poke the relevant maintainers to get this solved.
> >
>
> Maybe also rename tasklet_disable() to tasklet_pause() to make it
>
On Fri, Feb 21 2014, Gu Zheng wrote:
> Most code of function bio_integrity_verify and bio_integrity_generate
> is the same, so introduce a help function bio_integrity_generate_verify()
> to remove the duplicate code.
Thanks, queued up for the next release.
--
Jens Axboe
--
To unsubscribe from
On Fri, Feb 21, 2014 at 2:54 PM, Thomas Gleixner wrote:
> On Fri, 21 Feb 2014, John Stultz wrote:
>> I fully agree with this, but since the existing interface
>> only accepts #7 style negative timespecs, we have to continue
>> to support that style for this interface.
>>
>> Another possible view
dev_ output does not use printk() but directly
calls vprintk_emit().
kdb only traps direct printk() calls.
So, kdb hasn't emitted any dev_ or netdev_
output since structured logging and vprintk_emit() was
introduced a couple of years ago.
It seems no one has cared.
Maybe the kdb handling
On Friday, February 21, 2014 06:24:24 PM Catalin Marinas wrote:
> Hi Rafael,
>
> On Wed, Feb 19, 2014 at 01:50:22AM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, February 19, 2014 12:23:55 AM Hanjun Guo wrote:
> > > _PDC related stuff in processor_core.c is little bit X86/IA64 dependent,
> >
Hi,
On Thu, 2014-02-20 at 15:44 -0500, Tejun Heo wrote:
> ps3_vuart wasn't overriding the work item with multiple work functions
> but was using NULL for INIT_WORK() and then single PREPARE_WORK() to
> set the work function. We can simply invoke INIT_WORK() with the work
> function and remove
On Thu, Feb 20, 2014 at 11:43 PM, Jiang Liu wrote:
>
>
> On 2014/1/3 8:05, Yinghai Lu wrote:
>> iommu irq's irq_desc should be on local node ram.
>>
>> Fix the return value checking problem.
>> create_irq() will return -1 when fail to allocate.
>> create_irq_nr() will return 0 when fail to
On Fri, Feb 21, 2014 at 06:01:29PM -0500, Peter Hurley wrote:
> smp_mb__after_unlock_lock() is only for ordering memory operations
> between two spin-locked sections on either the same lock or by
> the same task/cpu. Like:
>
>i = 1
>spin_unlock(lock1)
>spin_lock(lock2)
>
* Mugunthan V N [140216 23:56]:
> From: Santosh Shilimkar
>
> for non SMP build, NR_CPUS is 1 and hence the code complains with below
> warnings.
>
> arch/arm/mach-omap2/cpuidle44xx.c:207:8: warning: array subscript is above
> array bounds [-Warray-bounds]
>
On 02/21/2014 11:01 AM, Greg Kroah-Hartman wrote:
On Thu, Feb 20, 2014 at 09:09:48PM -0800, Guenter Roeck wrote:
On 02/20/2014 03:50 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.32 release.
There are 66 patches in this series, all will be posted as a
On Fri, Feb 21, 2014 at 08:07:21AM -0800, Roland Dreier wrote:
> From: Roland Dreier
>
> In the code for Xeon devices in back-to-back mode with xeon_errata_workaround
> disabled, the downstream device puts the wrong value in SNB_B2B_XLAT_OFFSETL
> (SNB_MBAR01_DSD_ADDR vs. SNB_MBAR01_USD_ADDR).
>
* Sebastian Reichel [140217 13:33]:
> Without enabling the workaround for ARM errata 430973 thumb
> compiled userland crashes randomly on the Nokia N900.
>
> Signed-off-by: Sebastian Reichel
> Reviewed-by: Pavel Machek
> ---
> Hi,
>
> This is PATCHv2 for the thumb errata workaround for N900
On 02/21/2014 01:27 PM, Andrew Morton wrote:
> On Fri, 21 Feb 2014 13:18:26 -0800 "H. Peter Anvin" wrote:
>
>> On 02/21/2014 01:15 PM, Andrew Morton wrote:
I've been slapped down for adding more config options in the past, and
I think it's unlikely that people using
On 02/21/2014 11:57 AM, Tejun Heo wrote:
Yo,
On Fri, Feb 21, 2014 at 11:53:46AM -0500, Peter Hurley wrote:
Ok, I can do that. But AFAIK it'll have to be an smp_rmb(); there is
no mb__after unlock.
We do have smp_mb__after_unlock_lock().
[ After thinking about it some, I don't think
Hi Linus,
This is the first pull request I've had to do for you, so I'm still
sorting things out. The reason I'm sending this and not Ben should
be obvious from the first commit below - SGI has stepped down from
the XFS maintainership role. As such, I'd like to take another
opportunity to thank
> But, like I said, I'm not sure we'd ever be able to totally remove it
> because of backwards compatibility, but the point is that nobody would
> have to use it anymore as a hack for 1GB.
Again it's a perfectly fine and widely used interface. Any talk of removing
it is wrong.
-Andi
--
To
On Fri, 21 Feb 2014, John Stultz wrote:
> I fully agree with this, but since the existing interface
> only accepts #7 style negative timespecs, we have to continue
> to support that style for this interface.
>
> Another possible view is that the rule that the tv_nsec
> value always be [0,1e9).
Hi,
On Fri, Feb 21, 2014 at 11:01 AM, Kay Sievers wrote:
> Why did the tty0 change to tty1 now? That doesn't look like a "driver
> name" vs. "device name" issue?
I don't know if it's intentional, but the patch does:
+ int index = cs[i]->index;
...
+ driver =
Signed-off-by: Marcin Lulek
---
drivers/input/joystick/xpad.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
index 603fe0d..b94668f 100644
--- a/drivers/input/joystick/xpad.c
+++ b/drivers/input/joystick/xpad.c
@@ -124,6 +124,7
On Fri, Feb 21, 2014 at 02:46:17PM -0800, Ira W. Snyder wrote:
> From: "Ira W. Snyder"
>
> Commit 7808edcd306f22aeb23775d34e70b7fa2f58b852 "Basic support for
> Moschip 9900 family I/O chips" broke support for the 98xx boards. This
> is due to a missing check for the 99xx family inside the newly
Quoting Joe Perches (j...@perches.com):
> Prefix logging output with "capability: " via pr_fmt.
> Convert printks to pr_.
> Use pr__once instead of guard flags.
> Coalesce formats.
>
> Signed-off-by: Joe Perches
Thanks.
Acked-by: Serge E. Hallyn
> ---
> kernel/capability.c | 29
Andrew Morton wrote:
> > - * allocate an AFS inode struct from our slab cache
> > + * allocate an AFS inode struct
> > */
> > static struct inode *afs_alloc_inode(struct super_block *sb)
> > {
>
> err, this was obviously a product of senility.
My comment, or your comment on my comment?
On Thu, Feb 13, 2014 at 01:35:38PM +0100, Linus Walleij wrote:
> Hi ARM SoC folks,
>
> this is a set of patches I have sent for review and failed to get
> ACKs from the proper subsystem maintainers after repeated
> pings. However I now need to have this rotated in linux-next
> as a base for
] Dumping ftrace buffer:
[ 746.127484](ftrace buffer empty)
[ 746.127781] Modules linked in:
[ 746.128358] CPU: 2 PID: 19816 Comm: trinity-c127 Tainted: GW
3.14.0-rc3-next-20140221-sasha-8-g0e660cf-dirty #114
[ 746.130196] task: 8803a7cc3000 ti: 8803a7f1c000 task.ti
Trivially reduces text size too.
$ size drivers/net/wireless/ath/ath9k/debug.o*
textdata bss dec hex filename
3443625285128 42092a46c
drivers/net/wireless/ath/ath9k/debug.o.new
3446425285128 42120a488
drivers/net/wireless/ath/ath9k/debug.o.old
From: "Ira W. Snyder"
Commit 7808edcd306f22aeb23775d34e70b7fa2f58b852 "Basic support for
Moschip 9900 family I/O chips" broke support for the 98xx boards. This
is due to a missing check for the 99xx family inside the newly added
pci_netmos_9900_setup() function, which is now used for all boards
On Fri, 21 Feb 2014, Andi Kleen wrote:
> > > 2) it improves the kernel command line interface from incomplete
> > > (lacking the ability to specify node<->page correlation), to
> > > a complete interface.
> > >
> >
> > If GB hugepages can be allocated dynamically, I really think we should be
1 - 100 of 1526 matches
Mail list logo
