From: Stefani Seibold stef...@seibold.net
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c and make the functions
available for x86 32 bit kernels.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/Kconfig
From: Stefani Seibold stef...@seibold.net
The _install_special_mapping() is the new base function for
install_special_mapping(). This function will return a pointer to the vma
which was created or a error code in an ERR_PTR()
The install_special_mapping() will unscramble this to the old
Hi Suresh and other guys ,
In 3.4.4/3.6.6 ,I found a x2apic issue . if I am wrong , sorry first ,
and welcome your correction . thanks for your forwarding other maintainers.
I am testing a server , its BIOS is like this:
a) If BIOS think the system is of x2apic , it will set
Hi Laurent,
On Mon, 17 Dec 2012 22:04:19 +0100, Laurent Navet wrote:
fix these errors reported by checkpatch.pl
- drivers/i2c/busses/i2c-nforce2.c:191
- drivers/i2c/busses/i2c-nforce2.c:193
ERROR: foo * bar should be foo *bar
- drivers/i2c/busses/i2c-nforce2.c:302:
ERROR: (foo*) should be
On Mon, Dec 17, 2012 at 01:12:31PM -0500, Johannes Weiner wrote:
e986850 mm, vmscan: only evict file pages when we have plenty makes
a point of not going for anonymous memory while there is still enough
inactive cache around.
The check was added only for global reclaim, but it is just as
eurotechwdt hasn't any PCI-ID or DMI checks, thus is can be loaded on any
hardware. On my PC this leads to immediate reboot, because driver got irq right
after registering irq handler. This patch rejects interrupts until device
activation. There is no sense to load this driver without special
Hi,
On Thu, Nov 15, 2012 at 10:31:33AM +0200, Luciano Coelho wrote:
Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
regulator: twl: Remove references to 32kHz clock from DT bindings),
we've been having problems with our wl12xx chip that is connected
through the omap_hsmmc.
On Mon, Dec 17, 2012 at 01:12:33PM -0500, Johannes Weiner wrote:
A swappiness of 0 has a slightly different meaning for global reclaim
(may swap if file cache really low) and memory cgroup reclaim (never
swap, ever).
In addition, global reclaim at highest priority will scan all LRU
lists
The patch improves error handling in fuse_direct_IO(): if we successfully
submitted several fuse requests on behalf of synchronous direct write
extending file and some of them failed, let's try to do our best to clean-up.
Changed in v2: reuse fuse_do_setattr(). Thanks to Brian for suggestion.
Hi guys,
This is correct, however there are several other checkpatch errors and
warnings in this file and I would appreciate if you could fix them as
well. I'm not asking that you fix them all, but please consider fixing
the following:
WARNING: space prohibited between function name and
Hugh Dickins wrote:
On Fri, 14 Dec 2012, Konstantin Khlebnikov wrote:
Content of non-uptodate pages completely random, we cannot expose them into
userspace. This leads to information leak and will crash userspace for sure.
Good find, yes, it's very wrong as is. But, sorry, I don't like your
i have planned fixing these too, do you prefer one patch fixing all or
multiple patches (one per error/warning type )?
One patch, definately. You can skip the 80 char thing. Are you also able
to build-test the changes?
--
Pengutronix e.K. | Wolfram Sang
On Tue, Dec 18, 2012 at 01:29:07PM +1100, Stephen Rothwell wrote:
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/migrate.c: In function 'migrate_misplaced_transhuge_page':
mm/migrate.c:1738:2: error: incompatible type for
On 17 December 2012 16:24, Alex Shi alex@intel.com wrote:
The scheme below tries to summaries the idea:
Socket | socket 0 | socket 1 | socket 2 | socket 3 |
LCPU| 0 | 1-15 | 16 | 17-31 | 32 | 33-47 | 48 | 49-63 |
buddy conf0 | 0 | 0| 1 | 16| 2 | 32| 3 |
On 07:58 Tue 18 Dec , Wolfgang Grandegger wrote:
On 12/18/2012 06:55 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 20:47 Mon 17 Dec , Wolfgang Grandegger wrote:
On 12/17/2012 07:02 PM, Roland Stigge wrote:
On 12/17/2012 06:37 PM, Wolfgang Grandegger wrote:
/* Do synchronous data
On Tue, 18 Dec 2012 11:09:06 +0100, Wolfram Sang wrote:
i have planned fixing these too, do you prefer one patch fixing all or
multiple patches (one per error/warning type )?
One patch, definately.
Yes please :)
You can skip the 80 char thing.
For PCI device IDs, agreed.
Are you also
Are you also able to build-test the changes?
Most certainly yes, this driver has almost no dependencies. I will
build-test it anyway.
Me too :) I just wanted to express that I would love to see a compile
test before submission, even for checkpatch thingies. Can save some
hazzle for all of
16.11.2012, 00:36, Steven Rostedt rost...@goodmis.org:
Doing my INBOX maintenance (clean up), I've stumbled on this thread
again. I'm not sure the changes here are hopeless.
On Mon, 2012-06-04 at 13:27 +0800, Yong Zhang wrote:
On Fri, Jun 01, 2012 at 08:45:16PM +0400, Kirill Tkhai wrote:
On 17.12.2012 22:31, Paul Bolle wrote:
On an (outdated) laptop the radeon driver (almost always) prints, during
the first resume of each session:
[drm] crtc 1 is connected to a TV
This message is a bit puzzling as, as far as I know, no TV has ever
been connected to this laptop. Anyhow,
On Tue, 18 Dec 2012 18:38:20 +0800, wenhao zhang wrote:
*A Stupid Question*
This is not a stupid question, but a completely OFF-TOPIC question.
Don't do that again, please. If you have a question to ask, start a new
discussion thread on the appropriate list.
Thanks,
--
Jean Delvare
--
To
On Tue, 2012-12-18 at 14:59 +0530, Durgadoss R wrote:
This patch creates sensor level APIs, in the
generic thermal framework.
Just some trivial notes.
diff --git a/drivers/thermal/thermal_sys.c b/drivers/thermal/thermal_sys.c
[]
+static ssize_t
+sensor_temp_show(struct device *dev, struct
Are you also able to build-test the changes?
Yes,
Me too :) I just wanted to express that I would love to see a compile
test before submission, even for checkpatch thingies. Can save some
hazzle for all of us.
I agree,
thanks for your comments, i'll send new patch in a few days.
--
To
On Tue, 2012-12-18 at 14:59 +0530, Durgadoss R wrote:
This patch adds a new thermal_zone structure to
thermal.h. Also, adds zone level APIs to the thermal
framework.
[]
diff --git a/drivers/thermal/thermal_sys.c b/drivers/thermal/thermal_sys.c
+#define GET_INDEX(tz, ptr, indx, type)
On Tue, 18 Dec 2012 12:29:53 +0530
Laxman Dewangan ldewan...@nvidia.com wrote:
Nvidia's Tegra has multiple uart controller which supports:
- APB dma based controller fifo read/write.
- End Of Data interrupt in incoming data to know whether end
of frame achieve or not.
- Hw controlled RTS
On 2012-12-18 10:25, Ingo Molnar wrote:
* Jens Axboe ax...@kernel.dk wrote:
Hi Linus,
Now that the core bits are in, here are the driver bits for 3.8. The
branch contains:
FYI, I'm getting a divide-by-zero boot crash (serial log capture
below) with the attached config.
Reproduced
Hi Julia,
On Thu, 11 Oct 2012 08:45:43 +0200 (CEST), Julia Lawall wrote:
I found 6 cases where there are more than 2 messages in the array. I
didn't check how many cases where there are two messages but there is
something other than one read and one write.
Perhaps a reasonable option would
Hi Amaury,
On Wed, 29 Aug 2012 03:35:13 +0200, Amaury Decrême wrote:
This serie of patches brings SIS964 support to i2c-sis630.
The SiS datasheets have been used.
The SIS964 isn't part of the SIS96X family and behaves differently.
For i2c, this array show the differences between sis630
Uwe,
On Fri, 14 Sep 2012 10:25:36 +0200, Jean Delvare wrote:
On Wed, 12 Sep 2012 11:43:32 +0200, Uwe Kleine-König wrote:
The respective values are evaluated at each read/write, so no further
action is required than to change the perm argument to module_param.
Note there is no sanity
On Tue, Dec 18, 2012 at 5:53 PM, Vincent Guittot
vincent.guit...@linaro.org wrote:
On 17 December 2012 16:24, Alex Shi alex@intel.com wrote:
The scheme below tries to summaries the idea:
Socket | socket 0 | socket 1 | socket 2 | socket 3 |
LCPU| 0 | 1-15 | 16 | 17-31 |
I reviewed this patch 3 months ago and did not hear back. Are you going
to update this patch and resubmit, or should I just drop it?
Uwe is on holiday. I'll take care about it if the need is still there...
--
Pengutronix e.K. | Wolfram Sang|
stanley zhou wrote:
when call write_lock_bh() table is null cause crash in __ip6_del_rt().
kernel version is 2.6.30.10
:
static int __ip6_del_rt(struct rt6_info *rt, struct nl_info *info)
{
int err;
struct fib6_table *table;
struct net *net = dev_net(rt-rt6i_dev);
if (rt ==
In some SMP systems, cpu-local timers may stop delivering interrupts
when in low power states, or not all CPUs may have local timers. To
support these systems we have a mechanism for broadcasting timer ticks
to other CPUs. This mechanism relies on the struct
clock_event_device::broadcast function
Currently we only provide an implementation of smp_timer_broadcast in
smp.c if GENERIC_CLOCKEVENTS_BROADCAST is selected. As
smp_timer_broadcast is only used in smp.c, smp.c depends on SMP, and
GENERIC_CLOCKEVENTS_BROADCAST is selected by SMP, this is unnecessary.
This patch removes the redundant
Currently the broadcast mechanism used for timers is abstracted by a
function pointer on struct clock_event_device. As the fundamental
mechanism for broadcast is architecture-specific, this ties each
clock_event_device driver to a single architecture, even where the
driver is otherwise generic.
Currently, the ARM backend must maintain a redundant list of timers for
the purpose of centralising timer broadcast functionality. This prevents
sharing timer drivers across architectures.
This patch moves the pain of dealing with timer broadcasts to the core
clockevents tick broadcast code,
Currently, the timer broadcast mechanism is defined by a function
pointer on struct clock_event_device. As the fundamental mechanism for
broadcast is architecture-specific, this means that clock_event_device
drivers cannot be shared across multiple architectures.
This patch adds an (optional)
Implement timer_broadcast for the arm architecture, allowing for the use
of clock_event_device_drivers decoupled from the timer tick broadcast
mechanism.
Signed-off-by: Mark Rutland mark.rutl...@arm.com
---
arch/arm/Kconfig |1 +
arch/arm/kernel/smp.c |3 +--
2 files changed, 2
On Tue, 18 Dec 2012 12:59:26 +0100, Wolfram Sang wrote:
I reviewed this patch 3 months ago and did not hear back. Are you going
to update this patch and resubmit, or should I just drop it?
Uwe is on holiday. I'll take care about it if the need is still there...
The need was Uwe's
On Mon, 17 Dec 2012 09:30:33 -0600
Steve French smfre...@gmail.com wrote:
I don't think taking out debugging makes sense - we need debugging a
lot more often than expected even to diagnose user errors (usually
relating to session establishment failures, since we are very limited
in how much
On 2012-12-15, at 19:15, Dave Chinner da...@fromorbit.com wrote:
On Sat, Dec 15, 2012 at 11:25:23PM +0800, ys wrote:
From 3d56c131b58a21c05bcd677b9d2ba915abcbf195 Mon Sep 17 00:00:00 2001
From: yangsheng sick...@gmail.com
Date: Sat, 15 Dec 2012 21:46:22 +0800
Subject: [PATCH] vfs: update
The virtqueue_add_buf function has two limitations:
1) it requires the caller to provide all the buffers in a single call;
2) it does not support chained scatterlists: the buffers must be
provided as an array of struct scatterlist;
Because of these limitations, virtio-scsi has to copy each
This patch adds queue steering to virtio-scsi. When a target is sent
multiple requests, we always drive them to the same queue so that FIFO
processing order is kept. However, if a target was idle, we can choose
a queue arbitrarily. In this case the queue is chosen according to the
current VCPU,
This will be needed soon in order to retrieve the per-target
struct.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
drivers/scsi/virtio_scsi.c | 17 +
1 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
Using the new virtio_scsi_add_sg function lets us simplify the queueing
path. In particular, all data protected by the tgt_lock is just gone
(multiqueue will find a new use for the lock).
The speedup is relatively small (2-4%) but it is worthwhile because of
the code simplification---both in
On Tue, 18 Dec 2012, Jean Delvare wrote:
Hi Julia,
On Thu, 11 Oct 2012 08:45:43 +0200 (CEST), Julia Lawall wrote:
I found 6 cases where there are more than 2 messages in the array. I
didn't check how many cases where there are two messages but there is
something other than one read
On Tue, 2012-12-18 at 03:06 -0500, Tomas Hozza wrote:
- Original Message -
This is just for sanity. The value PATH_MAX was chosen after
discussion
with K. Y. Srinivasan and Olaf Hering instead of some magic
number like
256 or 512.
PATH_MAX is a magic name.
It is
virtio_scsi_target_state is now empty, but we will find new uses
for it in the next few patches. However, dropping the sglist lets
us turn the array-of-pointers into a simple array, which simplifies
the allocation.
However, we do not leave the virtio_scsi_target_state structs in the
flexible
Hi all,
this series adds multiqueue support to the virtio-scsi driver, based
on Jason Wang's work on virtio-net. It uses a simple queue steering
algorithm that expects one queue per CPU. LUNs in the same target always
use the same queue (so that commands are not reordered); queue switching
Whitespace at the end of line is not end of the world,
but nor useful too.
Signed-off-by: Michal Privoznik mpriv...@redhat.com
---
Documentation/networking/tuntap.txt | 64 ++---
1 file changed, 32 insertions(+), 32 deletions(-)
diff --git
Hi Linus,
Please pull the latest SLAB tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git slab/for-linus
This contains preparational work from Christoph Lameter and Glauber Costa for
SLAB memcg and cleanups and improvements from Ezequiel Garcia and Joonsoo Kim.
Please
Does anobody can helps me?
Hello. I'm newbie with cgroups (try to use blkio cgroups).
I need to shape disk activity on xen vps.
Each xen domU have block device that is software raid 1.
This raid have two devices that is lvm volume lies on srp (infiniband)
attached disk.
How can i limit disk usage
On Tuesday 18 December 2012 12:37 PM, Prashant Gaikwad wrote:
On Tuesday 18 December 2012 11:54 AM, Laxman Dewangan wrote:
On Tuesday 18 December 2012 11:44 AM, Prashant Gaikwad wrote:
My clock driver rework includes this fix. Divider supports both DIVU71
and DIVU151.
UART divider is set to
OMAP and ST-Ericsson platforms are both using mailbox to communicate
with some coprocessors.
Based on OMAP existing mailbox framework, this series proposes a
generic framework, living under drivers/mailbox.
This series:
- moves omap-mailbox framework to a newly drivers/mailbox folder
(part of
Now internal structures can remain hidden to the user and just API
related functions and defines are made available.
Signed-off-by: Omar Ramirez Luna omar.l...@linaro.org
---
drivers/mailbox/mailbox.c | 34 ++
drivers/mailbox/mailbox.h | 44
Coprocessor must be accessible during suspend transitions.
Signed-off-by: Loic Pallardy loic.palla...@st.com
---
drivers/mailbox/mailbox.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
index c0a8e49..57cb566 100644
---
Current message type is a u32 to fit HW fifo format.
This should be extended to support any message exchanges
and type of mailbox.
Propose structure owns the original u32 and an optional
pointer on additional data.
Signed-off-by: Loic Pallardy loic.palla...@st.com
---
drivers/mailbox/Kconfig
Actually moving it from plat-omap, as this framework/driver code is
supposed to be under drivers/ folder. The framework should work with
the current supported OMAP processors (OMAP1+) that have mailbox and
can be used as a method of interprocessor communication.
The mailbox hardware (in OMAP)
Some mailboxes are made up of cross interrupts
and associated shared memory.
Shared memory mapping is fixed and cross interrupt/shared
memory relation make impossible the use of virtio.
Mailbox framework must be enough opened to support
any kind of mailbox.
Signed-off-by: Loic Pallardy
In order to create a generic mailbox framework, functions
and structures should be renamed in mailbox.
Signed-off-by: Loic Pallardy loic.palla...@st.com
---
drivers/mailbox/Kconfig | 3 +-
drivers/mailbox/mailbox-omap1.c | 28 -
drivers/mailbox/mailbox-omap2.c | 60
TX: replace spin by mutex
RX: replace spin_lock_irq by spin_lock_irqsave
Signed-off-by: Loic Pallardy loic.palla...@st.com
---
drivers/mailbox/mailbox.c | 10 ++
drivers/mailbox/mailbox.h | 1 +
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/mailbox/mailbox.c
For debug purpose, mailbox must be available when
interrupts are disabled to collect dump information.
Signed-off-by: Loic Pallardy loic.palla...@st.com
---
drivers/mailbox/mailbox.c | 66 +++
include/linux/mailbox.h | 3 +++
2 files changed, 69
Add STEriccson DBX500 PRCM mailbox support.
Signed-off-by: Loic Pallardy loic.palla...@st.com
---
drivers/mailbox/Kconfig | 18 +-
drivers/mailbox/Makefile | 1 +
drivers/mailbox/mailbox-dbx500.c | 601 +++
Please note that I resigned from my position of i2c subsystem
maintainer, so I will not handle this. If you think this is important,
you'll have to resubmit and Wolfram will decide what he wants to do
about it.
OK, I had the impression that the conclusion was that the danger was
Liu, Jinsong wrote:
Liu, Jinsong wrote:
Konrad Rzeszutek Wilk wrote:
On Thu, Dec 06, 2012 at 04:27:36AM +, Liu, Jinsong wrote:
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig index
126d8ce..abd0396 100644 --- a/drivers/xen/Kconfig
+++ b/drivers/xen/Kconfig
@@ -206,4 +206,15 @@
On Tue, Dec 04, 2012 at 10:35:13AM +0800, Li Zhong wrote:
This patch adds user eqs exception hooks for async page fault page not
present code path, to exit the user eqs and re-enter it as necessary.
Async page fault is different from other exceptions that it may be
triggered from idle
Some comments without arguing about whether the performance
benefit is worth it.
On Tue, Dec 18, 2012 at 01:32:48PM +0100, Paolo Bonzini wrote:
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
index cf8adb1..39d56c4 100644
--- a/include/linux/virtio.h
+++ b/include/linux/virtio.h
On Tue, Dec 18, 2012 at 01:32:49PM +0100, Paolo Bonzini wrote:
Using the new virtio_scsi_add_sg function lets us simplify the queueing
path. In particular, all data protected by the tgt_lock is just gone
(multiqueue will find a new use for the lock).
vq access still needs some protection:
Il 18/12/2012 14:37, Michael S. Tsirkin ha scritto:
On Tue, Dec 18, 2012 at 01:32:49PM +0100, Paolo Bonzini wrote:
Using the new virtio_scsi_add_sg function lets us simplify the queueing
path. In particular, all data protected by the tgt_lock is just gone
(multiqueue will find a new use for
On Tue, Dec 18, 2012 at 01:32:47PM +0100, Paolo Bonzini wrote:
Hi all,
this series adds multiqueue support to the virtio-scsi driver, based
on Jason Wang's work on virtio-net. It uses a simple queue steering
algorithm that expects one queue per CPU. LUNs in the same target always
use the
Il 18/12/2012 14:36, Michael S. Tsirkin ha scritto:
Some comments without arguing about whether the performance
benefit is worth it.
On Tue, Dec 18, 2012 at 01:32:48PM +0100, Paolo Bonzini wrote:
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
index cf8adb1..39d56c4 100644
---
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Changes from v1:
- Changed the name of property for phy handler from'samsung,usb-phyctrl'
to 'samsung,usb-phyhandle' to make
On Tue, Dec 18, 2012 at 01:32:52PM +0100, Paolo Bonzini wrote:
This patch adds queue steering to virtio-scsi. When a target is sent
multiple requests, we always drive them to the same queue so that FIFO
processing order is kept. However, if a target was idle, we can choose
a queue
On Tue, Dec 18, 2012 at 02:43:51PM +0100, Paolo Bonzini wrote:
Il 18/12/2012 14:36, Michael S. Tsirkin ha scritto:
Some comments without arguing about whether the performance
benefit is worth it.
On Tue, Dec 18, 2012 at 01:32:48PM +0100, Paolo Bonzini wrote:
diff --git
Il 18/12/2012 14:57, Michael S. Tsirkin ha scritto:
-static int virtscsi_queuecommand(struct Scsi_Host *sh, struct scsi_cmnd *sc)
+static int virtscsi_queuecommand(struct virtio_scsi *vscsi,
+ struct virtio_scsi_target_state *tgt,
+
On Tue, Dec 18, 2012 at 10:44:19AM +0800, fangxiaozhi 00110321 wrote:
diff -uprN linux-3.7_bak/drivers/usb/storage/initializers.c
linux-3.7/drivers/usb/storage/initializers.c
--- linux-3.7_bak/drivers/usb/storage/initializers.c 2012-12-11
09:56:11.0 +0800
+++
On 12/18/2012 03:21 AM, Hiroshi Doyu wrote:
Hi Rob,
Rob Herring robherri...@gmail.com wrote @ Mon, 17 Dec 2012 15:00:46 +0100:
On 12/17/2012 12:18 AM, Hiroshi Doyu wrote:
Set Snoop Control Unit(SCU) register base address dynamically from DT.
Signed-off-by: Hiroshi Doyu hd...@nvidia.com
The following changes since commit
6f0c0580b70c89094b3422ba81118c7b959c7556:
Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
are available in the git repository at:
git://openrisc.net/~jonas/linux tags/for-3.8
for you to fetch changes up to 634bd40a894d64df09ba36c12bb6e70787989ba9:
openrisc:
On 12/14/2012 10:20 AM, Maxim V. Patlasov wrote:
Hi,
...
The throughput on some commodity (rather feeble) server was (in MB/sec):
original / patched
dd reads:~322 / ~382
dd writes: ~277 / ~288
aio reads: ~380 / ~459
aio writes: ~319 / ~353
It should mitigate the problem. The real fix shouldn't be that specific
(as per discussion in other thread). The chance this will get upstream
is not big and that means that it will not get to the stable tree
either.
OOM is no longer killing processes outside target cgroups, so everything looks
Hi Joe,
Can you make checkpatch.pl check that lines added to UAPI headers don't have
the form:
#include uapi/...
or:
#include uapi/...
Such as these should be regarded as errors as they will likely break userspace
which shouldn't get to see any uapi/ directories.
An example
Hi Mark,
On 12/17/2012 04:51 PM, Mark Rutland wrote:
+static int __devinit gpioblock_of_probe(struct platform_device *pdev)
+{
+struct device_node *block;
+unsigned *gpios;
+int ngpio;
+int ret;
+struct gpio_block *gb;
+
+
Il 18/12/2012 14:59, Michael S. Tsirkin ha scritto:
Can't we track state internally to the virtqueue? Exposing it
seems to buy us nothing since you can't call add_buf between
start and end anyway.
I wanted to keep the state for these functions separate from the
rest. I don't think it makes
Changes from v4:
- Moved architecture side changes out of this patch-set.
- Added support for multiple usbphy phandle parsing and
doing all pmu_isolation() and phy_cfg_sel() related changes
in samsung-usbphy driver only instead of architecture
as in v4 patch-set.
- Removed unnecessary
Updating the names of usb-phy types to more generic names:
USB_PHY_TYPE_DEIVCE USB_PHY_TYPE_HOST; and further update
its dependencies.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/host/ehci-s5p.c |9 +
This patch adds host phy support to samsung-usbphy.c and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 25 +-
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
---
drivers/usb/host/ehci-s5p.c | 70
Adding the phy-driver to ohci-exynos. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
---
drivers/usb/host/ohci-exynos.c | 70
Hello,
I'm sorry for the delay, I've been terribly busy recently.
On 12/11/2012 2:54 PM, Federico Vaga wrote:
This allocator is needed because some device (like STA2X11 VIP) cannot
work
with DMA sg or DMA coherent. Some other device (like the one used by
Jonathan when he proposes
On Tue, Dec 18, 2012 at 07:13:17AM -0500, Jeff Layton wrote:
I agree that we often need cifsFYI debug info in order to troubleshoot
problems. The question here though is whether compiling those in ought
to be the default.
In generic distro kernels, I think we do want that turned on even in
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-linus-3.8-rc0-bugfix-tag
which has two fixes. One of them is caused by the recent change introduced
by the 'x86-bsp-hotplug-for-linus' tip tree that inhibited bootup (old
Before waking up the tty line discipline idle queue first check if the queue is
active (non empty). This prevents unnecessary entering the critical section in
the wake_up() function and therefore avoid needless scheduling overhead on a
PREEMPT_RT system caused by two processes being in the same
On Tue, Dec 18, 2012 at 03:08:08PM +0100, Paolo Bonzini wrote:
Il 18/12/2012 14:57, Michael S. Tsirkin ha scritto:
-static int virtscsi_queuecommand(struct Scsi_Host *sh, struct scsi_cmnd
*sc)
+static int virtscsi_queuecommand(struct virtio_scsi *vscsi,
+ struct
On Tue, Dec 18, 2012 at 03:32:15PM +0100, Paolo Bonzini wrote:
Il 18/12/2012 14:59, Michael S. Tsirkin ha scritto:
Can't we track state internally to the virtqueue? Exposing it
seems to buy us nothing since you can't call add_buf between
start and end anyway.
I wanted to keep the state
Changes form v1:
- Moved architecture related patch out of this patch-set.
- Replaced unnecessary multi-line macro definitions by
single line definitions.
- Creating new data structure for USB 3.0 phy type and embedding
it in 'samsung_usbphy' structure.
- Adding a flag in
Adding support for USB3.0 phy for dwc3 controller on
exynos5250 SOC.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/phy/samsung-usbphy.c | 339 +-
1 files changed, 337 insertions(+), 2 deletions(-)
diff --git
Hi list,
commit 263a523d18bca306016d75f5c8d5c57c37fe52fb changes the code of
DIV_ROUND_CLOSEST in include/linux/kernel.h to fix a compile time warning.
But now feeding in a zero into this macro results into 4198403. Tested with
gcc 4.4.3 and 4.7.2, on arch x86 and ARM.
I can reproduce this
On Tue, 18 Dec 2012 15:44:52 +0100
Borislav Petkov b...@alien8.de wrote:
On Tue, Dec 18, 2012 at 07:13:17AM -0500, Jeff Layton wrote:
I agree that we often need cifsFYI debug info in order to troubleshoot
problems. The question here though is whether compiling those in ought
to be the
Hi Olof,
Le 18/12/2012 07:55, Olof Johansson a écrit :
Maxime Ripard (1):
ARM: sunxi: Change device tree naming scheme for sunxi
There's something odd about this one (commit 68136b10). The patch that
you seem to have applied differs from the one I sent. The DTs files
appears to have not
Rob Herring robherri...@gmail.com wrote @ Tue, 18 Dec 2012 14:46:36 +0100:
On 12/18/2012 03:21 AM, Hiroshi Doyu wrote:
Hi Rob,
Rob Herring robherri...@gmail.com wrote @ Mon, 17 Dec 2012 15:00:46 +0100:
On 12/17/2012 12:18 AM, Hiroshi Doyu wrote:
Set Snoop Control Unit(SCU) register
On 12/17/2012 01:12 PM, Johannes Weiner wrote:
A swappiness of 0 has a slightly different meaning for global reclaim
(may swap if file cache really low) and memory cgroup reclaim (never
swap, ever).
In addition, global reclaim at highest priority will scan all LRU
lists equal to their
501 - 600 of 932 matches
Mail list logo
