This patch adds simple python to display vhost satistics of vhost, the codes
were based on kvm_stat script from qemu. As work function has been recored,
filters could be used to distinguish which kinds of work are being executed or
queued:
vhost statistics
vhost_virtio_update_used_idx
To help performance analyze and debugging, this patch introduces
tracepoints for vhost_net. Two tracepoints were introduced, packets
sending and receiving.
Signed-off-by: Jason Wang
---
drivers/vhost/net.c | 5 +
drivers/vhost/net_trace.h | 53
Signed-off-by: Jason Wang
---
drivers/vhost/net.c | 1 +
drivers/vhost/vhost.h | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
index a0fa5de..85d666c 100644
--- a/drivers/vhost/net.c
+++ b/drivers/vhost/net.c
@@ -708,6 +708,7 @@ static int
The "secondary irq" in the nomadik pin control driver is actually
not secondary (as in: can occur any time alongside the ordinary
irq), it is a latent IRQ. It is an IRQ that has occurred when
the system was in sleep state and has been cached in a special
register flagged from the low power
The old platform data struct is just a leftover from the times
when the driver was not probed exclusively from the device tree.
Factor this into the general state container and simplify the
probe path.
Signed-off-by: Linus Walleij
---
drivers/pinctrl/pinctrl-nomadik.c | 39
On Thu, 2014-03-20 at 19:32 +, Zoltan Kiss wrote:
> Ian made some late comments about the grant mapping series, I incorporated the
> outcomes into this patch. Additional comments, refactoring etc.
I don't know how davem feels about merging these kinds of thing into one
patch but from my point
> >>This patch adds led-flash support to Maxim max77693 chipset.
> >>Device can be exposed to user space through LED subsystem
> >>sysfs interface or through V4L2 subdevice when the support
> >>for Multimedia Framework is enabled. Device supports up to
> >>two leds which can work in flash and
On Thu, 2014-03-20 at 19:32 +, Zoltan Kiss wrote:
> Since the early days TX stops if there isn't enough free pending slots to
> consume a maximum sized (slot-wise) packet. Probably the reason for that is to
> avoid the case when we don't have enough free pending slot in the ring to
> finish
>
This ensures that IRR bits are set in the KVM_GET_IRQCHIP result only if
the interrupt is still sitting in the IOAPIC. After the next patches, it
avoids spurious reinjection of the interrupt when KVM_SET_IRQCHIP is
called.
Reviewed-by: Alex Williamson
Signed-off-by: Paolo Bonzini
---
Commonize the handling of masking, which was absent for kvm_ioapic_set_irq.
Setting remote_irr does not need a separate function either, and merging
the two functions avoids confusion.
Reviewed-by: Alex Williamson
Signed-off-by: Paolo Bonzini
---
virt/kvm/ioapic.c | 29
We will reuse it to process a nonzero IRR that is passed to KVM_SET_IRQCHIP.
Reviewed-by: Alex Williamson
Signed-off-by: Paolo Bonzini
---
v1->v2:
more comments
change argument name from level to irq_level
virt/kvm/ioapic.c | 74
To create a global command queue we require that each command put on the
command ring is submitted with a command structure.
Functions that queue commands and wait for completion need to allocate a command
before submitting it, and free it once completed. The following command queuing
functions
After the previous patches, an interrupt whose bit is set in the IRR
register will never be in the LAPIC's IRR and has never been injected
on the migration source. So inject it on the destination.
This fixes migration of Windows guests without HPET (they use the RTC
to trigger the scheduler
Unlike the old qemu-kvm, which really never did that, with new QEMU
it is for some reason somewhat likely to migrate a VM with a nonzero
IRR in the ioapic. In the case of ISA edge-triggered interrupts,
this represents an interrupt that has not left the IOAPIC, which would
be okay but it is not
Create a list to store command structures, add a structure to it every time
a command is submitted, and remove it from the list once we get a
command completion event matching the command.
Callers that wait for completion will free their command structures themselves.
The other command structures
Use one timer to control command timeout.
start/kick the timer every time a command is completed and a
new command is waiting, or a new command is added to a empty list.
If the timer runs out, then tag the current command as "aborted", and
start the xhci command abortion process.
Previously
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 --
drivers/usb/host/xhci-mem.c | 1 -
Hi,
On Thursday, March 20, 2014 08:19:27 PM Hans de Goede wrote:
> Hi,
>
> On 03/20/2014 07:27 PM, Bartlomiej Zolnierkiewicz wrote:
> > [ v1 was named "ata: add remaining new-style AHCI platform drivers"
> > but we are down from 2 drivers to 1 driver so the title of the patch
> > series no
changes since v3:
* Use GFP_ATOMIC in xhci_stop_device() because we hold a spinlock
* Don't queue commands if host is dying.
* Flush command queue when host is dying (delete all commands in queue, call
pending completions/free commands).
changes since v2:
squash first
On Fri, 2014-03-21 at 23:02 +0300, Artem Fetishev wrote:
> Hi all,
>
> I am looking at a use-case when a real-time task (B) of higher
> priority is sometimes preempted by another real-time task (A) of lower
> priority. Well, B is not really preempted. It calls mlockall() which
> forces task B to
From: Scott Wood [mailto:scottw...@freescale.com]
> On Thu, 2014-03-20 at 11:59 +, David Laight wrote:
> > I tried to work out what the 'twi, isync' instructions were for (in
> > in_le32()).
> > The best I could come up with was to ensure a synchronous bus-fault.
> > But bus faults are
On 21 March 2014 14:12, Srivatsa S. Bhat
wrote:
>> You can find some information on this in
>> Documentation/memory-barriers.txt
>
> Yep, I know, I have read it several times, but I'm no expert ;-)
Not me either :) .. That file has so complex stuff in there that its
difficult to
understand
On 20/03/2014 21:39, Sebastian Hesselbarth wrote:
This adds scu and general purpose registers device nodes required for
SMP on Berlin BG2 and BG2Q SoCs. The secondary CPUs will pick their jump
address from general purpose (SW generic) register 1.
Signed-off-by: Sebastian Hesselbarth
On 20/03/2014 21:39, Sebastian Hesselbarth wrote:
This adds SMP support to Marvell Berlin2 SoCs. Secondary CPUs boot into
BootROM, wait for interrupt, and read SW generic register 1 with actual
boot code address. Synchronization by holding pen is copied from
plat-versatile and mach-prima2.
Guenter Roeck skrev 21.3.2014 07:37:
On 03/20/2014 05:02 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.13.7 release.
There are 149 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied,
From: Geert Uytterhoeven
When a serial port is closed, uart_close() takes care of shutting down the
hardware, and powering it down.
When a serial port is unbound while in use, uart_close() bypasses all of
this, as this is supposed to be done through uart_hangup() (invoked via
tty_vhangup() in
Hi Matias,
This looks really interesting and I'd love to get involved. Do you
have any recommendations for what hardware I should pick up?
- Joe
On Thu, Mar 20, 2014 at 11:32:17PM -0700, Matias Bjørling wrote:
> Hi,
>
> Users that have custom firmware SSDs, may choose to expose their flash
On Thu, 20 Mar 2014, Vince Weaver wrote:
> On Thu, 20 Mar 2014, Thomas Gleixner wrote:
> >
> > Yeah, it causes the explosion in the debug object code. This should
> > have been:
> >
> > + trace_printk("Tracking Object free: %s %p %pS\n",
> > +
On 03/21/2014 02:53 AM, Sasha Levin wrote:
On 12/13/2013 04:08 AM, Vlastimil Babka wrote:
On 12/13/2013 09:49 AM, Bob Liu wrote:
On 12/13/2013 05:05 AM, Sasha Levin wrote:
On 12/12/2013 07:41 AM, Vlastimil Babka wrote:
On 12/12/2013 06:03 AM, Bob Liu wrote:
On 12/12/2013 11:16 AM, Sasha
On Fri, 2014-03-21 at 14:54 +0800, Axel Lin wrote:
> Since commit ca5d1b3524b4d
> "regulator: helpers: Modify helpers enabling multi-bit control",
> we can set enable_val setting for device that use multiple bits for control.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/s5m8767.c | 78
Thomas Backlund skrev 21.3.2014 10:42:
Guenter Roeck skrev 21.3.2014 07:37:
On 03/20/2014 05:02 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.13.7 release.
There are 149 patches in this series, all will be posted as a response
to this one. If anyone has
Am 21.03.2014 09:28, schrieb Linus Walleij:
On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler wrote:
But I don't need any rush here, I'm just unable to understand why the -rc
phase isn't used for bug fixing as I believe that's what this phase is for.
Right now it is mostly a practical
(adding Andi Kleen)
On Fri, 2014-03-21 at 09:42 +0100, Jean Delvare wrote:
> Hi Andy, hi Joe,
>
> When running checkpatch on a patch which tweaks many Kconfig entries, I
> got the following output:
>
> WARNING: please write a paragraph that describes the config symbol fully
> #74: FILE:
Jaime T wrote:
> I'd like to use my 1TB Seagate hard disk on my linux box, and I've
> tested it using 3 different usb-sata enclosures.
>
> kernel: [10612.017588] usb 1-1: New USB device found, idVendor=14cd,
> idProduct=6116
> kernel: [10612.017602] usb 1-1: Product: USB Mass Storage Device
>
On 03/21/2014 09:53 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in
> arch/x86/kernel/cpu/perf_event_intel_uncore.c between commit 2c666adacc9e
> ("x86, intel, uncore: Fix CPU hotplug callback registration") from Linus'
> tree and commit
Replace OS_kmalloc/OS_kfree with kmalloc/kfree.
And also some allocation doesn't need to use GFP_DMA
so just use GFP_KERNEL.
c4_new() function is never called, remove it.
Signed-off-by: Daeseok Youn
---
v3: replace kzalloc with kmalloc.
v2: fix subject and comment correctly.
I'm not sure what
Hi Andy, hi Joe,
When running checkpatch on a patch which tweaks many Kconfig entries, I
got the following output:
WARNING: please write a paragraph that describes the config symbol fully
#74: FILE: drivers/hid/Kconfig:142:
config HID_BELKIN
WARNING: please write a paragraph that describes the
On 03/21/2014 01:28 PM, Viresh Kumar wrote:
> On 21 March 2014 13:16, Srivatsa S. Bhat
> wrote:
>> We need this assignment to happen exactly at this point, that is, *after*
>> the call to post_transition() completes and before calling wake_up().
>>
>> If the compiler or the CPU reorders the
On 2014/3/21 10:39, zheng.li wrote:
> 于 2014年03月21日 01:02, Jay Vosburgh 写道:
>> Zheng Li wrote:
>>
>>> Except bond mode 1, in other bond modes, inactive slaves should keep
>>> inactive flag to 1 to refuse to receive broadcast packets. Now, active
>>> slave send broadcast packets (for example ARP
Replaced comparisons on jiffies values with wrap-safe functions.
Signed-off-by: Michalis Pappas
---
drivers/staging/gdm72xx/gdm_usb.c | 2 +-
drivers/staging/gdm72xx/sdio_boot.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/gdm72xx/gdm_usb.c
Removed task related to replacement of kernel_thread with kthread,
as issue was fixed on ff5e4a1d2702582614996f6f6d005e9b5caadeb8.
Signed-off-by: Michalis Pappas
---
drivers/staging/gdm72xx/TODO | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/gdm72xx/TODO
This patch seems to make the bios_corruption_check not to cover the lowest
64kB of memory anymore but only the lowest 4kB. Was this deliberate?
When I use kernel 3.9 or higher I always get low mem corruption message from
the bios corruption checker when I resume from suspend.
Below kernel 3.9 I
Minor white-space fixes as suggested by checkpatch.pl.
Signed-off-by: Michalis Pappas
---
drivers/staging/gdm72xx/gdm_qos.c | 2 +-
drivers/staging/gdm72xx/gdm_wimax.c | 2 ++
drivers/staging/gdm72xx/usb_boot.c | 1 +
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git
The following patches perform various cleanups on the gdm72xx driver.
PATCH 1/3 fixes some small coding style issues
PATCH 2/3 removes an already completed item from the TODO list
PATCH 3/3 replaces some jiffies comparisons with wrap-safe functions
After all patches have been applied, the only
2014-03-21 6:23 GMT+04:00 Steven Rostedt :
> On Thu, 20 Mar 2014 17:02:39 -0400
> Jeff Layton wrote:
>
>> Eventually the server should just allow the read to complete even if
>> the client doesn't respond to the oplock break. It has to since clients
>> can suddenly drop off the net while holding
We free the skb immediately on kick failure during xmit without detaching it
from the virtqueue. This may lead double free for the skb during
free_unused_bufs(). This patch fixes this by not freeing it on kick failure and
let it to be freed through free_unused_bufs().
Fixes
On 03/20/2014 04:28 PM, Richard Purdie wrote:
On Thu, 2014-03-20 at 15:51 +0100, Jacek Anaszewski wrote:
Some LED devices support two operation modes - torch and
flash. This patch provides support for flash LED devices
in the LED subsystem by introducing new sysfs attributes
and kernel internal
On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler wrote:
> But I don't need any rush here, I'm just unable to understand why the -rc
> phase isn't used for bug fixing as I believe that's what this phase is for.
Right now it is mostly a practical issue to me, as I applied the patch to
the devel
Hi,
On Thu, Mar 20, 2014 at 10:05:33AM -0400, j...@ringle.org wrote:
> From: Jon Ringle
>
> The SC16IS7xx is a slave I2C-bus/SPI interface to a single-channel
> high performance UART. The SC16IS7xx’s internal register set is
> backward-compatible with the widely used and widely popular 16C450.
Signed-off-by: Sanjay Singh Rawat
---
drivers/tty/serial/omap-serial.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/tty/serial/omap-serial.c b/drivers/tty/serial/omap-serial.c
index 77f0351..56b61d4 100644
--- a/drivers/tty/serial/omap-serial.c
+++
On 03/20/2014 04:34 PM, Lee Jones wrote:
On Thu, 20 Mar 2014, Jacek Anaszewski wrote:
This patch adds led-flash support to Maxim max77693 chipset.
Device can be exposed to user space through LED subsystem
sysfs interface or through V4L2 subdevice when the support
for Multimedia Framework is
On 21.03.2014 02:39, Peter Hurley wrote:
> Does disabling the fifo on shutdown clear the fifo?
I did not try this, but if my theory is correct, it would
not help, as all this does is reducing the FIFO length
to one character. So you'd still get up to two characters:
one in the "FIFO" - it could
On 20/03/14 20:49, Laurent Pinchart wrote:
>> The CPU is the _controlling_ component - it's the component that has to
>> configure the peripherals so they all talk to each other in the right
>> way. Therefore, the view of it needs to be CPU centric.
>>
>> If we were providing a DT description
On Thu, Mar 20, 2014 at 03:09:03PM +0530, Janani Venkataraman wrote:
> Gencore Daemon
>
> The programs can request a dump using gencore() API, provided through
> libgencore. This is implemented through a daemon which listens on a UNIX File
> socket. The daemon is started immediately post
Current code misses updating the register when enable_shift is 0.
e.g. S2MPA01_BUCK4_RAMP_EN_SHIFT is 0.
Signed-off-by: Axel Lin
---
drivers/regulator/s2mpa01.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/regulator/s2mpa01.c
On Fri, 21 Mar 2014 00:26:12 +0100, Laurent Pinchart
wrote:
> On Thursday 20 March 2014 23:12:50 Grant Likely wrote:
> > On Thu, 20 Mar 2014 19:52:53 +0100, Laurent Pinchart wrote:
> > > Then we might not be talking about the same thing. I'm talking about DT
> > > bindings to represent the
Current code misses updating the register when enable_shift is 0.
e.g. S2MPS11_BUCK9_RAMP_SHIFT and S2MPS11_BUCK6_RAMP_EN_SHIFT are 0.
Signed-off-by: Axel Lin
---
drivers/regulator/s2mps11.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git
> The PM8xxx family of PMICs contain an RTC. This RTC is described as a
> subnode of the PM8xxx. Document these bindings, and replace the pwrkey
> node in the example with the RTC, which is now described in this
> document.
>
> While we're here, add a short description to the device tree
Hi all,
I am looking at a use-case when a real-time task (B) of higher priority is
sometimes preempted by another real-time task (A) of lower priority. Well, B is
not really preempted. It calls mlockall() which forces task B to yield the CPU.
Under certain conditions, mlockall() calls
On Thu, Mar 20, 2014 at 2:21 PM, Richard Cochran
wrote:
> This patch updates the many PTP Hardware Clock drivers with the
> newly introduced field that advertises the number of programmable
> pins. Some of these devices do have programmable pins, but the
> implementation will have to wait for
Here we add the necessary device nodes required for successful device
probing and Pinctrl setup for the FSM when booting on an STiH415 (Orly1)
or STiH416 (Orly2) based b2020 development board.
Acked-by: Srinivas Kandagatla
Acked-by Angus Clark
Acked-by: Brian Norris
Acked-by: Maxime Coquelin
Here we add the necessary device nodes required for successful device
probing and Pinctrl setup for the FSM when booting on an STiH416 (Orly2).
Acked-by: Srinivas Kandagatla
Acked-by Angus Clark
Acked-by: Brian Norris
Acked-by: Maxime Coquelin
Signed-off-by: Lee Jones
---
On 21 March 2014 13:18, Srivatsa S. Bhat
wrote:
> Nitpick: Instead of using 'false' as an argument to _post_transition(),
> you could use '0', since the argument is supposed to be an int. But that's
> minor, I won't insist.
You should :)
I will update that with a Macro actually, to make it more
On 21 March 2014 13:16, Srivatsa S. Bhat
wrote:
> Wonderful! I was going to do this today, but thanks a lot for taking
> care of this for me!
I just wanted to finish this long lasting thread as soon as possible.
> We need this assignment to happen exactly at this point, that is, *after*
> the
* Dimitri Sivanich wrote:
> Fix conditional in gru_exit to match gru_init.
>
> Signed-off-by: Dimitri Sivanich
> ---
> drivers/misc/sgi-gru/grufile.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux/drivers/misc/sgi-gru/grufile.c
>
On 03/14/2014 10:04 PM, Alexey Khoroshilov wrote:
There is request_irq() in init_device(), but the interrupt is not removed
on failure paths. The patch adds proper error handling.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
Hi,
Thanks
* Dimitri Sivanich wrote:
> Set the UV n_lshift value based on the GAM_GR_CONFIG MMR for UV3, making it
> independent of the socket m_val.
>
> Remove unneeded macros.
>
> Signed-off-by: Dimitri Sivanich
> ---
> arch/x86/include/asm/uv/uv_hub.h | 12 -
>
On 03/21/2014 11:04 AM, Viresh Kumar wrote:
> cpufreq_notify_transition() and cpufreq_notify_post_transition() shouldn't be
> called directly by cpufreq drivers anymore and so these should be marked
> static.
>
> Signed-off-by: Viresh Kumar
Reviewed-by: Srivatsa S. Bhat
Regards,
Srivatsa S.
On 03/21/2014 11:04 AM, Viresh Kumar wrote:
> CPUFreq core has new infrastructure that would guarantee serialized calls to
> target() or target_index() callbacks. These are called
> cpufreq_freq_transition_begin() and cpufreq_freq_transition_end().
>
> This patch converts existing drivers to use
On 03/21/2014 11:04 AM, Viresh Kumar wrote:
> From: "Srivatsa S. Bhat"
>
> Whenever we change the frequency of a CPU, we call the PRECHANGE and
> POSTCHANGE
> notifiers. They must be serialized, i.e. PRECHANGE and POSTCHANGE notifiers
> should strictly alternate, thereby preventing two
[...]
diff --git a/drivers/staging/iio/accel/adis16220_core.c
b/drivers/staging/iio/accel/adis16220_core.c
index 6f38ca9..31c7a9d 100644
--- a/drivers/staging/iio/accel/adis16220_core.c
+++ b/drivers/staging/iio/accel/adis16220_core.c
@@ -392,7 +392,8 @@ static const struct iio_info
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140320:
The powerpc tree still had its build failure.
The omap_dss2 tree gained a conflict the pm tree.
The tip tree gained a conflict against Linus' tree.
The akpm tree gained a conflict the tip
On (03/20/14 14:44), Andrew Morton wrote:
> > zcomp returns error-valued pointer, also include err.h header
> > in zram_drv.
> >
> > Per Arnd Bergmann:
> > The zram driver uses the ERR_PTR macro defined in
> > and relies on this header to be included implicitly through
> > other headers, which
Since commit ca5d1b3524b4d
"regulator: helpers: Modify helpers enabling multi-bit control",
we can set enable_val setting for device that use multiple bits for control.
Signed-off-by: Axel Lin
---
drivers/regulator/s5m8767.c | 78 +++--
1 file changed, 19
On 20.03.2014 20:47, Andrew Bresticker wrote:
> mmc_request() reads the cd-gpio via mmc_gpio_get_cd(), which can sleep,
> while holding host->lock. This may result in the following BUG:
>
> BUG: spinlock wrong CPU on CPU#2, kworker/u8:16/4296
> lock: 0xea6b9c80, .magic: dead4ead, .owner:
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
arch/x86/include/asm/Kbuild between commit 073d8224d299 ("arch: Remove
stub cputime.h headers") from the tip tree and commit "x86: use generic
early_ioremap" from the akpm tree.
I fixed it up (see below) and can carry the fix
Hi Mark,
Has this patch been missing? I couldn't found it anywhere in the next branch.
:)
Thanks very much,
--
Best Regards,
Xiubo
> -Original Message-
> From: Nicolin Chen [mailto:guangyu.c...@freescale.com]
> Sent: Thursday, February 20, 2014 11:08 AM
> To: Mark Brown
> Cc: Xiubo
On 03/21/2014 07:18 AM, Andrew Morton wrote:
On Wed, 12 Feb 2014 18:00:38 +0800 wrote:
From: Roger Tseng
Realtek USB memstick host driver provides memstick host support based on the
Realtek USB card reader MFD driver.
...
+static int rtsx_usb_ms_drv_probe(struct platform_device *pdev)
+{
From: Jan-Simon Möller
Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
compliant equivalent. This is the original VLAIS struct.
struct {
struct aead_request req;
u8 priv[crypto_aead_reqsize(tfm)];
} aead_req;
This patch instead
Hi,
Users that have custom firmware SSDs, may choose to expose their flash directly.
This allows the host to control logical to physical address mappings, garbage
collection strategy, wear-leveling, and so on.
This is beneficial when you either want to strip the cost of a costly controller
or
microblaze-uclinux mailing list is almost dead and
it is just causing troubles for non subscribers which are
getting email about waiting for moderator.
Approval never happens. Move it to LKML.
Reported-by: Richard Guy Briggs
Signed-off-by: Michal Simek
---
Changes in v2:
- LKML is default
On 03/20/2014 09:18 PM, Joe Perches wrote:
> On Thu, 2014-03-20 at 21:15 +0100, Paul Bolle wrote:
>> On Thu, 2014-03-20 at 16:09 +0100, Michal Simek wrote:
>>> microblaze-uclinux mailing list is almost dead and
>>> it is just causing troubles for non subscribers which are
>>> getting email about
Dear Friend,
Greetings to you and your family.
My name is Mrs Monate Adama, the current Chief Auditor of a formidable bank
here in Ouagadougou, Burkina Faso, West Africa. I have a transaction worth of
12.5 Million U.S dollars for transferring into your care for our mutual
benefits, so i
Dear Friend,
Greetings to you and your family.
My name is Mrs Monate Adama, the current Chief Auditor of a formidable bank
here in Ouagadougou, Burkina Faso, West Africa. I have a transaction worth of
12.5 Million U.S dollars for transferring into your care for our mutual
benefits, so i
On 03/20/2014 09:18 PM, Joe Perches wrote:
On Thu, 2014-03-20 at 21:15 +0100, Paul Bolle wrote:
On Thu, 2014-03-20 at 16:09 +0100, Michal Simek wrote:
microblaze-uclinux mailing list is almost dead and
it is just causing troubles for non subscribers which are
getting email about waiting for
microblaze-uclinux mailing list is almost dead and
it is just causing troubles for non subscribers which are
getting email about waiting for moderator.
Approval never happens. Move it to LKML.
Reported-by: Richard Guy Briggs r...@redhat.com
Signed-off-by: Michal Simek michal.si...@xilinx.com
---
Hi,
Users that have custom firmware SSDs, may choose to expose their flash directly.
This allows the host to control logical to physical address mappings, garbage
collection strategy, wear-leveling, and so on.
This is beneficial when you either want to strip the cost of a costly controller
or
From: Jan-Simon Möller dl...@gmx.de
Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
compliant equivalent. This is the original VLAIS struct.
struct {
struct aead_request req;
u8 priv[crypto_aead_reqsize(tfm)];
} aead_req;
This
On 03/21/2014 07:18 AM, Andrew Morton wrote:
On Wed, 12 Feb 2014 18:00:38 +0800 rogera...@realtek.com wrote:
From: Roger Tseng rogera...@realtek.com
Realtek USB memstick host driver provides memstick host support based on the
Realtek USB card reader MFD driver.
...
+static int
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
arch/x86/include/asm/Kbuild between commit 073d8224d299 (arch: Remove
stub cputime.h headers) from the tip tree and commit x86: use generic
early_ioremap from the akpm tree.
I fixed it up (see below) and can carry the fix as
Hi Mark,
Has this patch been missing? I couldn't found it anywhere in the next branch.
:)
Thanks very much,
--
Best Regards,
Xiubo
-Original Message-
From: Nicolin Chen [mailto:guangyu.c...@freescale.com]
Sent: Thursday, February 20, 2014 11:08 AM
To: Mark Brown
Cc: Xiubo
On 20.03.2014 20:47, Andrew Bresticker wrote:
mmc_request() reads the cd-gpio via mmc_gpio_get_cd(), which can sleep,
while holding host-lock. This may result in the following BUG:
BUG: spinlock wrong CPU on CPU#2, kworker/u8:16/4296
lock: 0xea6b9c80, .magic: dead4ead, .owner:
Since commit ca5d1b3524b4d
regulator: helpers: Modify helpers enabling multi-bit control,
we can set enable_val setting for device that use multiple bits for control.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/s5m8767.c | 78 +++--
1
On (03/20/14 14:44), Andrew Morton wrote:
zcomp returns error-valued pointer, also include err.h header
in zram_drv.
Per Arnd Bergmann:
The zram driver uses the ERR_PTR macro defined in linux/err.h
and relies on this header to be included implicitly through
other headers, which is
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140320:
The powerpc tree still had its build failure.
The omap_dss2 tree gained a conflict the pm tree.
The tip tree gained a conflict against Linus' tree.
The akpm tree gained a conflict the tip
[...]
diff --git a/drivers/staging/iio/accel/adis16220_core.c
b/drivers/staging/iio/accel/adis16220_core.c
index 6f38ca9..31c7a9d 100644
--- a/drivers/staging/iio/accel/adis16220_core.c
+++ b/drivers/staging/iio/accel/adis16220_core.c
@@ -392,7 +392,8 @@ static const struct iio_info
On 03/21/2014 11:04 AM, Viresh Kumar wrote:
From: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
Whenever we change the frequency of a CPU, we call the PRECHANGE and
POSTCHANGE
notifiers. They must be serialized, i.e. PRECHANGE and POSTCHANGE notifiers
should strictly alternate, thereby
On 03/21/2014 11:04 AM, Viresh Kumar wrote:
CPUFreq core has new infrastructure that would guarantee serialized calls to
target() or target_index() callbacks. These are called
cpufreq_freq_transition_begin() and cpufreq_freq_transition_end().
This patch converts existing drivers to use these
On 03/21/2014 11:04 AM, Viresh Kumar wrote:
cpufreq_notify_transition() and cpufreq_notify_post_transition() shouldn't be
called directly by cpufreq drivers anymore and so these should be marked
static.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
Reviewed-by: Srivatsa S. Bhat
* Dimitri Sivanich sivan...@sgi.com wrote:
Set the UV n_lshift value based on the GAM_GR_CONFIG MMR for UV3, making it
independent of the socket m_val.
Remove unneeded macros.
Signed-off-by: Dimitri Sivanich sivan...@sgi.com
---
arch/x86/include/asm/uv/uv_hub.h | 12 -
401 - 500 of 966 matches
Mail list logo
