On Fri, Jun 07, 2013 at 03:08:29PM +0200, Laura Lawniczak wrote:
> blen and bn were only used in commented code fragments.
> since comments should be informative and not for storing old
> code, both, commented code and variables, were removed.
>
> Signed-off-by: Laura Lawniczak
> Signed-off-by:
Hi David,
On 06/07/2013 11:06 PM, David Lang wrote:
> On Fri, 7 Jun 2013, Preeti U Murthy wrote:
>
>> Hi Catalin,
>>
>> On 06/07/2013 08:21 PM, Catalin Marinas wrote:
>
>>> Take the cpuidle example, it uses the load average of the CPUs,
>>> however this load average is currently controlled by
Hi Catalin,
On 06/08/2013 04:58 PM, Catalin Marinas wrote:
> On Fri, Jun 07, 2013 at 07:08:47PM +0100, Preeti U Murthy wrote:
>> On 06/07/2013 08:21 PM, Catalin Marinas wrote:
>>> I think you are missing Ingo's point. It's not about the scheduler
>>> complying with decisions made by various
Hi Rafael,
On 06/08/2013 07:32 PM, Rafael J. Wysocki wrote:
> On Saturday, June 08, 2013 12:28:04 PM Catalin Marinas wrote:
>> On Fri, Jun 07, 2013 at 07:08:47PM +0100, Preeti U Murthy wrote:
>>> On 06/07/2013 08:21 PM, Catalin Marinas wrote:
I think you are missing Ingo's point. It's not
On Fri, Jun 07, 2013 at 02:37:12PM -0500, Shawn Bohrer wrote:
> I've started testing the 3.10 kernel, previously I was on 3.4, and I'm
> encounting some fairly large stalls in my memory mapped writes in the
> range of .01 to 1s. I've managed to capture two of these stalls so
> far and both looked
On 06/08/2013 02:31 AM, Haojian Zhuang wrote:
> On 8 June 2013 03:18, Stephen Warren wrote:
>> On 06/06/2013 09:30 AM, Christian Ruppert wrote:
>>> On Thu, Jun 06, 2013 at 10:32:21PM +0800, Haojian Zhuang wrote:
On 6 June 2013 22:11, Christian Ruppert
wrote:
> On Wed, Jun 05, 2013
On some systems, __used is already defined in sys/cdefs.h and causes
a build warning:
scripts/mod/file2alias.c:85:1: warning: "__used" redefined
In file included from /usr/include/stdio.h:64,
from scripts/mod/modpost.h:1,
from
The pointer passed to the _r() macro does not always match the type
of the function that it is aliasing and raises several of the following
warnings at compile time:
warning: passing argument 1 of ‘r8’ from incompatible pointer type
Fixed by casting the pointers to (void *) so they work with
Uk National Lottery
Ref: L/200-26937
Batch: 2007MJL-01
FINAL NOTIFICATION
We are pleased to inform you today 6th June, 2013 of the result
of the winners of the UK NATIONAL LOTTERY ONLINE PROMO PROGRAMME, held
on the 30th of May, 2013.
You have therefore been approved
Immutable biovecs: Drivers no longer modify the biovec array directly
(bv_len/bv_offset in particular) - we add a real iterator to struct bio
that lets drivers partially complete a bio while only modifying the
iterator. The iterator has the existing bi_sector, bi_size, bi_idx
memembers, and also
Some of bcache's utility code has made it into the rest of the kernel,
so drop the bcache versions.
Bcache used to have a workaround for allocating from a bio set under
generic_make_request() (if you allocated more than once, the bios you
already allocated would get stuck on current->bio_list
This adds a mechanism by which we can advance a bio by an arbitrary
number of bytes without modifying the biovec: bio->bi_iter.bi_bvec_done
indicates the number of bytes completed in the current bvec.
Various driver code still needs to be updated to not refer to the bvec
directly before we can
Now that we've got a mechanism for immutable biovecs -
bi_iter.bi_bvec_done - we need to convert drivers to use primitives that
respect it instead of using the bvec array directly.
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
Cc: NeilBrown
Cc: "Ed L. Cashin"
Cc: Alasdair Kergon
Cc:
Our fancy new bvec iterator makes code like this much easier to write.
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
---
fs/bio.c | 60 +---
1 file changed, 25 insertions(+), 35 deletions(-)
diff --git a/fs/bio.c b/fs/bio.c
index
bio_iovec_idx() and __bio_iovec() don't have any valid uses anymore -
previous users have been converted to bio_iovec_iter() or other methods.
__BVEC_END() has to go too - the bvec array can't be used directly for
the last biovec because we might only be using the first portion of it,
we have to
Now that drivers have been converted to the new bvec_iter primitives,
there's no need to trim the bvec before we submit it; and we can't trim
it once we start sharing bvecs.
It used to be that passing a partially completed bio (i.e. one with
nonzero bi_idx) to generic_make_request() was a
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
Cc: "Martin K. Petersen"
Cc: "James E.J. Bottomley"
---
block/blk-integrity.c | 40 ++-
drivers/scsi/sd_dif.c | 30 +++---
fs/bio-integrity.c| 108 --
For immutable biovecs, we'll be introducing a new bio_iovec() that uses
our new bvec iterator to construct a biovec, taking into account
bvec_iter->bi_bvec_done - this patch updates existing users for the new
usage.
Some of the existing users really do need a pointer into the bvec array
- those
This adds a generic mechanism for chaining bio completions. This is
going to be used for a bio_split() replacement, and some other things in
the future.
This is implemented with a new bio flag that bio_endio() checks; it
would definitely be cleaner to implement chaining with a bi_end_io
function,
When we start sharing biovecs, keeping bi_vcnt accurate for splits is
going to be error prone - and unnecessary, if we refactor some code.
So bio_segments() has to go - but most of the existing users just needed
to know if the bio had multiple segments, which is easier - add a
We need to convert the dm code to the new bvec_iter primitives which
respect bi_bvec_done; they also allow us to drastically simplify dm's
bio splitting code.
Also kill bio_sector_offset(), dm was the only user and it doesn't make
much sense anymore.
Signed-off-by: Kent Overstreet
Cc: Jens
This is prep work for introducing a more general bio_split().
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
Cc: NeilBrown
Cc: Alasdair Kergon
Cc: Lars Ellenberg
Cc: Peter Osterlund
Cc: Sage Weil
---
drivers/block/pktcdvd.c | 2 +-
drivers/md/linear.c | 2 +-
drivers/md/raid0.c |
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
---
fs/bio-integrity.c | 45 ---
fs/bio.c| 90 -
include/linux/bio.h | 30 --
3 files changed, 165 deletions(-)
diff --git a/fs/bio-integrity.c
The new bio_split() can split arbitrary bios - it's not restricted to
single page bios, like the old bio_split() (previously renamed to
bio_pair_split()). It also has different semantics - it doesn't allocate
a struct bio_pair, leaving it up to the caller to handle completions.
Then convert the
The way the block layer is currently written, it goes to great lengths
to avoid having to split bios; upper layer code (such as bio_add_page())
checks what the underlying device can handle and tries to always create
bios that don't need to be split.
But this approach becomes unwieldy and
Now that we've got drivers converted to the new immutable bvec
primitives, bio splitting becomes much easier. In a few patches,
bio_clone() will be changed to share the old bio's bvec instead of
copying it, and bio_split() will do exactly what's being done here.
Signed-off-by: Kent Overstreet
Next patch is going to make generic_make_request() handle arbitrary
sized bios by splitting them if necessary. It makes more sense to call
blk_queue_bounce() first, before the bios have been fragmented.
Also, __blk_recalc_rq_segments() now doesn't have to take into account
potential bouncing -
generic_make_request() will now do for us what the code in blk-lib.c was
doing manually, with the bio_batch stuff - we still need some looping in
case we're trying to discard/zeroout more than around a gigabyte, but
when we can submit that much at a time doing the submissions in parallel
really
So we get to delete our hacky workaround.
Signed-off-by: Kent Overstreet
---
drivers/md/bcache/bcache.h| 18
drivers/md/bcache/debug.c | 2 +-
drivers/md/bcache/io.c| 100 +-
drivers/md/bcache/journal.c | 4 +-
Near total rewrite of fs/direct-io.c. This makes use of our new bio
splitting functionality, and the fact that generic_make_request() will
take arbitrary size bios - we allocate a bio, pin pages to it directly,
then call the getblocks() function to map it wherever the filesystem
tells us -
Now that drivers have been converted to the bvec_iter primitives, they
shouldn't be modifying the biovec anymore and thus saving it is
unnecessary - code that was previously making a backup of the bvec array
can now just save bio->bi_iter.
Also, when cloning bios we can usually just reuse the
This replaces some of the code that was in __bio_map_user_iov(), and
soon we're going to use this helper in the dio code.
Note that this relies on the recent change to make
generic_make_request() take arbitrary sized bios - we're not using
bio_add_page() here.
Signed-off-by: Kent Overstreet
Cc:
Bcache has a hack to avoid cloning the biovec if it's all full pages -
but with immutable biovecs coming this won't be necessary anymore.
For now, we remove the special case and always clone the bvec array so
that the immutable biovec patches are simpler.
Signed-off-by: Kent Overstreet
---
This patch doesn't itself have any functional changes, but immutable
biovecs are going to add a bi_bvec_done member to bi_iter, which will
need to be saved too here.
Signed-off-by: Kent Overstreet
Cc: Alasdair Kergon
Cc: dm-de...@redhat.com
---
drivers/md/dm-bio-record.h | 12 +++-
1
Yes, it's that time again - another week or so has passed, and a new
release candidate is made in order to encourage and remind people to
try things out.
I wish I could say that things are calming down, but I'd be lying. rc5
is noticeably bigger than rc4, both in number of commits and in files
On 06/06/2013 06:54:17 AM, Markus Trippelsdorf wrote:
Since v3.8.0 several people reported intermittent IO errors that
happen
during high system load while using "emerge" under Gentoo:
...
see: https://bugs.gentoo.org/show_bug.cgi?id=459674
(A similar issue also happens when building
On 06/05/2013 09:49:30 PM, Kees Cook wrote:
Avoid strncpy anti-pattern. Use strdup() instead, as already done for
the logfile optarg.
Signed-off-by: Kees Cook
---
Fix for -mm clean-up-scary-strncpydst-src-strlensrc-uses-fix.patch
---
Documentation/accounting/getdelays.c |4 ++--
1 file
Hi!
I'd like to convert Nokia N900 to device tree.
Unfortunately, serial port is not easily available (very special cable
would be needed, does someone know where to get one?) and I don't have
BDI (and very special cable would be needed, too).
So I tried doing very small first step, hoping that
On 06/09/2013 09:19 AM, Aaron Lu wrote:
> On 06/09/2013 06:28 AM, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> There is no particular reason why acpi_bus_driver_init() needs to be
>> a separate function and its location with respect to its only caller,
>> acpi_device_probe(), makes
On 06/09/2013 01:49 AM, Bjorn Helgaas wrote:
> s/geniric/generic/ in subject
>
Could you provide more details information ?
Thanks.
--
Chen Gang
Asianux Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
On 2013/6/7 23:10, Greg KH wrote:
> On Fri, Jun 07, 2013 at 05:09:16PM +0800, Li Zefan wrote:
>> On 2013/5/25 2:23, Greg KH wrote:
>>> I'm announcing the release of the 3.0.80 kernel.
>>>
>>> All users of the 3.0 kernel series must upgrade.
>>>
>>> The updated 3.0.y git tree can be found at:
>>>
On 06/09/2013 06:28 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> There is no particular reason why acpi_bus_driver_init() needs to be
> a separate function and its location with respect to its only caller,
> acpi_device_probe(), makes the code a bit difficult to follow.
>
>
On 06/08/2013 10:14 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> With the introduction of ACPI scan handlers, ACPI device objects
> with an ACPI scan handler attached to them must not be bound to
> an ACPI driver any more. Unfortunately, however, the ACPI video
> driver attempts
This driver adds support the Cortex-A9 based SoCs from Rockchip,
so at least the RK2928, RK3066 (a and b) and RK3188.
Earlier Rockchip SoCs seem to use similar mechanics for gpio
handling so should be supportable with relative small changes.
Pull handling on the rk3188 is currently a stub, due to
The previous patch introduced constants to combine pinconfig settings
into one value for easier devicetree handling.
Therefore also add a function, that can separate these bitmaps into
regular generic pinconfig options for handling inside pinctrl drivers.
Signed-off-by: Heiko Stuebner
---
Most pinconfig options either ignore the argument or only have two states
for them. Therefore it's possible to combine them into one value in dt
bindings as bits, resulting in smaller pin definitions.
Signed-off-by: Heiko Stuebner
---
.../bindings/pinctrl/pinctrl-bindings.txt |6
Hi Linus,
following your suggestions for a common handling of things like pulls in dt,
I've come up with the following solution - hopefully I've gotten the correct
meaning of your explanaitions.
It handles all the pinconfigs that either ignore the argument, or have very
simple one, like
On 06/07/13 04:23, Markos Chandras wrote:
> The VIRTUALIZATION symbol depends on HAVE_KVM but CONFIG_REMOTEPROC
> and CONFIG_RPMSG do not select HAVE_KVM leading to the following
> warning and build problems later on:
>
> warning: (REMOTEPROC && RPMSG) selects VIRTUALIZATION which has unmet
>
From: Rafael J. Wysocki
There is no particular reason why acpi_bus_driver_init() needs to be
a separate function and its location with respect to its only caller,
acpi_device_probe(), makes the code a bit difficult to follow.
Besides, it doesn't really make sense to check if 'device' is not
On Saturday, June 08, 2013 11:31:37 PM Stratos Karafotis wrote:
> On 06/08/2013 05:05 PM, Rafael J. Wysocki wrote:
> > On Saturday, June 08, 2013 03:34:29 PM Stratos Karafotis wrote:
> >> I also did the test with the way you mentioned. But I thought to run
> >> turbostat for 100 sec as I did with
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
* Trivial fixes: Unused variable removal
* Posix-timers: Add the clock ID to the new proc interface to make it
useful. The interface
Hi Linus,
Please pull the following branch with irqdomain bug fixes.
Thanks,
g.
The following changes since commit d683b96b072dc4680fc74964eca77e6a23d1fa6e:
Linux 3.10-rc4 (2013-06-02 17:11:17 +0900)
are available in the git repository at:
git://git.secretlab.ca/git/linux
On Mon, 3 Jun 2013, Uwe Kleine-König wrote:
> Hello Rusty,
>
> [added akpm to Cc: who took the patch back then and Julia for the
> coccinelle part below]
>
> On Mon, Jun 03, 2013 at 11:59:15AM +0930, Rusty Russell wrote:
> >
> > Back in 2011, Uwe Kleine-König added the nonsensically-named
> >
Hi all,
On 08/06/13 09:52 AM, Graeme Smecher wrote:
Other architectures don't do it, and it conflicts with the extern'd definition
in include/linux/kgdb.h.
Signed-off-by: Graeme Smecher
CC: Michal Simek
CC:linux-kernel@vger.kernel.org
---
arch/microblaze/kernel/kgdb.c |2 +-
1 files
Am Freitag, 24. Mai 2013, 13:03:18 schrieb Martin Steigerwald:
> Hi!
>
> With 3.10-rc2 I see fan always or almost always on, even during extended
> periods of basically idling around. I did not notice this with 3.9. This is
> on an ThinkPad T520 with Intel Sandybridge i5-2520M dual core with
>
On 4/11/2013 1:46 AM, Tomasz Stanislawski wrote:
> This patch adds a hash table to quicken searching of a smack label by its
> name.
>
> For a typical idle for TIZEN the CPU wastes circa 5-10% of its cycles for
> processing the smk_find_entry function. This patch adds a hash map that should
>
On 06/08/2013 05:05 PM, Rafael J. Wysocki wrote:
> On Saturday, June 08, 2013 03:34:29 PM Stratos Karafotis wrote:
>> I also did the test with the way you mentioned. But I thought to run
>> turbostat for 100 sec as I did with powertop.
>
> Ah, OK.
>
>> Actually benchmark lasts about 96 secs.
>>
On Sat, Jun 8, 2013 at 2:04 PM, Grant Likely wrote:
> The irqdomain core will report a log message for any attempted map call
> that fails unless the error code is -EPERM. This patch changes the
> Versatile irq controller drivers to use -EPERM because it is normal for
> a subset of the IRQ inputs
After bisecting I found the responsible commit.
50d8f87d2b3: powerpc/fsl-pci Make PCIe hotplug work with Freescale
PCIe controllers
Reverting this commit allowed my board to boot again.
@Rojhalat: Please have a look at
http://marc.info/?l=linux-kernel=137071294204858=2
for my initial bugreport.
On Thu, 30 May 2013, Paul Bolle wrote:
> promcon.o is built if CONFIG_PROM_CONSOLE is set. But there's no Kconfig
> symbol PROM_CONSOLE, so promcon.c is unbuildable. Remove it.
>
> Signed-off-by: Paul Bolle
> ---
> 0) Untested.
>
> 1) There used to be a Kconfig symbol PROM_CONSOLE. But it was
On 08/06/2013 00:48, David Miller wrote:
From: Eliezer Tamir
Date: Wed, 05 Jun 2013 13:34:00 +0300
And here is v9.
Except for typo fixes in comments/description, only 2/7 and 5/7 were changed.
Thanks to everyone for their input.
Since there is some discussion about the way the poll() bits
s/geniric/generic/ in subject
--
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://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
The following changes since commit d683b96b072dc4680fc74964eca77e6a23d1fa6e:
Linux 3.10-rc4 (2013-06-02 17:11:17 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to
On Saturday 08 June 2013 11:42:54 Daniel Tang wrote:
>
> On 08/06/2013, at 3:55 AM, Arnd Bergmann wrote:
>
> If it hasn't been merged yet, would it be possible for me to
> send version 2 of the patches? Or would you rather I wait
> until it is merged and send in a separate patch to fix them?
Good evening,
I recently tested the latest 3.10-rc release (rc4) on my powerpc based
routerboard which is currently running very stable on a 3.9 release.
During boot I immediately got a kernel panic.
I was able to get a log of the trace with the serial console.
[0.039522] PCI: Probing PCI
Other architectures don't do it, and it conflicts with the extern'd definition
in include/linux/kgdb.h.
Signed-off-by: Graeme Smecher
CC: Michal Simek
CC: linux-kernel@vger.kernel.org
---
arch/microblaze/kernel/kgdb.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Fri, Jun 07, 2013 at 11:12:47AM +0200, Hans Verkuil wrote:
> On Fri May 31 2013 13:40:25 Jon Arne Jørgensen wrote:
> > Implement i2c_board_info.platform_data handling in the driver so we can
> > make device specific changes to the chips we support.
> >
> > Signed-off-by: Jon Arne Jørgensen
>
On Fri, Jun 07, 2013 at 11:01:06AM +0200, Hans Verkuil wrote:
> On Fri May 31 2013 13:40:26 Jon Arne Jørgensen wrote:
> > On video std change, the driver would disable the automatic field
> > detection on the gm7113c chip, and force either 50Hz or 60Hz.
> > Don't do this any more.
>
> Sorry, I'm
From: Borislav Petkov
arch/x86/kernel/cpu/intel_cacheinfo.c: In function ‘init_intel_cacheinfo’:
arch/x86/kernel/cpu/intel_cacheinfo.c:642:28: warning: ‘this_leaf.size’ may be
used uninitialized in this function [-Wmaybe-uninitialized]
arch/x86/kernel/cpu/intel_cacheinfo.c:643:29: warning:
From: Julia Lawall
The argument to kfree should not be the address of a structure field.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/free/kfreeaddr.cocci | 32
1 file changed, 32 insertions(+)
diff --git a/scripts/coccinelle/free/kfreeaddr.cocci
Hi Linus,
Please consider the follwing fixes for the slave-dmaengine.
Fix from Andy is for dmatest regression reported by Will and Rabin has fixed
runtime ref counting for st_dma40
The following changes since commit e4aa937ec75df0eea0bee03bffa3303ad36c986b:
Linus Torvalds (1):
Linux
2013/6/8 Julia Lawall :
> From: Julia Lawall
>
> The argument to kfree should not be the address of a structure field.
> The argument is adjusted to correspond to what is found in the subsequent
> remove function.
This was already addressed in
[PATCH RESEND 1/2] mtd: bcm47: convert kzalloc to
From: Julia Lawall
The argument to kfree should not be the address of a structure field.
The argument is adjusted to correspond to what is found in the subsequent
remove function.
The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)
//
@@
expression e;
On Sat, Jun 08, 2013 at 07:08:17AM -0700, Greg KH wrote:
> On Fri, Jun 07, 2013 at 08:53:12PM -0700, Guenter Roeck wrote:
> > On Fri, Jun 07, 2013 at 12:58:16PM -0700, Greg KH wrote:
> > > I'm announcing the release of the 3.9.5 kernel.
> > >
> > > All users of the 3.9 kernel series must upgrade.
On Fri, Jun 07, 2013 at 12:58:16PM -0700, Greg KH wrote:
> I'm announcing the release of the 3.9.5 kernel.
>
> All users of the 3.9 kernel series must upgrade.
>
> The updated 3.9.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>
2013/6/7 Tejun Heo :
> Hello,
>
> On Thu, Jun 06, 2013 at 09:52:56PM +0900, Akinobu Mita wrote:
>> +static bool sg_miter_get_next_page(struct sg_mapping_iter *miter)
>> +{
>> + if (!miter->__remaining) {
>> + struct scatterlist *sg;
>> + unsigned long pgoffset;
>> +
>>
On Sat, Jun 08, 2013 at 11:14:47AM +0200, Tobias Winter wrote:
> On 06/07/2013 07:25 PM, Greg KH wrote:
> > On Fri, Jun 07, 2013 at 11:55:59AM +0200, Tobias Winter wrote:
> >> On 06/07/2013 08:00 AM, Tobias Winter wrote:
> >>> CC drivers/usb/serial/console.o
> >>>
On Fri, Jun 07, 2013 at 08:53:12PM -0700, Guenter Roeck wrote:
> On Fri, Jun 07, 2013 at 12:58:16PM -0700, Greg KH wrote:
> > I'm announcing the release of the 3.9.5 kernel.
> >
> > All users of the 3.9 kernel series must upgrade.
> >
> > The updated 3.9.y git tree can be found at:
> >
From: Rafael J. Wysocki
With the introduction of ACPI scan handlers, ACPI device objects
with an ACPI scan handler attached to them must not be bound to
an ACPI driver any more. Unfortunately, however, the ACPI video
driver attempts to do just that if there is a _ROM ACPI control
method defined
2013/6/6 Imre Deak :
> Looks ok to me, perhaps adding the seek functionality to the mapping
> iterator would make things more generic and the mapping iterator more
> resemble the page iterator. So we'd have a new sg_miter_start_offset and
> call it here something like:
>
> sg_miter_start_offset(,
On Saturday, June 08, 2013 03:34:29 PM Stratos Karafotis wrote:
> I also did the test with the way you mentioned. But I thought to run
> turbostat for 100 sec as I did with powertop.
Ah, OK.
> Actually benchmark lasts about 96 secs.
>
> I think that we use almost the same energy for 100 sec to
On Saturday, June 08, 2013 12:28:04 PM Catalin Marinas wrote:
> On Fri, Jun 07, 2013 at 07:08:47PM +0100, Preeti U Murthy wrote:
> > On 06/07/2013 08:21 PM, Catalin Marinas wrote:
> > > I think you are missing Ingo's point. It's not about the scheduler
> > > complying with decisions made by
On Thu, Jun 6, 2013 at 10:11 AM, Guenter Roeck wrote:
> On Thu, Jun 06, 2013 at 08:30:01AM +0530, anish singh wrote:
>> Hello Wim Van,
>> Can you look into below?
>>
> Please be patient. Wim tends to be busy.
Sorry, I will wait.
>
> Guenter
>
>> On Wed, Jun 5, 2013 at 8:39 AM, anish singh
>>
The irqdomain core will report a log message for any attempted map call
that fails unless the error code is -EPERM. This patch changes the
Versatile irq controller drivers to use -EPERM because it is normal for
a subset of the IRQ inputs to be marked as reserved on the various
Versatile platforms.
I also did the test with the way you mentioned. But I thought to run turbostat
for 100 sec as I did with powertop.
Actually benchmark lasts about 96 secs.
I think that we use almost the same energy for 100 sec to run the same load a
little bit faster. I think this means also a reduce to power
From: Namjae Jeon
Remove the redundant code from this function and make it aligned with
usages of latest generic vfs layer function e.g using the setattr_copy()
instead of using the f2fs specific function.
Also correct the condition for updating the size of file via
truncate_setsize().
From: Namjae Jeon
The function truncate_data_blocks_range() decrements the valid
block count of inode via dec_valid_block_count(). Since this
function updates the i_blocks field of inode, we can update this
field once we have calculated total the number of blocks
to be freed.
Therefore we can
From: Namjae Jeon
Fix the function get_victim_by_default, where it checks
for the condition that p.min_segno != NULL_SEGNO as
shown:
if (p.min_segno != NULL_SEGNO)
goto got_it;
and if above condition is true then
got_it:
if (p.min_segno != NULL_SEGNO) {
So this condition
From: Namjae Jeon
In f2fs_ioctl() function, it is using generic flags.
Since F2FS specific flags are defined. So lets use
those flags.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
---
fs/f2fs/file.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Thursday 06 of June 2013 16:52:28 Tushar Behera wrote:
> cpufreq driver for EXYNOS4 based SoCs are not platform drivers, hence
> we cannot currently pass the clock names through a device tree node.
> Instead, we need to make them available through a global alias.
>
> 'armclk', 'moutcore',
Hello Tejun Heo,
I've backported the schedule_on_each_cpu() "direct excution" patch on
3.0.30-rt50,
and It fixed my problem.
attachment is the effective patch.
However, I do not understand why machine1 can expose problem, but
machine2 not.
I guess, because it's rt-kernel's preempt
On 06/07/2013 10:13 PM, Joe Perches wrote:
> On Fri, 2013-06-07 at 19:07 +0400, Alexey Brodkin wrote:
>> Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
>> instantiated in some legacy ARC (Synopsys) FPGA Boards such as
>> ARCAngel4/ML50x.
>
> trivial comments only:
>
>>
On Fri, Jun 07, 2013 at 07:08:47PM +0100, Preeti U Murthy wrote:
> On 06/07/2013 08:21 PM, Catalin Marinas wrote:
> > I think you are missing Ingo's point. It's not about the scheduler
> > complying with decisions made by various governors in the kernel
> > (which may or may not have enough
On 06/08/2013 04:49 PM, Alexey Brodkin wrote:
> >> + if (!priv->phy_node) {
> >> + dev_err(>dev, "failed to retrieve phy description "
> >> + "from device tree\n");
> >
> > Coalesce formats please
>
> Could you please clarify how should I format lines in question?
>
On Sat, 2013-06-08 at 14:15 +0300, Artem Bityutskiy wrote:
> On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
> > From: Matt Fleming
> >
> > pcibios_add_device() assumes that the physical addresses stored in
> > setup_data are accessible via the direct kernel mapping, and that
> > calling
On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
> From: Matt Fleming
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the direct kernel mapping, and that
> calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
>
On Saturday, June 08, 2013 12:56:00 PM Stratos Karafotis wrote:
> On 06/07/2013 11:57 PM, Rafael J. Wysocki wrote:
> > On Friday, June 07, 2013 10:14:34 PM Stratos Karafotis wrote:
> >> On 06/05/2013 11:35 PM, Rafael J. Wysocki wrote:
> >>> On Wednesday, June 05, 2013 08:13:26 PM Stratos Karafotis
On Wed, May 22, 2013 at 11:43:55AM -0700, David Daney wrote:
> From: David Daney
>
> Because not all 256 CP0 registers are ever implemented, we need a
> different method of manipulating them. Use the
> KVM_SET_ONE_REG/KVM_GET_ONE_REG mechanism.
>
> Now unused code and definitions are removed.
On Friday 07 of June 2013 16:37:14 Tushar Behera wrote:
> From: Sachin Kamat
>
> Added FIMD and display timing node to Origen4210 board.
>
> Signed-off-by: Sachin Kamat
> Signed-off-by: Tushar Behera
> ---
> arch/arm/boot/dts/exynos4210-origen.dts | 21 +
> 1 file
Hi Tushar, Sachin,
On Friday 07 of June 2013 16:37:13 Tushar Behera wrote:
> From: Sachin Kamat
>
> Adds pinctrl entries required by FIMD.
>
> Signed-off-by: Sachin Kamat
> Signed-off-by: Tushar Behera
> ---
> arch/arm/boot/dts/exynos4210-pinctrl.dtsi | 75
> +
1 - 100 of 280 matches
Mail list logo