Hi Tomi,
On Wed, Oct 31, 2012 at 10:52:59, Manjunathappa, Prakash wrote:
Hi,
On Wed, Oct 31, 2012 at 21:26:08, Pantelis Antoniou wrote:
This driver can be used for AM33xx devices, like the popular beaglebone.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
Hi Paul Ingo:
In a short word of this issue: burst forking/waking tasks have no time
accumulate the load contribute, their runnable load are taken as zero.
that make select_task_rq do a wrong decision on which group is idlest.
As you pointed out above, new tasks can (and imho should) be
Hi Kamal,
On Wed, Dec 05, 2012 at 04:16:15PM -0800, Kamal Mostafa wrote:
From: Dudley Du d...@cypress.com
Input/mouse driver for Cypress PS/2 Trackpad.
Original code contributed by Dudley Du (Cypress Semiconductor Corporation),
modified by Kamal Mostafa and Kyle Fazzari.
BugLink:
Hi!
Just a quick update
Johannes Weiner wrote on 03.12.2012 20:42:
On Mon, Dec 03, 2012 at 09:30:12AM +0100, Thorsten Leemhuis wrote:
BTW, I built that kernel without the patch you mentioned in
http://thread.gmane.org/gmane.linux.kernel.mm/90911/focus=91153
(buffer_heads_over_limit can put
On 12/06/2012 02:52 PM, Preeti U Murthy wrote:
Hi Alex,
Hi Paul Ingo:
In a short word of this issue: burst forking/waking tasks have no time
accumulate the load contribute, their runnable load are taken as zero.
On performing certain experiments on the way PJT's metric calculates the
On 01/12/2012 00:45, Bjorn Helgaas wrote:
On Thu, Nov 29, 2012 at 10:28 PM, Daniel J Blueman
On 29/11/2012 07:08, Bjorn Helgaas wrote:
On Wed, Nov 21, 2012 at 1:39 AM, Daniel J Blueman
dan...@numascale-asia.com wrote:
Add NumaChip-specific PCI access mechanism via MMCONFIG cycles, but
On Wed, 5 Dec 2012 23:48:17 -0800, Dmitry Torokhov wrote:
Hi Benson,
On Wed, Dec 05, 2012 at 04:48:19PM -0800, Benson Leung wrote:
This patch introduces a driver for Cypress All Points Addressable
I2C Trackpad, including the ones in 2012 Samsung Chromebooks.
This device is compatible
This patch removes the trailing white space in fs/sysfs/mount.c.
Signed-off-by: Bin Wang wbi...@gmail.com
---
diff --git a/fs/sysfs/mount.c b/fs/sysfs/mount.c
index 71eb7e2..24bfcb4 100644
--- a/fs/sysfs/mount.c
+++ b/fs/sysfs/mount.c
@@ -10,7 +10,7 @@
* Please see
On 12/05/2012 10:46 PM, Andrew Morton wrote:
--- a/include/linux/scatterlist.h
+++ b/include/linux/scatterlist.h
@@ -198,6 +198,9 @@ static inline dma_addr_t sg_phys(struct scatterlist *sg)
**/
static inline void *sg_virt(struct scatterlist *sg)
{
+#ifdef CONFIG_DEBUG_SG
+
6e20a0a429bd4dc07d6de16d9c247270e04e4aa0
(gpio: pcf857x: enable gpio_to_irq() support)
added gpio_to_irq() support on pcf857x driver,
but it used pdata-irq.
This patch modifies driver to use client-irq instead of it.
It modifies kzm9g board platform settings,
and device probe information too.
This
On Wed, Dec 05, 2012 at 10:48:41AM -0600, Mark Langsdorf wrote:
Highbank processors depend on the external ECME to perform voltage
management based on a requested frequency. Communication between the
A9 cores and the ECME happens over the pl320 IPC channel.
Signed-off-by: Mark Langsdorf
[Sorry for taking so long to respond, after a week of silence I
assumed I wouldn't get any responses, plus I had moved on to other
things.]
I happen to still have the logs, the relevant part is pasted at the end.
Answering some of the questions: the driver is on the platform bus, in
fact, it's
On Thursday 06 December 2012 04:41:01 Hans J. Koch wrote:
@@ -63,7 +68,7 @@ static irqreturn_t uio_pdrv_genirq_handler(int irq,
struct uio_info *dev_info)
* remember the state so we can allow user space to enable it later.
*/
- if (!test_and_set_bit(0, priv-flags))
+
On Thu, 2012-12-06 at 16:06 +0800, Alex Shi wrote:
Hi Paul Ingo:
In a short word of this issue: burst forking/waking tasks have no time
accumulate the load contribute, their runnable load are taken as zero.
that make select_task_rq do a wrong decision on which group is idlest.
Hi Linus,
This is the third time I encounter this oops in 3.7, but the first
time I managed to get a decent screenshot:
http://bitmath.org/test/oops-3.7-rc8.jpg
It seems to have to do with page migration. I run with transparent
hugepages configured, just for the fun of it.
I am happy to test
On 05/12/12 17:11, Al Viro wrote:
On Wed, Dec 05, 2012 at 04:08:18PM +, James Hogan wrote:
other work not included:
* switch to generic kernel_{thread,execve} (will be posted separately to
aid review)
other changes:
...
* switch to generic sys_execve
... which should've broken
On 05/12/12 22:28, Grant Likely wrote:
On Wed, 5 Dec 2012 16:08:24 +, James Hogan james.ho...@imgtec.com wrote:
The powervr prefix which is currently described as Imagination
Technologies isn't really appropriate for non-PowerVR hardware, so
deprecate it, changing the description of
Am Donnerstag, 6. Dezember 2012 schrieb Dave Chinner:
That being said, you'll note that unlike Dave, I have
**not** thrown a hissy fit when btrfs grabbed bits from the inode
field, even though quite a bit more bits allocated for the inode
flags than the fallocate flags.
IOWs, pointing
Namjae Jeon linkinj...@gmail.com writes:
I know encode_fh(). But NFS is network protocol, and network can input
any data, and I guess the userland interface (open_by_handle()?) can be
any too.
And generic_fh_to_dentry()'s input verify choose to check the minimum
length only. But your logic
Hi,
On Thu, Nov 29, 2012 at 10:44:11AM -0700, Toshi Kani wrote:
On Thu, 2012-11-29 at 12:04 +0100, Vasilis Liaskovitis wrote:
Yes, that's what I had in mind along with device_lock(). I think the
lock is necessary to close the window.
http://www.spinics.net/lists/linux-mm/msg46973.html
This patch removes the trailing white space in fs/sysfs/mount.c.
Signed-off-by: Bin Wang wbi...@gmail.com
---
fs/sysfs/mount.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/sysfs/mount.c b/fs/sysfs/mount.c
index 71eb7e2..24bfcb4 100644
--- a/fs/sysfs/mount.c
+++
On Thu, Dec 6, 2012 at 6:18 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Wed, Dec 5, 2012 at 7:43 PM, Dan Carpenter dan.carpen...@oracle.com
wrote:
line6_send_sysex_message_async() isn't called from anywhere.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
Reviewed-by: Stefan
On 05/12/12 18:53, Joe Perches wrote:
On Wed, 2012-12-05 at 16:08 +, James Hogan wrote:
Add source files from the Thread Binary Interface (TBI) library which
provides useful low level operations and traps/context management.
[]
arch/metag/tbx/tbicache.c | 462
On 05.12.2012, Daniel Vetter wrote:
Nope, we could only reproduce quickly with rc6 enabled :(
Could reproduce it today this way:
dd if=/dev/zero of=deleteme bs=1M count=5
while watching several HD videos on Youtube. Just tried once, so I'm
not shure if this will work all the way. Will
Am Donnerstag, 6. Dezember 2012 schrieb Linus Torvalds:
On Wed, Dec 5, 2012 at 5:14 PM, Dave Chinner da...@fromorbit.com
wrote:
And for changes to syscalls? That's something that must be peer
reviewed because we are going to be stuck with those changes forever
as we can't undo them at a
On Wed, 5 Dec 2012, Nadia Yvette Chambers wrote:
OK, that may be a problem. Does this patch apply to Linus' tree
currently? I guess not. So, either you need to split it up and send it
to the various maintainers (most if it can probably go through the trivial
tree (cc'd)). Or wait
2012/12/6, OGAWA Hirofumi hirof...@mail.parknet.co.jp:
Namjae Jeon linkinj...@gmail.com writes:
I know encode_fh(). But NFS is network protocol, and network can input
any data, and I guess the userland interface (open_by_handle()?) can be
any too.
And generic_fh_to_dentry()'s input verify
dmaengine from the beginning has placed the burden of unmapping dma
buffers on the individual drivers. The thought being that since the dma
driver already has the descriptor it can use that information for
unmapping. This results in a lot of cruft to read back data from
descriptors, places a
Use the generic unmap object to unmap dma buffers.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Signed-off-by: Dan Williams d...@fb.com
---
crypto/async_tx/async_memcpy.c | 39
Use the generic unmap object to unmap dma buffers.
Later we can push this unmap object up to the raid layer and get rid of
the 'scribble' parameter.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Use the generic unmap object to unmap dma buffers.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Signed-off-by: Dan Williams d...@fb.com
---
crypto/async_tx/async_pq.c | 117
From: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Remove support for DMA unmapping from drivers as it is no longer
needed (DMA core code is now handling it).
Cc: Vinod Koul vinod.k...@intel.com
Cc: Tomasz Figa t.f...@samsung.com
Signed-off-by: Bartlomiej Zolnierkiewicz
From: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Remove no longer needed DMA unmap flags:
- DMA_COMPL_SKIP_SRC_UNMAP
- DMA_COMPL_SKIP_DEST_UNMAP
- DMA_COMPL_SRC_UNMAP_SINGLE
- DMA_COMPL_DEST_UNMAP_SINGLE
Cc: Vinod Koul vinod.k...@intel.com
Cc: Tomasz Figa t.f...@samsung.com
Use the generic unmap object to unmap dma buffers.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Signed-off-by: Dan Williams d...@fb.com
---
crypto/async_tx/async_pq.c | 58
Use the generic unmap object to unmap dma buffers.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Signed-off-by: Dan Williams d...@fb.com
---
crypto/async_tx/async_xor.c | 30
Use the generic unmap object to unmap dma buffers.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Signed-off-by: Dan Williams d...@fb.com
---
crypto/async_tx/async_raid6_recov.c | 69
Use the generic unmap object to unmap dma buffers.
Cc: Tomasz Figa t.f...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Reported-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Signed-off-by: Dan Williams d...@fb.com
---
crypto/async_tx/async_memset.c | 18 +-
hang a common 'unmap' object off of dma descriptors for the purpose of
providing a unified unmapping interface. The lifetime of a mapping may
span multiple descriptors, so these unmap objects are reference counted
by related descriptor.
Cc: Vinod Koul vinod.k...@intel.com
Cc: Tomasz Figa
Add a hook for a common dma unmap implementation to enable removal of
the per driver custom unmap code. (A reworked version of Bartlomiej
Zolnierkiewicz's patches to remove the custom callbacks and the size
increase of dma_async_tx_descriptor for drivers that don't care about raid).
Cc:
Copying from page to page (dma_async_memcpy_pg_to_pg) is the superset,
make the other two apis use that one in preparation for providing a
common dma unmap implementation. The common implementation just wants
to assume all buffers are mapped with dma_map_page().
Signed-off-by: Dan Williams
But regardless, it is the responsiblity of the probe function to go and
look if of_driver_match_device() matches against anything if it cares
about the of_match_table entries (for instance, if there is extra data
attached).
Ok, so filling .data field in of_device_id[] is not required
On Thu 06-12-12 01:29:24, azurIt wrote:
OK, so the ENOMEM seems to be leaking from mem_cgroup_newpage_charge.
This can only happen if this was an atomic allocation request
(!__GFP_WAIT) or if oom is not allowed which is the case only for
transparent huge page allocation.
The first case can be
Hi Prabhakar and Hans,
On Thu, Dec 06, 2012 at 10:24:18AM +0530, Prabhakar Lad wrote:
Hi Hans,
On Wed, Dec 5, 2012 at 5:38 PM, Hans Verkuil hverk...@xs4all.nl wrote:
(resend without HTML formatting)
On Wed 5 December 2012 12:49:29 Prabhakar Lad wrote:
From: Lad, Prabhakar
On Wed, 5 Dec 2012, Jean Delvare wrote:
HID descriptors contains 4 bytes of reserved field.
The previous implementation was overriding the next fields in struct
i2c_hid.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@gmail.com
---
drivers/hid/i2c-hid/i2c-hid.c | 9 -
On Wed, 5 Dec 2012, Benjamin Tissoires wrote:
Simplifies i2c_hid_alloc_buffers tests, and makes this function
responsible of the assignment of ihid-bufsize.
The condition for the reallocation in i2c_hid_start is then simpler.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@gmail.com
On Wed, 5 Dec 2012, Jean Delvare wrote:
On Wed, 5 Dec 2012 15:02:55 +0100, Benjamin Tissoires wrote:
There is no point in keeping the irq in i2c_hid as it's already
there in client.
Signed-off-by: Benjamin Tissoires benjamin.tissoi...@gmail.com
Applied.
---
Merely reorganizing documentation. No functional changes. It makes more
sense for the gpio-leds binding to be grouped with other led bindings
than with gpio drivers.
Signed-off-by: Grant Likely grant.lik...@secretlab.ca
---
Posting for reference. I've applied this to my tree already
g.
On Mon, 12 Nov 2012 15:41:10 +0100, Peter Ujfalusi peter.ujfal...@ti.com
wrote:
Support for device tree booted kernel.
When the kernel is booted with DeviceTree blob we support one led per
leds-pwm device to have cleaner integration with the PWM subsystem.
For usage see:
On Wed, 5 Dec 2012, Jean Delvare wrote:
The previous memcpy implementation relied on the size advertized by the
device. There were no guarantees that buf was big enough.
Some gymnastic is also required with the +2/-2 to take into account
the first 2 bytes of the returned buffer where
On Thu, 06 Dec 2012, Viresh Kumar wrote:
On 6 December 2012 15:20, Lee Jones lee.jo...@linaro.org wrote:
But regardless, it is the responsiblity of the probe function to go and
look if of_driver_match_device() matches against anything if it cares
about the of_match_table entries (for
Dohh. The very same stack mem_cgroup_newpage_charge called from the page
fault. The heavy inlining is not particularly helping here... So there
must be some other THP charge leaking out.
[/me is diving into the code again]
* do_huge_pmd_anonymous_page falls back to handle_pte_fault
*
Can you regenerate against current queue branch in
git://git.kernel.org/pub/scm/virt/kvm/kvm.git please?
On Wed, Dec 05, 2012 at 03:58:50PM +0800, Zhang Yanfei wrote:
Currently, kdump just makes all the logical processors leave VMX operation by
executing VMXOFF instruction, so any VMCSs active
Hi Maya,
On 4 December 2012 22:17, me...@codeaurora.org wrote:
Hi Ulf,
Let me try to better explain:
The idea behind the periodic BKOPS is to check the card's need for BKOPS
periodically in order to prevent an urgent BKOPS need by the card.
In order to actually manage to prevent the urgent
On 6 December 2012 15:41, Lee Jones lee.jo...@linaro.org wrote:
So then I'm back to my original question, why?
What is it used for? What difference does it make?
I could understand if the .data attribute was used in the driver
to make vital decisions based on STMPE version, but it's not. So
On Tue, Dec 04, 2012 at 02:10:01PM -0800, Laura Abbott wrote:
The current calculation in pfn_to_bitidx assumes that
(pfn - zone-zone_start_pfn) pageblock_order will return the
same bit for all pfn in a pageblock. If zone_start_pfn is not
aligned to pageblock_nr_pages, this may not always be
On 6 December 2012 15:20, Lee Jones lee.jo...@linaro.org wrote:
But regardless, it is the responsiblity of the probe function to go and
look if of_driver_match_device() matches against anything if it cares
about the of_match_table entries (for instance, if there is extra data
attached).
On Wed, Dec 05, 2012 at 08:40:31PM -0500, Steven Rostedt wrote:
You can have a config that enables these trace points, and when you
enable one of the systems that uses them, have that config select the
config that enables tracepoints. Have that config compile the file for
tracepoints. For
On Tue, Dec 04, 2012 at 04:19:06PM -0600, Steven Kinney wrote:
drivers/iommu/Kconfig | 10 +
drivers/iommu/amd_iommu_init.c | 85
+++
drivers/iommu/amd_iommu_types.h | 13 +-
3 files changed, 107 insertions(+), 1 deletion(-)
So
On Thu, 06 Dec 2012, Viresh Kumar wrote:
On 6 December 2012 15:41, Lee Jones lee.jo...@linaro.org wrote:
So then I'm back to my original question, why?
What is it used for? What difference does it make?
I could understand if the .data attribute was used in the driver
to make vital
Il 05/12/2012 17:45, Kirill A. Shutemov ha scritto:
From: Kirill A. Shutemov kirill.shute...@linux.intel.com
This driver is intended to run as fast as possible, hence the options to
discard writes and reads. It's designed to let us find latency issues
elsewhere in the storage stack (eg
On 6 December 2012 16:05, Lee Jones lee.jo...@linaro.org wrote:
Or you could not put unnecessary bindings into the Device Tree
by putting two and two together and realise that using the table
is the correct thing to do instead. This actually gives reason
to you previous patch, but should
On Wed, Dec 5, 2012 at 7:13 PM, Alex Shi alex@intel.com wrote:
On 12/05/2012 11:19 PM, Alex Shi wrote:
Hi PaulIngo:
Runnable load tracking patch set introduce a good way to tracking each
entity/rq's running time.
But when I try to enable it in load balance, I found burst forking
many
On Wed, Dec 05, 2012 at 07:51:34PM +, Uwe Kleine-König wrote:
Hello,
Hi Uwe,
On Mon, Dec 03, 2012 at 05:46:17PM +, Will Deacon wrote:
I think Uwe also requires some of the stuff there for his M3 port.
I didn't check more context than available in the patch and I also
didn't
On 27.11.2012 02:43, Randy Dunlap wrote:
On 11/26/2012 01:22 PM, Yacine Belkadi wrote:
If a function has a return value, but its kernel-doc comment doesn't contain
a
Return section, then emit the following warning:
Warning(file.h:129): No description found for return value of 'fct'
Use more coherent locking in the driver. Use bitfield to store the GPIO
direction and if the pin is configured as output store the status also in a
bitfiled.
In this way we can just look at these bitfields when we need information
about the pin status and only reach out to the chip when it is
This GPIO driver should not configure anything else then GPIOs.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/gpio/gpio-twl4030.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpio/gpio-twl4030.c b/drivers/gpio/gpio-twl4030.c
index a38e6e9c..1e9f08c4 100644
---
On Thu, Dec 6, 2012 at 5:11 PM, Wedson Almeida Filho wedso...@gmail.com wrote:
[Sorry for taking so long to respond, after a week of silence I
assumed I wouldn't get any responses, plus I had moved on to other
things.]
I happen to still have the logs, the relevant part is pasted at the end.
Hi,
As Grant commneted on the first version:
https://lkml.org/lkml/2012/12/5/53
Introduce bitfields to cache the directionand output status of the pins so we
can report them correctly.
To do this I did some cleanup within the driver to get rid of the global
variables and moved them under a
Move most of the global variables inside a private structure and allocate
it dynamically.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/gpio/gpio-twl4030.c | 82 +++--
1 file changed, 50 insertions(+), 32 deletions(-)
diff --git
On 12/05/2012 11:48 PM, Grant Likely wrote:
-base = REG_GPIODATAIN1 + d_bnk;
+direction = gpio_twl4030_read(REG_GPIODATADIR1 + d_bnk);
+if (direction 0 (direction d_off) 0x1)
+base = REG_SETGPIODATAOUT1 + d_bnk;
+else
+base = REG_GPIODATAIN1 +
On Thu, 06 Dec 2012, Viresh Kumar wrote:
On 6 December 2012 16:05, Lee Jones lee.jo...@linaro.org wrote:
Or you could not put unnecessary bindings into the Device Tree
by putting two and two together and realise that using the table
is the correct thing to do instead. This actually
Hi Al,
Thanks for reviewing.
On 05/12/12 17:16, Al Viro wrote:
+if (__copy_from_user(st, frame-uc.uc_stack, sizeof(st)))
+goto badframe;
+/* It is more difficult to avoid calling this function than to
+ call it and ignore errors. */
+do_sigaltstack((__force
On 6 December 2012 16:42, Lee Jones lee.jo...@linaro.org wrote:
I thought we'd be over this? The 'ID' will be represented by the
address of the chip i.e. stmpe1601@40, where '40' will be
distinguishing factor?
I haven't tested it but i thought we are getting i2c device name from
modalias() fn
NFSd resources are partially per-net and partially globally used.
This patch splits resources init and shutdown and moves per-net code to
separated functions.
Generic and per-net init and shutdown are called sequentially for a while.
Signed-off-by: Stanislav Kinsbursky skinsbur...@parallels.com
This patch introduces introduces per-net nfsd_net_up boolean flag, which has
the same purpose as general nfsd_up flag - skip init or shutdown of per-net
resources in case of they are inited on shutted down respectively.
Signed-off-by: Stanislav Kinsbursky skinsbur...@parallels.com
---
All is simple: NFSd service can be started in diffent moments of time in
different network environments. So, it's boot time have to be assigned per
net.
Signed-off-by: Stanislav Kinsbursky skinsbur...@parallels.com
---
fs/nfsd/netns.h|5 +
fs/nfsd/nfs3xdr.c | 14 ++
This patch makes main step in NFSd containerisation.
There could be different approaches in how to make NFSd able to handle
incomming RPC request from different network namespaces.
But there are two main ideas:
1) Share NFSd kthreads betwween all network namespaces.
2) Create separated pool of
This patch moves nfsd_startup_generic() and nfsd_shutdown_generic() calls to
nfsd_startup_net() and nfsd_shutdown_net() respectively, which allow to call
nfsd_startup_net() instead of nfsd_startup() and makes code looks clearer.
It alos modifies nfsd_svc() and nfsd_shutdown() to check for
Function nfsd_shutdown is called from two places: nfsd_last_thread (when last
kernel thread is exiting) and nfsd_svc (in case of kthreads starting error).
When calling from nfsd_svc(), we can be sure that per-net resources are
allocated, so we don't need to check per-net nfsd_net_up boolean flag.
Converted staging/rtl8187se to use tabs instead of spaces for
indentation to fix the checkpatch error code indent should use tabs
where possible.
Signed-off-by: Sebastian Hahn snseh...@cip.cs.fau.de
---
drivers/staging/rtl8192u/ieee80211/ieee80211.h | 14 +-
Since we have generic NFSd resurces, we have to introduce some way how to
allocate and destroy those resources on first per-net NFSd start and on
last per-net NFSd stop respectively.
This patch replaces global boolean nfsd_up flag (which is unused now) by users
counter and use it to determine
NFSd have per-net resources and resources, used globally.
Let's move generic resources init and shutdown to separated functions since
they are going to be allocated on first NFSd service start and destroyed after
last NFSd service shutdown.
Signed-off-by: Stanislav Kinsbursky
This patch set prepares service control to be able to start separated
independent NFSd services in different network namespace environments.
Key changes are:
1) Create independent instances of NFSd service (and thus threads pool) for
each network namespace.
2) Control generic resources allocation
Hi Ted,
Did you get any time to look into this patch?
This problem is with ext4 only as ext4_truncate does not clean the
orphan list unlike that of ext3_truncate.
Instead, in case of failure to obtain handle, orphan list cleanup is
done in ext4_setattr.
But during mount, ext4_truncate is not
Hi Greg,
For next time: Once you have received an acked-by or reviewed-by, you
may add that line under your own signed-off-by in subsequent
mails. That way, the status of the patch can be tracked properly,
making life easier for everyone.
Greg, I think we are ready now. :-)
All
Commit cb57a2b4cff7edf2a4e32c0163200e9434807e0a (x86-32: Export
kernel_stack_pointer() for modules) added an include of the
module.h header in conjunction with adding an EXPORT_SYMBOL_GPL
of kernel_stack_pointer.
But module.h should be avoided for simple exports, since it in turn
includes the
On Thu, 06 Dec 2012, Viresh Kumar wrote:
On 6 December 2012 16:42, Lee Jones lee.jo...@linaro.org wrote:
I thought we'd be over this? The 'ID' will be represented by the
address of the chip i.e. stmpe1601@40, where '40' will be
distinguishing factor?
I haven't tested it but i thought we
Hello Nicolas, Havard, all,
I have a very obscure problem with a at91sam9260 board (almost 1 to 1
copy of the Atmel EK).
The MACB seems to stall when I use large (2 * MTU) UDP datagrams. The
test case is that a udp echo client (PC) sends datagrams with increasing
length to the AT91 until the max
Hi Al,
On 05/12/12 17:40, Al Viro wrote:
On Wed, Dec 05, 2012 at 04:08:41PM +, James Hogan wrote:
+TBIRES tail_end(TBIRES State, unsigned long orig_syscall)
+{
+struct pt_regs *regs = (struct pt_regs *)State.Sig.pCtx;
+unsigned long flags;
+
+if (user_mode(regs)) {
+
On Wed, Dec 05, 2012 at 07:45:39AM -0800, Linus Torvalds wrote:
On Wed, Dec 5, 2012 at 2:48 AM, Martin Steigerwald mar...@lichtvoll.de
wrote:
Linus, while I am interested in an answer I think that Dave and Christoph
as Linux filesystem developers actually deserve one (instead of silently
On Thu, Dec 06, 2012 at 12:14:02PM +1100, Dave Chinner wrote:
On Wed, Dec 05, 2012 at 10:25:17AM -0800, Linus Torvalds wrote:
Yes, people can argue that process is about technical issues too,
but let's be honest: our process is fluid. Not everything gets
reviewed on the mailing list, and
Linus,
please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
* Trivial CPU hotplug regression fix for the watchdog code.
Thanks,
tglx
--
Thomas Gleixner (1):
watchdog: Fix
Ed,
On Thu, 6 Dec 2012, Edward Donovan wrote:
So, let me try to confirm some things now, so I can learn as I go. To
spell out what's in the new patch:
The later line,
action = desc-action;
should have been this all along?
action = action-next;
Yes. My bad :(
And with that
The following changes since commit 84ad6845fbb1248228d3beab8084e4b5f6f82b1d:
Merge branch 'stable/for-jens-3.8' of
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen into for-3.8/drivers
(2012-12-01 09:42:41 +0100)
are available in the git repository at:
Hi Grant,
On 12/06/2012 11:00 AM, Grant Likely wrote:
On Mon, 12 Nov 2012 15:41:10 +0100, Peter Ujfalusi peter.ujfal...@ti.com
wrote:
Support for device tree booted kernel.
When the kernel is booted with DeviceTree blob we support one led per
leds-pwm device to have cleaner integration with
Hi,
(add lkml)
On 12/06, Ben Hutchings wrote:
On Wed, 2012-12-05 at 14:13 -0500, Joseph Salisbury wrote:
Hi Oleg,
A bug was opened against the Ubuntu kernel[0]. It was found that
reverting commit b40a79591ca918e7b91b0d9b6abd5d00f2e88c19 resolved this
bug, and allowed suspend/resume
On 04.12.2012, Daniel Vetter wrote:
Yeah, if anyone can somewhat reliably reproduce this
While writing a big file with dd and watching high resolution videos
on youtube, I've managed to reproduce the hang. Unfortunately, it
doesn't occur within seconds. Some playing around is neccessary, and
On Thursday, December 06, 2012 10:30:19 AM Vasilis Liaskovitis wrote:
Hi,
On Thu, Nov 29, 2012 at 10:44:11AM -0700, Toshi Kani wrote:
On Thu, 2012-11-29 at 12:04 +0100, Vasilis Liaskovitis wrote:
Yes, that's what I had in mind along with device_lock(). I think the
lock is necessary to
A kernel module can create a uio device. Get a reference to the module, if the
UIO device is in use. Otherwise the device can be removed and a uio write or an
access to am mmaped memory can cause a kernel Oops or other strange effects.
Signed-off-by: Benedikt Spranger b.spran...@linutronix.de
---
Using uio_pdrv_genirq can cause a system hangup due to accessing mmaped memory,
since the pm_runtime_put_sync() call in uio_release can disable clocks.
Also unloading a module wich creates/removes UIO devices can cause a system
crash. Track mappings and get a module reference to avoid this.
1 - 100 of 1216 matches
Mail list logo
