Re: [PATCH v3 3/3] hugetlbfs: add swap entry check in follow_hugetlb_page()

On 04/03/2013 02:35 PM, Naoya Horiguchi wrote: With applying the previous patch "hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)" to reenable hugepage coredump, if a memory error happens on a hugepage and the affected processes try to access the error hugepage, we hit

Re: [PATCH 2/3] resource: Add release_mem_region_adjustable()

On Wed, 2013-04-03 at 10:26 +0900, Yasuaki Ishimatsu wrote: > 2013/04/03 1:17, Toshi Kani wrote: > > Added release_mem_region_adjustable(), which releases a requested > > region from a currently busy memory resource. This interface > > adjusts the matched memory resource accordingly if the

Re: [PATCH 0/3] mtip32xx: recovery improvement and fix for a crash

On Wed, Apr 03 2013, Asai Thambi S P wrote: > Hi Jens, > > This patchset includes the following. It was generated against your > for-3.9/drivers > > * improved recovery for command timeout > * fix for a crash during rmmod > * add new debugfs entry 'device_status' > > > Asai Thambi S P (3): >

Re: [PATCH] block: avoid using uninitialized value in from queue_var_store

On Wed, Apr 03 2013, Arnd Bergmann wrote: > As found by gcc-4.8, the QUEUE_SYSFS_BIT_FNS macro creates functions > that use a value generated by queue_var_store independent of whether > that value was set or not. > > block/blk-sysfs.c: In function 'queue_store_nonrot': >

[PATCH v2] pinctrl/pinconfig: add debug interface

From: Laurent Meunier This update adds a debugfs interface to modify a pin configuration for a given state in the pinctrl map. This allows to modify the configuration for a non-active state, typically sleep state. This configuration is not applied right away, but only when the state will be

Re: [PATCHSET v2] workqueue, writeback: better worker information in task dumps

On Wed 03-04-13 12:24:29, Tejun Heo wrote: > Hello, > > Andrew, this one depends on the debug info unification patch and > should be routed through -mm too. The writeback folks seem to be okay > with the proposed changes although nobody explicitly acked it yet > (please do so). Please route

Re: [PATCH 0/7] USB: PHY: Tegra: registering TEGRA USB PHY as platform driver

On 03/19/2013 01:51 PM, Stephen Warren wrote: > On 03/18/2013 06:29 AM, Venu Byravarasu wrote: >> As part of this series, apart from patch containing changes to register TEGRA >> USB PHY driver as platform driver, prepared below patches: >> 1. Re-arranging & adding new DT properties. >> 2. Getting

Re: [PATCH 2/7] ARM: tegra: update device trees for USB binding rework

On 03/19/2013 01:53 PM, Stephen Warren wrote: > On 03/18/2013 06:29 AM, Venu Byravarasu wrote: >> This patch updates all Tegra board files so that they contain all the >> properties required by the updated USB DT binding. Note that this patch >> only adds the new properties and does not yet remove

[PATCH] Do not force shutdown/reboot to boot cpu.

We noticed that recently, reboot of a 1024 cpu machine takes approx 16 minutes of just stopping the cpus. The slowdown was tracked to commit f96972f which went into v3.7 and then to the stable trees. x86 does not need to be running the boot cpu to pull reset and I don't think it is really needed

Re: [PATCH v2 6/7] usb: phy: tegra: Add error handling & clean up.

On 04/03/2013 02:41 AM, Venu Byravarasu wrote: > Check return values from all GPIO APIs and handle errors accordingly. > Remove clk_disable_unprepare which is no more needed. checkpatch fails: > WARNING: line over 80 characters > #27: FILE: drivers/usb/phy/phy-tegra-usb.c:547: > +

Re: [PATCH 6/7] usb: phy: tegra: Add error handling & clean up.

On 03/19/2013 02:10 PM, Stephen Warren wrote: > On 03/18/2013 06:29 AM, Venu Byravarasu wrote: >> Check return values from all GPIO APIs and handle errors accordingly. > >> Remove clk_disable_unprepare which is no more needed. > > The call to clk_disable_unprepare is incorrect in the current

Re: [PATCH v2 2/7] ARM: tegra: update device trees for USB binding rework

On 04/03/2013 02:41 AM, Venu Byravarasu wrote: > This patch updates all Tegra board files so that they contain all the > properties required by the updated USB DT binding. Note that this patch > only adds the new properties and does not yet remove the old properties, > in order to maintain

Re: [PATCH] SUNRPC/cache: add module_put() on error path in cache_open()

Thanks, applying.--b. On Sat, Mar 23, 2013 at 12:36:44AM +0400, Alexey Khoroshilov wrote: > If kmalloc() fails in cache_open(), module cd->owner left locked. > The patch adds module_put(cd->owner) on this path. > > Found by Linux Driver Verification project (linuxtesting.org). > >

