On Wed, Nov 28, 2012 at 07:24:52PM +0800, Chuansheng Liu wrote:
>
> By default, the watchdog threshold is 10, it means every 4s
> every CPU will receive one hrtimer interrupt, for low power
> device, it will cause 4-5mV power impact when device is deep
> sleep.
>
> So here want to optimize it as
Correct spelling typo in messages/i2o.
Signed-off-by: Masanari Iida
---
drivers/message/i2o/README.ioctl | 12 ++--
drivers/message/i2o/i2o_block.c | 2 +-
drivers/message/i2o/i2o_config.c | 2 +-
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/message/i2o/READM
On Fri, Nov 23, 2012 at 1:18 PM, Tushar Behera wrote:
> The objects allocated by devm_* APIs are managed by devres and are
> freed when the device is detached. Hence there is no need to remove
> them explicitly in remove function.
>
> Signed-off-by: Tushar Behera
Looks good to me.
Acked-by: Lin
The only EEPROM I know about or can speak to is the one attached to the 82571
and it doesn't set the MaxPayloadSize. That's done by the BIOS.
Todd Fujinaka
Technical Marketing Engineer
LAN Access Division (LAD)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
On Fri, Nov 09, 2012 at 05:27:47PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> When an event fails to parse and it's not in a new style format,
> try to parse it again as a cpu event.
>
> This allows to use sysfs exported events directly without //, so I can use
>
> perf record -e tx-aborts
On Wed, 2012-11-28 at 12:10 +0100, Thierry Reding wrote:
> Add myself as the maintainer of the NVIDIA Tegra DRM driver.
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -2504,6 +2504,14 @@ S: Supported
> F: drivers/gpu/drm/exynos
> F: include/drm/exynos*
>
> +NVIDIA TEGRA DRM DRIVER
A
On Wed, Nov 28, 2012 at 02:56:55PM +0100, Jiri Olsa wrote:
> aargh.. fixed subject.. copy&paste error ;-)
>
> also patches are available here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/linux.git
> perf/multi2
worked out some fixies with Arnaldo, new version is here:
git://git.kern
On Fri, Nov 23, 2012 at 4:08 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> The SP805 driver is only used by the Spear machines, and uses
> writel_relaxed, which is not available on all architectures.
>
> The dependency from CONFIG_ARM avoids compilation problems under
> randomconfig
On Wed, Nov 28, 2012 at 5:22 PM, Rabin Vincent
wrote:
> In order to provide per-user accounting, this separates the struct clk
> used in the common clock framework into two structures 'struct clk_core'
> and 'struct clk'. struct clk_core will be used for internal
> manipulation and struct clk wil
Adding more people (and the acpi list) to this report.
I'm seeing *very* few changes to the core suspend/resume path in 3.7,
and while there are some acpia updates, they seem to be pretty mild
too.
I think the acpi_os_wait_semaphore thing is a red herring - that's
just stale on the stack.
Do you
Quoting Shawn Guo (2012-11-28 07:17:44)
> On Wed, Nov 28, 2012 at 10:58:02PM +0800, Shawn Guo wrote:
> > On Wed, Nov 28, 2012 at 07:16:12AM -0600, Mark Langsdorf wrote:
> > > I'd
> > > have to move most of the logic of hb_set_target() into
> > > clk_highbank.c:clk_pll_set_rate() and then add extra
On Sat, Nov 24, 2012 at 1:22 AM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
>
> The header is used by drivers/dma/amba-pl08x.c, which can be compiled
> under x86, where PL080 exists under a PCI-to-AMBA bridge. This patche
> moves it where it can be accessed by other architectures, and fix
On Wed 28-11-12 10:26:31, Johannes Weiner wrote:
> On Tue, Nov 27, 2012 at 09:59:44PM +0100, Michal Hocko wrote:
> > @@ -3863,7 +3862,7 @@ int mem_cgroup_cache_charge(struct page *page, struct
> > mm_struct *mm,
> > return 0;
> >
> > if (!PageSwapCache(page))
> > - ret
On Wed, Nov 28, 2012 at 9:31 PM, viresh kumar wrote:
> On Wed, Nov 28, 2012 at 5:22 PM, Rabin Vincent
> Isn't something wrong here? For common clk case shouldn't
> this be:
>
>> +#define clk_to_clk_core(clk) (&clk->clk)
>> +#define clk_core_to_clk(core) (container_of(clk, ...)) //not getting int
On Fri, Nov 23, 2012 at 4:08 PM, Davide Ciminaghi wrote:
> Not all the architectures have readsl/writesl,
> use the more portable ioread32_rep/iowrite32_rep functions instead.
>
> Signed-off-by: Davide Ciminaghi
Can't think of anything better, put it in Russell's patch tracker when
you think yo
On Wed, Nov 28, 2012 at 07:35:20PM +0400, Stanislav Kinsbursky wrote:
> 28.11.2012 19:15, J. Bruce Fields пишет:
> >On Wed, Nov 28, 2012 at 07:12:03PM +0400, Stanislav Kinsbursky wrote:
> >>28.11.2012 19:09, J. Bruce Fields пишет:
> >>>On Tue, Nov 27, 2012 at 02:11:44PM +0300, Stanislav Kinsbursky
On Wed, 2012-11-28 at 00:41 +0100, Rafael J. Wysocki wrote:
> On Tuesday, November 27, 2012 03:03:47 PM Toshi Kani wrote:
> > On Tue, 2012-11-27 at 19:32 +0100, Vasilis Liaskovitis wrote:
> > > On Mon, Nov 26, 2012 at 05:19:01PM -0700, Toshi Kani wrote:
> > > > > >> Consider the following sequence
On Wed, Nov 28, 2012 at 10:14:33AM +1100, Dave Chinner wrote:
> From: Dave Chinner
>
> Several subsystems use the same construct for LRU lists - a list
> head, a spin lock and and item count. They also use exactly the same
> code for adding and removing items from the LRU. Create a generic
> type
Citeren "Wolfram Sang" :
Have you tested it? There have been problems reported when using
i2cdetect...
--
Pengutronix e.K. | Wolfram Sang
|
Industrial Linux Solutions |
http://www.pengutronix.de/ |
I've tested it with multiple configs.
i2cd
Olof / Kukjin,
On Tue, Nov 27, 2012 at 10:05 PM, Olof Johansson wrote:
> On Wed, Nov 28, 2012 at 02:23:09PM +0900, Kukjin Kim wrote:
>> Olof Johansson wrote:
>> >
>> > On Tue, Nov 27, 2012 at 2:27 PM, Kukjin Kim wrote:
>> > > On 11/28/12 07:11, Olof Johansson wrote:
>> > >>
>> > >> On Tue, Nov 2
> + if (!xfs_dqflock_nowait(dqp))
> + xfs_dqunlock(dqp);
> + goto out_miss_busy;
This seems to miss braces.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://v
On Sat, Nov 24, 2012 at 04:35:37PM +0530, Jassi Brar wrote:
> On 24 November 2012 12:33, Alessandro Rubini wrote:
> > My patch:
> >>> This driver would not compile if ARM_AMBA is selected under x86,
> >>> because "CS" and "DS" are already defined there. But AMBA
> >>> is used in the x86 world by
On 11/28/2012 10:01 AM, Mike Turquette wrote:
> Quoting Shawn Guo (2012-11-28 07:17:44)
>> On Wed, Nov 28, 2012 at 10:58:02PM +0800, Shawn Guo wrote:
>>> On Wed, Nov 28, 2012 at 07:16:12AM -0600, Mark Langsdorf wrote:
I'd
have to move most of the logic of hb_set_target() into
clk_hig
From: Paolo Valente
Date: Fri, 23 Nov 2012 22:03:19 +0100
> This patch turns QFQ into QFQ+, a variant of QFQ that provides the
> following two benefits: 1) QFQ+ is faster than QFQ, 2) differently
> from QFQ, QFQ+ correctly schedules also non-leaves classes in a
> hierarchical setting. A detailed
Dne 28.11.2012 17:01, Linus Torvalds napsal(a):
Adding more people (and the acpi list) to this report.
I'm seeing *very* few changes to the core suspend/resume path in 3.7,
and while there are some acpia updates, they seem to be pretty mild
too.
I think the acpi_os_wait_semaphore thing is a red
On Wed, Nov 28, 2012 at 2:33 PM, Michael Kerrisk wrote:
> On Thu, May 3, 2012 at 2:29 AM, Kay Sievers wrote:
>> From: Kay Sievers
> [...]
>> case SYSLOG_ACTION_SIZE_UNREAD:
>> - error = log_end - log_start;
>> + raw_spin_lock_irq(&logbuf_lock);
>> +
On 28.11.2012 17:13, Lucas Stach wrote:
> To be honest I still don't grok all of this, but nonetheless I try my
> best.
Sorry. I promised in another thread a write-up explaining the design. I
still owe you guys that.
> Anyway, shouldn't nvhost be something like an allocator used by host1x
> clien
On 11/28/2012 07:45 AM, Terje Bergström wrote:
> On 28.11.2012 16:06, Lucas Stach wrote:
>> Why do even need/use dma-buf for this use case? This is all one DRM
>> device, even if we separate host1x and gr2d as implementation modules.
>
> I didn't want to implement dependency to drm gem objects in
> I've tested it with multiple configs.
Please specify a bit more what you tested and what configs mean. It is
especially important to talk to slaves since this is where DMA problems
occured.
> i2cdetect -l gives me:
> i2c-0 i2c MXS I2C adapter I2C adapter
From: "Michael S. Tsirkin"
Date: Mon, 26 Nov 2012 17:14:16 +0200
> On Mon, Nov 19, 2012 at 10:26:41PM +0200, Michael S. Tsirkin wrote:
>> >
>> > Userspace bits:
>> > -
>> > 1) LKVM
>> > The latest vhost-blk userspace bits for kvm tool can be found here:
>> > g...@gith
From: "Michael S. Tsirkin"
Date: Mon, 26 Nov 2012 17:57:27 +0200
> If a single descriptor crosses a region, the
> second chunk length should be decremented
> by size translated so far, instead it includes
> the full descriptor length.
>
> Signed-off-by: Michael S. Tsirkin
Applied, thanks.
--
T
On Wed 28-11-12 02:29:08, Anton Vorontsov wrote:
> This is an attempt to implement David Rientjes' idea of mempressure
> cgroup.
>
> The main characteristics are the same to what I've tried to add to vmevent
> API:
>
> Internally, it uses Mel Gorman's idea of scanned/reclaimed ratio for
> pre
The code that relied on that flag was ripped out of btrfs quite some
time ago, and never added back. Josef indicated that he was going to
take a different approach to the problem in btrfs, and that we
could just eliminate this flag.
Cc: Josef Bacik
Signed-off-by: Jeff Layton
---
fs/btrfs/inode.
On Wed, Nov 28, 2012 at 08:57:31AM +, Lee Jones wrote:
> > I applied these 3 patches, but for DT we also need to specify compatible
> > ID and set up of_match_table pointer.
> Why do you need a compatible string?
The I2C subsystem guesses at a compatible string by default but it's
much bett
On Wed, Nov 28, 2012 at 05:08:27PM +0100, Linus Walleij wrote:
> On Fri, Nov 23, 2012 at 4:08 PM, Davide Ciminaghi wrote:
>
> > Not all the architectures have readsl/writesl,
> > use the more portable ioread32_rep/iowrite32_rep functions instead.
> >
> > Signed-off-by: Davide Ciminaghi
>
> Can'
From: Paul Bolle
Date: Tue, 27 Nov 2012 10:47:17 +0100
> Building ewrk3.o triggers this GCC warning:
> drivers/net/ethernet/dec/ewrk3.c: In function '__check_irq':
> drivers/net/ethernet/dec/ewrk3.c:1915:1: warning: return from
> incompatible pointer type [enabled by default]
>
> This c
From: Paul Bolle
Date: Tue, 27 Nov 2012 10:48:34 +0100
> Remove an outdated comment, that should have been removed in the
> patch named "MODULE_PARM conversions" from early 2005.
>
> Signed-off-by: Paul Bolle
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
On Wed, Nov 28, 2012 at 8:22 AM, Kay Sievers wrote:
> On Wed, Nov 28, 2012 at 2:33 PM, Michael Kerrisk
> wrote:
>
>> On a 2.6.31 system, immediately after SYSLOG_ACTION_READ_CLEAR, a
>> SYSLOG_ACTION_SIZE_UNREAD returns 0.
>
> Hmm, sounds like the right thing to do.
Right.
And that's the *OLD*
On Wed, Nov 28, 2012 at 05:04:47PM +0100, Michal Hocko wrote:
> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> index 095d2b4..5abe441 100644
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -57,13 +57,14 @@ extern int mem_cgroup_newpage_charge(struc
From: David Woodhouse
Date: Tue, 27 Nov 2012 23:28:36 +
> + if (test_bit(ATM_VF_RELEASED, &atmvcc->flags)
> + || test_bit(ATM_VF_CLOSE, &atmvcc->flags)
> + || !test_bit(ATM_VF_READY, &atmvcc->flags)) {
Please:
if (X ||
Y ||
Z)
not:
On Wed, 2012-11-28 at 01:29 +0100, Rafael J. Wysocki wrote:
> On Monday, November 26, 2012 10:44:08 AM Toshi Kani wrote:
> > Hi Rafael,
> >
> > Thanks for reviewing! My comments are in-line.
> >
> > On Sat, 2012-11-24 at 23:01 +0100, Rafael J. Wysocki wrote:
> > > On Thursday, November 08, 2012
On Wed, Nov 28, 2012 at 10:13:59AM +, Mel Gorman wrote:
> On Tue, Nov 27, 2012 at 03:19:38PM -0800, Linus Torvalds wrote:
> > On Tue, Nov 27, 2012 at 2:26 PM, Johannes Weiner wrote:
> > > On Tue, Nov 27, 2012 at 05:02:36PM -0500, Rik van Riel wrote:
> > >>
> > >> Kswapd going crazy is certainl
From: Zach Brown
use_mm() is used in more places than just aio. There's no need to
mention callers when describing the function.
Signed-off-by: Zach Brown
Signed-off-by: Kent Overstreet
---
mm/mmu_context.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/mm/mmu_context.c b/mm/mmu_conte
Signed-off-by: Kent Overstreet
---
drivers/usb/gadget/inode.c | 1 +
fs/aio.c | 61 ++
include/linux/aio.h| 61 --
3 files changed, 62 insertions(+), 61 deletions(-)
diff --git a/dr
The number of outstanding kiocbs is one of the few shared things left
that has to be touched for every kiocb - it'd be nice to make it percpu.
We can make it per cpu by treating it like an allocation problem: we
have a maximum number of kiocbs that can be outstanding (i.e. slots) -
then we just al
This just converts the ioctx refcount to the new generic dynamic percpu
refcount code.
Signed-off-by: Kent Overstreet
---
fs/aio.c | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 94218b7..0975675 100644
--- a/fs/aio.c
So, for sticking kiocb completions on the kioctx ringbuffer, we need a
lock - it unfortunately can't be lockless.
When the kioctx is shared between threads on different cpus and the rate
of completions is high, this lock sees quite a bit of contention - in
terms of cacheline contention it's the ho
Previously, aio_read_event() pulled a single completion off the
ringbuffer at a time, locking and unlocking each time.
Changed it to pull off as many events as it can at a time, and copy them
directly to userspace. The easiest way to do this was by making it
lockless, since we can't copy_to_user()
Yay faster kernel compiles
Signed-off-by: Kent Overstreet
---
arch/s390/hypfs/inode.c | 1 +
block/scsi_ioctl.c | 1 +
drivers/char/mem.c | 1 +
drivers/infiniband/hw/ipath/ipath_file_ops.c | 1 +
drivers/infiniband/hw/qib/
tested with:
CONFIG_I2C_MXS=m
CONFIG_I2C_MXS=y
in combination with CONFIG_GPIO_MXS enabled and disabled
used kernels: 3.6 and 3.7.0-rc6
My I2C slave is a PCF8575 i/o expander with some LEDs at the output.
These are controlled through sysfs.
Just tested with "i2cdetc -y -r 0" that crashes with
This implements a refcount with similar semantics to
atomic_get()/atomic_dec_and_test(), that starts out as just an atomic_t
but dynamically switches to per cpu refcounting when the rate of
gets/puts becomes too high.
It also implements two stage shutdown, as we need it to tear down the
percpu cou
See the previous patch for why we want to do this - this basically
implements a per cpu allocator for reqs_available that doesn't actually
allocate anything.
Note that we need to increase the size of the ringbuffer we allocate,
since a single thread won't necessarily be able to use all the
reqs_av
On Wed 28-11-12 11:37:36, Johannes Weiner wrote:
> On Wed, Nov 28, 2012 at 05:04:47PM +0100, Michal Hocko wrote:
> > diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> > index 095d2b4..5abe441 100644
> > --- a/include/linux/memcontrol.h
> > +++ b/include/linux/memcontrol.h
> > @
struct aio_ring_info was kind of odd, the only place it's used is where
it's embedded in struct kioctx - there's no real need for it.
The next patch rearranges struct kioctx and puts various things on their
own cachelines - getting rid of struct aio_ring_info now makes that
reordering a bit cleare
From: Zach Brown
This removes the retry-based AIO infrastructure now that nothing in tree
is using it.
We want to remove retry-based AIO because it is fundemantally unsafe.
It retries IO submission from a kernel thread that has only assumed the
mm of the submitting task. All other task_struct r
Converting read_events() to prepare_to_wait_exclusive() and
hrtimers simplifies it quite a bit.
Signed-off-by: Kent Overstreet
---
fs/aio.c | 78 +---
1 file changed, 21 insertions(+), 57 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
i
The usage of ctx->dead was fubar - it makes no sense to explicitly
check it all over the place, especially when we're already using RCU.
Now, ctx->dead only indicates whether we've dropped the initial
refcount. The new teardown sequence is:
set ctx->dead
hlist_del_rcu();
synchronize_rcu();
Now we
Signed-off-by: Kent Overstreet
---
fs/aio.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 1ff4d3b..7dee3aa 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -67,13 +67,6 @@ struct kioctx {
unsigned long user_id;
On Wed, Nov 28, 2012 at 04:14:30PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in
> drivers/staging/dgrp/dgrp_tty.c between commit 3ba89e96610b ("staging:
> dgrp: dgrp_tty.c: Remove the TIOCSSOFTCAR ioctl handler from dgrp
> driver") fr
Previously, allocating a kiocb required touching quite a few global
(well, per kioctx) cachelines... so batching up allocation to amortize
those was worthwhile. But we've gotten rid of some of those, and in
another couple of patches kiocb allocation won't require writing to any
shared cachelines, s
On Wed 28-11-12 17:46:40, Michal Hocko wrote:
> On Wed 28-11-12 11:37:36, Johannes Weiner wrote:
> > On Wed, Nov 28, 2012 at 05:04:47PM +0100, Michal Hocko wrote:
> > > diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> > > index 095d2b4..5abe441 100644
> > > --- a/include/linux
The aio code tries really hard to avoid having to deal with the
completion ringbuffer overflowing. To do that, it has to keep track of
the number of outstanding kiocbs, and the number of completions
currently in the ringbuffer - and it's got to check that every time we
allocate a kiocb. Ouch.
But
Cancelling kiocbs requires adding them to a per kioctx linked list,
which is one of the few things we need to take the kioctx lock for in
the fast path. But most kiocbs can't be cancelled - so if we just do
this lazily, we can avoid quite a bit of locking overhead.
Signed-off-by: Kent Overstreet
On Wed, Nov 28, 2012 at 5:37 PM, Linus Torvalds
wrote:
> On Wed, Nov 28, 2012 at 8:22 AM, Kay Sievers wrote:
>> On Wed, Nov 28, 2012 at 2:33 PM, Michael Kerrisk
>> wrote:
>>
>>> On a 2.6.31 system, immediately after SYSLOG_ACTION_READ_CLEAR, a
>>> SYSLOG_ACTION_SIZE_UNREAD returns 0.
>>
>> Hmm,
Freeing a kiocb needed to touch the kioctx for three things:
* Pull it off the reqs_active list
* Decrementing reqs_active
* Issuing a wakeup, if the kioctx was in the process of being freed.
This patch moves these to aio_complete(), for a couple reasons:
* aio_complete() already has to issu
aio_get_req() will fail if we have the maximum number of requests
outstanding, which depending on the application may not be uncommon. So
avoid doing an unnecessary fget().
Signed-off-by: Kent Overstreet
---
fs/aio.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
On Wed, Nov 28, 2012 at 05:41:32PM +0200, Eli Billauer wrote:
> These entries are referred to by the Xillybus driver.
>
> Signed-off-by: Eli Billauer
> ---
> include/linux/pci_ids.h |6 ++
Please read the top of this file for why you shouldn't be adding these
device ids to that file.
Ca
Signed-off-by: Kent Overstreet
---
fs/aio.c | 57 -
1 file changed, 24 insertions(+), 33 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 4dcc02f..0ed14e8 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -8,6 +8,8 @@
*
* See ../COPYING fo
On Fri, Nov 16, 2012 at 07:38:41PM -0800, Yinghai Lu wrote:
> Now init_memory_mapping is called two times, later will be called for every
> ram ranges.
What is 'later'? Can you say in which of the patches it will
be called for every RAM range?
>
> Could put all related init_mem calling together
On Fri, Nov 16, 2012 at 07:38:44PM -0800, Yinghai Lu wrote:
> We should not do that in every calling of init_memory_mapping.
Right.
>
> At the same time need to move down early_memtest, and could remove
> after_bootmem
->'remov
Bunch of performance improvements and cleanups Zach Brown and I have
been working on. The code should be pretty solid at this point, though
it could of course use more review and testing.
The results in my testing are pretty impressive, particularly when an
ioctx is being shared between multiple t
From: Zach Brown
These are handy for measuring the cost of the aio infrastructure with
operations that do very little and complete immediately.
Signed-off-by: Zach Brown
Signed-off-by: Kent Overstreet
---
drivers/char/mem.c | 35 +++
1 file changed, 35 insertio
On Fri, Nov 16, 2012 at 07:38:40PM -0800, Yinghai Lu wrote:
> It will need to call split_mem_range().
.. which implies that it needs to call it now, but I could
not find the call in your patch. Then realized you meant
to do that in the further patches. To avoid this confusion
I would recommend you
Minor refactoring, to get rid of some duplicated code
Signed-off-by: Kent Overstreet
---
fs/aio.c | 72 +++-
1 file changed, 39 insertions(+), 33 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 91879d4..a993234 100644
--- a/fs/aio.
s/paramters/parameters/
On Fri, Nov 16, 2012 at 07:38:43PM -0800, Yinghai Lu wrote:
> call split_mem_range inside the function.
So this looks to introduce an extra split_mem_range which
does the same operations on 'mr' that is done in find_early_table_space.
Could the find_early_table_space use
Nothing used the return value, and it probably wasn't possible to use it
safely for the locked versions (aio_complete(), aio_put_req()). Just
kill it.
Acked-by: Zach Brown
Signed-off-by: Kent Overstreet
---
fs/aio.c| 19 +++
include/linux/aio.h | 8
2 files
From: Zach Brown
This removes the only in-tree user of aio retry. This will let us
remove the retry code from the aio core.
Removing retry is relatively easy as the USB gadget wasn't using it to
retry IOs at all. It always fully submitted the IO in the context of
the initial io_submit() call.
From: Zach Brown
Signed-off-by: Zach Brown
Signed-off-by: Kent Overstreet
---
include/linux/aio.h | 24
1 file changed, 24 deletions(-)
diff --git a/include/linux/aio.h b/include/linux/aio.h
index 31ff6db..b46a09f 100644
--- a/include/linux/aio.h
+++ b/include/linux/a
On Wed, 28 Nov 2012 14:48:52 +0800
Jason Wang wrote:
> On 11/28/2012 12:49 AM, Stephen Hemminger wrote:
> > On Tue, 27 Nov 2012 14:45:13 +0800
> > Jason Wang wrote:
> >
> >> On 11/27/2012 01:37 AM, Stephen Hemminger wrote:
> >>> On Mon, 26 Nov 2012 15:56:52 +0800
> >>> Jason Wang wrote:
> >>>
>
On 11/23/2012 08:11 AM, Norbert Warmuth wrote:
Thomas Gleixner writes:
On Wed, 21 Nov 2012, Norbert Warmuth wrote:
3.7-rc6 booted with nmi_watchdog=0 fails to suspend to RAM or
offline CPUs. It's reproducable with a KVM guest and physical
system.
Does the patch below fix it?
Yes.
- Norbert
On Wed, Nov 28, 2012 at 05:41:33PM +0200, Eli Billauer wrote:
> Xillybus is a general-purpose framework for communication between programmable
> logic (FPGA) and a host. It provides a simple connection between hardware
> FIFOs
> in the FPGA and their respective device files on the host. The user s
On Fri, Nov 16, 2012 at 07:38:45PM -0800, Yinghai Lu wrote:
> It should take physical address range that will need to be mapped.
> find_early_table_space should take range that pgt buff should be in.
>
> Separating page table size calculating and finding early page table to
> reduce confusing.
Yo
On Wed, 2012-11-28 at 11:41 -0500, David Miller wrote:
>
> Please:
>
> if (X ||
> Y ||
> Z)
>
> not:
>
> if (X
> || Y
> || Z)
Thanks. Fixed in both Krzysztof's original pppoatm version, and my
br2684 patch, in the git tree at git:
On Wed, Nov 28, 2012 at 8:21 AM, Zdenek Kabelac wrote:
>
> I've opened https://bugzilla.kernel.org/show_bug.cgi?id=51071
> and attached picture there which is all I have.
>
> I'll try to decode exact code line.
Uhhuh. It's missing much of the relevant parts of the code line, in
particular the ac
> > > > > By using acpi_install_notify_handler(), each driver needs to walk
> > > > > through the entire ACPI namespace to find its associated ACPI devices
> > > > > and call it to register one by one. I think this is more work for
> > > > > non-ACPI drivers than defining acpi_driver.
> > > >
> >
From: David Woodhouse
Date: Wed, 28 Nov 2012 17:01:10 +
> On Wed, 2012-11-28 at 11:41 -0500, David Miller wrote:
>>
>> Please:
>>
>> if (X ||
>> Y ||
>> Z)
>>
>> not:
>>
>> if (X
>> || Y
>> || Z)
>
> Thanks. Fixed in both Kr
On Fri, Nov 16, 2012 at 07:38:49PM -0800, Yinghai Lu wrote:
> We are going to map ram only, so under max_low_pfn_mapped,
> between 4g and max_pfn_mapped does not mean mapped at all.
I think I know what you are saying but I am having a hard
time parsing it. Is this what you mean?
"We check to see
On Fri, Nov 16, 2012 at 07:38:50PM -0800, Yinghai Lu wrote:
> We are going to map ram only, so under max_low_pfn_mapped,
> between 4g and max_pfn_mapped does not mean mapped at all.
Perhaps the re-write I mentioned in the earlier email could
help here.
>
> Use pfn_range_is_mapped() directly.
>
Hi,
(adding the i2c list)
On Wed, Nov 28, 2012 at 05:44:49PM +0100, Sander van Ginkel wrote:
> tested with:
> CONFIG_I2C_MXS=m
> CONFIG_I2C_MXS=y
>
> in combination with CONFIG_GPIO_MXS enabled and disabled
>
> used kernels: 3.6 and 3.7.0-rc6
>
> My I2C slave is a PCF8575 i/o expander with som
On Wed, 2012-11-28 at 12:04 -0500, David Miller wrote:
> Do you want me to pull that tree into net-next or is there a plan to
> repost the entire series of work for a final submission?
I think it needs a little more testing/consensus first. I'd like an ack
from Chas on the atm ->release_cb() thing
On Fri, Nov 16, 2012 at 07:38:51PM -0800, Yinghai Lu wrote:
> We are going to map ram only, so under max_low_pfn_mapped,
> between 4g and max_pfn_mapped does not mean mapped at all.
>
> Use pfn_range_is_mapped() to find out if range is mapped for initrd.
>
> That could happen bootloader put initr
Helps with figuring out when things went wrong.
Signed-off-by: Mark Brown
---
drivers/regulator/core.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index fe4a1b6..af97b62 100644
--- a/drivers/regulator/core.c
+++ b
Hi Sekhar,
On Wed, 2012-11-28 at 14:19 +0530, Sekhar Nori wrote:
> Hi Vivien,
>
> On 9/11/2012 5:59 AM, Vivien Didelot wrote:
> > Without this patch, da8xx_register_spi() registers the SPI board info,
> > the SPI controller, and sets its number of chipselect to the size of the
> > static spi_boar
From: David Woodhouse
Date: Wed, 28 Nov 2012 17:09:15 +
> And then I'll either send an explicit pull request, or submit it as
> patches ― whichever you prefer.
The canonical thing is to do both, send the pull request in the
"[PATCH 0/N]" email, and then the patches so everyone can see the
fi
On Fri, Nov 16, 2012 at 07:38:52PM -0800, Yinghai Lu wrote:
> From: Jacob Shin
>
> Currently direct mappings are created for [ 0 to max_low_pfn< and [ 4GB to max_pfn< backed by actual DRAM. This is fine for holes under 4GB which are covered
> by fixed and variable range MTRRs to be UC. However, w
On Wed, Nov 28, 2012 at 10:18:02AM -0200, Mauro Carvalho Chehab wrote:
> Em Wed, 28 Nov 2012 12:56:10 +0100
> Hans Verkuil escreveu:
>
> > On Wed 28 November 2012 12:45:37 Dan Carpenter wrote:
> > > I wish people wouldn't submit big patches right before the merge
> > > window opens... :/ It's be
Some Arizona devices such as the WM5102 can use DVFS on their digital core,
for these devices allow the voltage range to vary in the default setup.
Signed-off-by: Mark Brown
---
drivers/regulator/arizona-ldo1.c | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --
These entries are referred to by the Xillybus driver.
Signed-off-by: Eli Billauer
---
include/linux/pci_ids.h |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 9d36b82..9f2c724 100644
--- a/include/linux/pci_ids.
The number of voltage slots supported by the LDO is 7, not 6.
Signed-off-by: Mark Brown
---
drivers/regulator/arizona-ldo1.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index a1e0451..e4b7dd4 100644
--
Signed-off-by: Mark Brown
---
drivers/regulator/arizona-ldo1.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index b44fa6f..908996a 100644
--- a/drivers/regulator/arizona-ldo1.c
+++ b/drivers/regulator/arizona-ldo1.c
@@
201 - 300 of 820 matches
Mail list logo
