Hi Stephen,
On Thu, 11 Jul 2013 10:27:24 +1000, Stephen Rothwell wrote:
> Why have you just rebased the jdelvare-hwmon series
> (http://khali.linux-fr.org/devel/linux-3/jdelvare-hwmon/)? You have
> just invalidated your testing and made it likely that Linus will blast
> you if you ask him to
Exynos PCIe IP consists of Synopsys specific part and Exynos
specific part. Only core block is a Synopsys designware part;
other parts are Exynos specific.
Also, the Synopsys designware part can be shared with other
platforms; thus, it can be split two parts such as Synopsys
designware part and
2013/7/11 Srivatsa S. Bhat :
> Hi Toralf,
>
> On 07/11/2013 02:20 AM, Toralf Förster wrote:
>> I tested the patch several times on top of a66b2e5 - the origin issue is
>> fixed but - erratically another issue now appears : all 4 cores are runs
>> after wakeup at 2.6 GHz.
>> The temporary hot fix
On 07/10/2013 06:02 PM, Joonsoo Kim wrote:
> On Wed, Jul 10, 2013 at 03:52:42PM -0700, Dave Hansen wrote:
>> On 07/03/2013 01:34 AM, Joonsoo Kim wrote:
>>> - if (page)
>>> + do {
>>> + page = buffered_rmqueue(preferred_zone, zone, order,
>>> +
On Wed, Jul 10, 2013 at 05:35:58PM -0700, Greg Kroah-Hartman wrote:
> Hi all,
>
> Here's the second iteration of the patchset to add better attribute
> group support to the driver core and sysfs.
>
> I've tested these (shocker!) and everything works fine with them (I'm
> sending this from
On 07/10/2013 08:05 PM, Alexander Graf wrote:
>
> On 10.07.2013, at 07:00, Alexey Kardashevskiy wrote:
>
>> On 07/10/2013 03:02 AM, Alexander Graf wrote:
>>> On 07/06/2013 05:07 PM, Alexey Kardashevskiy wrote:
This adds real mode handlers for the H_PUT_TCE_INDIRECT and
H_STUFF_TCE
This patch fix typo (sorce -> source)
Signed-off-by: Chanwoo Choi
---
include/linux/pm_wakeup.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/pm_wakeup.h b/include/linux/pm_wakeup.h
index 569781f..a0f7080 100644
--- a/include/linux/pm_wakeup.h
+++
On Wed, 10 Jul 2013, Ingo Molnar wrote:
> Exactly - PMUs enumerated in /sys should be self-identifying, it's a
> hardware topology after all ...
>
> Anytime userspace is forced to look into /proc, or into weird places in
> /sys it's a FAIL really.
well on x86 you have to look at /proc/cpuinfo
>
> BTW speaking of introductory-level patches, what about the following
> one:
>
> Now that lz4 kernel compression is available, add *.lz4 to .gitignore
>
> diff --git a/.gitignore b/.gitignore
> index 3b8b9b3..7e9932e 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -29,6 +29,7 @@
I'm getting a SEGV when running perf annotate on a ppc64 box. The
objdump -S output causing the SEGV looks like:
b .ret_from_except_lite
c000a508: b c000a4d4 <.ret_from_except_lite>
1: bl .save_nvgprs
c000a50c: bl
On 07/11/2013 12:08 PM, Laxman Dewangan wrote:
> On Thursday 11 July 2013 08:12 AM, Chanwoo Choi wrote:
>> Hi Laxman,
>>
>>> static int palmas_usb_probe(struct platform_device *pdev)
>>> @@ -137,20 +140,26 @@ static int palmas_usb_probe(struct platform_device
>>> *pdev)
>>> struct
On Wed, Jul 10, 2013 at 07:11:53PM -0700, Linus Torvalds wrote:
> Commit d2aae8477cd00325bb7c7c7e95be488088900c48 is broken. It causes
> root to re-write "include/config/kernel.release".
>
> There is no excuse for this. That commit is shit. There's no way in
> hell that "make modules_install"
On Thu, Jul 11, 2013 at 09:29:49AM +0530, Akhil Goyal wrote:
> On 7/8/2013 3:19 PM, akhil.go...@freescale.com wrote:
> >From: Akhil Goyal
> >
> >RF signal path is integral part of any system that transmits/receives RF
> >(radio frequency) signals. In these systems Data is processed/converted
> >to
Hi all,
Changes since 20130710:
The slab tree lost its build failure.
The akpm tree lost a patch that turned up elsewhere.
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next
When sysfs_create_file() fails, need consider about it. And process it
with BUG_ON(), because sysfs_create_file() can fail due to OOM (not at
boot) or name duplication (not here).
Also correct the error printing information when failure occurs.
Signed-off-by: Chen Gang
---
kernel/params.c |
On 7/8/2013 3:19 PM, akhil.go...@freescale.com wrote:
From: Akhil Goyal
RF signal path is integral part of any system that transmits/receives RF
(radio frequency) signals. In these systems Data is processed/converted
to IQ samples (digital representation a RF signal) and passed to a RFIC
(RF
>> We should do nothing in pciehp_resume, but we call
>> pciehp_enable_slot(), so some uncomfortable messages show like above.
>> In this case, we can improve it a little by add a guard
>> if (!list_empty(bus->devices)).
>
> Great!
>
> I'm currently trying to bisect another problem, but
On 7/10/2013 3:05 PM, Linus Walleij wrote:
On Thu, Jun 27, 2013 at 11:08 PM, Hanumant Singh
wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
This
add qt1070 support on at91sam9n12ek board
Signed-off-by: Bo Shen
---
Changes in v2:
- using micro for interrupt trigger mode
arch/arm/boot/dts/at91sam9n12ek.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9n12ek.dts
add pinctrl of TWI for at91sam9n12 SoC
Signed-off-by: Bo Shen
---
Changes in v2:
- remove comments as use micro
arch/arm/boot/dts/at91sam9n12.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9n12.dtsi
correct pin number of gpio-key for at91sam9n12ek board
the pioB4 is connect to LED, the pioB3 use as gpio-key
Signed-off-by: Bo Shen
---
Changes in v2: None
arch/arm/boot/dts/at91sam9n12ek.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
this patch is based on linux master branch, implementation as following:
- add the i2c pinctrl which needed for using at91sam9n12 TWI
- enable qt1070
- trival fix for the gpio-key pin number
Changes in v2:
- remove comments as use micro
- using micro for interrupt trigger mode
Bo Shen
(2013/07/11 6:36), H. Peter Anvin wrote:
> On 07/10/2013 02:31 PM, Jiri Kosina wrote:
>>
>> If any CPU instruction execution would collide with the patching,
>> it'd be trapped by the int3 breakpoint and redirected to the provided
>> "handler" (which would typically mean just skipping over the
"Michael S. Tsirkin" writes:
> On Wed, Jul 10, 2013 at 04:27:00PM +0530, Ramkumar Ramachandra wrote:
>> Signed-off-by: Ramkumar Ramachandra
>> ---
>
> Why not.
>
> Acked-by: Michael S. Tsirkin
Applied.
Thanks,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Thursday, July 11, 2013 10:01:17 AM Stephen Rothwell wrote:
> Hi Paul,
Hi Stephen,
I know you already emailed me privately about my @hp.com email address, but
for the sake of everyone else on the list, my @hp.com address no longer works,
it hasn't for some time now. Please check my entry
On Thu, 11 Jul 2013 12:26:34 +1000 Dave Chinner wrote:
> > Just for reference. wait_on_page_writeback is issued only for memcg
> > reclaim because there is no other throttling mechanism to prevent from
> > too many dirty pages on the list, thus pre-mature OOM killer. See
> > e62e384e9d (memcg:
On Thursday 11 July 2013 08:12 AM, Chanwoo Choi wrote:
Hi Laxman,
static int palmas_usb_probe(struct platform_device *pdev)
@@ -137,20 +140,26 @@ static int palmas_usb_probe(struct platform_device *pdev)
struct palmas_usb *palmas_usb;
int status;
- if (node && !pdata) {
-
On 07/11/2013 09:53 AM, Rusty Russell wrote:
> Chen Gang F T writes:
>> > On 07/09/2013 04:07 PM, Rusty Russell wrote:
>>> >> Chen Gang writes:
>>> When sysfs_create_file() fails, recommend to print the related failure
>>> information. And it is useless to still 'KOBJ_ADD' to user
2013/7/5 Vinod Koul :
> On Tue, Jun 18, 2013 at 04:41:20PM +0800, Xiang Wang wrote:
>> From: Xiang Wang
>>
>> In some of our drivers (e.g. UART) we may stop a running DMA
>> before it finishes. So we need APIs to know how many bytes
>> have been transferred.
>>
>> Signed-off-by: Xiang Wang
>>
From: Geert Uytterhoeven
Date: Wed, 10 Jul 2013 23:03:34 +0200
> If NO_DMA=y:
>
> drivers/built-in.o: In function `sh_eth_free_dma_buffer':
> drivers/net/ethernet/renesas/sh_eth.c:1103: undefined reference to
> `dma_free_coherent'
> drivers/net/ethernet/renesas/sh_eth.c:1110: undefined
Hi, Sergey
On 07/11/2013 07:13 AM, Sergey Senozhatsky wrote:
[snip]
>
>
> Please kindly review the following patch.
>
>
>
> Remove cpu device only upon succesful cpu down on CPU_POST_DEAD event,
> so we can kill off CPU_DOWN_FAILED case and eliminate potential extra
> remove/add path:
>
Hi Laxman,
> static int palmas_usb_probe(struct platform_device *pdev)
> @@ -137,20 +140,26 @@ static int palmas_usb_probe(struct platform_device
> *pdev)
> struct palmas_usb *palmas_usb;
> int status;
>
> - if (node && !pdata) {
> - pdata = devm_kzalloc(>dev,
Chen Gang F T writes:
> On 07/09/2013 04:07 PM, Rusty Russell wrote:
>> Chen Gang writes:
>>> When sysfs_create_file() fails, recommend to print the related failure
>>> information. And it is useless to still 'KOBJ_ADD' to user space.
>>>
>>> Signed-off-by: Chen Gang
>>
>> sysfs_create_file()
>> + */
>> +void pci_get_dsn(struct pci_dev *dev, u64 *sn)
>
> How about:
>
> u64 pci_device_serial_number(struct pci_dev *dev)
>
> "get" suggests reference counting, which isn't happening here. And
> why pass a pointer to a return value when we can just as easily return
> it directly?
On 07/10/2013 06:00 PM, Stefani Seibold wrote:
Am Mittwoch, den 10.07.2013, 16:48 +0800 schrieb tiejun.chen:
On 07/10/2013 04:39 PM, Stefani Seibold wrote:
Hi,
i have tried to kexec a 32 bit kernel on a Freescale P2020 dual core CPU
(e500v2, revison 5.1 - pvr 8021 1051), but Kexec will hang
>> If the slot support surprise hot remove, this action maybe safe. right?
>
> If there's no device, config space accesses performed by .remove()
> will fail (reads will return -1 data or error; writes will be
> dropped). MMIO or I/O port accesses may fail with machine checks or
> similar bad
On Wed, Jul 10, 2013 at 10:06:05AM +0200, Michal Hocko wrote:
> On Wed 10-07-13 12:31:39, Dave Chinner wrote:
> [...]
> > > 20761 [] xlog_grant_head_wait+0xdd/0x1a0 [xfs]
> > > [] xlog_grant_head_check+0xc6/0xe0 [xfs]
> > > [] xfs_log_reserve+0xff/0x240 [xfs]
> > > [] xfs_trans_reserve+0x234/0x240
(2013/07/11 5:25), Jiri Kosina wrote:
> Hi,
>
> this is a resurrection of a few years old idea to have jump labels use
> synchronization based on int3 breakpoint rather than relying on
> stop_machine() with all the consequences.
>
> ftrace has been doing exactly this kind of patching for year
于 2013年07月11日 10:14, Huang Shijie 写道:
> 于 2013年07月10日 23:57, Wolfram Sang 写道:
>> Since commit ab78029 (drivers/pinctrl: grab default handles from device
>> core),
>> we can rely on device core for setting the default pins. Compile tested only.
>>
>> Acked-by: Linus Walleij (personally at LCE13)
On Tue, Jul 02, 2013 at 07:49:47PM +, Bjarni Ingi Gislason wrote:
> On Mon, Jul 01, 2013 at 11:40:08AM +0200, Clemens Ladisch wrote:
> > > On 29.6.2013 22:42, Bjarni Ingi Gislason wrote:
> > >> The file "drivers/rtc/rtc_cmos.c" needs CONFIG_HPET to get linked.
> > >>
> > >>
On Wed, Jul 10, 2013 at 6:37 AM, Michal Marek wrote:
>
> please pull the kbuild bits for v3.11-rc1:
THIS IS SOME HORRIBLY BROKEN CRAP.
"make install" and "make modules_install" ABSOLUTELY MUST NOT MODIFY
THE SOURCE TREE.
Dammit, this has happened before, and it was broken then, and it is
于 2013年07月10日 23:57, Wolfram Sang 写道:
> Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
> we can rely on device core for setting the default pins. Compile tested only.
>
> Acked-by: Linus Walleij (personally at LCE13)
> Signed-off-by: Wolfram Sang
> ---
i remember
On Thu, Jul 11, 2013 at 10:31:16AM +1000, Stephen Rothwell wrote:
> You have
> just invalidated your testing
On the contrary, it is part of my testing.
> Your whole series was already
> based after v3.10 (i.e. released or rebased after the merge window
> opened), so why move it again?
I
On Wed, Jul 10, 2013 at 04:12:36PM -0700, Paul Taysom wrote:
> The following commit introduced a 10x regression for
> syncing inodes in ext4 with relatime enabled where just
> the atime had been modified.
>
> commit 4ea425b63a3dfeb7707fc7cc7161c11a51e871ed
> Author: Jan Kara
> Date:
On 07/10/2013 08:36 PM, Matt Fleming wrote:
> On 10/07/13 07:36, Dave Young wrote:
>> Another problem is: With this patch applied I tried noefi boot, but
>> kernel paniced, looks like efivar_init depends on efi runtime. Below
>> patches works for me about noefi boot though I'm not sure if it's a
On Thu, Jul 11, 2013 at 10:31:16AM +1000, Stephen Rothwell wrote:
> Why have you just rebased the device-mapper series
I was confirming there weren't any unexpected conflicts or other issues to
deal with from a point after the block tree went in before generating
the pull request.
Alasdair
--
On Wednesday, July 10, 2013 11:02 PM, Kishon Vijay Abraham I:
> On Friday 05 July 2013 01:59 PM, Jingoo Han wrote:
> > Exynos PCIe IP consists of Synopsys specific part and Exynos
> > specific part. Only core block is a Synopsys designware part;
> > other parts are Exynos specific.
> > Also, the
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm
tags/dm-3.11-changes
to get the following device-mapper changes for 3.11.
Thanks,
Alasdair
Add a device-mapper target called dm-switch to provide a
Hi Peter,
On 07/10/2013 05:30 PM, Peter Hüwe wrote:
>>
>> tpm_tis_resume() is defined originally in CONFIG_PM_SLEEP scope. I can
>> make the change to have tpm_tis_resume() not be in CONFIG_PM_SLEEP scope
>> and remove this CONFIG_PM_SLEEP when defining .pm.
>> That does make sense looking at
Linux as a guest on KVM hypervisor, the only user of the pvclock
vsyscall interface, does not require notification on task migration
because:
1. cpu ID number maps 1:1 to per-CPU pvclock time info.
2. per-CPU pvclock time info is updated if the
underlying CPU changes.
3. that version
Hi J,
On 7/10/2013 22:38, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 17:51 Wed 10 Jul , Bo Shen wrote:
add qt1070 support on at91sam9n12ek board
Signed-off-by: Bo Shen
---
arch/arm/boot/dts/at91sam9n12ek.dts | 16
1 file changed, 16 insertions(+)
diff --git
Hi J,
On 7/10/2013 22:39, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 17:51 Wed 10 Jul , Bo Shen wrote:
add pinctrl of TWI for at91sam9n12 SoC
Signed-off-by: Bo Shen
---
arch/arm/boot/dts/at91sam9n12.dtsi | 20
1 file changed, 20 insertions(+)
diff --git
On Wed, Jul 10, 2013 at 01:27:37PM +0200, Michal Hocko wrote:
> On Wed 10-07-13 18:55:33, Joonsoo Kim wrote:
> > On Wed, Jul 10, 2013 at 11:17:03AM +0200, Michal Hocko wrote:
> > > On Wed 10-07-13 09:31:42, Joonsoo Kim wrote:
> > > > On Thu, Jul 04, 2013 at 12:00:44PM +0200, Michal Hocko wrote:
>
On Wed, Jul 10, 2013 at 03:52:42PM -0700, Dave Hansen wrote:
> On 07/03/2013 01:34 AM, Joonsoo Kim wrote:
> > - if (page)
> > + do {
> > + page = buffered_rmqueue(preferred_zone, zone, order,
> > + gfp_mask,
I've applied this, but:
On Wed, 2013-07-10 at 19:42 -0500, suravee.suthikulpa...@amd.com wrote:
> From: Suravee Suthikulpanit
>
> For AMD Families 10h ~ 14h Processors
> file: amd-ucode/microcode_amd.bin
> md5sum: 55ae79b82cbfddcf7142058be3c9ec2d
>
> For AMD Family 15h Processors
> file:
On Thu, 11 Jul 2013, Arnd Bergmann wrote:
> On Wednesday 10 July 2013, Alan Stern wrote:
> > This isn't right. There are USB host controllers that use PIO, not
> > DMA. The HAS_DMA dependency should go with the controller driver, not
> > the USB core.
> >
> > On the other hand, the USB core
From: Suravee Suthikulpanit
For AMD Families 10h ~ 14h Processors
file: amd-ucode/microcode_amd.bin
md5sum: 55ae79b82cbfddcf7142058be3c9ec2d
For AMD Family 15h Processors
file: amd-ucode/microcode_amd_fam15h.bin
md5sum: 122ac7e56442c2b7c28eb26978b2d57c
Version: 07_10_2013
Signed-off-by:
On Mon, 2013-07-08 at 17:11 +0800, Hayes Wang wrote:
> File: rtl_nic/rtl8411-2.fw
> Version: 0.0.1
>
> Signed-off-by: Hayes Wang
> ---
> WHENCE | 3 +++
> rtl_nic/rtl8411-2.fw | Bin 0 -> 1040 bytes
> 2 files changed, 3 insertions(+)
> create mode 100644 rtl_nic/rtl8411-2.fw
On 07/10/2013 07:44 PM, Peter Zijlstra wrote:
> On Wed, Jul 10, 2013 at 07:37:43PM +0800, Yan, Zheng wrote:
>> On 07/08/2013 08:15 PM, Peter Zijlstra wrote:
>>> On Thu, Jun 06, 2013 at 01:58:06PM +0800, Yan, Zheng wrote:
From: "Yan, Zheng"
>
before overwrite mode after
Third time is the charm crbug.com/240411
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Jul 9, 2013 at 12:09 PM, Doug Anderson wrote:
> Hi,
>
> On Tue, Jul 9, 2013 at 10:31 AM, Doug Anderson wrote:
>> If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
>> looping around forever.
>>
>> Signed-off-by: Doug Anderson
>> ---
>>
From: Francois Romieu
Date: Wed, 10 Jul 2013 01:00:16 +0200
> David Miller :
> [...]
>> Francois, please review.
>
> The style is consistent with the driver.
>
> The commit message may state that this 8411 chipset does not require
> any special action in rtl_link_chg_patch (whence differing
Remove debugfs directories for tracing instances during creation if an error
occurs causing the trace_array for that instance to not be added to
ftrace_trace_arrays. If the directory continues to exist after the error, it
cannot be removed because the respective trace_array is not in
On Wed, Jul 10, 2013 at 4:56 PM, Dave Jones wrote:
> On Wed, Jul 10, 2013 at 04:12:36PM -0700, Paul Taysom wrote:
>
> > Note, when running the test, the slow down doesn't always happen
> > but most of the tests will show a slow down.
> >
> > In response to crbug.com/240422
>
> Just in case
This makes it easier to create static binary attributes, which is needed
in a number of drivers, instead of "open coding" them.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/sysfs.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/linux/sysfs.h b/include/linux/sysfs.h
Hi all,
Here's the second iteration of the patchset to add better attribute
group support to the driver core and sysfs.
I've tested these (shocker!) and everything works fine with them (I'm
sending this from Linus's latest kernel with these 7 on top of it.)
I'd like to send these to Linus for
Hi Simon,
On Thu, 11 Jul 2013 09:31:33 +0900 Simon Horman wrote:
>
> I am not planning to send any pull requests for v3.11,
> at least not for the branches that I rebased.
Then none of that stuff should be in -next at the moment (not until after
v3.11-rc1 is released). It just mucks up
To make it easier for driver subsystems to work with attribute groups,
create the ATTRIBUTE_GROUPS macro to remove some of the repetitive
typing for the most common use for attribute groups.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/sysfs.h | 9 +
1 file changed, 9
Make it easier to create attributes without having to always audit the
mode settings.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/device.h | 28 +---
1 file changed, 21 insertions(+), 7 deletions(-)
diff --git a/include/linux/device.h b/include/linux/device.h
We should be using groups, not attribute lists, for classes to allow
subdirectories, and soon, binary files. Groups are just more flexible
overall, so add them.
The dev_attrs list will go away after all in-kernel users are converted
to use dev_groups.
Signed-off-by: Greg Kroah-Hartman
---
groups should be able to support binary attributes, just like it
supports "normal" attributes. This lets us only handle one type of
structure, groups, throughout the driver core and subsystems, making
binary attributes a "full fledged" part of the driver model, and not
something just "tacked on".
From: Guenter Roeck
device_create_groups lets callers create devices as well as associated
sysfs attributes with a single call. This avoids race conditions seen
if sysfs attributes on new devices are created later.
[fixed up comment block placement and add checks for printk buffer
formats -
A number of parts of the kernel created their own version of this, might
as well have the sysfs core provide it instead.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/sysfs.h | 2 ++
kernel/events/core.c | 2 --
mm/backing-dev.c | 2 --
3 files changed, 2 insertions(+), 4
On Wed, Jul 10, 2013 at 12:00:57PM +0200, Yann Droneaud wrote:
> Hi,
>
> Le 09.07.2013 22:53, Ben Myers a écrit :
> >On Mon, Jul 08, 2013 at 05:41:33PM -0500, Ben Myers wrote:
> >>On Tue, Jul 02, 2013 at 06:39:34PM +0200, Yann Droneaud wrote:
>
> >>> diff --git a/fs/xfs/xfs_ioctl.c
On Wed, Jul 10, 2013 at 04:19:06PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Joonsoo Kim
>
> Currently, lib lk doesn't use CROSS_COMPILE environment variable, so
> cross build always fails.
Hello, Arnaldo.
Fix for lib lk cross build is already merged into mainline.
It may be from your
Some error paths did not handle ref counting properly, and some trace files need
ref counting.
Cc: Vaibhav Nagarnaik
Cc: David Sharp
Cc: Alexander Z Lam
Signed-off-by: Alexander Z Lam
---
kernel/trace/trace.c| 34 +++---
kernel/trace/trace_events.c | 21
Like other trace_selftest_startup_*, trace_selftest_startup_function()
and trace_selftest_startup_function_graph() need in normal section, or
may cause section mismatch.
The related warnings:
LD kernel/trace/built-in.o
WARNING: kernel/trace/built-in.o(.data+0x154c): Section mismatch
On Thu, Jul 11, 2013 at 10:08:51AM +1000, Stephen Rothwell wrote:
> Hi Simon,
>
> Why have you just rebased the renesas tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git#next)?
> You have just invalidated your testing and made it likely that your
> upstream maintainers will
Hi Alasdair,
Why have you just rebased the device-mapper series
(http://people.redhat.com/agk/patches/linux/editing/)? You have
just invalidated your testing and made it likely that Linus will blast
you if you ask him to pull your patches. Your whole series was already
based after v3.10 (i.e.
On Wednesday, July 10, 2013 05:48:26 PM Toshi Kani wrote:
> On Thu, 2013-07-11 at 00:45 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, July 10, 2013 02:11:05 AM Rafael J. Wysocki wrote:
> > > On Tuesday, July 09, 2013 01:32:42 PM Toshi Kani wrote:
> > > > On Mon, 2013-07-08 at 02:10 +0200,
Hi Jean,
Why have you just rebased the jdelvare-hwmon series
(http://khali.linux-fr.org/devel/linux-3/jdelvare-hwmon/)? You have
just invalidated your testing and made it likely that Linus will blast
you if you ask him to pull your patches. Your whole series was already
based after v3.10 (i.e.
On 07/03/2013 09:56 PM, Ben Hutchings wrote:
On Fri, 2013-06-28 at 14:27 -0500, Sherry Hurwitz wrote:
For AMD Families 10h ~ 14h Processors
file: amd-ucode/microcode_amd.bin
md5sum: 55ae79b82cbfddcf7142058be3c9ec2d
For AMD Family 15h Processors
file: amd-ucode/microcode_amd_fam15h.bin
On Wed, Jul 10, 2013 at 04:59:28PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Jul 10, 2013 at 04:00:57PM -0700, Guenter Roeck wrote:
> > > + for (bin_attr = grp->bin_attrs; *bin_attr; bin_attr++) {
> >
> > What happens here if grp->bin_attrs is NULL ? Doesn't that cause a NULL
> > reference when
Gleb Natapov wrote:
>On Wed, Jul 10, 2013 at 11:03:15AM -0400, Konrad Rzeszutek Wilk wrote:
>> On Wed, Jul 10, 2013 at 01:47:17PM +0300, Gleb Natapov wrote:
>> > On Wed, Jul 10, 2013 at 12:40:47PM +0200, Peter Zijlstra wrote:
>> > > On Wed, Jul 10, 2013 at 01:33:25PM +0300, Gleb Natapov wrote:
>>
From: Eliezer Tamir
Date: Wed, 10 Jul 2013 17:13:07 +0300
> Here are three patches that complete the rename of lls to busy-poll
>
> 1. rename include/net/ll_poll.h to include/net/busy_poll.h
> 2. Rename ndo_ll_poll to ndo_busy_poll.
>Rename sk_mark_ll to sk_mark_napi_id.
>Rename
Hi Simon,
Why have you just rebased the renesas tree
(git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git#next)?
You have just invalidated your testing and made it likely that your
upstream maintainers will blast you if you ask them to pull your tree
(though it is probably too late
On Wed, 10 Jul 2013, Jason Baron wrote:
> > this is a resurrection of a few years old idea to have jump labels use
> > synchronization based on int3 breakpoint rather than relying on
> > stop_machine() with all the consequences.
> >
> > ftrace has been doing exactly this kind of patching for
Hi Matthew,
Why have you just rebased the drivers-x86 tree
(git://cavan.codon.org.uk/platform-drivers-x86.git#linux-next)? You have
just invalidated your testing and made it likely that Linus will blast
you if you ask him to pull your tree. Your whole tree was already based
after v3.10 (i.e.
Hello Linus!
Here are the target pending patches for the v3.11-rc1 merge window.
Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next
Lots of activity this round on performance improvements in target-core
while benchmarking the
Hi Julius,
On Wed, Jul 10, 2013 at 2:42 PM, Julius Werner wrote:
> Hi Felipe,
>
> This is intended to pull down a reset signal line, not to switch power
> to the device. I could implement that with the regulator framework
> too, but I think that would just be confusing and harder to understand
>
Hi Paul,
Why have you just rebased the lblnet tree
(git://git.infradead.org/users/pcmoore/lblnet-2.6_next#master)? You have
just invalidated your testing and made it likely that Linus will blast
you if you ask him to pull your tree. Your whole tree was already based
after v3.10 (i.e. released
On Wed, Jul 10, 2013 at 04:00:57PM -0700, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 01:05:13PM -0700, Greg Kroah-Hartman wrote:
> > @@ -52,6 +55,17 @@ static int create_files(struct sysfs_dirent *dir_sd,
> > struct kobject *kobj,
> > }
> > if (error)
> >
On 07/10/2013 01:52 PM, Christian Sünkenberg wrote:
> Hello,
>
> On 05/01/2013 07:33 PM, H. Peter Anvin wrote:
>> On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
>>> Hello, I tried the newest kernel, 3.9 today but the bug is still
>>> present. Applying the attached patch solves the bug for me.
>>>
On Wed, Jul 10, 2013 at 04:12:36PM -0700, Paul Taysom wrote:
> Note, when running the test, the slow down doesn't always happen
> but most of the tests will show a slow down.
>
> In response to crbug.com/240422
Just in case this ends up as the actual commit msg, that url
seems to be the
On Wed, Jul 10, 2013 at 01:42:17PM -0700, Eric W. Biederman wrote:
> I meant code not hardware architecture. We keep having code thrown in
> the the shutdown paths because ARM only supports cpu shutdown via cpu
> hotunplug and cpu hotunplug is not universally available.
>
> That is a software
On Wednesday, July 10, 2013 9:34 AM, Julius Werner wrote:
>
> This patch adds support for a new 'samsung,hsic-reset-gpio' in the
> device tree, which will be interpreted as an active-low reset pin during
> PHY initialization when it exists. Useful for intergrated HSIC devices
> like an SMSC 3503
On Thu, 2013-07-11 at 00:45 +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 10, 2013 02:11:05 AM Rafael J. Wysocki wrote:
> > On Tuesday, July 09, 2013 01:32:42 PM Toshi Kani wrote:
> > > On Mon, 2013-07-08 at 02:10 +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> > > >
> >
Instead of delaying inode initialization until first ->open(), we can use
an anonymous inode. This avoids modifying FS internal inode fields and
provides us a private address_space right during initialization.
Delayed TTM dev_mapping initialization is currently left untouched to keep
this simple.
DRM core shares a single address_space across all inodes that belong to
the same DRM device. This allows efficient unmapping of user-space
mappings during buffer destruction. However, there is no easy way to get a
shared address_space for DRM devices during initialization. Therefore, we
currently
Hi Steven,
On Wed, 10 Jul 2013 14:05:45 +0800 Steven Miao wrote:
>
> Pls use for-linus branch on
> http://git.kernel.org/pub/scm/linux/kernel/git/realmz6/blackfin-linux.git
Done.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpa2k9AByyhk.pgp
Description: PGP
1 - 100 of 1208 matches
Mail list logo