[PATCH] pinctrl/pinconfig: add debug interface

From: Laurent Meunier This update adds a debugfs interface to modify a pin configuration for a given state in the pinctrl map. This allows to modify the configuration for a non-active state, typically sleep state. This configuration is not applied right away, but only when the state will be

[PATCH 1/3] kthread: implement probe_kthread_data()

Implement probe_kthread_data() which returns kthread_data if accessible. The function is equivalent to kthread_data() except that the specified @task may not be a kthread or its vfork_done is already cleared rendering struct kthread inaccessible. In the former case, probe_kthread_data() may

[PATCH v3] netdev/phy: Implement ieee802.3 clause 45 in mdio-octeon.c

From: David Daney The Octeon SMI/MDIO interfaces can do clause 45 communications, so implement this in the driver. Also fix some comment formatting to make it consistent and to comply with the netdev style. Signed-off-by: David Daney --- v3: Remove now bogus comment noted by Ben Huchings

Re: [PATCH v3 2/3] fix hugetlb memory check in vma_dump_size()

On 04/03/2013 02:35 PM, Naoya Horiguchi wrote: Documentation/filesystems/proc.txt says about coredump_filter bitmask, Note bit 0-4 doesn't effect any hugetlb memory. hugetlb memory are only effected by bit 5-6. However current code can go into the subsequent flag checks of bit 0-4 for

[PATCH 2/3] workqueue: include workqueue info when printing debug dump of a worker task

One of the problems that arise when converting dedicated custom threadpool to workqueue is that the shared worker pool used by workqueue anonimizes each worker making it more difficult to identify what the worker was doing on which target from the output of sysrq-t or debug dump from oops, BUG()

[PATCH 3/3] writeback: set worker desc to identify writeback workers in task dumps

Writeback has been recently converted to use workqueue instead of its private thread pool implementation. One negative side effect of this conversion is that there's no easy to tell which backing device a writeback work item was working on at the time of task dump, be it sysrq-t, BUG, WARN or

[PATCHSET v2] workqueue, writeback: better worker information in task dumps

Hello, Andrew, this one depends on the debug info unification patch and should be routed through -mm too. The writeback folks seem to be okay with the proposed changes although nobody explicitly acked it yet (please do so). Please route these together with the previous set through -mm. Thanks.

Re: [PATCH v2 4/6] nfsd: convert nfs4_alloc_stid to use idr_alloc_cyclic

Err, and ack v2.--b. On Wed, Mar 27, 2013 at 03:29:36PM -0400, Jeff Layton wrote: > Signed-off-by: Jeff Layton > Cc: "J. Bruce Fields" > Cc: linux-...@vger.kernel.org > --- > fs/nfsd/nfs4state.c | 7 +-- > 1 file changed, 1 insertion(+), 6 deletions(-) > > diff --git a/fs/nfsd/nfs4state.c

Re: [PATCH v1 4/6] nfsd: convert nfs4_alloc_stid to use idr_alloc_cyclic

ACK.--b. On Wed, Mar 27, 2013 at 09:18:06AM -0400, Jeff Layton wrote: > Signed-off-by: Jeff Layton > Cc: "J. Bruce Fields" > Cc: linux-...@vger.kernel.org > --- > fs/nfsd/nfs4state.c | 9 ++--- > 1 file changed, 2 insertions(+), 7 deletions(-) > > diff --git a/fs/nfsd/nfs4state.c

Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

On 04/03/2013 02:35 PM, Naoya Horiguchi wrote: Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 "mm: kill vma flag VM_RESERVED and mm->reserved_vm counter". This looks to me

Re: [v3.8 Regression] Merge tag 'v3.7-rc2' into drm-intel-next-queued

On 04/03/2013 03:16 PM, Daniel Vetter wrote: On Wed, Apr 3, 2013 at 9:08 PM, Joseph Salisbury > wrote: Hi Daniel, A bug was opened against the Ubuntu kernel[0]. After a kernel bisect, it was found the following was the first bad commit:

[PATCH] clk: Properly handle notifier return values

Notifiers may return NOTIFY_(OK|DONE|STOP|BAD). The CCF uses an inconsistent mix of checking against NOTIFY_STOP or NOTIFY_BAD. This inconsistency leaves errors undetected in some cases: clk_set_parent() calls __clk_speculate_rates(), which stops when it hits a NOTIFIER_BAD (STOP is ignored), and

[PATCH 4/7] dmi: morph dmi_dump_ids() into dmi_format_ids() which formats into a buffer

We're gonna use DMI identification for other purposes too. Morph dmi_dump_ids() which is used to print DMI identification as a debug message during boot into dmi_format_ids() which formats the same information sans the leading "DMI:" tag into a string buffer. dmi_present() is updated to format

Re: [PATCH v2 2/7] ARM: tegra: update device trees for USB binding rework

