On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote:
> Hi all:
>
> This series try to share MSIX irq for each tx/rx queue pair. This is
> done through:
>
> - introducing virtio pci channel which are group of virtqueues that
> sharing a single MSIX irq (Patch 1)
> - expose channel
> -Original Message-
> From: Пламен Петров [mailto:pla...@petrovi.no-ip.info]
> Sent: Sunday, December 28, 2014 9:20 AM
> To: 'Juergen Gross'; 'linux-kernel@vger.kernel.org'
> Cc: 'Thomas Gleixner'
> Subject: RE: [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB
> 0.97 (GRUB
> -Original Message-
> From: Juergen Gross [mailto:jgr...@suse.com]
> Sent: Saturday, December 27, 2014 3:48 PM
> To: Пламен Петров; linux-kernel@vger.kernel.org
> Cc: 'Thomas Gleixner'
> Subject: Re: [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB
> 0.97 (GRUB Legacy)
>
>
Signed-off-by: Alexander Kuleshov
---
drivers/edac/mpc85xx_edac.c | 2 +-
drivers/edac/mpc85xx_edac.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
index ffb1a9a..1fa76a5 100644
--- a/drivers/edac/mpc85xx_edac.c
Signed-off-by: Alexander Kuleshov
---
block/blk-merge.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/blk-merge.c b/block/blk-merge.c
index 89b97b5..5d6a2bc 100644
--- a/block/blk-merge.c
+++ b/block/blk-merge.c
@@ -446,7 +446,7 @@ void blk_rq_set_mixed_merge(struct
Signed-off-by: Alexander Kuleshov
---
fs/overlayfs/copy_up.c | 1 +
fs/overlayfs/overlayfs.h | 10 ++
fs/overlayfs/super.c | 5 +
3 files changed, 16 insertions(+)
diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
index ea10a87..593b00d 100644
---
On Sun, Dec 28, 2014 at 12:44 AM, Rafał Miłecki wrote:
> On 27 December 2014 at 20:24, Oscar Forner Martinez
> wrote:
>> Three lines with more than 80 characters per line have been split in several
>> lines.
>>
>> Signed-off-by: Oscar Forner Martinez
>
> Acked-by: Rafał Miłecki
>
As for the
On Sat, Dec 27, 2014 at 3:08 PM, Stefan Agner wrote:
Thanks for picking this up.
> Add early fixmap support, initially to support permanent, fixed
> mapping support for early console. A temporary, early pte is
> created which is migrated to a permanent mapping in paging_init.
> This is also
ddpt is yet another variant of the venerable Unix dd command
line utility. It offers more precise control over a storage
copy and can bypass upper layers to use SCSI commands like READ,
WRITE, WRITE AND VERIFY, WRITE ATOMIC or offloaded copy
mechanisms to move the data. ddpt supports both the
sdparm is a command line utility designed to get and set
SCSI device parameters (cf hdparm for ATA disks). The
parameters are held in mode pages. Apart from SCSI devices
(e.g. disks, tapes and enclosures) sdparm can be used on
any device that uses a SCSI command set. sdparm also can
decode VPD
Hi Masami,
0day kernel testing robot got the below dmesg and the first bad commit is
commit 003002e04ed38618fc37b92ba128f5ca79d39f4f
Author: Masami Hiramatsu
AuthorDate: Wed Jun 5 12:12:16 2013 +0900
Commit: Ingo Molnar
CommitDate: Thu Jun 20 14:25:48 2013 +0200
kprobes: Fix
On 12/24/14 12:15 AM, Namhyung Kim wrote:
Otherwise it'll break the machine->threads tree.
Signed-off-by: Namhyung Kim
---
tools/perf/util/machine.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
index 031bace39fdc..beae6e8fe789
On 27 December 2014 at 20:24, Oscar Forner Martinez
wrote:
> Three lines with more than 80 characters per line have been split in several
> lines.
>
> Signed-off-by: Oscar Forner Martinez
Acked-by: Rafał Miłecki
Kalle: will you pick this patch?
--
To unsubscribe from this list: send the line
On 27 December 2014 at 23:04, Oscar Forner Martinez
wrote:
> 2014-12-27 21:14 GMT+00:00 Oscar Forner Martinez
> :
>>
>> 2014-12-27 20:19 GMT+00:00 Rafał Miłecki :
>>>
>>> On 27 December 2014 at 20:24, Oscar Forner Martinez
>>> wrote:
>>> > Three lines with more than 80 characters per line have
On Sat, Dec 27, 2014 at 4:37 PM, Fabian Frederick wrote:
> Fix sparse warning:
> drivers/gpu/drm/gma500/psb_drv.c:
> 328:56: warning: Using plain integer as NULL pointer
>
> Signed-off-by: Fabian Frederick
Reviewed-by: Patrik Jakobsson
> ---
> drivers/gpu/drm/gma500/psb_drv.c | 2 +-
> 1
On Fri 2014-12-26 13:34:53, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This patch provides
> a DT based driver for the temperature sensor based on an older driver
> written by Peter De
On Sat 2014-12-27 20:58:25, Pavel Machek wrote:
> On Fri 2014-12-26 13:34:53, Sebastian Reichel wrote:
> > OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> > which can be used to determine the SoCs temperature. This patch provides
> > a DT based driver for the temperature
A missing va_end in connection with vsnprintf
Was found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/staging/unisys/uislib/uisutils.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/unisys/uislib/uisutils.c
-Move operation structures to avoid forward declarations.
-Fix some checkpatch warnings:
WARNING: Missing a blank line after declarations
+ struct inode *host_inode = file_inode(host_file);
+ mutex_lock(_inode->i_mutex);
ERROR: that open brace { should be on the
Add early fixmap support, initially to support permanent, fixed
mapping support for early console. A temporary, early pte is
created which is migrated to a permanent mapping in paging_init.
This is also needed since the attributs may change as the memory
types are initialized. The 3MiB range of
Fix the sparse warning about a context imbalance in the
sfw_deactivate_session function by telling sparse that it
should expect the lock to be held on entry and held on exit.
drivers/staging/lustre/lnet/selftest/framework.c:210:9: warning: context
imbalance in 'sfw_deactivate_session' -
Fix the sparse warning about a context imbalance in the
srpc_service_recycle_buffer function by telling sparse that it
should expect the lock to be held on entry and held on exit.
drivers/staging/lustre/lnet/selftest/rpc.c:725:20: warning: context imbalance
in 'srpc_service_recycle_buffer' -
Fix several "symbol '...' was not declared" sparse warnings which
are caused by global variables by declaring them in the header file.
Signed-off-by: Jeremiah Mahler
---
drivers/staging/lustre/lnet/selftest/selftest.h | 12
1 file changed, 12 insertions(+)
diff --git
Fix several "symbol '...' was not declared" sparse warnings
for variables which are only used locally by declaring them static.
Signed-off-by: Jeremiah Mahler
---
drivers/staging/lustre/lnet/selftest/framework.c | 2 +-
drivers/staging/lustre/lnet/selftest/rpc.c | 2 +-
Fix the sparse warning about a context imbalance in the
srpc_service_post_buffer function by telling sparse that it
should expect the lock to be held on entry and held on exit.
drivers/staging/lustre/lnet/selftest/rpc.c:508:17: warning: context imbalance
in 'srpc_service_post_buffer' -
These patches fix most of the "undeclared" and "context imbalance"
sparse warnings for the lustre code in the selftest/ directory.
Jeremiah Mahler (5):
staging: lustre: selftest: fix "not declared" by declaring in header
staging: lustre: selftest: fix "not declared" by declaring static
On 27 December 2014 at 20:24, Oscar Forner Martinez
wrote:
> Three lines with more than 80 characters per line have been split in several
> lines.
Thanks for the next version :)
1) You missed version number. Something like
git format-patch --subject-prefix="PATCH V3"
(you saying for the
logfs_segment_read() receives a page not a buffer.
Signed-off-by: Fabian Frederick
---
fs/logfs/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/logfs/segment.c b/fs/logfs/segment.c
index 7f9b096..b2dddce 100644
--- a/fs/logfs/segment.c
+++ b/fs/logfs/segment.c
On Sat, 2014-12-27 at 21:22 +0100, Rafael J. Wysocki wrote:
[]
> +++ linux-pm/include/acpi/acpi_bus.h
> @@ -589,7 +589,8 @@ static inline u32 acpi_target_system_sta
>
> static inline bool acpi_device_power_manageable(struct acpi_device *adev)
> {
> - return adev->flags.power_manageable;
>
On Wednesday, December 24, 2014 09:06:05 AM Nishanth Menon wrote:
> On 12/18/2014 08:08 PM, Rafael J. Wysocki wrote:
> > On Friday, December 19, 2014 07:11:19 AM Viresh Kumar wrote:
> >> On 18 December 2014 at 20:19, Nishanth Menon wrote:
> >>> I can add "could be unstable" -> the point being
On Wednesday, December 24, 2014 02:37:14 PM Nishanth Menon wrote:
> On 12/24/2014 11:44 AM, Dmitry Torokhov wrote:
> > On Wed, Dec 24, 2014 at 9:37 AM, Nishanth Menon wrote:
> >> On 12/24/2014 11:31 AM, Dmitry Torokhov wrote:
> >>> On Wed, Dec 24, 2014 at 9:16 AM, Nishanth Menon wrote:
> On
On Saturday, December 27, 2014 09:19:49 AM Pali Rohár wrote:
> Hello,
>
> in attachment is output of ls -l /sys/bus/acpi/devices from both
> 3.13 and 3.19 kernels.
>
> Anyway Gabriele Mazzotta wrote me that new acpi devices could be
> created after commit faae404ebdc6bba (ACPICA: Add "Windows
On Fri 2014-12-26 13:34:53, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This patch provides
> a DT based driver for the temperature sensor based on an older driver
> written by Peter De
On Fri, 2014-12-26 at 15:35 +0100, Julia Lawall wrote:
> Convert a call to init_timer and accompanying intializations of
> the timer's data and function fields to a call to setup_timer.
>
> A simplified version of the semantic match that fixes this problem is as
> follows:
On Fri 2014-12-26 13:34:53, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This patch provides
> a DT based driver for the temperature sensor based on an older driver
> written by Peter De
On Fri 2014-12-26 13:34:53, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This patch provides
> a DT based driver for the temperature sensor based on an older driver
> written by Peter De
On 25/12/2014 08:46, Chen, Tiejun wrote:
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index f528343..910bc48 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -672,6 +672,7 @@ static void update_memslots(struct kvm_memslots *slots,
>
Three lines with more than 80 characters per line have been split in several
lines.
Signed-off-by: Oscar Forner Martinez
---
drivers/bcma/driver_chipcommon.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/bcma/driver_chipcommon.c
Hi!
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This patch provides
> a DT based driver for the temperature sensor based on an older driver
> written by Peter De Schrijver for the Nokia N900 and N9.
>
>
On Fri 2014-12-26 13:34:52, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This provides a
> DT binding specification for the temperature monitor.
>
> Signed-off-by: Sebastian Reichel
On Fri 2014-12-26 13:34:54, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the
> syscon area, which can be used to determine the SoCs temperature.
>
> Signed-off-by: Sebastian Reichel
Acked-by: Pavel Machek
Tested-by: Pavel Machek
Driver binds and does
On Fri, 2014-12-26 at 13:43 +0100, Sedat Dilek wrote:
> On Fri, Dec 26, 2014 at 1:02 PM, Sedat Dilek wrote:
> [...]
> >
> > Any other make (PHONY) target I don't know?
> >
>
> I fell over "clean-dirs"...
>
> scripts/package/Makefile:93:clean-dirs += $(objtree)/debian/
>
> ...but did not really
Avoid allocate memory if we will exit the function.
Was found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/staging/ft1000/ft1000-usb/ft1000_hw.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On Sat, Dec 27, 2014 at 6:30 AM, Koshy George wrote:
> This patch fix checkpatch warning for nfs4_fs.h
>
> fs/nfs/nfs4_fs.h:134: ERROR: "foo * bar" should be "foo *bar"
> fs/nfs/nfs4_fs.h:416: ERROR: "foo * bar" should be "foo *bar"
>
> Signed-off-by: Koshy George
> [Being first patch, need
Am Montag, 22. Dezember 2014, 10:47:29 schrieb Doug Anderson:
> I was seeing cases where I was losing interrupts when inserting and
> removing SD cards. Sometimes the card would get "stuck" in the
> inserted state.
>
> I believe that the problem was related to the code to handle the case
> where
On Sat, Dec 27, 2014 at 06:39:54PM +0100, Piotr Karbowski wrote:
> Hi,
>
> There's something wrong about exe symlink that can be found insde
> /proc// directories. When the running binary is replaced with
> another, using rename() call, the symlink may point to wrong path.
>
> As example let me
Hi,
There's something wrong about exe symlink that can be found insde
/proc// directories. When the running binary is replaced with
another, using rename() call, the symlink may point to wrong path.
As example let me use sshd. I have running sshd from /usr/sbin. If I
replace /usr/sbin/sshd
On Sat, 2014-12-27 at 03:42 -0500, Matthew Emerson wrote:
> Fixed multiple space issues found by checkpatch.pl in
> drivers/staging/rtl8723au/core/rtw_ap.c
Hello.
Please strive for more than simple robotic like
adherence to checkpatch messages.
A lot of the time, there is a better way.
> diff
On Sat, Dec 27, 2014 at 11:24 AM, Pranith Kumar wrote:
> On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote:
>> Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the
>> "select SRCU" to "config PPC" in arch/powerpc/Kconfig. Are you able
>> to cross-build powerpc?
>>
>
> ppc 32
Isolate the SRCU functions and data structures within CONFIG_SRCU so that there
is a compile time failure if srcu is used when not enabled. This was decided to
be better than waiting until link time for a failure to occur.
There are places which include kvm headers and utilize kvm data structures
In an allnoconfig we get the following build failure:
arch/powerpc/platforms/built-in.o: In function
`.__machine_initcall_powernv_opal_init':
opal.c:(.init.text+0x468): undefined reference to `.log_buf_addr_get'
opal.c:(.init.text+0x474): undefined reference to `.log_buf_len_get'
make: ***
On Fri, Dec 26, 2014 at 07:14:55PM -0800, Linus Torvalds wrote:
> On Fri, Dec 26, 2014 at 4:36 PM, Dave Jones wrote:
> > >
> > > Oh - and have you actually seen the "TSC unstable (delta = xyz)" +
> > > "switched to hpet" messages there yet?
> >
> > not yet. 3 hrs in.
>
> Ok, so then
On 12/24/14 12:15 AM, Namhyung Kim wrote:
@@ -61,12 +61,12 @@ static int unwind_entry(struct unwind_entry *entry, void
*arg)
__attribute__ ((noinline))
static int unwind_thread(struct thread *thread)
{
- struct perf_sample sample;
+ struct perf_sample sample = {
+
On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote:
> Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the
> "select SRCU" to "config PPC" in arch/powerpc/Kconfig. Are you able
> to cross-build powerpc?
>
ppc 32 seems fine without selecting srcu unconditionally. So I added
On Sat, Dec 27, 2014 at 04:30:57AM -0700, Koshy George wrote:
> This patch fix checkpatch warning for nfs4_fs.h
>
> fs/nfs/nfs4_fs.h:134: ERROR: "foo * bar" should be "foo *bar"
> fs/nfs/nfs4_fs.h:416: ERROR: "foo * bar" should be "foo *bar"
>
> Signed-off-by: Koshy George
> [Being first
On Thu, Dec 25, 2014 at 11:37:45PM +0100, Helge Deller wrote:
> Hi Michael,
>
> On 12/25/2014 10:29 AM, Michael S. Tsirkin wrote:
> >virtio wants to read bitwise types from userspace using get_user. At the
>
> I don't know the virtio code much yet, but does it makes sense to read
> bitwise
On Sat, Dec 27, 2014 at 03:31:26PM +0200, Leon Pollak wrote:
> Hi, all.
> There was a discussion here:
> https://lkml.org/lkml/2007/1/10/231
>
> Linus wrote in this discussion:
> "So don't use O_DIRECT. Use things like madvise() and posix_fadvise()
> instead"
>
> After the full week of tests,
On Fri, Dec 26, 2014 at 12:33:36PM +1100, Stephen Rothwell wrote:
> Hi Andy,
>
> On Mon, 22 Dec 2014 11:16:56 -0800 Andy Lutomirski
> wrote:
> >
> > I'm re-adding the branch, since 3.19-rc1 is out, the change appears to
> > still exist as-is in your tree, and it merges cleanly and builds in
> >
On Fri, Dec 26, 2014 at 06:51:20PM +1100, Stephen Rothwell wrote:
> Hi Paul,
>
> After merging the rcu tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0,
> from
On 12/27/2014 04:52 AM, Davidlohr Bueso wrote:
>> Hello，
>> > Does ACCESS_ONCE() can help this issue? I have no evidence that its lack is
>> > responsible for the issue, but I think here need it indeed. Is that right?
>> >
>> > SPIN_BUG_ON(ACCESS_ONCE(lock->owner) == current, "recursion");
> Hmm
Fix sparse warning:
drivers/gpu/drm/gma500/psb_drv.c:
328:56: warning: Using plain integer as NULL pointer
Signed-off-by: Fabian Frederick
---
drivers/gpu/drm/gma500/psb_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/psb_drv.c
On 12/24/14 12:15 AM, Namhyung Kim wrote:
@@ -106,8 +117,8 @@ void machine__delete_threads(struct machine *machine)
while (nd) {
struct thread *t = rb_entry(nd, struct thread, rb_node);
- rb_erase(>rb_node, >threads);
nd = rb_next(nd);
+
Transition the PXA25x and PXA27x CPUs to the clock framework.
This transition still enables legacy platforms to run without device
tree as before, ie relying on platform data encoded in board specific
files.
The transition breaks the previous clocks activation of pin
control (gpio11 and gpio12).
This series makes the transition from old clock code to the clock framework for
the pxa25x and pxa27x. That will only leave pxa3xx to be converted. As there is
no defconfig using both pxa3xx and any other pxa2xx variant, the previous mess
should be avoided.
This change can be very disruptive for
The pxa25x gpio11 clock output was previously selected on its pin by the
clock enabling, toggling the pin function.
As we transition to common clock framework, the pin function is moved to
board file for the 2 users, ie. lubbock and eseries.
Signed-off-by: Robert Jarzmik
---
Add 2 clocks which were erronously forgotten by the clock framework
port, namely :
- sa1100-rtc
- irda for pxa2xx-ir:UARTCLK
Signed-off-by: Robert Jarzmik
---
drivers/clk/pxa/clk-pxa27x.c | 29 +
1 file changed, 29 insertions(+)
diff --git
Since pxa clocks were ported to the clock framework, an ordering issue
appears between clocks and clocksource initialization. As a consequence,
the pxa timer clock cannot be acquired in pxa_timer, and is disabled by
clock framework because it is "unused".
The ordering issue is that in the kernel
Fix sparse warning:
drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c:
815:32: warning: Using plain integer as NULL pointer
Signed-off-by: Fabian Frederick
---
drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Linus,
please pull sound fixes for v3.19-rc2 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-3.19-rc2
The topmost commit is d6795827bd79b28fef1abdaf7e525fcca506b831
sound fixes for 3.19-rc2
On Tue, Dec 23, 2014 at 01:18:15PM +0100, Dongsu Park wrote:
> I think so too. Patches #07-10 can be split into a separate patchset.
> I guess they are included just because Kent tried to follow up
> suggestions in the previous discussion.
> I don't care about either way. So I'll split them up.
Signed-off-by: Fabian Frederick
---
This is untested.
fs/ext3/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/ext3/super.c b/fs/ext3/super.c
index 9b4e7d7..d4dbf3c 100644
--- a/fs/ext3/super.c
+++ b/fs/ext3/super.c
@@ -466,6 +466,8 @@ static void ext3_put_super (struct
On Tue, Dec 23, 2014 at 12:41:40PM +0100, Dongsu Park wrote:
> You mean, checking rq->cmd_type == REQ_TYPE_BLOCK_PC, right?
>
> I'm wondering about how to check that in blk_queue_split().
> At the moment when blk_queue_split() is called, it's even before a request
> is mapped e.g. in
At Fri, 26 Dec 2014 14:27:58 +0100,
Alexandre Belloni wrote:
>
> From: Arnd Bergmann
>
> at91 will no longer export the mach/cpu.h and mach/hardware.h header files
> in the future, which would break building the atmel ac97c driver.
>
> Since the cpu_is_* check is only used to find out whether
On Thursday 25 December 2014 22:54:34 Gabriele Mazzotta wrote:
> On Thursday 18 December 2014 12:08:58 Pali Rohár wrote:
> > On Wednesday 10 December 2014 14:32:16 Gabriele Mazzotta wrote:
> > > On Wednesday 10 December 2014 12:51:30 Pali Rohár wrote:
> > > > On Tuesday 09 December 2014 21:07:01
Use the PDE to get proc_dir_entry instead of coding it directly.
Signed-off-by: Alexander Kuleshov
---
fs/proc/generic.c | 2 +-
fs/proc/inode.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/proc/generic.c b/fs/proc/generic.c
index 7fea132..de14e46 100644
---
On 12/26/2014 02:57 AM, Qu Wenruo wrote:
Hi all,
When testing v3.19-rc1 kernel(in fact, try to test), the kernel itself
fail to boot on VMware ESXi 5.1 guest.
The boot failure is quite easy to describe, only one line is output:
"Probing EDD (edd=off to disable)...ok"
No other output(including
On 12/24/2014 01:28 AM, Пламен Петров wrote:
Hello!
I use GRUB Legacy bootloader (version 0.97) on a couple machines, and where
3.18.x loads fine, 3.19-rc1 does not.
While compiling I used the attached .config file accompanied by "make
olddefconfig"
Can you tell me something about the
Hi,
On 27-12-14 00:51, Jeremiah Mahler wrote:
Ilia,
On Fri, Dec 26, 2014 at 04:39:08PM -0500, Ilia Mirkin wrote:
On Fri, Dec 26, 2014 at 4:26 PM, Jeremiah Mahler wrote:
If a display supports backlight control using the nouveau driver, and
also supports standard ACPI backlight control, there
wait_for_completion_timeout does not return negative values so
"result" handling here should be simplified to cover the actually
possible cases only.
patch was only compile tested for imx_v6_v7_defconfig
V2 spellchecked this time and proper labeling as
suggested by Sedat Dilek
patch is
Hi, all.
There was a discussion here:
https://lkml.org/lkml/2007/1/10/231
Linus wrote in this discussion:
"So don't use O_DIRECT. Use things like madvise() and posix_fadvise()
instead"
After the full week of tests, searches, discussions, I have impudence to
turn to the community - has one tried
Editors like emacs and vi recognize a number of error message
formats. The format used by the kerneldoc tool is not recognized
by emacs. Change the kerneldoc error message format to the GNU
style such that the emacs prev-error and next-error commands can
be used to navigate through kerneldoc error
Hi,
On 27-12-14 13:58, Hans de Goede wrote:
Hi Gregory,
Thanks for working on this. Overall the patch-set / concept looks good,
you can add "Acked-by: Hans de Goede " to the first
2 patches.
I've some comments on this patch, see below.
On 27-12-14 11:34, Gregory CLEMENT wrote:
The current
Hi Gregory,
Thanks for working on this. Overall the patch-set / concept looks good,
you can add "Acked-by: Hans de Goede " to the first
2 patches.
I've some comments on this patch, see below.
On 27-12-14 11:34, Gregory CLEMENT wrote:
The current implementation of the libahci allows using
[ Not sure which persons and MLs you CCed - I am reading LKML offline ]
Hi,
your patch needs some refreshing...
First your Subject... add a subject-prefix like...
$ git format-patch --subject-prefix="next-20141226"
[ The subject-prefix won't be seen if you push out the commit, but is
good for
Merhaba,
Size, Dünya üzerinde birçok Hekim'in kullandığı "Online Hasta Kayıt ve Portföy
Yönetim" sistemimiz https://healthrecordapp.com/tr/ hakkında bilgi vermek için
ulaştık.
HealthRecordApp, basit ve kolay kullanımlı arayüzü ile geleneksel hasta kayıt
sistemlerinden ve yazılımlarından hem
wati_for_completion_timeout does not return negative values so
"result" handlin here should be simplified to cover the actually
possible cases only.
patch was only compile tested for imx_v6_v7_defconfig
patch is against 3.19.0-rc1 -next-20141226
Signed-off-by: Nicholas Mc Guire
---
When two or more fingers are on the touchpad, the 'w' slot holds the
finger count rather than the width. Retrieve the correct value encoded
in the lower bits of 'x', 'y' and 'z'.
The minimum width reported is 8 rather than 4 in this case, while the
maximum remains 15.
Signed-off-by: Gabriele
Despite claiming to be able to report ABS_TOOL_WIDTH, image sensors
were not doing it. Make them report widths and use ABS_MT_TOUCH_MAJOR
instead ABS_TOOL_WIDTH.
Since the 'w' slot is used to report the finger count when two or more
fingers are on the touchpad, make sure that only meaningful
Image sensors were not reporting finger widths despite being able to do
it. These patches will make sure that finger widths are always reported.
Gabriele Mazzotta (2):
input: synaptics - make image sensors report ABS_MT_TOUCH_MAJOR
input: synaptics - fix width calculation on image sensors
This patch fix checkpatch warning for nfs4_fs.h
fs/nfs/nfs4_fs.h:134: ERROR: "foo * bar" should be "foo *bar"
fs/nfs/nfs4_fs.h:416: ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: Koshy George
[Being first patch, need some assistance]
---
fs/nfs/nfs4_fs.h | 4 ++--
1 file changed, 2
NACK!
As bfin_can.c is the only user of defines from this include file just add the
needed(!) defines directly to bfin_can.c
Currently bfin_can.h holds a *lot* of defines that are NOT referenced
anywhere, e.g. search for MC0 - MC31, MD0 - MD31, RMP0 - RMP31, RML0 - RML31
and lots more in
The current implementation of the libahci allows using multiple PHYs
but not multiple regulators. This patch adds the support of multiple
regulators. Until now it was mandatory to have a PHY under a subnode,
now a port subnode can contain either a regulator or a PHY (or both).
There was only one
The phy_ functions handle the NULL pointer case, so there is no need
to skip them if there is a NULL pointer. Moreover, after the error
label there is already no check on the pointer. This patch removes the
unnecessary tests and brings some consistency.
Signed-off-by: Gregory CLEMENT
---
It is now possible to use a regulator property for each port of the
AHCI controller.
Signed-off-by: Gregory CLEMENT
---
Documentation/devicetree/bindings/ata/ahci-platform.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Hi,
The current implementation of the libahci allows using one PHY per
port but we still have one single regulator for the whole
controller. This series adds the support of multiple regulators. Until
now it was mandatory to have a PHY under a subnode, now a port subnode
can contain either a
On Fri, 2014-12-26 at 14:45 +0800, Li Bin wrote:
> On 2014/7/8 4:05, Peter Zijlstra wrote:
> > On Mon, Jul 07, 2014 at 09:55:43AM -0400, Sasha Levin wrote:
> >> I've also had this one, which looks similar:
> >>
> >> [10375.005884] BUG: spinlock recursion on CPU#0, modprobe/10965
> >>
"Michael S. Tsirkin" writes:
> On Thu, Dec 25, 2014 at 05:05:01PM +0200, Michael S. Tsirkin wrote:
>> vhost incorrectly asked for 8 byte alignment for
>> used ring pointer, it should be 4 byte.
>>
>> Let's add explicit macros for ring element alignment,
>> this makes it easier to make sure our
On 2014/12/26 15:01, Sasha Levin wrote:
> On 12/26/2014 01:45 AM, Li Bin wrote:
>> On 2014/7/8 4:05, Peter Zijlstra wrote:
On Mon, Jul 07, 2014 at 09:55:43AM -0400, Sasha Levin wrote:
>> I've also had this one, which looks similar:
>>
>> [10375.005884] BUG: spinlock recursion on
Fixed multiple space issues found by checkpatch.pl in
drivers/staging/rtl8723au/core/rtw_ap.c
Signed-off-by: Matthew Emerson
---
drivers/staging/rtl8723au/core/rtw_ap.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
Hello,
in attachment is output of ls -l /sys/bus/acpi/devices from both
3.13 and 3.19 kernels.
Anyway Gabriele Mazzotta wrote me that new acpi devices could be
created after commit faae404ebdc6bba (ACPICA: Add "Windows 2013"
string to _OSI support).
Maybe this another output could help you:
1 - 100 of 202 matches
Mail list logo
