Hi Tuomas,
A bunch of small nit picks from me.
On Wed, Aug 20, 2014 at 2:04 PM, Tuomas Tynkkynen wrote:
> Add shared code to support the Tegra DFLL clocksource in open-loop
> mode. This root clocksource is present on the Tegra124 SoCs. The
> DFLL is the intended primary clock source for the
On Wed, 27 Aug 2014 23:32:00 +0200 (CEST) Jiri Kosina wrote:
> On Wed, 27 Aug 2014, Jiri Kosina wrote:
>
> > > Is it worth adding report->id to this hid_warn()?
> > >
> > > A valid device is not expected to ever send >64 bytes reports but in
> > > case a firmware update would do so it would help
On 8/28/2014 6:59 AM, Ley Foon Tan wrote:
Warning:
drivers/net/ethernet/stmicro/stmmac/dwmac-socfpga.c:122:41:
sparse: cast removes address space of expression
drivers/net/ethernet/stmicro/stmmac/dwmac-socfpga.c:122:38:
sparse: incorrect type in assignment (different address spaces)
On Thu, Aug 28, 2014 at 12:30 PM, Pramod Gurav
wrote:
> This function releases clk and regulator in remove function for clean
> unloading.
>
> CC: Shawn Guo
> CC: "Rafael J. Wysocki"
> CC: Viresh Kumar
> Signed-off-by: Pramod Gurav
> ---
> drivers/cpufreq/cpufreq-cpu0.c |2 ++
> 1 files
On (Wed) 27 Aug 2014 [16:43:40], Pranith Kumar wrote:
> The nocb callbacks generated before the nocb kthreads are spawned are
> enqueued in the nocb queue for later processing. Commit fbce7497ee5af ("rcu:
> Parallelize and economize NOCB kthread wakeups") introduced nocb leader
> kthreads
> which
Hi all,
Changes since 20140827:
The usb.current tree lost its build failure.
The percpu tree lost its build failure.
The staging tree still had its build failure for which I applied a
fix patch.
Non-merge commits (relative to Linus' tree): 2146
2292 files changed, 58126 insertions(+), 36066
On Thu, Aug 28, 2014 at 12:00:10AM -0700, Pramod Gurav wrote:
> This function releases clk and regulator in remove function for clean
> unloading.
>
> CC: Shawn Guo
> CC: "Rafael J. Wysocki"
> CC: Viresh Kumar
> Signed-off-by: Pramod Gurav
> ---
> drivers/cpufreq/cpufreq-cpu0.c |2 ++
>
Using PWD breaks out-of-tree builds in certain circumstances [1], and
other kernel Makefiles use relative paths just fine.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=83251
Signed-off-by: Shea Levy
---
drivers/usb/gadget/Makefile | 2 +-
drivers/usb/gadget/function/Makefile | 4
Warning:
drivers/net/ethernet/stmicro/stmmac/dwmac-socfpga.c:122:41:
sparse: cast removes address space of expression
drivers/net/ethernet/stmicro/stmmac/dwmac-socfpga.c:122:38:
sparse: incorrect type in assignment (different address spaces)
Signed-off-by: Ley Foon Tan
---
From: chai wen
For now, soft lockup detector warns once for each case of process softlockup.
But the thread 'watchdog/n' may not always get the cpu at the time slot between
the task switch of two processes hogging that cpu to reset soft_watchdog_warn.
An example would be two processes hogging
Dear Andrew,
On 08/27/2014 06:31 AM, Andrew Morton wrote:
> On Mon, 25 Aug 2014 09:57:33 +0900 Chanwoo Choi wrote:
>
>> Dear Andrew,
>>
>> On 08/23/2014 05:42 AM, Andrew Morton wrote:
>>> On Tue, 12 Aug 2014 11:01:07 +0900 y...@samsung.com wrote:
>>>
This patch define s3c_rtc structure
On 08/27/14 at 10:32am, Christoph Lameter wrote:
> Maybe something like this may be a proper fix:
>
> Subject: slub: Disable tracing of mergeable slabs
>
> Tracing of mergeable slabs is confusing since the objects
> of multiple slab caches will be traced. Moreover this creates
> a situation
Hi Jingoo,
On Wed, Aug 27, 2014 at 7:28 AM, Jingoo Han wrote:
> On Thursday, August 21, 2014 11:55 PM, Vivek Gautam wrote:
>>
>> Adding phy calibrate callback, which facilitates setting certain
>> PHY settings post initialization of the PHY controller.
>> Exynos5420 and Exynos5800 have 28nm USB
Dear Eduardo,
This patch is wrong. It is my mistake.
Please ignore only this patch because
the offset calculation of 'case 0' is different from 'case 2'.
Best Regards,
Chanwoo Choi
On 08/26/2014 10:31 AM, Chanwoo Choi wrote:
> This patch remove simply duplicate code when reading triminfo
From: "vishnu.ps"
This patch fixes minor errors and warning messages in sys.c file.
These errors were reported while working with some modifications in sys.c file.
Fixing this first will help me to improve my further patches.
ERROR: trailing whitespace - 9
ERROR: do not use assignment in if
e branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid
git bisect good d05446ae2128064a4bb8f74c84f6901ffb5c94bc # 04:22 60+
0 Add linux-next specific files for 20140827
This script may
Hi,
On Fri, Aug 22, 2014 at 4:19 PM, Andreas Färber wrote:
> Hi,
>
> s/Caibrate/Calibrate/
Sure, will rectify the title, thanks for pointing it out.
--
Best Regards
Vivek Gautam
Samsung R Institute, Bangalore
India
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Adds documentation for perf support to SDT events.
Signed-off-by : Hemant Kumar
---
tools/perf/Documentation/SDT-support.txt | 48 ++
tools/perf/Documentation/perf-list.txt |4 ++-
2 files changed, 51 insertions(+), 1 deletion(-)
create mode 100644
This patch enables perf to look for SDT markers in a single file.
An individual file argument must be given to "perf list" to find out the SDT
markers
present in that file.
Usage is as below :
# perf list sdt /home/hemant/tmp
/home/hemant/tmp:
%user : foo
%user : bar
On using this command,
On Thu, Apr 10, 2014 at 09:32:34PM +0200, Julia Lawall wrote:
>
>
> On Thu, 10 Apr 2014, Luis R. Rodriguez wrote:
>
> > On Thu, Apr 10, 2014 at 07:51:29PM +0200, Johannes Berg wrote:
> > > On Thu, 2014-04-10 at 10:48 -0700, Luis R. Rodriguez wrote:
> > >
> > > > You just pass it a cocci file,
This patch serves as the initial support to identify and list SDT events in
binaries.
When programs containing SDT markers are compiled, gcc with the help of
assembler
directives identifies them and places them in the section ".note.stapsdt". To
find these
markers from the binaries, one needs
On 08/27/14 at 10:25am, Christoph Lameter wrote:
> On Wed, 27 Aug 2014, WANG Chao wrote:
>
> > Mergeable slab can be changed to unmergeable after tuning its sysfs
> > interface, for example echo 1 > trace. But the sysfs kobject with the unique
> > name will be still there.
>
> Hmmm... Merging
The v3 patchset had some spacing errors because of my editor messing up during
sending the patches. Resending the patchset again.
This patchset helps in listing dtrace style markers(SDT) present in user space
applications through perf.
Notes/markers are placed at important places by the
> -Original Message-
> From: Dexuan Cui
> Sent: Wednesday, August 27, 2014 8:22 PM
> To: KY Srinivasan; Sitsofe Wheeler
> Cc: Greg Kroah-Hartman; Haiyang Zhang; de...@linuxdriverproject.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [PANIC, hyperv] BUG: unable to handle kernel paging
On Wed, 2014-08-27 at 14:29 +0200, Tomas Henzl wrote:
> On 08/27/2014 10:19 PM, Ching Huang wrote:
> > On Tue, 2014-08-26 at 15:20 +0200, Tomas Henzl wrote:
> >> On 08/26/2014 10:27 PM, Ching Huang wrote:
> >>> On Mon, 2014-08-25 at 12:29 +0200, Tomas Henzl wrote:
> On 08/25/2014 07:59 PM,
Hi,
On Wed, Aug 27, 2014 at 7:58 PM, Olof Johansson wrote:
> On Wed, Aug 27, 2014 at 5:56 PM, Stephen Boyd wrote:
>> On 08/27/14 15:33, Olof Johansson wrote:
>>> On Wed, Aug 27, 2014 at 3:26 PM, Stephen Boyd wrote:
>>>
Is there any reason why the virtual counter can't be read? Maybe we're
On Thu, Aug 28, 2014 at 7:33 AM, David Miller wrote:
> From: Ley Foon Tan
> Date: Tue, 26 Aug 2014 15:11:16 +0800
>
>> @@ -119,7 +119,8 @@ static int socfpga_dwmac_parse_data(struct socfpga_dwmac
>> *dwmac, struct device *
>> return -EINVAL;
>> }
>>
>> -
On Wed, 27 Aug 2014, Joe Perches wrote:
> The general form for commit id and description is
>
> 'Commit <12+hexdigits> ("commit description/subject line")'
>
> But commit logs often have relatively long commit ids and
> the commit description is on a separate line like:
>
> Some explanation
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of KY Srinivasan
> Sent: Thursday, August 28, 2014 7:14 AM
> > > > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > > > Sent: Wednesday, August 27, 2014 9:19 AM
> >
Hi all,
We finished a round of tests for AIM7 workload for the patch v5 by LKP, the
result is as follows:
Hostname: brickland3
Model: Brickland Ivy Bridge-E
CPU: 120
Memory: 512G
v3.16-rc7 rewrite-v5 testbox/testcase/testparams
--- -
Move the Lantiq device-trees to arch/mips/boot/dts/lantiq/ and update
the Makefiles accordingly. There is currently only a single Lantiq
device-tree (EASY50712), and it's required to be built into the kernel,
so select BUILTIN_DTB for it.
Signed-off-by: Andrew Bresticker
---
Move the Netlogic XLP device-trees to arch/mips/boot/dts/netlogic/ and
update the Makefiles accordingly. A built-in device-tree is optional,
so select BUILTIN_DTB when it is requested.
Signed-off-by: Andrew Bresticker
---
arch/mips/boot/dts/Makefile | 1 +
On Wed, Aug 27, 2014 at 03:04:32PM -0400, Dan Streetman wrote:
> On Wed, Aug 27, 2014 at 12:59 PM, David Horner wrote:
> > On Wed, Aug 27, 2014 at 12:29 PM, Dan Streetman wrote:
> >> On Wed, Aug 27, 2014 at 11:35 AM, David Horner wrote:
> >>> On Wed, Aug 27, 2014 at 11:14 AM, Dan Streetman
On Wed, Aug 27, 2014 at 5:56 PM, Stephen Boyd wrote:
> On 08/27/14 15:33, Olof Johansson wrote:
>> On Wed, Aug 27, 2014 at 3:26 PM, Stephen Boyd wrote:
>>
>>> Is there any reason why the virtual counter can't be read? Maybe we're
>>> the hyp and we need to make sure we don't use the virtual
On Wed, Aug 27, 2014 at 12:29:22PM -0400, Dan Streetman wrote:
> On Wed, Aug 27, 2014 at 11:35 AM, David Horner wrote:
> > On Wed, Aug 27, 2014 at 11:14 AM, Dan Streetman wrote:
> >> On Wed, Aug 27, 2014 at 10:44 AM, David Horner wrote:
> >>> On Wed, Aug 27, 2014 at 10:03 AM, Dan Streetman
Hello,
On Wed, Aug 27, 2014 at 10:03:45AM -0400, Dan Streetman wrote:
> On Tue, Aug 26, 2014 at 10:51 PM, Minchan Kim wrote:
> > Hey Joonsoo,
> >
> > On Wed, Aug 27, 2014 at 10:26:11AM +0900, Joonsoo Kim wrote:
> >> Hello, Minchan and David.
> >>
> >> On Tue, Aug 26, 2014 at 08:22:29AM -0400,
Add a 'dtbs' Makefile target that just builds the device-tree binaries
enabled by the configuration.
Signed-off-by: Andrew Bresticker
---
arch/mips/Makefile | 5 +
arch/mips/boot/.gitignore | 1 +
arch/mips/boot/dts/Makefile | 7 ++-
3 files changed, 12 insertions(+), 1
A long-lasting buffer-cache can distrub page migration so that
it must be allocated from non-movable area.
The journal_init_inode is creating a buffer-cache for superblock journaling.
The superblock exists until system shutdown so that the buffer-cache
for the superblock would also exist for a
Hi Linus,
Nothing major, one core oops fixes, some radeon oops fixes, some sti
driver fixups, msm driver fixes and a minor Kconfig update for the ww
mutex debugging.
Dave.
The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
Linux 3.17-rc2 (2014-08-25 15:36:20
A buffer-cache for superblock is disturbing page migration,
because the buffer-cache is not released until unmount.
The buffer-cache must be allocated from non-movable area.
Signed-off-by: Gioh Kim
---
fs/ext4/super.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
A buffer cache is allocated from movable area
because it is referred for a while and released soon.
But some filesystems are taking buffer cache for a long time
and it can disturb page migration.
New APIs are introduced to allocate buffer cache
with user specific flag.
*_gfp APIs are for user
Because the Tx has the features of stopping queue and aggregation,
We don't need many tx buffers. Change the tx number from 10 to 4
to reduce the usage of the memory. This could save 16K * 6 bytes
memory.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 2 +-
1 file changed, 1
Hello,
This patch try to solve problem that a long-lasting page caches of
ext4 superblock and journaling of superblock disturb page migration.
I've been testing CMA feature on my ARM-based platform
and found that two page caches cannot be migrated.
They are page caches of superblock of ext4
Now all code in processor_core.c is APIC ID related, so rename it as
apic_id.c. Later IOAPIC ID related code will be added into apic_id.c.
Signed-off-by: Jiang Liu
---
drivers/acpi/Makefile |2 +-
drivers/acpi/apic_id.c| 202
Hi,
On Wed, Aug 27, 2014 at 04:28:07PM -0700, Tony Lindgren wrote:
> It's not being used any longer.
>
> Signed-off-by: Tony Lindgren
> ---
> drivers/phy/phy-twl4030-usb.c | 2 --
> drivers/usb/phy/phy-twl6030-usb.c | 2 --
> 2 files changed, 4 deletions(-)
>
> diff --git
On 08/28/2014 10:20 AM, Janet Liu wrote:
Original Message
Subject: Re: [PATCH] staging:lustre:lnet: lib-md.c fix checkpath
warnings and errors.
Date: Tue, 26 Aug 2014 18:22:45 -0700
From: Greg KH
To: Janet Liu
CC: de...@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Enable support of IOAPIC hotplug by:
1) reintroducing ACPI based IOAPIC driver
2) enhance pci_root driver to hook hotplug events
The ACPI IOAPIC driver is always enabled if all of ACPI, PCI and IOAPIC
are enabled.
Signed-off-by: Jiang Liu
---
drivers/acpi/Kconfig|6 ++
Introduce acpi_ioapic_registered() to check whether an IOAPIC has already
been registered, it will be used when enabling IOAPIC hotplug.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |1 +
arch/x86/kernel/acpi/boot.c| 11 +++
arch/x86/kernel/apic/io_apic.c | 11
To support IOAPIC hotplug on x86 and IA64 platforms, OS needs to figure
out global interrupt source number(GSI) and IOAPIC enumeration ID
through ACPI interfaces. So BIOS must implement an ACPI IOAPIC device
with _GSB/_UID or _MAT method to support IOAPIC hotplug. OS also needs
to figure out base
We are going to support ACPI based IOAPIC hotplug, so introduce a rwsem
to protect IOAPIC data structures from IOAPIC hotplug. We choose to
serialize in ACPI instead of in the IOAPIC core because:
1) currently we are only plan to support ACPI based IOAPIC hotplug
2) it's much more cleaner and
Implement acpi_unregister_ioapic() to support ACPI based IOAPIC hot-removal.
An IOAPIC could only be removed when all its pins are unused.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |1 +
arch/x86/kernel/acpi/boot.c| 13 +++---
arch/x86/kernel/apic/io_apic.c |
Refine mp_register_ioapic() to prepare for IOAPIC hotplug by:
1) change return value from void to int.
2) check for gsi range conflicts
3) check for IOAPIC physical address conflicts
4) enhance the way to allocate IOAPIC index
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |4
Implement acpi_register_ioapic() and enhance mp_register_ioapic()
to support ACPI based IOAPIC hot-addition.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/acpi/boot.c| 31 +--
arch/x86/kernel/apic/io_apic.c | 27 ---
2 files changed, 53
From: Yinghai Lu
Split alloc_ioapic_save_registers() from early_irq_init(),
so it will be used per ioapic.
Will call that later for hot-added ioapic controller.
Signed-off-by: Yinghai Lu
Signed-off-by: Jiang Liu
Cc: Joerg Roedel
Cc: Konrad Rzeszutek Wilk
Cc: Sebastian Andrzej Siewior
---
From: Yinghai Lu
We need to parse APIC ID for IOAPIC registration for IOAPIC hotplug.
ACPI _MAT method and MADT table are used to figure out IOAPIC ID, just
like parsing CPU APIC ID for CPU hotplug.
Signed-off-by: Yinghai Lu
Signed-off-by: Jiang Liu
---
drivers/acpi/apic_id.c | 96
From: Yinghai Lu
Perfer the assigned ID in APIC ID register for x86_64 if it's still
available.
Signed-off-by: Yinghai Lu
Cc: Joerg Roedel
Cc: Konrad Rzeszutek Wilk
Cc: Sebastian Andrzej Siewior
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/io_apic.c | 38
Remove __init marker for functions which will be used by IOAPIC hotplug
at runtime.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |4 ++--
arch/x86/kernel/apic/io_apic.c | 14 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git
To keep balance of IOAPIC pin reference count, we need to protect
pirq_enable_irq(), acpi_pci_irq_enable() and intel_mid_pci_irq_enable()
from reentrance. There are two cases which will cause reentrance.
The first case is caused by suspend/hibernation. If pcibios_disable_irq
is called during
Fix minor syntax issues in processor.c to follow coding styles.
Signed-off-by: Jiang Liu
---
drivers/acpi/processor_core.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
index
Private function resource_to_addr() is used to parse ACPI resources
for PCI host bridge. There are public interfaces available for that
purpose, so replace resource_to_addr() with public interfaces.
Reviewed-by: Bjorn Helgaas
Signed-off-by: Jiang Liu
---
arch/x86/pci/acpi.c | 142
Change acpi_dev_resource_address_space() to return failure if the
acpi_resource structure can't be converted to an ACPI address64
structure, so caller could correctly detect failure.
Signed-off-by: Jiang Liu
---
drivers/acpi/resource.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This patch set enhances IOAPIC core and ACPI drivers to support IOAPIC
hotplug on x86 platforms. It's based on latest mainstream kernel at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
You may pull it from
https://github.com/jiangliu/linux.git ioapic/hotplug_v4
We have pick
On Wed, Aug 27, 2014 at 9:32 PM, Dave Airlie wrote:
>> On Wed, Aug 27, 2014 at 3:01 PM, Alex Williamson
>> wrote:
>>> If we assign a Radeon device to a virtual machine, we can no longer
>>> assume a fixed hardware topology, like the GPU having a parent device.
>>> This patch simply adds a few
Because the Tx has the features of stopping queue and aggregation,
We don't need many tx buffers. Change the tx number from 10 to 4
to reduce the usage of the memory. This could save 16K * 10 bytes
memory.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 2 +-
1 file changed, 1
Move the SEAD-3 device-tree to arch/mips/boot/dts/mti/ and update the
Makefiles accordingly. Since SEAD-3 requires the device-tree to be
built into the kernel, select BUILTIN_DTB when building for SEAD-3.
Signed-off-by: Andrew Bresticker
---
arch/mips/Kconfig | 1
Move the Octeon device-trees to arch/mips/boot/dts/cavium-octeon/ and
update the Makefiles accordingly. Since Octeon requires the device-tree
to be built into the kernel, select BUILTIN_DTB as well.
Signed-off-by: Andrew Bresticker
---
arch/mips/Kconfig |
On 8/28/14, Zach Brown wrote:
> On Wed, Aug 27, 2014 at 09:19:36PM +0400, Maxim Patlasov wrote:
>> On 08/27/2014 08:29 PM, Benjamin LaHaise wrote:
>> >On Wed, Aug 27, 2014 at 08:08:59PM +0400, Maxim Patlasov wrote:
>> >...
>> >>1) /dev/loop0 of 3.17.0-rc1 with Ming's patches applied -- 11K iops
In preparation for moving the device-trees to a common location,
introduce the config option BUILTIN_DTB, which can be selected by
platforms that use a device-tree built into the kernel image, and
create a Makefile to build the device-trees in arch/mips/boot/dts/.
Signed-off-by: Andrew Bresticker
To be consistent with other architectures and to avoid unnecessary
makefile duplication, move all MIPS device-trees to arch/mips/boot/dts
and build them with a common makefile. Per Olof's suggestion in v1,
device-trees are grouped into per-vendor subdirectories. Note that
since there is
On Thu, 2014-08-28 at 11:32 +1000, Dave Airlie wrote:
> > On Wed, Aug 27, 2014 at 3:01 PM, Alex Williamson
> > wrote:
> >> If we assign a Radeon device to a virtual machine, we can no longer
> >> assume a fixed hardware topology, like the GPU having a parent device.
> >> This patch simply adds a
On 8/28/14, Maxim Patlasov wrote:
> On 08/21/2014 09:44 AM, Ming Lei wrote:
>> On Wed, Aug 20, 2014 at 4:50 AM, Jens Axboe wrote:
>>
>>>
>>> Reworked a bit more:
>>>
>>> http://git.kernel.dk/?p=linux-block.git;a=commit;h=a323185a761b9a54dc340d383695b4205ea258b6
>> One big problem of the commit
On 08/27/2014 09:32 PM, Eduardo Valentin wrote:
> Hello Wei,
>
> On Wed, Aug 27, 2014 at 10:54:07AM +0800, Wei Ni wrote:
>> On 08/26/2014 08:12 PM, Eduardo Valentin wrote:
>>> On Tue, Aug 26, 2014 at 10:17:29AM +0800, Wei Ni wrote:
On 08/25/2014 07:07 PM, Eduardo Valentin wrote:
> Hello
Hi Chao,
I agree it's correct unlock_new_inode should be located after make_bad_inode.
About this scenario,
I think we should check some condition if this could be occured;
A inode allocated newly could be victim by gc thread.
Then, f2fs_iget called by Thread A have to fail because we handled it
The else condition is redundant after a return. Remove these redundant else
conditions.
Signed-off-by: Fred Chou
---
drivers/staging/vme/devices/vme_pio2_gpio.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/vme/devices/vme_pio2_gpio.c
We need use the hrtimer, which need the arch-timer to be 'always-on'
Signed-off-by: Kever Yang
---
arch/arm/boot/dts/rk3288.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 5950b0a..698e6ea 100644
---
(2014/08/27 23:16), Hannes Reinecke wrote:
On 08/08/2014 01:50 PM, Yoshihiro YUNOMAE wrote:
Previous printk messages of SCSI command can be mixed into other printk
messages because multiple printk messages are output for it. To avoid the
problem, patch 4e64bb8d6 in Hannes' branch(*1) introduced
On Tue, Aug 19, 2014 at 09:20:38PM -0700, Eric W. Biederman wrote:
> Cong Wang writes:
>
> > I saw the following kernel warning:
>
> Cong thanks for finding and tracking this. I was clearly asleep at the
> switch when I was testing my fix to the nfs client code :(
>
> I have applied this
(2014/08/27 23:16), Hannes Reinecke wrote:
On 08/08/2014 01:50 PM, Yoshihiro YUNOMAE wrote:
There are no mean that additional sense code and additional sense code
qualifier
are output as different messages of sense key, so those information
are added.
Note:
scsi_show_extd_sense() is changed
(2014/08/27 23:15), Hannes Reinecke wrote:
On 08/08/2014 01:50 PM, Yoshihiro YUNOMAE wrote:
Previous sense messages can be mixed into other sense messages,
because continuous printk (KERN_CONT) was used. To avoid the problem,
patch d87f3a6f51 introduced a local buffer in Hannes's baranch (*1).
(2014/08/27 23:12), Hannes Reinecke wrote:
On 08/08/2014 01:50 PM, Yoshihiro YUNOMAE wrote:
Current SCSI trace has hostbyte table and driverbyte table, so we
don't need to
have the same table in scsi/constants.c.
- Result examples
(printk)
sd 2:0:0:0: [sda] Result: hostbyte=DID_OK
The general form for commit id and description is
'Commit <12+hexdigits> ("commit description/subject line")'
But commit logs often have relatively long commit ids and
the commit description is on a separate line like:
Some explanation as to why commit <12+hexdigits>
("commit
On Wed, Aug 13, 2014 at 5:03 PM, Andy Lutomirski wrote:
> Currently, creating a new mount (as opposed to bindmount) in a
> non-root userns will implicitly set nodev unless the fs is devpts.
> Something like this will be necessary for file systems that allow
> the mounter to create device nodes
> On Wed, Aug 27, 2014 at 3:01 PM, Alex Williamson
> wrote:
>> If we assign a Radeon device to a virtual machine, we can no longer
>> assume a fixed hardware topology, like the GPU having a parent device.
>> This patch simply adds a few pci_is_root_bus() tests to avoid passing
>> a NULL pointer
On 08/27/2014 02:46 PM, Andrew Morton wrote:
> I assume (because I wasn't told!) that there are two objectives here:
>
> 1) reduce memory consumption by not maintaining pagecache and
> 2) reduce CPU cost by avoiding the double-copies.
>
> These things are pretty easily quantified. And really
On Wed, Aug 27, 2014 at 09:39:21AM +0100, Lee Jones wrote:
> On Wed, 27 Aug 2014, Gyungoh Yoo wrote:
> > On Tue, Aug 26, 2014 at 09:22:58AM +0100, Lee Jones wrote:
> > > On Mon, 25 Aug 2014, Gyungoh Yoo wrote:
> > > > On Thu, Aug 21, 2014 at 10:45:02AM +0100, Lee Jones wrote:
> > > > > When you
Hi Laura,
On Wed, 27 Aug 2014 17:56:13 -0700 Laura Abbott wrote:
>
> I sent fixes for this to Andrew yesterday, did those not get picked up
> or fix the problem?
Things do not migrate to mmotm (and hence linux-next) very quickly
(depending on Andrew's load). I don't remember seeing the fix
On Wed, 2014-08-27 at 10:01 +0200, Peter Feuerer wrote:
> Zhang Rui writes:
>
> > On Tue, 2014-07-22 at 17:37 +0200, Peter Feuerer wrote:
> >> acerhdf has been doing an on-off fan control using hysteresis by
> >> post-manipulating the outcome of thermal subsystem trip point handling.
> >> This
On Wed, Aug 27, 2014 at 11:51 AM, Oleg Nesterov wrote:
>
> Who can review this? And where should I send FPU changes?
FWIW, I have nothing against this series (or, indeed, the last series
with the exception of 2/5 that got replaced by just the preemption
disable).
Although with the whole i387
>
> Hi Weike,
>
> I tried out these patches on the current master branch (v3.17-rc2-9-g68e3702)
> with a socfpga cyclone5 board.
>
> If I apply all 3 patches, the kernel doesn't boot.
>
> If I rebuild with only the first patch, I get only one gpio block showing up
> (should
> have 3 for this
From: Andreea-Cristina Bernat
Date: Tue, 26 Aug 2014 16:46:32 +0300
> According to RCU_INIT_POINTER()'s block comment 3.a, it can be used if
> "3. The referenced data structure has already been exposed to readers either
> at compile time or via rcu_assign_pointer() -and-
> a. You have not
In tg3_set_ringparam(), the tx_pending test to cover the cases where
tg3_tso_bug() is entered has two problems
1) the check is only done for certain hardware whereas the workaround
is now used more broadly. IOW, the check may not be performed when it
is needed.
2) the check is too optimistic.
For
It is duplicated. Also, the first instance in tg3_start_xmit() is racy.
Consider:
tg3_start_xmit()
if budget <= ...
tg3_tx()
(free up the entire ring)
tx_cons =
The rest of the driver assumes at least one free descriptor in the tx ring.
Therefore, since an skb with max frags takes up (MAX_SKB_FRAGS + 1)
descriptors, tx_pending must be > (MAX_SKB_FRAGS + 1).
Signed-off-by: Benjamin Poirier
---
Changes v1->v2
Moved ahead in the series from 3/3 to 2/3, no
tx_pending may be set by the user (via ethtool -G) to a low enough value that
TG3_TX_WAKEUP_THRESH becomes smaller than MAX_SKB_FRAGS + 1. This may cause
the tx queue to be waked when there are in fact not enough descriptors to
handle an skb with max frags. This in turn causes tg3_start_xmit() to
Thermal is TS-ADC Controller module supports user-defined mode and automatic
mode.
User-defined mode refers,TSADC all the control signals entirely by software
writing to register for direct control.
Automaic mode refers to the module automatically poll TSADC output,and the
results
Were
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288-evb.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288-evb.dtsi
b/arch/arm/boot/dts/rk3288-evb.dtsi
index 2964370..fe85dde 100644
--- a/arch/arm/boot/dts/rk3288-evb.dtsi
+++
Changes in v3:(add dts configure)
* address comments from Dmitry Torokhov and Arnd Bergmann:
- fix clock-names in rockchip-thermal.txt
- remove rockchip_thermal_control() in rockchip_set_mode()
- fix some code style.
- add dts configure.
Changes in v2:
This add the necessary binding documentation for the thermal
found on Rockchip SoCs
Signed-off-by: zhaoyifeng
Signed-off-by: Caesar Wang
---
.../devicetree/bindings/thermal/rockchip-thermal.txt | 20
1 file changed, 20 insertions(+)
create mode 100644
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 36be7bb..3d672e3 100644
--- a/arch/arm/boot/dts/rk3288.dtsi
+++ b/arch/arm/boot/dts/rk3288.dtsi
On 08/27/14 15:33, Olof Johansson wrote:
> On Wed, Aug 27, 2014 at 3:26 PM, Stephen Boyd wrote:
>
>> Is there any reason why the virtual counter can't be read? Maybe we're
>> the hyp and we need to make sure we don't use the virtual timer so that
>> the guest can use it, but that doesn't have any
1 - 100 of 1630 matches
Mail list logo