On 04/03/2013 02:41 AM, Venu Byravarasu wrote: > This patch updates all Tegra board files so that they contain all the > properties required by the updated USB DT binding. Note that this patch > only adds the new properties and does not yet remove the old properties, > in order to maintain

[PATCH 6/7] dump_stack: unify debug information printed by show_regs()

show_regs() is inherently arch-dependent but it does make sense to print generic debug information and some archs already do albeit in slightly different forms. This patch introduces a generic function to print debug information from show_regs() so that different archs print out the same

[PATCH 7/7] arc, print-fatal-signals: reduce duplicated information

From: Vineet Gupta After the recent generic debug info on dump_stack() and friends, arc is printing duplicate information on debug dumps. [ARCLinux]$ ./crash crash/50: potentially unexpected fatal signal 11. <-- [1] /sbin/crash, TGID 50 <-- [2] Pid:

[PATCH 5/7] dump_stack: implement arch-specific hardware description in task dumps

x86 and ia64 can acquire extra hardware identification information from DMI and print it along with task dumps; however, the usage isn't consistent. * x86 show_regs() collects vendor, product and board strings and print them out with PID, comm and utsname. Some of the information is printed

[PATCH 3/7] dump_stack: consolidate dump_stack() implementations and unify their behaviors

Both dump_stack() and show_stack() are currently implemented by each architecture. show_stack(NULL, NULL) dumps the backtrace for the current task as does dump_stack(). On some archs, dump_stack() prints extra information - pid, utsname and so on - in addition to the backtrace while the two are

[PATCH 2/7] sparc32: make show_stack() acquire %fp if @_ksp is not specified

show_stack(current or NULL, NULL) is used by arch-independent code to dump backtrace of the current task; however, sparc32 show_stack() doesn't implement it and wouldn't print any backtrace when NULL @_ksp is specfied. Make show_stack() acquire and use %fp if @tsk is NULL or current and @_ksp is

[PATCHSET v2] arch: unify task dump debug info

Hello, Andrew, I think it's about ready and nobody seems to be against the proposed changes. Can you please take these into -mm? This v2 of this patchset. Changes from the last posting[1] are, * CPU is now printed for both dump_stack() and show_regs() which s390 folks tell me should be

[PATCH 1/7] x86: don't show trace beyond show_stack(NULL, NULL)

show_stack(current or NULL, NULL) is used to print the backtrace of the current task. As trace beyond the function itself isn't of much interest to anyone, don't show it by determining sp and bp in show_stack()'s frame and passing them to show_stack_log_lvl(). This brings show_stack(NULL,

Re: [PATCH] netdev/phy: Implement ieee802.3 clause 45 in mdio-octeon.c

On 04/03/2013 12:08 PM, Ben Hutchings wrote: On Wed, 2013-04-03 at 11:16 -0700, David Daney wrote: From: David Daney The Octeon SMI/MDIO interfaces can do clause 45 communications, so implement this in the driver. Signed-off-by: David Daney --- drivers/net/phy/mdio-octeon.c | 89

Re: [ 105/124] af_unix: dont send SCM_CREDENTIAL when dest socket is NULL

Hi On Wednesday 03 April 2013, Greg Kroah-Hartman wrote: > On Wed, Apr 03, 2013 at 05:10:40PM +0200, Sven Joachim wrote: > > On 2013-04-03 16:00 +0200, Eric Dumazet wrote: > > > On Wed, 2013-04-03 at 13:41 +0200, Sven Joachim wrote: > > >> On 2013-04-03 00:11 +0200, Greg Kroah-Hartman wrote: > >

Re: [PATCH v2] ARM: at91: add Acme Systems Aria G25 board

On 13-04-02 02:48 PM, Olof Johansson wrote: Hi, I just saw this since it came in through a pull request On Tue, Mar 26, 2013 at 4:39 AM, Nicolas Ferre wrote: From: Douglas Gilbert Signed-off-by: Douglas Gilbert Signed-off-by: Nicolas Ferre --- arch/arm/boot/dts/ariag25.dts | 175

Re: [PATCH] netdev/phy: Implement ieee802.3 clause 45 in mdio-octeon.c

On Wed, 2013-04-03 at 11:16 -0700, David Daney wrote: > From: David Daney > > The Octeon SMI/MDIO interfaces can do clause 45 communications, so > implement this in the driver. > > Signed-off-by: David Daney > --- > drivers/net/phy/mdio-octeon.c | 89 >

[v3.8 Regression] Merge tag 'v3.7-rc2' into drm-intel-next-queued

Hi Daniel, A bug was opened against the Ubuntu kernel[0]. After a kernel bisect, it was found the following was the first bad commit: commit c2fb7916927e989ea424e61ce5fe617e54878827 Merge: 29de6ce 6f0c058 Author: Daniel Vetter Date: Mon Oct 22 14:34:51 2012 +0200 Merge tag

