Removed various checkpatch.sh warnings and errors.
Split patch by warning/error type.
Corrected line wraps in emails.
Signed-off-by: Ben Minerds
---
drivers/usb/serial/keyspan.c | 106 +-
1 files changed, 53 insertions(+), 53 deletions(-)
diff --git
On Wed 11 July 2012 15:36:25 Federico Vaga wrote:
> Hi Hans,
>
> Thank you for your review
>
> > > +static int adv7180_init_controls(struct adv7180_state *state)
> > > +{
> > > + v4l2_ctrl_handler_init(>ctrl_hdl, 2);
> >
> > 2 -> 4, since there are 4 controls. It's a hint only, but it helps
> >
On 07/11/2012 07:29 PM, Raghavendra K T wrote:
On 07/11/2012 02:30 PM, Avi Kivity wrote:
On 07/10/2012 12:47 AM, Andrew Theurer wrote:
For the cpu threads in the host that are actually active (in this case
1/2 of them), ~50% of their time is in kernel and ~43% in guest. This
is for a no-IO
On 07/11/2012 02:30 PM, Avi Kivity wrote:
On 07/10/2012 12:47 AM, Andrew Theurer wrote:
For the cpu threads in the host that are actually active (in this case
1/2 of them), ~50% of their time is in kernel and ~43% in guest. This
is for a no-IO workload, so that's just incredible to see so
On 07/11/2012 02:03 AM, Minchan Kim wrote:
> On 07/03/2012 06:15 AM, Seth Jennings wrote:
>> zsmapbench measures the copy-based mapping at ~560 cycles for a
>> map/unmap operation on spanned object for both KVM guest and bare-metal,
>> while the page table mapping was ~1500 cycles on a VM and ~760
Daniel Lezcano writes:
> On 06/18/2012 08:15 PM, Colin Cross wrote:
>> On Mon, Jun 18, 2012 at 1:40 AM, Daniel Lezcano
>> wrote:
>>> I propose to host a cpuidle-next tree where all these modifications will
>>> be and where people can send patches against, preventing last minutes
>>> conflicts
The following changes since commit 6887a4131da3adaab011613776d865f4bcfb5678:
Linux 3.5-rc5 (2012-06-30 16:08:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-3.5-rc6
for you to fetch changes up to
The following changes since commit 6887a4131da3adaab011613776d865f4bcfb5678:
Linux 3.5-rc5 (2012-06-30 16:08:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.5-rc6
for you to fetch changes up to
The following changes since commit bd0a521e88aa7a06ae7aabaed7ae196ed4ad867a:
Linux 3.5-rc6 (2012-07-07 17:23:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-3.5-rc6
for you to fetch changes up to
On Wed, Jul 11, 2012 at 11:07:56AM +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 11, 2012, Greg KH wrote:
> > On Sun, Apr 29, 2012 at 10:44:16PM +0200, Rafael J. Wysocki wrote:
> > > From: Oleksij Rempel
> > >
> > > This patch makes _SxD/_SxW check follow the ACPI 4.0a specification
> > >
From: "Javier M. Mellid"
This patchs renames index var on sm712vga_setup.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/sm7xxfb/sm7xxfb.c
On 06/20/2012 10:56 AM, Xiao Guangrong wrote:
> Changlog:
> - always atomicly update the spte if it can be updated out of mmu-lock
> - rename spte_can_be_writable() to spte_is_locklessly_modifiable()
> - cleanup and comment spte_write_protect()
>
> Performance result:
> (The benchmark can be
From: "Javier M. Mellid"
This patch renames sm712vga_setup to sm7xx_vga_setup. sm7xx_vga_setup
process command line options in order to get the vga parameter. This
parameter will be the lookup index to match the right vesa mode. It is
chip independent.
Signed-off-by: Javier M. Mellid
---
From: "Javier M. Mellid"
sm712_set_timing handles timing for 0x710, 0x712 and 0x720 chips. This
patch renames the name of the function of sm712_set_timing to
sm7xx_set_timing.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c | 24
From: "Javier M. Mellid"
This patch improves coding style on smtc_alloc_fb_info.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git
From: "Javier M. Mellid"
This patch keeps smtc_set_timing and sm7xx_set_timing functions closed
to smtcfb_setmode. This change eases reviewing and maintaining this
logic path.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c | 238
From: "Javier M. Mellid"
This patch moves pseudo palette into smtcfb_info struct.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/sm7xxfb/sm7xxfb.c
From: "Javier M. Mellid"
This patch keeps code related to sm7xx_vga_setup closed. It is useful to
understand/maintain the logic behind sm7xx_vga_setup with a simple look.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c | 106
From: "Javier M. Mellid"
This patchset is part of the effort to get sm7xxfb in shape. It resolves
some issues in functions related with mode setting and timing logic
paths.
The first 5 patches work on sm712vga_setup in order to get a more
coherent and clear code.
Patches 6 and 7 work on timing
From: "Javier M. Mellid"
This patch renames structs related to vesa modes in order to get more
readable code on sm712vga_setup.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
drivers/staging/sm7xxfb/sm7xxfb.c | 24 +---
1 file changed, 13 insertions(+), 11
From: "Javier M. Mellid"
This change of name improves readability on sm712_vga_setup and
smtcfb_pci_probe. It is coherent with the name of vars being used on
code while avoiding the use of extra long lines in functions.
Tested with SM712.
Signed-off-by: Javier M. Mellid
---
A few sparse warnings fire in drivers/iommu/amd_iommu_init.c.
Fix most of them with this patch. Also fix the sparse
warnings in drivers/iommu/irq_remapping.c while at it.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |2 +-
drivers/iommu/amd_iommu_init.c | 16
To easily map device ids to interrupt remapping table
entries a new lookup table is necessary.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 16
drivers/iommu/amd_iommu_types.h |9 +
2 files changed, 25 insertions(+)
diff --git
On Wed 11-07-12 21:24:41, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Since hierachical_memory_limit shows "of bytes of memory limit with
> regard to hierarchy under which the memory cgroup is", the count should
> calculate max hierarchy limit when use_hierarchy in order to show hierarchy
> subtree
This makes it easier to propagate errors while parsing the
IVRS table and makes the amd_iommu_init_err hack obsolete.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 118 ++--
1 file changed, 66 insertions(+), 52 deletions(-)
diff --git
This flag will show whether the interrupt is remapped in a
way that works for VT-d and AMD-Vi.
Cc: x...@kernel.org
Cc: Yinghai Lu
Cc: Suresh Siddha
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/hw_irq.h |1 +
arch/x86/kernel/apic/io_apic.c |2 +-
The message belongs there anyway, so move it to that
function.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |5 +
drivers/iommu/amd_iommu_init.c |8
2 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/iommu/amd_iommu.c
From: Jan Kara
The last user of ext4_mark_super_dirty() in ext4_file_open() is so rare it
can well be modifying the superblock properly by journalling the change.
Change it and get rid of ext4_mark_super_dirty() as it's not needed anymore.
Artem: small amendments.
Artem: tested using xfstests
From: Artem Bityutskiy
This patch changes the 'ext4_handle_dirty_super()' function which submits
the superblock for I/O in the following cases:
1. When creating the first large file on a file system without
EXT4_FEATURE_RO_COMPAT_LARGE_FILE feature.
2. When re-sizing the file-system.
3. When
From: Artem Bityutskiy
The '__ext4_handle_dirty_metadata()' does not need the 'now' argument anymore
and we can kill it.
Signed-off-by: Artem Bityutskiy
Reviewed-by: Jan Kara
---
fs/ext4/ext4_jbd2.c |3 +--
fs/ext4/ext4_jbd2.h |7 ++-
fs/ext4/inode.c |2 +-
From: Artem Bityutskiy
We do not depend on VFS's '->write_super()' anymore and do not need the
's_dirt' flag anymore, so weed out 'ext4_write_super()' and 's_dirt'.
Signed-off-by: Artem Bityutskiy
Reviewed-by: Jan Kara
---
fs/ext4/super.c | 10 --
1 files changed, 0 insertions(+),
This patch-set makes ext4 file-system stop using the VFS '->write_supers()'
call-back and the '->s_dirt' superblock field because I plan to remove them
once all users are gone.
What we do in this patch-set is we notice that ext4 does not really needed the
'write_super()' functionality and we can
From: Jan Kara
Commit a0375156 properly notes that superblock doesn't need to be marked
as dirty when only number of free inodes / blocks / number of directories
changes since that is recomputed on each mount anyway. However that comment
leaves some unnecessary markings as dirty in place. Remove
Replace tps65910_misc_init with a dedicated init function for the
32-kHz-crystal input.
Signed-off-by: Johan Hovold
---
Hi Samuel,
How about something like this? My thought with misc_init was that it could be
extended should more simple initialisation like for the ck32k_xtal need to be
done,
This function will initialize everthing necessary so that
devices can do DMA. This includes dma_ops and iommu_ops.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git
Split out the code to parse the ACPI table and setup
relevant data structures into a new function.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |1 -
drivers/iommu/amd_iommu_init.c | 38 +++---
2 files changed, 23 insertions(+), 16
Finally enable interrupt remapping for AMD systems.
Signed-off-by: Joerg Roedel
---
drivers/iommu/irq_remapping.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c
index 9276996..92ce0c7 100644
---
Add the six routines required to setup interrupt remapping
with the AMD IOMMU. Also put it all together into the AMD
specific irq_remap_ops.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 18 +
drivers/iommu/amd_iommu_init.c | 42
When the IOMMU is enabled very early (as with irq-remapping)
some devices are still in BIOS hand. When dma is blocked
early this can cause lots of IO_PAGE_FAULTs. So delay the
DMA initialization and do it right before the dma_ops are
initialized.
To be secure, block all interrupts by default when
Split the enable_iommus() routine so that a part of it can
run in early code.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/amd_iommu_init.c
This function will be called before the PCI subsystem is
initialized. Therefore dev_name doen't work and IOMMU
information can't be printed to the klog as before. Move the
code to print that information to a later point where PCI
initializtion has already happened.
Signed-off-by: Joerg Roedel
Add a data structure to store information the IOMMU driver
can use to get from a 'struct irq_cfg' to the remapping
entry.
Cc: x...@kernel.org
Cc: Yinghai Lu
Cc: Suresh Siddha
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/hw_irq.h | 14 +-
When the IOAPIC information provided in the IVRS table is
not correct or not complete the system may not boot at all
when interrupt remapping is enabled. So check if this
information is correct and print out a firmware bug message
when it is not.
Signed-off-by: Joerg Roedel
---
For interrupt remapping the relevant IOMMU initialization
needs to run earlier at boot when the PCI subsystem is not
yet initialized. To support that this patch splits the parts
of IOMMU initialization which need PCI accesses out of the
initial setup path so that this can be done later.
The IVRS ACPI table provides information about the IOAPICs
and the HPETs available in the system and which PCI device
ID they use in transactions. Save that information for later
usage in interrupt remapping.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |3 ++
Add routine to invalidate the IOMMU cache for interupt
translations. Also include the IRTE caches when flushing all
IOMMU caches.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 27 +++
drivers/iommu/amd_iommu_types.h |1 +
2 files changed, 28
Add a routine to setup a HPET MSI interrupt for remapping.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
index 9a24a1b..ac6e731 100644
---
Add the routine to setup interrupt remapping for ioapic
interrupts. Also add a routine to change the affinity of an
irq and to free an irq allocation for interrupt remapping.
The last two functions will also be used for MSI interrupts.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |
Print an indicator to dmesg to easily find out if interrupt
remapping is enabled of a given system.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
index
The IVRS table usually includes the IOMMU device. But the
IOMMU does never translate itself, so make sure the IOMMU
driver knows this.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/iommu/amd_iommu_init.c
Add routines to setup interrupt remapping for MSI
interrupts.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 74 +
1 file changed, 74 insertions(+)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
index
Do not deinitialize the AMD IOMMU driver completly when
interrupt remapping is already in use but the initialization
of the DMA layer fails for some reason. Make sure the IOMMU
can still be used to remap interrupts.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 40
The irq remapping tables for the AMD IOMMU need to be
aligned on a 128 byte boundary. Create a seperate slab-cache
to guarantee this alignment.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |2 ++
drivers/iommu/amd_iommu_init.c | 23 +++
Hi,
here is the second and revised patch-set to add interrupt remapping
support to the AMD IOMMU driver.
Changes v1->v2:
* Improved print_iommu_info() function as suggested by Joe
Perches
* Fixed all five problems reported by Fengguang Wu from Intel,
thanks
Report the availability of irq remapping through the
IOMMU-API to allow KVM device passthrough again without
additional module parameter overrides.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/iommu/amd_iommu.c
Add routines to:
* Alloc remapping tables and single entries from these
tables
* Change entries in the tables
* Free entries in the table
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 230 +
1 file changed, 230 insertions(+)
diff
This step makes it very easy to keep track about the current
intialization state of the iommu driver. With this change we
can initialize the IOMMU hardware to a point where it can
remap interrupts and later resume the initializion to enable
dma remapping.
Signed-off-by: Joerg Roedel
---
On 07/11/2012 03:25 PM, Arnd Bergmann wrote:
> On Wednesday 11 July 2012, Roland Stigge wrote:
>> OK, thanks!
>>
>> Is a patch on top of the already provided lpc32xx-next branches the
>> preferred form for a fix? On top of which branch do you need it?
>>
>
> Yes, I think in this case, changing it
On Wed, 2012-07-11 at 09:05 -0400, Prarit Bhargava wrote:
>
> Both of those options seem like a lot of work for something that happens once
> every 3-4 years, and may not happen ever again[1]. Based on that statement,
> if
> we're going to modify code I would prefer that it be as lightweight as
I am working on a kernel module to monitor all TCP packets. I created a protocol
handler with protocol code ETH_P_ALL to handle all incoming and outgoing
TCP packets. The code worked fine on 2.6.14 kernel, but in current 3.2.0-26
kernel, I am no longer able to get the TCP payload for outgoing
Hello,
we've recently hit a deadlock in our QA runs which is caused by the
per-process plugging code. The problem is as follows:
process A process B (kjournald)
generic_file_aio_write()
blk_start_plug();
...
somewhere in here we allocate
On 7/11/12 3:53 AM, Gleb Natapov wrote:
On Wed, Jul 11, 2012 at 11:49:47AM +0200, Peter Zijlstra wrote:
On Wed, 2012-07-11 at 10:10 +0300, Gleb Natapov wrote:
Looks like Avi is right about the overshoot. Can you test something like this?
I head to the airport in a few minutes; I'll try it
On 06/21/2012 04:48 AM, Xiao Guangrong wrote:
> On 06/20/2012 10:11 PM, Takuya Yoshikawa wrote:
>
>
>> We can change the debug message later if needed.
>
>
> Actually, i am going to use tracepoint instead of
> these debug code.
Yes, these should be in the kvmmmu namespace.
--
error
Hi Hans,
Thank you for your review
> > +static int adv7180_init_controls(struct adv7180_state *state)
> > +{
> > + v4l2_ctrl_handler_init(>ctrl_hdl, 2);
>
> 2 -> 4, since there are 4 controls. It's a hint only, but it helps
> optimizing the internal hash data structure.
Sure :)
> >
> > @@
On Wed, 2012-07-11 at 12:11 +0200, Jan Kara wrote:
> > > So case 2.b is a bit controversial, but I think it is acceptable. After
> > > all, by
> > > enabling checksumming we already sign up for paying the price of
> > > calculating
> > > it. The way to improve checksumming performance globally
> -Original Message-
> From: Joerg Roedel [mailto:joerg.roe...@amd.com]
> Sent: Wednesday, July 11, 2012 5:47 PM
> To: Sethi Varun-B16395
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 2/7] iommu/amd: Implement DOMAIN_ATTR_GEOMETRY
> attribute
On Wed, Jul 11, 2012 at 01:10:01PM +0100, Krystian Garbaciak wrote:
> Fix typo for case REGULATOR_STATUS_STANDBY -> REGULATOR_MODE_STANDBY.
> For undefined mode, return REGULATOR_STATUS_ERROR (0 is not valid status).
This is deliberate. It's not reporting an error, it's reporting an
On Wednesday 11 July 2012, Roland Stigge wrote:
> OK, thanks!
>
> Is a patch on top of the already provided lpc32xx-next branches the
> preferred form for a fix? On top of which branch do you need it?
>
Yes, I think in this case, changing it on top of that branch is best.
I'm not sure how that
From: Wanpeng Li
Since hierachical_memory_limit shows "of bytes of memory limit with
regard to hierarchy under which the memory cgroup is", the count should
calculate max hierarchy limit when use_hierarchy in order to show hierarchy
subtree limit. hierachical_memsw_limit is the same case.
Looks nice.. How about something like the below on top.. I couldn't
immediately find a sane reason for the grand-parent to always be red in
the insertion case.
---
--- a/lib/rbtree.c
+++ b/lib/rbtree.c
@@ -23,6 +23,25 @@
#include
#include
+/*
+ * red-black trees properties:
On 07/11/2012 04:06 AM, Axel Lin wrote:
> Current code has been converted to use regmap APIs, the io_mutex is not
> needed.
> Thus remove the io_mutex.
>
> Signed-off-by: Axel Lin
Thanks for cleanup,
Acked-by: Peter Ujfalusi
--
To unsubscribe from this list: send the line "unsubscribe
On Wed, 11 Jul 2012 12:57:55 +0100, Catalin Marinas
wrote:
> On Wed, Jul 11, 2012 at 12:28:29PM +0100, Arnd Bergmann wrote:
>> On Wednesday 11 July 2012, James Bottomley wrote:
>> > Hi All,
>> >
>> > We have set aside the second day of the kernel summit (Tuesday 28
>> > August) as mini-summit
According to the Wikipedia article on CUBIC, it's used in Linux kernels
2.6.19 and above. Is that still the case? Are there any plans to use a
different algorithm in the foreseeable future?
Is it as described in the 2008 ACM SIGOPS paper by Ha, Rhee and Xu:
On 07/11/2012 05:21 PM, Raghavendra K T wrote:
On 07/11/2012 03:47 PM, Christian Borntraeger wrote:
On 11/07/12 11:06, Avi Kivity wrote:
[...]
So there is no win here, but there are other cases were diag44 is
used, e.g. cpu_relax.
I have to double check with others, if these cases are
>> I wish there was a nicer way to do this ... but looking at the code I can't
>> figure out a better way. (no offense John, it's just the way the code is ;)
>> )
>
> Yeah, I had the same discussion with Peter earlier today. There is
> only a rather limited set of options.
>
> 1) Retrigger
On Wed, 2012-07-11 at 14:45 +0200, Thomas Gleixner wrote:
> On Wed, 11 Jul 2012, Prarit Bhargava wrote:
> > On 07/10/2012 06:43 PM, John Stultz wrote:
> > > clock_was_set() cannot be called from hard interrupt context because
> > > it calls on_each_cpu(). For fixing the widely reported leap
On Wed, Jul 11, 2012 at 10:36:46AM +0200, Bjørn Mork wrote:
> Greg Kroah-Hartman writes:
> > On Tue, Jul 10, 2012 at 06:51:03PM -0300, Gustavo Padovan wrote:
> >
> >> { USB_VENDOR_AND_INTERFACE_INFO(0x0a5c, 0xff, 0x01, 0x01) }
> >
> > Two entries in the cdc_wdm driver can also be converted to use
[34323.844970] [ cut here ]
[34323.84] kernel BUG at kernel/timer.c:711!
[34323.846110] invalid opcode: [#1] PREEMPT SMP
[34323.846657] CPU 6
[34323.846670] Modules linked in:
[34323.853968] ebtables
[34323.866941] xt_cpu
[34323.890355] msdos
[34323.920927]
On Wed, Jul 11, 2012 at 08:36:16PM +0800, Fengguang Wu wrote:
> On Wed, Jul 11, 2012 at 12:49:24AM -0700, Paul E. McKenney wrote:
> > On Tue, Jul 10, 2012 at 12:47:00PM +0800, Fengguang Wu wrote:
> > > Hi Paul,
> > >
> > > Fortunately this bug is bisectable and the first bad commit is:
> > >
> >
On Wed, Jul 11, 2012 at 01:07:17PM +0300, Valentin, Eduardo wrote:
> Hello Greg,
>
> On Mon, Jul 9, 2012 at 11:33 PM, Valentin, Eduardo
> wrote:
> > Hello Greg,
> >
> > On Mon, Jul 9, 2012 at 10:31 PM, Greg Kroah-Hartman
> > wrote:
> >> On Sat, Jul 07, 2012 at 10:57:49AM +0300, Eduardo Valentin
于 2012年07月11日 20:11, Neil Horman 写道:
> On Wed, Jul 11, 2012 at 04:30:06PM +0800, Gao feng wrote:
>> there are some out of bound accesses in netprio cgroup.
>>
>> now before accessing the dev->priomap.priomap array,we only check
>> if the dev->priomap exist.and because we don't want to see
>>
On 07/11/2012 02:52 PM, Alexander Graf wrote:
>
> On 11.07.2012, at 13:23, Avi Kivity wrote:
>
>> On 07/11/2012 02:16 PM, Alexander Graf wrote:
> yes the data structure itself seems based on the algorithm
> and not on arch specific things. That should work. If we move that to
On Wed, 11 Jul 2012, Prarit Bhargava wrote:
> On 07/10/2012 06:43 PM, John Stultz wrote:
> > clock_was_set() cannot be called from hard interrupt context because
> > it calls on_each_cpu(). For fixing the widely reported leap seconds
> > issue it's necessary to call it from the timer interrupt
- Original Message -
> >
> > Hm, suppose we're the next-in-line for a ticket lock and exit due
> > to
> > PLE. The lock holder completes and unlocks, which really assigns
> > the
> > lock to us. So now we are the lock owner, yet we are marked as
> > don't
> > yield-to-us in the PLE
On 07/11/2012 02:33 PM, Arnd Bergmann wrote:
> On Wednesday 11 July 2012, Roland Stigge wrote:
>> Thanks for the note! Looks like the interface consolidated to replace
>> ch->cd->min_signal with sth. like cd->min_signal directly.
>>
>> Accessing the signal id/number is/was quite convenient because
On Wed, Jul 11, 2012 at 12:49:24AM -0700, Paul E. McKenney wrote:
> On Tue, Jul 10, 2012 at 12:47:00PM +0800, Fengguang Wu wrote:
> > Hi Paul,
> >
> > Fortunately this bug is bisectable and the first bad commit is:
> >
> > commit 9b2e4f1880b789be1f24f9684f7a54b90310b5c0
> >
On Wednesday 11 July 2012, Roland Stigge wrote:
> Thanks for the note! Looks like the interface consolidated to replace
> ch->cd->min_signal with sth. like cd->min_signal directly.
>
> Accessing the signal id/number is/was quite convenient because as you
> can see in the 3 above cases that now
No waiting is needed for mac_ocp_{write / read}. And the bit 31 of
OCPDR would not change, so rtl_udelay_loop_wait_high always return
false. That is, the r8168_mac_ocp_read always retuen ~0.
Signed-off-by: Hayes Wang
---
drivers/net/ethernet/realtek/r8169.c | 12 +---
1 file changed,
> --- /dev/null
> +++ b/include/linux/mfd/samsung/core.h
> @@ -0,0 +1,147 @@
> +/*
> + * core.h
> + *
> + * copyright (c) 2011 Samsung Electronics Co., Ltd
> + * http://www.samsung.com
In most of the files you mentioned 2011.
Should they not be changed to 2012?
> + *
> + * This
Hi,
I see the same build-error as Randy in latest linux.git
(055c9fa8874fa7261eec7a268366565db84af474).
Where is this patch queued up (see original posting)?
I do not see any patch in [2].
And please please please rename your repo... "linux-2.6" died many
months ago :-).
I also do not see any
H Hartley Sweeten's recent series of patches to clean up the rtd520
driver made some of the register accesses harder to understand. Add a
few comments to provide some clues to the reader.
Signed-off-by: Ian Abbott
Cc: H Hartley Sweeten
Cc: Greg Kroah-Hartman
---
To be applied after Hartley's
Fix typo for case REGULATOR_STATUS_STANDBY -> REGULATOR_MODE_STANDBY.
For undefined mode, return REGULATOR_STATUS_ERROR (0 is not valid status).
Signed-off-by: Krystian Garbaciak
---
drivers/regulator/core.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi,
> Hi Masatake,
>
> On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
>> (The patch sets are rebased to bluetooth-next. Unnecessary white
>> spaces are trimmed.)
>>
>> lsof command can tell the type of socket processes are using.
>> Internal lsof uses inode numbers on socket
Hi Sethi,
On Wed, Jul 11, 2012 at 11:47:39AM +, Sethi Varun-B16395 wrote:
> I am currently working on upstreaming the Freescale IOMMU driver. As
> discussed (with Scott Wood) a while back, this representation of the
> GEOMETRY attribute doesn't go well with our IOMMU implementation. Our
>
Hello.
On 10-07-2012 10:32, Gerard Snitselaar wrote:
commit ff9cce82 added back 2 lines that were removed by commit
c83a8542
Please also specify the summaries of those 2 commits in parens.
causing build of twl6030-usb to get an error due to otg being
referenced, but not declared. This
On 07/10/2012 06:43 PM, John Stultz wrote:
> Over the weekend, Thomas got a chance to review the leap second fix
> in more detail and had a few additional changes he wanted to make
> to improve performance as well as style.
>
> So this iteration includes his modifications.
>
> Once merged,
On 07/10/2012 06:43 PM, John Stultz wrote:
> clock_was_set() cannot be called from hard interrupt context because
> it calls on_each_cpu(). For fixing the widely reported leap seconds
> issue it's necessary to call it from the timer interrupt context.
>
> Provide a new function which denotes it
Hi Russell,
On Thu, Jul 5, 2012 at 10:50 AM, Gupta, Ramesh wrote:
> From 393c4effbbec74ff9b969d53ce4d36fde56b71df Mon Sep 17 00:00:00 2001
> From: Ramesh Gupta G
> Date: Wed, 4 Jul 2012 16:43:41 +0530
> Subject: [PATCH v4 0/2] add new cache maintenance api
>
> This patch series is the next
On Wed, Jul 11, 2012 at 04:30:06PM +0800, Gao feng wrote:
> there are some out of bound accesses in netprio cgroup.
>
> now before accessing the dev->priomap.priomap array,we only check
> if the dev->priomap exist.and because we don't want to see
> additional bound checkings in fast path, so we
File: rtl_nic/rtl8168g-1.fw
Version: 0.0.2
Change the ocp_base of linux driver to OCP_STD_PHY_BASE after setting
firmware. The firmware would modify the ocp_base, and that results the
driver uses the wrong ocp_base to access standard phy after setting
firmware.
Signed-off-by: Hayes Wang
---
401 - 500 of 1348 matches
Mail list logo
