Mathieu Desnoyers wrote:
> This leads to very unfortunate consequences for any user relying on
> version.h to expose the kernel version accurately, since the old "stale"
> kernel version will be seen by the build.
>
> Sadly, make clean does not even take care of removing this stale file.
I
Hi Linus,
The following changes since commit 71bd98aff05a644a2cfc3ac6ca848a586fa210b9:
Merge tag 'mvebu_fixes_for_v3.9_round3' of
git://git.infradead.org/users/jcooper/linux into fixes (2013-04-11 16:55:29
+0200)
are available in the git repository at:
Use a more current logging style.
Convert homegrown ERROR/INFO macros to pr_.
Convert homegrown parse_err macros to pr_err and
expand hidden flow control.
Signed-off-by: Joe Perches
---
drivers/mtd/devices/block2mtd.c | 58 ++---
1 file changed, 31
On Thu, Apr 18, 2013 at 09:01:25PM +, Winkler, Tomas wrote:
> >
> > This enum leaks out to userspace via error messages, so fix the spelling.
> >
> > Signed-off-by: Bill Nottingham
> ACK
Why do you ack a patch that doesn't apply? :)
thanks,
greg k-h
--
To unsubscribe from this list:
On Fri, 2013-04-19 at 10:35 -0700, Greg Kroah-Hartman wrote:
> On Wed, Apr 17, 2013 at 08:00:55PM -0700, Joe Perches wrote:
> > Use a more current logging style with dev_printk
> > where possible.
[]
> With your other patch applied, this one seems to not apply to my tree:
I'll respin and
On 19.04.2013 15:28, Michal Bachraty wrote:
> As pointed of by Vaibhav, commit message: "ASoC: davinci-mcasp: Add support
> for multichannel playback"
> number of active serializers can be hidden into fifo_level variable, which is
> set in davimci-mcasp.
You need to reformat the commit log so
On 19 April 2013 18:14, Catalin Marinas wrote:
> On Fri, Apr 19, 2013 at 05:33:18PM +0100, Peter Maydell wrote:
>> The command line lives in the DTB anyway so if you can't look
>> in the DTB you can't get at earlyprintk config either way.
>
> Linux indeed looks in the DT for the command line and
Hi guys,
There's a few bug fixes sitting in the EFI urgent branch. Please
consider pulling.
The following changes since commit ca0ba26fbbd2d81c43085df49ce0abfe34535a90:
efivars: Fix check for CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE (2013-03-22
20:08:01 +)
are available in the git
> I feel we are hitting the same issue than this patch:
> https://lkml.org/lkml/2013/4/5/116
>
> I'm adding Kosaki in Cc, who proposed roughly the same fix.
Thanks to CCing. I'm now sitting LSF and I can't read whole tons emails.
However the fix is definitely same and I definitely agree this
On 19.04.2013 15:28, Michal Bachraty wrote:
> For TDM mode, BCLK-to-LCLK ratio is computed as (tdm_slots) x (word_length).
> I2S mode is only subset of TDM mode with specific tdm_slots = 2 channels.
> Also bclk_lrclk_ratio can be greater than 255, therefore u16 need to be used.
>
> Signed-off-by:
Hi Michal,
On 19.04.2013 15:38, Michal Bachraty wrote:
> Add devicetree support for this dummy audio soc driver.
I think Mark wants to see only "ASoC:" in the patch subjects now.
>
> Signed-off-by: Michal Bachraty
> ---
> sound/soc/codecs/spdif_transciever.c | 10 ++
> 1 file
On Wed, Apr 17, 2013 at 08:00:55PM -0700, Joe Perches wrote:
> Use a more current logging style with dev_printk
> where possible.
>
> o Convert uses of US_DEBUGP to usb_stor_dbg
> o Add "struct us_data *" to usb_stor_dbg uses
> o usb_stor_dbg now uses struct device */dev_vprint_emit
> o Removed
Hi,
With a kernel tree that contains a generated include/linux/version.h, if
someone just does a git pull to update to a newer kernel version that
includes
commit 10b63956fce7f369cc37fd4d994f09bd5203efe4
"UAPI: Plumb the UAPI Kbuilds into the user header installation and
checking"
and
commit
On 04/18/13 18:37, Rob Herring wrote:
> On 04/18/2013 07:00 PM, Stephen Boyd wrote:
>> On 04/18/13 12:30, Rob Herring wrote:
>>> diff --git a/drivers/clocksource/arm_arch_timer.c
>>> b/drivers/clocksource/arm_arch_timer.c
>>> index 122ff05..17ed8e4 100644
>>> ---
Hi,
2013-04-19 17:14 keltezéssel, Aaron Lu írta:
On 04/16/2013 07:58 PM, Boszormenyi Zoltan wrote:
Hi,
The SATA interface can be switched between AHCI and legacy modes as usual:
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA
Controller [AHCI mode] (rev 02)
The device
This patch is relative to next-20130419 of linux-next
This is the ADC component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC
driver. It depends on the DA9058 CORE component driver.
The HWMON component driver depends on this ADC component driver
Architectural MSRs associated with microcode are for P6 or higher.
Add a check to early microcode to detect < P6.
Without a check for < P6 - we end up reading from unimplemented MSRs
on Pentium.
Signed-off-by: Bryan O'Donoghue
---
arch/x86/kernel/microcode_intel_early.c | 21
[+cc Bryan, Zhang]
On Fri, Apr 19, 2013 at 8:51 AM, Scott Simpson wrote:
> Stack trace is here: http://www.flickr.com/photos/94373754@N06/8662259093/
> --
Hi Scott,
This is an openSUSE bug, so you'll probably get more help there. I
added a CC: for that,
This patch is relative to next-20130419 of linux-next
This is the ONKEY component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE component driver of the DA9058 MFD.
Changes relative to V5 of this patch:
- rebased
On Fri, Apr 19, 2013 at 05:33:18PM +0100, Peter Maydell wrote:
> On 19 April 2013 17:22, Catalin Marinas wrote:
> > earlyprintk is used for debugging early problems, like DT parsing. You
> > don't have to use it unless you are debugging something. Without
> > earlyprintk you just get a normal
This patch is relative to next-20130419 of linux-next
This is the HWMON component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE and ADC component drivers of the DA9058 MFD.
Please note that this driver does use regmap
This patch is relative to next-20130419 of linux-next
This is the RTC component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE component driver of the DA9058 MFD.
Changes relative to V5 of this patch:
- rebased to next
This patch is relative to next-20130419 of linux-next
This is the REGULATOR component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE component driver of the DA9058 MFD.
There are 4 CamelCase warnings from scripts
This patch is relative to next-20130419 of linux-next
This is the GPIO component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE component driver of the DA9058 MFD.
The meaning of the PMIC register 21 bits 1 and 5 has
to, but if I have missed
something please let me know.
In a clean check out of next-20130419 in linux-next, each patch has been
applied individually and the final result has been built successfully.
Many thanks,
Anthony Olech, Dialog Semiconductor Ltd.
Tony Olech (at Home) (7):
drivers/mfd
This patch is relative to next-20130419 of linux-next
This is the HWMON component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE and ADC component drivers of the DA9058 MFD.
Please note that this driver does use regmap
This patch is relative to next-20130419 of linux-next
This is the REGULATOR component driver of the Dialog DA9058 PMIC.
This driver is just one component of the whole DA9058 PMIC driver.
It depends on the CORE component driver of the DA9058 MFD.
There are 4 CamelCase warnings from scripts
On Fri, 19 Apr 2013, Nicolas Pitre wrote:
> On Fri, 19 Apr 2013, Ian Campbell wrote:
>
> > On Fri, 2013-04-19 at 16:47 +0100, Nicolas Pitre wrote:
> > > No one should be probing registers without making sure it is safe to do
> > > so. Even on non virtualized hardware this can be a dangerous
to, but if I have missed
something please let me know.
In a clean check out of next-20130419 in linux-next, each patch has been
applied individually and the final result has been built successfully.
Many thanks,
Anthony Olech, Dialog Semiconductor Ltd.
Tony Olech (at Home) (7):
drivers/mfd
On Fri, Apr 19, 2013 at 2:25 PM, Ingo Molnar wrote:
>
> * Paul Gortmaker wrote:
>
>> On 13-04-18 07:14 AM, Peter Zijlstra wrote:
>> > On Mon, 2013-04-15 at 11:33 +0200, Ingo Molnar wrote:
>> >> * Paul Gortmaker wrote:
>> >>
>> >>> Recent activity has had a focus on moving functionally related
On Sat, Apr 06, 2013 at 10:32:12PM +0800, Jiang Liu wrote:
> Prepare for removing num_physpages and simplify mem_init().
>
> Signed-off-by: Jiang Liu
> Cc: Russell King
> Cc: Catalin Marinas
> Cc: Will Deacon
> Cc: linux-arm-ker...@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> ---
On Sat, Apr 06, 2013 at 09:54:55PM +0800, Jiang Liu wrote:
> Fix following build warnings cuased by free_reserved_area():
>
> arch/arm/mm/init.c: In function 'mem_init':
> arch/arm/mm/init.c:603:2: warning: passing argument 1 of 'free_reserved_area'
> makes integer from pointer without a cast
[Do not drop people from the CC please]
On Fri 19-04-13 10:33:45, Han Pingtian wrote:
> On Thu, Apr 18, 2013 at 10:55:14AM -0700, Michal Hocko wrote:
[...]
> > What is the kernel that you are using and what config?
> >
> We are testing a alpha version of a enterprise linux which using a 3.7
>
parallel-make-jobs).
>>>>>
>>>>> Any hints welcome!
>>>>
>>>> The panic handlers in our modeset code are pretty decent fubar - they
>>>> take mutexes all over the place. So I think the backtrace you see
>>>> there is actual
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
Hi Mike,
On 03/04/13 22:34, Mike Turquette wrote:
> diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
> index 9fdfae7..1a19186 100644
> --- a/include/linux/clk-provider.h
> +++ b/include/linux/clk-provider.h
> @@ -126,6 +126,9 @@ struct clk_ops {
>
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged,
From: Namjae Jeon
https://lkml.org/lkml/2013/4/1/292
As per above discussion, there is possibility that request's __data_len
field may overflow when max_discard_sectors greater than UINT_MAX >> 9
If multiple discard requests get merged, merged discard request's
size exceeds 4GB, there is
From: Namjae Jeon
https://lkml.org/lkml/2013/4/1/292
As per above discussion, it has been oberved that few drivers are
setting q->limits.max_discard_sectors to more than (UINT_MAX >> 9)
If multiple discard requests get merged, merged discard request's
size exceeds 4GB, there is possibility
From: Namjae Jeon
linux-v3.8-rc1 and later support for plug for blkdev_issue_discard with
commit 0cfbcafcae8b7364b5fa96c2b26ccde7a3a296a9
(block: add plug for blkdev_issue_discard )
For example,
1) DISCARD rq-1 with size size 4GB
2) DISCARD rq-2 with size size 1GB
If these 2 discard requests
Hi Kent,
> + /* u8 LOC+DIR u8 ADD u16 LENGHT u8* data */
> + /* u8 LATENCY u8 LATENCY */
Kent: What do these comments mean?
Mathias: These comments describe the I2C command protocol.
Regarding the return value of these W/R functions, it's an error of comment,
these functions return 0
Any comments? it's been 2 weeks now.
Thanks,
-George
On 03/04/13 15:46, George Dunlap wrote:
check_hw_exists has a number of checks which go to two exit paths:
msr_fail and bios_fail. Checks classified as msr_fail will cause
check_hw_exists() to return false, causing the PMU not to be used;
On 19 April 2013 17:22, Catalin Marinas wrote:
> earlyprintk is used for debugging early problems, like DT parsing. You
> don't have to use it unless you are debugging something. Without
> earlyprintk you just get a normal console during boot, based on the DT
> description.
The command line
On Fri, 19 Apr 2013, Ian Campbell wrote:
> On Fri, 2013-04-19 at 16:47 +0100, Nicolas Pitre wrote:
> > No one should be probing registers without making sure it is safe to do
> > so. Even on non virtualized hardware this can be a dangerous thing to
> > do.
>
> Won't people writing per machine
From: Namjae Jeon
Add tracepoints to debug the various page write operation
like data pages, meta pages.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
Acked-by: Steven Rostedt
---
fs/f2fs/checkpoint.c|2 +
fs/f2fs/data.c |2 +
fs/f2fs/segment.c
Hi Wei,
On Fri, Apr 19, 2013 at 09:50:33AM +0800, wwang wrote:
> 于 2013年04月19日 06:50, Samuel Ortiz 写道:
> >Hi Wei,
> >
> >On Thu, Apr 11, 2013 at 10:43:40AM +0800, wei_w...@realsil.com.cn wrote:
> >>From: Wei WANG
> >>
> >>Support new model: RTS5249
> >Could you please provide me with a more
Add core support to allow clock implementations to select the best
parent clock when rounding a rate, e.g. the one which can provide the
closest clock rate to that requested. This is by way of adding a new
clock op, determine_rate(), which is like round_rate() but has an extra
parameter to allow
Add a new clock flag called CLK_SET_RATE_REMUX to indicate that the
clock can have it's parent changed automatically in response to a
set_rate.
Implement clk-mux remuxing if the CLK_SET_RATE_REMUX flag is set. This
implements determine_rate for clk-mux to propagate to each parent and to
choose
Abstract access to the clock parent cache by defining
__clk_get_parent_by_index(clk, index). This allows access to parent
clocks from clock drivers.
Signed-off-by: James Hogan
---
drivers/clk/clk.c| 21 ++---
include/linux/clk-provider.h | 1 +
2 files changed, 15
From: Namjae Jeon
Add tracepoints to debug checkpoint request.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
Acked-by: Steven Rostedt
---
fs/f2fs/checkpoint.c|4
include/trace/events/f2fs.h | 22 ++
2 files changed, 26 insertions(+)
diff
This patchset adds support for automatic selection of the best parent
for a clock mux, i.e. the one which can provide the closest clock rate
to that requested. It can be controlled by a new CLK_SET_RATE_REMUX flag
so that it doesn't happen unless explicitly allowed.
This works by way of adding a
From: Namjae Jeon
Add tracepoints for tracing the garbage collector
threads in f2fs with status of collection & type.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
Acked-by: Steven Rostedt
---
fs/f2fs/gc.c|2 ++
include/trace/events/f2fs.h | 38
From: Namjae Jeon
Add tracepoints to debug the block allocation & fallocate.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
Acked-by: Steven Rostedt
---
fs/f2fs/data.c |1 +
fs/f2fs/file.c |6 -
include/trace/events/f2fs.h | 59
From: Namjae Jeon
add tracepoints for tracing the truncate operations
like truncate node/data blocks, f2fs_truncate etc.
Tracepoints are added at entry and exit of operation
to trace the success & failure of operation.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
Acked-by: Steven
From: Namjae Jeon
Add tracepoints for page i/o operations and block allocation
tracing during page read operation.
Signed-off-by: Namjae Jeon
Signed-off-by: Pankaj Kumar
Acked-by: Steven Rostedt
---
fs/f2fs/data.c | 16 +--
include/trace/events/f2fs.h | 63
From: Namjae Jeon
Add tracepoints in f2fs for tracing the syncing
operations like filesystem sync, file sync enter/exit.
It will helf to trace the code under debugging scenarios.
Also add tracepoints for tracing the various inode operations
like building inode, eviction of inode, link/unlike of
From: Namjae Jeon
Add tracepoints in f2fs filesystem for tracing the filesystem
operations for information/debugging purpose if needed. All the
tracepoints are clubbed with respect to functionalities.
Change Log:
v4: Modified the tracepoints as per the review comments of
Jaegeuk Kim. Following
From: Namjae Jeon
Adding REQ_META for all the metadata requests can help in improving the
FS performance, if the underlying device supports TAGGING.
So, when considering the submit_bio path for all the f2fs requests. We can
add REQ_META for all the META requests.
As a precursor to this change we
From: Namjae Jeon
The code conditions put inside the function is_multimedia_file are
reverse to the name i.e, we need to negate the return to actually
check if the file is a multimedia file. So, change the code and usage
path to align both the name and comparision conditions.
Signed-off-by:
On an SMP system with only one global clockevent and a dummy
clockevent per CPU we run into problems. We want the dummy
clockevents to be registered as the per CPU tick devices, but
we can only achieve that if we register the dummy clockevents
before the global clockevent or if we artificially
On Fri, Apr 19, 2013 at 05:14:36PM +0100, Peter Maydell wrote:
> On 19 April 2013 17:12, Catalin Marinas wrote:
> > On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
> >> Please make the kernel pick the device out of the device tree
> >> blob. The whole point of device tree is that
Drop ARM's version of the dummy timer now that we have a generic
implementation in drivers/clocksource.
Cc: Russell King
Signed-off-by: Stephen Boyd
---
arch/arm/kernel/smp.c | 22 ++
1 file changed, 2 insertions(+), 20 deletions(-)
diff --git a/arch/arm/kernel/smp.c
On 14:55-20130419, Taras Kondratiuk wrote:
> Using a "voltage tolerance" for doing DVFS is not a proper way.
> It leads to a few issues:
> - voltage is limited to a narrow range near OPP voltage,
> so other consumers of the same regulator can't set their own constraints
>
Now that the TWD doesn't rely on the local timer API, OMAP can
stop selecting it in Kconfig and relying on the config option to
decide if it should call smp_twd functions.
Acked-by: Santosh Shilimkar
Acked-by: Tony Lindgren
Signed-off-by: Stephen Boyd
---
arch/arm/mach-omap2/Kconfig | 1 -
Separate the smp_twd timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Russell King
Cc: Tony Lindgren
Tested-by: Mark Rutland
Signed-off-by: Stephen Boyd
---
Separate the marco local timers from the local timer API. This
will allow us to remove ARM local timer support in the near future
and gets us closer to moving this driver to drivers/clocksource.
Cc: Barry Song
Signed-off-by: Stephen Boyd
---
drivers/clocksource/timer-marco.c | 100
Separate the mct local timers from the local timer API. This will
allow us to remove ARM local timer support in the near future and
gets us closer to moving this driver to drivers/clocksource.
Cc: Kukjin Kim
Cc: Thomas Abraham
Signed-off-by: Stephen Boyd
---
drivers/clocksource/exynos_mct.c |
Separate the armada 370xp local timers from the local timer API.
This will allow us to remove ARM local timer support in the near
future and makes this driver multi-architecture friendly.
Acked-by: Gregory CLEMENT
Tested-by: Gregory CLEMENT
Signed-off-by: Stephen Boyd
---
In light of Mark Rutland's recent work on divorcing the ARM architected
timers from the ARM local timer API and introducing a generic arch hook for
broadcast it seems that we should remove the local timer API entirely.
Doing so will reduce the architecture dependencies of our timer drivers,
reduce
Separate the msm_timer from the local timer API. This will allow
us to remove ARM local timer support in the near future and gets
us closer to moving this driver to drivers/clocksource.
Acked-by: David Brown
Cc: Daniel Walker
Cc: Bryan Huntsman
Signed-off-by: Stephen Boyd
---
drivers/clocksource/time-armada-370-xp.c:217:13: warning: symbol
'armada_370_xp_timer_init' was not declared. Should it be static?
Also remove the __init marking in the prototype as it's
unnecessary and drop the init.h file.
Acked-by: Gregory CLEMENT
Signed-off-by: Stephen Boyd
---
There are no more users of this API, remove it.
Cc: Russell King
Acked-by: Tony Lindgren
Signed-off-by: Stephen Boyd
---
arch/arm/Kconfig | 10 --
arch/arm/include/asm/localtimer.h | 34 ---
arch/arm/kernel/smp.c | 69
From: Mark Rutland
Several architectures have a dummy timer driver tightly coupled with
their broadcast code to support machines without cpu-local timers (or
where there is a lack of driver support).
Since 12ad100046: "clockevents: Add generic timer broadcast function"
it's been possible to
On Fri, 2013-04-19 at 16:47 +0100, Nicolas Pitre wrote:
> No one should be probing registers without making sure it is safe to do
> so. Even on non virtualized hardware this can be a dangerous thing to
> do.
Won't people writing per machine code consider, not unreasonably, that
having been
On 19 April 2013 17:12, Catalin Marinas wrote:
> On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
>> Please make the kernel pick the device out of the device tree
>> blob. The whole point of device tree is that it's how to tell
>> the kernel where things live -- making kvmtool/QEMU
On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
> On 19 April 2013 10:39, Will Deacon wrote:
> > The point of mach-virt is that it is completely parameterised. So, if you're
> > not emulating an 8250, then don't tell the kernel that you have one!
> > Similarly, if you *do* emulate
Hi Fabio,
Le Fri, 19 Apr 2013 12:26:33 -0300,
Fabio Estevam a écrit :
> On Fri, Apr 19, 2013 at 12:05 PM, Eric Bénard wrote:
> > Only auart0 was filled.
> > Tested on a custom i.MX283 board for ttyAPP1/2/3/4.
> >
> > Signed-off-by: Eric Bénard
> > ---
> > arch/arm/boot/dts/imx28.dtsi | 4
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive 2 more small fixups to the wacom driver.
Changelog:
-
Ping Cheng (2):
Input:
From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
There are more and more applications coming to WinRT, Wine could support them,
but mostly they expect to have the thread environment block (TEB) in TPIDRURW.
This register must be preserved per thread instead of being cleared.
Signed-off-by: André
On Fri, 19 Apr 2013, Stefano Stabellini wrote:
> On Thu, 18 Apr 2013, Nicolas Pitre wrote:
> > On Thu, 18 Apr 2013, Stefano Stabellini wrote:
> >
> > > On Thu, 18 Apr 2013, Nicolas Pitre wrote:
> > > > On Thu, 18 Apr 2013, Stefano Stabellini wrote:
> > > >
> > > > > On Thu, 18 Apr 2013, Russell
On Tue, Apr 16, 2013 at 8:12 PM, Linus Torvalds
wrote:
> Guys, I just pushed out a new helper function intended for cleaning up
> various device driver mmap functions, because they are rather messy,
> and at least part of the problem was the bad impedance between what a
> driver author would want
* Roger Quadros [130419 03:02]:
> Hi Benoit/Tony
>
> I've consolidated all the USB host device tree patches for Panda and Beagles
> to one place and addressed Tony's comments.
>
> NOTE: patch 1 depends on OMAP clock binding introduced in
> https://lkml.org/lkml/2013/4/12/407
>
> v3:
> -
On Fri, Apr 19, 2013 at 10:09 PM, Russell King - ARM Linux
wrote:
> On Sat, Apr 13, 2013 at 09:08:12PM +0800, Haojian Zhuang wrote:
>> On Thu, Apr 11, 2013 at 11:39 AM, Neil Zhang wrote:
>> > + /*
>> > +* Synchronise with the boot thread.
>> > +*/
>> > +
On Mon 15-04-13 11:59:59, l...@tigusoft.pl wrote:
> There are 2 hard drives (normal, magnetic) in software raid 1
> on 3.2.41 kernel.
Any possibility in trying a newer kernel? Like 3.8 / 3.9?
> When I write into them e.g. using dd from /dev/zero to a local file
> (ext4 on default settings),
Hey Linus,
I am heading out for a week of vacation but would hate to have missed
the merge window. Hence sending it out early in anticipation that you
will release v3.9 on Sunday.
With that said, please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
Hi Eric,
On Fri, Apr 19, 2013 at 12:05 PM, Eric Bénard wrote:
> Only auart0 was filled.
> Tested on a custom i.MX283 board for ttyAPP1/2/3/4.
>
> Signed-off-by: Eric Bénard
> ---
> arch/arm/boot/dts/imx28.dtsi | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
On 04/19/2013 12:12 AM, Srivatsa S. Bhat wrote:
On 04/19/2013 11:04 AM, Simon Jeons wrote:
Hi Srivatsa,
On 04/10/2013 05:45 AM, Srivatsa S. Bhat wrote:
[I know, this cover letter is a little too long, but I wanted to clearly
explain the overall goals and the high-level design of this patchset
* Roger Quadros [130419 01:23]:
> On 04/18/2013 11:09 PM, Tony Lindgren wrote:
>
> > the naming should be mode0name.modename to be consistent. Here's
> > what I dumped out, please check and replace spaces with tabs:
> >
> > 0x82 0x10c /*
> >
drivers/rtc/hctosys (CONFIG_RTC_HCTOSYS) doesn't work for
rtc-hid-sensor-time because it will be called in late_init, and thus before
rtc-hid-sensor-time gets loaded. To set the time through rtc-hid-sensor-time
at startup, the module now checks by default if the system time is before
1970-01-02
There is no real reason to not support 16 or 32 bit values too.
Signed-off-by: Alexander Holler
---
drivers/rtc/rtc-hid-sensor-time.c | 59 +--
1 file changed, 32 insertions(+), 27 deletions(-)
diff --git a/drivers/rtc/rtc-hid-sensor-time.c
Linus,
Could you please pull this single fix from
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This fixes android builds. The patch appears large, but is just
search & replace.
Thanks,
Miklos
Miklos Szeredi (1):
fuse: fix type definitions in uapi
The draft for HID-sensors (HUTRR39) currently doesn't define the range
for the attribute year. Asking one of the authors revealed that full years
(e.g. 2013 instead of just 13) were meant.
So we now allow both, 8 bit and 16 bit values for the attribute year and
assuming full years when the value
Hello,
as I'm not sure if the maintainer of the RTC subsystem is active again,
I've added the people which where involved with rtc-hid-sensor-time
before to cc too. That might be a good idea even he is active again,
as the driver depends on hid-sensor-hub and as such works a bit
outside the
On 04/16/2013 07:58 PM, Boszormenyi Zoltan wrote:
Hi,
The SATA interface can be switched between AHCI and legacy modes as usual:
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA
Controller [AHCI mode] (rev 02)
The device attached to the SATA controller is always a CF card via
On Thu, Apr 18, 2013 at 11:35:22AM +0200, Thomas Gleixner wrote:
> On Wed, 17 Apr 2013, Uwe Kleine-König wrote:
> > +struct nvic_bank_data {
> > + /*
> > +* For irq i base holds nvic_base + 4 * i / 32. So you can access the
> > +* right ISER register (i.e ISER[i / 32]) by just taking
101 - 200 of 904 matches
Mail list logo