Re: [PATCH v2 1/7] ARM: tegra: finalize USB EHCI and PHY bindings

On 04/03/2013 02:41 AM, Venu Byravarasu wrote: > The existing Tegra USB bindings have a few issues: ... > This patch fixes the binding definition to resolve these issues. > diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt >

[PATCH] pinctrl/pinconf: partial revert of pin config debugfs

From: Linus Walleij I accidentally left this patch: commit 6f9e41f4e673bf9ae6a5c0831b1524a91ea1c440 "pinctrl/pinconfig: add debug interface" in the tree though the patch was not yet finished. Revert it partially (we need the infrastructural changes). Cc: Laurent Meunier Signed-off-by: Linus

Re: [ 105/124] af_unix: dont send SCM_CREDENTIAL when dest socket is NULL

On Wed, Apr 3, 2013 at 11:43 AM, Eric Dumazet wrote: > On Wed, 2013-04-03 at 10:58 -0700, Andy Lutomirski wrote: > >> >> This sounds suspiciously like an SCM_CREDENTIALS bug triggered by a >> race. There's a fix (that needs both a new version from me and a review >> by someone) here: >> >>

Re: [PATCH v2] nfsd: fix bug on nfs4 stateid deallocation

On Wed, Apr 03, 2013 at 06:58:43PM +0800, Yanchuan Nian wrote: > On Mon, Apr 01, 2013 at 09:50:44PM -0400, J. Bruce Fields wrote: > > On Wed, Mar 13, 2013 at 11:04:54PM +0800, Yanchuan Nian wrote: > > > 2013/3/11 J. Bruce Fields > > > > > > > On Mon, Mar 11, 2013 at 08:46:14AM +0800,

Re: [PATCHv5 2/7] of: Remove duplicated code for validating property and value

On 04/03/2013 01:24 AM, Tony Prisk wrote: > Several functions in of/base.c have the same code duplicated for > finding and validating a property and value. > > struct property *prop = of_find_property(np, propname, NULL); > if (!prop) > return -EINVAL; > if (!prop->value) > return

Re: [PATCH] NMI: fix NMI period is not correct when cpu frequency changes issue.

On Mon, Apr 01, 2013 at 03:47:42AM +, Pan, Zhenjie wrote: > Watchdog use performance monitor of cpu clock cycle to generate NMI to detect > hard lockup. > But when cpu's frequency changes, the event period will also change. > It's not as expected as the configuration. > For example, set the

Re: [ 105/124] af_unix: dont send SCM_CREDENTIAL when dest socket is NULL

On Wed, 2013-04-03 at 10:58 -0700, Andy Lutomirski wrote: > > This sounds suspiciously like an SCM_CREDENTIALS bug triggered by a > race. There's a fix (that needs both a new version from me and a review > by someone) here: > > http://www.spinics.net/lists/netdev/msg229948.html Hmm... this is

Re: systemtap broken by removal of register_timer_hook

On 04/03/2013 07:44 AM, Frank Ch. Eigler wrote: > Hi - > > On Wed, Apr 03, 2013 at 02:49:53PM +0200, Frederic Weisbecker wrote: > >> Sounds good, would you like to propose a version? We are also >> interested in a timer tick event tracepoint for dynticks debugging. > > How about this? > >

[PATCH v3 2/3] fix hugetlb memory check in vma_dump_size()

Documentation/filesystems/proc.txt says about coredump_filter bitmask, Note bit 0-4 doesn't effect any hugetlb memory. hugetlb memory are only effected by bit 5-6. However current code can go into the subsequent flag checks of bit 0-4 for vma(VM_HUGETLB). So this patch inserts 'return' and

[PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 "mm: kill vma flag VM_RESERVED and mm->reserved_vm counter". This looks to me a serious regression, so let's fix it. ChangeLog

[PATCH v3 0/3] fix hugepage coredump

Hi, Here is 3nd version of hugepage coredump fix. I added some minor changes based on Hatayama-san's and Michal's comments. Thank you very much. Naoya Horiguchi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More

[PATCH v3 3/3] hugetlbfs: add swap entry check in follow_hugetlb_page()

With applying the previous patch "hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)" to reenable hugepage coredump, if a memory error happens on a hugepage and the affected processes try to access the error hugepage, we hit VM_BUG_ON(atomic_read(>_count) <= 0) in get_page(). The

[PATCH v2] netdev/phy: Implement ieee802.3 clause 45 in mdio-octeon.c

From: David Daney The Octeon SMI/MDIO interfaces can do clause 45 communications, so implement this in the driver. Also fix some comment formatting to make it consistent and to comply with the netdev style. Signed-off-by: David Daney --- No code changes from v1, just fixed comment formatting

Re: [PATCH 0/16] extcon: arizona: Updates for v3.10

On Tue, Apr 02, 2013 at 12:31:57PM +0100, Mark Brown wrote: > The following changes since commit df8c3dbee9e6f19ddb0ae8e05cdf76eb2d3b7f00: > > extcon: arizona: Fix interaction between headphone outputs and > identification (2013-03-26 15:45:26 +) > > are available in the git repository

pull request: wireless 2013-04-03

Dave, Here are some more fixes intended for the 3.9 stream... Regarding the mac80211 bits, Johannes says: "I had changed the idle handling to simplify it, but broken the sequencing of commands, at least for ath9k-htc, one patch restores the sequence. The other patch fixes a crash Jouni found

Re: [PATCH v9 00/14] Tegra114 clockframework

On 04/03/2013 11:52 AM, Stephen Warren wrote: > On 04/03/2013 08:40 AM, Peter De Schrijver wrote: >> This is the nineth version of the Tegra114 clockframework. It is based on the >> next-20130320-fixed branch of >> git://nv-tegra.nvidia.com/user/swarren/linux-2.6.git, ... [it depends on] >>

Re: [PATCH] nfsd4: Fix NULL dereference in legacy_recdir_name_error()

On Wed, Apr 03, 2013 at 06:27:26PM +0200, Takashi Iwai wrote: > The recent rewrite of NFSv4 recovery client tracking options per net > (commit 9a9c6478) introduced Oops when it faces an error for recdir > generation. Thanks. Looks like that could hit a lot of people actually, so I'll pass that

[GIT PULL] ext4 updates for 3.9-rc6

The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9: Linux 3.9-rc5 (2013-03-31 15:12:43 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable for you to fetch changes up to

Re: linux-next: build failure after merge of the final tree (nfsd tree related)

On Wed, 3 Apr 2013 14:05:19 -0400 "J. Bruce Fields" wrote: > On Wed, Apr 03, 2013 at 07:38:57AM -0400, Jeff Layton wrote: > > On Wed, 3 Apr 2013 07:33:01 -0400 > > "J. Bruce Fields" wrote: > > > > > On Wed, Apr 03, 2013 at 07:10:54AM -0400, Jeff Layton wrote: > > > > On Wed, 3 Apr 2013

[PATCH] netdev/phy: Implement ieee802.3 clause 45 in mdio-octeon.c

From: David Daney The Octeon SMI/MDIO interfaces can do clause 45 communications, so implement this in the driver. Signed-off-by: David Daney --- drivers/net/phy/mdio-octeon.c | 89 +-- 1 file changed, 86 insertions(+), 3 deletions(-) diff --git

Re: [PATCH v2 2/2] PM / devfreq: tie suspend/resume to runtime-pm

Rajagopal Venkat writes: > Devfreq core suspend/resume of a device is explicitly handled > by devfreq driver through devfreq_suspend_device() and > devfreq_resume_device() apis typically called from runtime > suspend/resume callbacks. This patch aims to take away this > from devfreq drivers and

Re: [PATCH v3 01/11] usb: phy: Add APIs for runtime power management

On Wed, 3 Apr 2013, Felipe Balbi wrote: > > Lets suppose DWC3 enables runtime_pm on USB 2 type phy, > > it will try to go into suspend state and thereby call runtime_suspend(), if > > any. > > And PHY will come to active state only when its consumer wakes it up, > > and this consumer is

Re: [PATCH v9 12/14] clk: tegra: devicetree match for nvidia,tegra114-car

On 04/03/2013 08:40 AM, Peter De Schrijver wrote: > Signed-off-by: Peter De Schrijver I see this patch does depend on my "clk: tegra: defer application of init table", although my patch was based on top of this series so needs to be adjusted to remove the Tegra114 portions so it can be applied

Re: [PATCH 1/5 v2] USB: regroup all depends on USB within an if USB block

On Wed, 3 Apr 2013, Felipe Balbi wrote: > On Wed, Apr 03, 2013 at 02:18:20PM +0200, Florian Fainelli wrote: > > Le 04/03/13 14:15, Felipe Balbi a �crit : > > >On Wed, Apr 03, 2013 at 02:11:13PM +0200, Florian Fainelli wrote: > > >>Le 04/02/13 20:06, Alan Stern a �crit : > > >>>On Tue, 2 Apr 2013,

Re: [PATCHv5 0/7] arm: vt8500: Add support for pinctrl/gpio module

On 04/04/13 02:40, Linus Walleij wrote: On Wed, Apr 3, 2013 at 8:24 AM, Tony Prisk wrote: v5 changes: Changed as requested by Rob Herring: Added of_find_property_value_of_size() to drivers/of/base.c to remove some code that was being duplicated. Changed as requested by Stephen Warren: Redid

Re: [PATCH] sysfs: fix compile warning in i386

On Wed, Apr 03, 2013 at 12:22:06PM +0800, Zhang Yanfei wrote: > This patch fixes compile warning in i386: > > drivers/base/cpu.c: In function 'show_crash_notes_size': > drivers/base/cpu.c:142:2: warning: format '%lu' expects argument of type > 'long unsigned int', but argument 3 has type

Re: [ 105/124] af_unix: dont send SCM_CREDENTIAL when dest socket is NULL

On 04/03/2013 08:35 AM, Eric Dumazet wrote: > On Wed, 2013-04-03 at 17:10 +0200, Sven Joachim wrote: >> On 2013-04-03 16:00 +0200, Eric Dumazet wrote: > >> >>> It might be a wrong sender (application bug or bad identity), and udevd >>> correctly discards the incoming message. >> >> How would I

[PATCH 1/3] mfd: arizona: Hold device in reset while ramping supplies

Acquire the /RESET GPIO before we enable regulators and hold the device in reset while the regulators power up in order to improve robustness during the initial power up. Also fix the error path so that the device is left in reset while we're at it. Signed-off-by: Mark Brown ---

[PATCH 3/3] mfd: wm5102: Don't wait for boot when boot sequencer is disabled

From: Charles Keepax As we are using a custom boot sequence we don't need to wait for the standard boot sequence in device init when the normal write sequence is disabled. Signed-off-by: Charles Keepax Signed-off-by: Mark Brown --- drivers/mfd/arizona-core.c | 22 ++ 1

[PATCH 2/3] mfd: arizona: Wait for internal clocks to startup after reset

From: Charles Keepax Signed-off-by: Mark Brown Signed-off-by: Charles Keepax --- drivers/mfd/arizona-core.c |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c index e4c8dc2..69e9796 100644 ---

Re: linux-next: build failure after merge of the final tree (nfsd tree related)

On Wed, Apr 03, 2013 at 07:38:57AM -0400, Jeff Layton wrote: > On Wed, 3 Apr 2013 07:33:01 -0400 > "J. Bruce Fields" wrote: > > > On Wed, Apr 03, 2013 at 07:10:54AM -0400, Jeff Layton wrote: > > > On Wed, 3 Apr 2013 17:42:19 +1100 > > > Stephen Rothwell wrote: > > > > > > > Hi all, > > > > >

Re: [PATCH] arm64: Fix task tracing

Hi Christopher, On Wed, Apr 03, 2013 at 07:01:01PM +0100, Christopher Covington wrote: > For accurate accounting call contextidr_thread_switch before a > task is scheduled, rather than after. > > Signed-off-by: Christopher Covington > --- > arch/arm64/kernel/process.c | 2 +- > 1 file changed,

Re: [PATCH 0/15] arizona updates for v3.10

On Mon, Apr 01, 2013 at 06:27:48PM +0100, Mark Brown wrote: > mfd: arizona: Updates for v3.10 > > This is really a few separate topics which I can split out if required: > > - WM5102 updates to improve robustness > - Improved support for interoperation with edge triggered interrupt >

Re: [PATCH] alpha: makefile: don't enforce small data model for kernel builds

Hi guys, On Mon, Mar 18, 2013 at 04:11:15AM +, Michael Cree wrote: > On 18/03/2013, at 10:48 AM, Will Deacon wrote: > > Due to all of the goodness being packed into today's kernels, the > > resulting image isn't as slim as it once was. > > > > In light of this, don't pass -msmall-data to the

Re: [PATCH 1/1] Introduce Intel RAPL cooling device driver

On Wed, 3 Apr 2013 09:30:52 -0700 Greg KH wrote: > On Tue, Apr 02, 2013 at 05:17:14PM -0700, Jacob Pan wrote: > > On Tue, 2 Apr 2013 16:48:05 -0700 > > Greg KH wrote: > > > > > On Tue, Apr 02, 2013 at 04:33:57PM -0700, Jacob Pan wrote: > > > > On Tue, 2 Apr 2013 16:00:42 -0700 > > > > Greg KH

Re: [PATCH 5/5 v11] iommu/fsl: Freescale PAMU driver and iommu implementation.

On Tue, 2013-04-02 at 18:18 +0200, Joerg Roedel wrote: > Cc'ing Alex Williamson > > Alex, can you please review the iommu-group part of this patch? Sure, it looks pretty reasonable. AIUI, all PCI devices are below some kind of host bridge that is either new and supports partitioning or old and

[PATCH] arm64: Fix task tracing

For accurate accounting call contextidr_thread_switch before a task is scheduled, rather than after. Signed-off-by: Christopher Covington --- arch/arm64/kernel/process.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c

Re: [PATCH v9 00/14] Tegra114 clockframework

On 04/03/2013 08:40 AM, Peter De Schrijver wrote: > This is the nineth version of the Tegra114 clockframework. It is based on the > next-20130320-fixed branch of > git://nv-tegra.nvidia.com/user/swarren/linux-2.6.git, That's not a particularly useful base; these patches won't be applied to

Re: [RFC] perf: need to expose sched_clock to correlate user samples with kernel samples

On 04/03/2013 07:22 AM, Stephane Eranian wrote: On Wed, Apr 3, 2013 at 4:14 PM, David Ahern wrote: On 4/3/13 8:00 AM, Stephane Eranian wrote: Why not have perf convert its perf_clock timestamps into monotonic or realtime when dumping events? So this is exactly what I've been wondering

[PATCH] pnp: extend char array field in pnp_fixup structure

The length of id field of pnp_fixup structure is 7: struct pnp_fixup { char id[7]; void (*quirk_function) (struct pnp_dev * dev); /* fixup function */ } In other hand the field is initialized with a constant cstring consisting of 7 characters in pnp_fixups

Re: [PATCH v9 10/14] ARM: tegra: Define Tegra114 CAR binding

On 04/03/2013 08:40 AM, Peter De Schrijver wrote: > The device tree binding models Tegra114 CAR (Clock And Reset) as a single > monolithic clock provider. > diff --git a/Documentation/devicetree/bindings/clock/nvidia,tegra114-car.txt >

Re: [RFC] perf: need to expose sched_clock to correlate user samples with kernel samples

On 04/03/2013 10:35 AM, Pawel Moll wrote: On Wed, 2013-04-03 at 18:29 +0100, John Stultz wrote: On 04/03/2013 10:19 AM, Pawel Moll wrote: On Tue, 2013-04-02 at 17:19 +0100, John Stultz wrote: But if we're going to have to do this via a clockid, I'm going to want it to be done via a dynamic

Re: [PATCH v1 0/9] uretprobes: Return uprobes implementation

On 04/03, Anton Arapov wrote: > > Anton Arapov (9): > uretprobes: Introduce uprobe_consumer->ret_handler() > uretprobes: Reserve the first slot in xol_vma for trampoline > uretprobes/x86: Hijack return address > uretprobes/ppc: Hijack return address > uretprobes: Return probe entry,

Re: [PATCH/Resend 2/2] arm: mach-omap2: prevent UART console idle on suspend while using "no_console_suspend"

Sourav Poddar writes: > Hi Kevin, > On Wednesday 20 March 2013 05:36 PM, Sourav Poddar wrote: >> Realised the list to whom the patch was send got dropped. Ccing >> them all.. >> On Wednesday 20 March 2013 05:18 PM, Sourav Poddar wrote: >>> Hi Kevin, >>> On Tuesday 19 March 2013 12:24 AM, Kevin

Re: [PATCH 3/4] x86, kdump: Retore crashkernel= to allocate low

On Wed, Apr 03, 2013 at 10:32:23AM -0700, Yinghai Lu wrote: > On Wed, Apr 3, 2013 at 10:12 AM, Yinghai Lu wrote: > > On Wed, Apr 3, 2013 at 6:18 AM, Vivek Goyal wrote: > > > >> - implement crashkernel_no_auto_low option to opt out of auto reserved > >> low memory > > > > No, that is ugly. >

Re: [PATCH 2/2] regulator: lp8788: Implement list_voltage for lp8788_ldo_voltage_fixed_ops

On Mon, Apr 01, 2013 at 11:28:48PM +0800, Axel Lin wrote: > For fixed voltage, we can just set min_uV and use > regulator_list_voltage_linear > for list_voltage callback. Regulator core will call list_voltage(rdev, 0) if > both get_voltage get_voltage_sel are not implemented. Thus we can also

Re: [PATCH 1/4] regulator: ab8500: Remove set_voltage_time_sel and delay to fix build error

On Wed, Apr 03, 2013 at 10:30:43AM +0800, Axel Lin wrote: > The delay field is removed from struct ab8500_regulator_info in commit > 29234928 > "regulator: ab8500: Remove set_voltage_time_sel and delay setting". I've now finished applying all Lee's outstanding patches (which weren't sent to the

[PATCH] gpio: pca953x: fix irq_domain_add_simple usage

We actually have to pass chip as the host_data parameter of irq_domain_add_simple() as later on, it is used to initialize chip_data in pca953x_gpio_irq_map(). Failing to do so is leading to a NULL pointer dereference after calling irq_data_get_irq_chip_data() in pca953x_irq_mask(),

Re: [PATCH -next] mxs/spi: fix error return code in mxs_spi_probe()

On Wed, Apr 03, 2013 at 09:06:40PM +0800, Wei Yongjun wrote: > From: Wei Yongjun > > Fix to return a negative error code from the error handling > case instead of 0, as returned elsewhere in this function. Applied, thanks. signature.asc Description: Digital signature

Re: [PATCH 3/4] x86, kdump: Retore crashkernel= to allocate low

On Wed, Apr 03, 2013 at 10:12:46AM -0700, Yinghai Lu wrote: [..] > >> Can we just keep it separated? > > > > Kernel does not know about old kexec-tools or new kexec-tools. Neither > > kernel can enforce what command line options are passed by user. So > > kernel needs to define a clean interface

Re: [PATCH 1/1] Introduce Intel RAPL cooling device driver

On Wed, 3 Apr 2013 09:35:09 -0700 Greg KH wrote: > On Tue, Apr 02, 2013 at 09:48:18PM -0700, Jacob Pan wrote: > > > Let's step back and start over, what exactly are you trying to > > > tell userspace? What data do you have that you need to express > > > to it? How do you want userspace to

Re: [RFC] perf: need to expose sched_clock to correlate user samples with kernel samples

On Wed, 2013-04-03 at 18:29 +0100, John Stultz wrote: > On 04/03/2013 10:19 AM, Pawel Moll wrote: > > On Tue, 2013-04-02 at 17:19 +0100, John Stultz wrote: > >> But if we're going to have to do > >> this via a clockid, I'm going to want it to be done via a dynamic posix > >> clockid, so its clear

Re: [PATCH 4/9] ia64: cpufreq: move cpufreq driver to drivers/cpufreq

On Mon, Apr 1, 2013 at 5:49 PM, Viresh Kumar wrote: > For now, your Ack will work :) Acked-by: Tony Luck -- 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

Re: [PATCH 3/4] x86, kdump: Retore crashkernel= to allocate low

On Wed, Apr 3, 2013 at 10:12 AM, Yinghai Lu wrote: > On Wed, Apr 3, 2013 at 6:18 AM, Vivek Goyal wrote: > >> - implement crashkernel_no_auto_low option to opt out of auto reserved >> low memory > > No, that is ugly. ... > > It's *you* want me to change "Crash kernel low" to "Crash kernel". > >

Re: [PATCH V3 2/2] cpufreq: AMD "frequency sensitivity feedback" powersave bias for ondemand governor

On Wed, Apr 03, 2013 at 12:17:38PM -0500, Jacob Shin wrote: > Writing 0 to powersave_bias or unloading the AMD driver could do that. > > When the AMD driver loads, it will give a sane default value to > powersave_bias to enable it, when it unloads, it will put it back to > 0. ... and on systems

Re: [RFC] perf: need to expose sched_clock to correlate user samples with kernel samples

On 04/03/2013 10:19 AM, Pawel Moll wrote: On Tue, 2013-04-02 at 17:19 +0100, John Stultz wrote: But if we're going to have to do this via a clockid, I'm going to want it to be done via a dynamic posix clockid, so its clear its tightly tied with perf and not considered a generic interface (and I

Re: [PATCH v3 00/11] usb: dwc3/xhci/phy: Enable runtime power management

Question: Do you still need this patch for 3.10? http://marc.info/?l=linux-usb=136057666911621=2 Does this patchset build on top of that? I'm really behind on my patches for 3.10, sorry. Sarah Sharp On Mon, Apr 01, 2013 at 07:23:59PM +0530, Vivek Gautam wrote: > This patch-series enables

Re: [RFC PATCH 2/3] perf: Add persistent event facilities

On Thu, Mar 28, 2013 at 07:15:16PM +0100, Robert Richter wrote: > The mmap'ed region is already allocated by the kernel. How does a user > know the buffer size of the mmap'ed region? Right, so normal perf events get a buffer allocated at mmap time. The size of that buffer is determined from the

[PATCH] pinctrl/nomadik: add device tree bindings for db8540

From: Gabriel Fernandez This adds a simple device tree binding for db8540 boards. Signed-off-by: Gabriel Fernandez Reviewed-by: Philippe Langlais Signed-off-by: Linus Walleij --- drivers/pinctrl/pinctrl-nomadik.c | 4 1 file changed, 4 insertions(+) diff --git

Re: [PATCH] mm, x86: Do not zero hugetlbfs pages at boot. -v2

On Wed, Apr 03, 2013 at 04:00:49PM +0200, Michal Hocko wrote: > On Tue 02-04-13 21:43:44, Robin Holt wrote: > [...] > > diff --git a/mm/bootmem.c b/mm/bootmem.c > > index 2b0bcb0..b2e4027 100644 > > --- a/mm/bootmem.c > > +++ b/mm/bootmem.c > > @@ -705,12 +705,16 @@ void * __init

Re: [PATCH 0/2] These two patches to s3c_pm_arch_prepare_irqs() were part of the work

Kukjin, On Tue, Apr 2, 2013 at 7:16 PM, Kukjin Kim wrote: >> Applied with 1st one, BTW, do you want to send this for stable tree? I don't have any need for it to be in stable tree. The ARM Chromebook hasn't reached critical functionality on any released/upstram Linux versions so it doesn't

<    1   2   3   4   5   6   7   8   9   10   >