Stephen Rothwell writes:
> Hi Rusty,
>
> On Thu, 25 Jun 2015 17:34:31 -0400 Dan Streetman wrote:
>>
>> On Thu, Jun 25, 2015 at 5:18 PM, Rusty Russell wrote:
>> > Dan Streetman writes:
>> >> Only include the built-in and per-module param_lock, and corresponding
>> >> lock/unlock functions, if
On Sat, Jun 27, 2015 at 11:11:44PM +0200, Philippe Reynes wrote:
> The clocksource imx27 wasn't defined in timer-imx-gpt.c,
> so the kernel no longer boot on imx27. Just define
> clocksource imx27 as an imx21.
>
> Signed-off-by: Philippe Reynes
Acked-by: Shawn Guo
Daniel,
Please help send
Maciej S. Szmigiero wrote:
+ if (newbinding && fsl_ssi_is_ac97(ssi_private)) {
Is the "newbinding" necessary? I thought only the original PowerPC
device trees were the only one that have the old binding, and they never
supported AC97.
--
To unsubscribe from this list: send the line
From: Vitaly Kuznetsov
When general-purpose kexec (not kdump) is being performed in Hyper-V guest
the newly booted kernel fails with an MCE error coming from the host. It
is the same error which was fixed in the "Drivers: hv: vmbus: Implement
the protocol for tearing down vmbus state" commit -
From: Vitaly Kuznetsov
We already have hv_synic_free() which frees all per-cpu pages for all
CPUs, let's remove the hv_synic_free_cpu() call from hv_synic_cleanup()
so it will be possible to do separate cleanup (writing to MSRs) and final
freeing. This is going to be used to assist kexec.
From: Vitaly Kuznetsov
If some piece of code wants to check kexec_in_progress it has to be put
in #ifdef CONFIG_KEXEC block to not break the build in !CONFIG_KEXEC
case. Overcome this limitation by defining kexec_in_progress to false.
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y.
In addition to enabling kexec, this patch-set has a bunch of miscellaneous
fixes.
Alex Ng (1):
Drivers: hv: balloon: Enable dynamic memory protocol negotiation with
Windows 10 hosts
K. Y. Srinivasan (1):
Drivers: hv: vmbus: Permit sending of packets without payload
Vitaly Kuznetsov (8):
On Sat, 2015-06-27 at 18:02 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 27 Jun 2015, Mike Galbraith wrote:
> > > > BIOS setting "Limit CPUID Maximum" upsets new fpu code mightily.
> >
> > That BIOS setting is annotated with the helpful text "Disabled for
> > Windows XP". It makes box say
--
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/
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Thursday, June 25, 2015 9:12 AM
> To: linux-s...@vger.kernel.org
> Cc: Long Li; KY Srinivasan; Haiyang Zhang; James E.J. Bottomley;
> de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; Radim
On Fri, Jun 26, 2015 at 11:17 PM, Ville Syrjälä
wrote:
> On Fri, Jun 26, 2015 at 06:31:37PM +0200, Daniel Vetter wrote:
>> On Fri, Jun 26, 2015 at 02:32:03PM +0530, Shobhit Kumar wrote:
>> > Hi,
>> > Next update of the series reviewed at
>> > https://lkml.org/lkml/2015/6/22/155
>> >
>> > Major
On powerpc, setting CONFIG_NVRAM=n builds a kernel with no NVRAM support.
Setting CONFIG_NVRAM=m enables the /dev/nvram misc device module without
enabling NVRAM support in drivers. Setting CONFIG_NVRAM=y enables the
misc device (built-in) and also enables NVRAM support in drivers.
m68k shares
Move the m68k-specific code elsewhere to make the driver generic.
Change the vmode calculation from logical OR to bitwise OR, since it is
obviously wrong.
Signed-off-by: Finn Thain
---
BTW, I didn't change the SCSI ID location in NVRAM. This code says 16
whereas atari_scsi says 14. Which one
By implementing an arch_nvram_ops struct, any platform can re-use the
drivers/char/nvram module without needing any arch-specific code
in that module. Atari does so here.
Atari has one user of nvram_check_checksum() whereas the other platforms
(i.e. x86 and ARM platforms) have none at all.
Refactor the RTC "CMOS" NVRAM functions so that they can be used as
arch_nvram_ops methods. Checksumming logic is moved from the misc device
operations to the nvram read/write operations.
This makes the misc device implementation more generic. This also
preserves the locking semantics such that
Make use of arch_nvram_ops in the thinkpad_acpi driver so that the
nvram_* function exports can be removed.
This patch series was tested on a ThinkPad T43.
Signed-off-by: Finn Thain
Acked-by: Henrique de Moraes Holschuh
Reviewed-by: Darren Hart
---
drivers/platform/x86/thinkpad_acpi.c |
The drivers/char/nvram module has previously only supported RTC "CMOS"
NVRAM, for which it provides appropriate checksum ioctls. Make these
ioctls optional so the module can be re-used with other kinds of NVRAM.
The ops struct methods that implement the ioctls now return error
codes so that a
The nvram_read_byte() and nvram_write_byte() definitions in asm/nvram.h
duplicate those in linux/nvram.h. Get rid of the former to prepare for
adoption of struct arch_nvram_ops (which is defined in linux/nvram.h for
general use).
Signed-off-by: Finn Thain
---
arch/powerpc/include/asm/nvram.h
Atari RTC NVRAM has a checksum so implement the remaining arch_nvram_ops
methods for the set_checksum and initialize ioctls. Enable
CONFIG_HAVE_ARCH_NVRAM_OPS.
Signed-off-by: Finn Thain
---
This re-enables the nvram module for Atari.
---
arch/m68k/Kconfig |3 +++
Signed-off-by: Finn Thain
---
drivers/char/nvram.c | 16 +---
1 file changed, 1 insertion(+), 15 deletions(-)
Index: linux/drivers/char/nvram.c
===
--- linux.orig/drivers/char/nvram.c 2015-06-28
Signed-off-by: Finn Thain
---
drivers/char/nvram.c |1 +
1 file changed, 1 insertion(+)
Index: linux/drivers/char/nvram.c
===
--- linux.orig/drivers/char/nvram.c 2015-06-28 11:41:38.0 +1000
+++
Adopt nvram module to reduce code duplication.
The IOC_NVRAM_GET_OFFSET ioctl as implemented on PPC64 validates the offset
returned by pmac_get_partition(). Add this test to the nvram module.
Note that the old PPC32 generic_nvram module lacked this test.
So when CONFIG_PPC32 && CONFIG_PPC_PMAC,
Switch PPC32 kernels from the generic_nvram module to the nvram module.
Also fix a theoretical bug where CHRP omits the chrp_nvram_init()
call when CONFIG_NVRAM_MODULE=m.
As before, when CONFIG_PPC && !CONFIG_PPC_PMAC, the IOC_NVRAM_GET_OFFSET
ioctl is unimplemented. For the nvram module,
Drivers now use the arch_nvram_ops calls so remove the function exports and
prototypes. nvram_check_checksum() is unused so remove it.
Signed-off-by: Finn Thain
---
arch/m68k/atari/nvram.c |6 +++---
drivers/char/nvram.c| 27 +--
include/linux/nvram.h |8
Make use of arch_nvram_ops in device drivers so that the nvram_*
function exports can be removed.
Since they are no longer global symbols, rename the PPC32 nvram_* functions
appropriately.
Add the missing CONFIG_NVRAM test to imsttfb to avoid a build failure.
Signed-off-by: Finn Thain
---
Add the nvram_size() function to those PowerPC platforms that don't already
have one: CHRP and PowerMac. This means that the ppc_md.nvram_size()
function can be used to implement arch_nvram_ops.get_size()
Since we are addressing inconsistencies here, also rename chrp_nvram_read
and
Implement arch_nvram_ops for PPC32 and make use of it in the generic_nvram
misc device module so that the nvram_* function exports can be removed.
Signed-off-by: Finn Thain
---
arch/powerpc/include/asm/nvram.h |3 ---
arch/powerpc/kernel/setup_32.c | 10 +++---
Signed-off-by: Finn Thain
---
This is intended to improve code style and not affect code behaviour.
I've tested this on a Quadra 650.
I don't know the meanings of the 4 undocumented write protect register
bits 0x55, so I decided against defining 4 macros for those bits.
---
And thus eliminate some twisted CONFIG_GENERIC_NVRAM logic.
Signed-off-by: Finn Thain
---
drivers/char/Makefile|6 -
drivers/char/generic_nvram.c | 176 ---
2 files changed, 1 insertion(+), 181 deletions(-)
Index:
Add the powerpc-specific sync() method to struct nvram_ops and implement
the corresponding ioctl in the nvram module. This allows the nvram module
to replace the generic_nvram module.
Signed-off-by: Finn Thain
---
On PPC32, the IOC_NVRAM_SYNC ioctl call always returns 0, even for those
A multi-platform kernel binary needs to decide at run-time how to dispatch
the arch_nvram_ops calls. Add platform-independent arch_nvram_ops, for use
when multiple platform-specific NVRAM ops implementations are needed.
Enable CONFIG_HAVE_ARCH_NVRAM_OPS for Macs.
Signed-off-by: Finn Thain
---
Signed-off-by: Finn Thain
---
Tested on a PowerBook 520 and Quadra 650.
Changes since v2:
- Make use of the RTC_* macros from the previous patch and add a few more
besides.
---
arch/m68k/mac/misc.c | 39 +--
include/uapi/linux/pmu.h |2 ++
2
Adopt the existing *_read_byte and *_write_byte naming convention.
Rename via_pram_readbyte and via_pram_writebyte to avoid confusion.
Adjust calling conventions of mac_pram_* functions to match the
arch_nvram_ops struct methods.
Signed-off-by: Finn Thain
---
Changes since v1:
- Don't
Also give functions more sensible names: nvram_misc_* for misc device ops,
nvram_proc_* for proc file ops and nvram_module_* for init and exit
functions. This makes them distict from nvram_ops members.
Signed-off-by: Finn Thain
---
drivers/char/nvram.c | 194
The generic NVRAM module, drivers/char/generic_nvram, implements a
/dev/nvram misc device. It is used only by 32-bit PowerPC platforms and
isn't generic enough to be more widely used.
The RTC NVRAM module, drivers/char/nvram, also implements a /dev/nvram
misc device. It is used by x86, ARM and
Different platforms and architectures offer different NVRAM sizes and
access methods. E.g. PPC32 has byte-at-a-time read/write functions whereas
PPC64 has byte-range read/write functions. Adopt the nvram_ops struct so
the nvram module can call such functions as are defined by the various
On Sat, Jun 27, 2015 at 7:26 PM, Greg Kroah-Hartman
wrote:
> On Sat, Jun 27, 2015 at 05:17:03PM -0400, Patrick Donnelly wrote:
>> This fixes a bug where a process can set the foreground process group to its
>> pid even if its pid is not a valid pgrp.
>>
>> Signed-off-by: Patrick Donnelly
>> ---
task_pgrp requires an rcu or tasklist lock to be obtained if the returned pid
is to be dereferenced, which kill_pgrp does. Obtain an RCU lock for the
duration of use.
Signed-off-by: Patrick Donnelly
---
drivers/tty/tty_io.c | 24 +++-
1 file changed, 15 insertions(+), 9
This fixes a bug where a process can set the foreground process group to its
pid even if its pid is not a valid pgrp.
Signed-off-by: Patrick Donnelly
---
drivers/tty/tty_io.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index
On Sun, 28 Jun 2015, Ruslan Bilovol wrote:
> > Weren't you going to replace this loop with a simple list_del()? IIRC,
> > this is the third time I have asked you to make this change.
>
> I understand the improvement that replacing this loop with a list_del()
> may bring for us, but I disagree
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
wrote:
> Some devices take a long time when initializing, and not all drivers are
> suited to initialize their devices when they are open. For example,
> input drivers need to interrogate their devices in order to publish
> device's capabilities
On Sat, Jun 27, 2015 at 05:17:03PM -0400, Patrick Donnelly wrote:
> This fixes a bug where a process can set the foreground process group to its
> pid even if its pid is not a valid pgrp.
>
> Signed-off-by: Patrick Donnelly
> ---
> drivers/tty/tty_io.c | 8 +++-
> 1 file changed, 7
On Sat, Jun 27, 2015 at 05:17:03PM -0400, Patrick Donnelly wrote:
> This fixes a bug where a process can set the foreground process group to its
> pid even if its pid is not a valid pgrp.
>
> Signed-off-by: Patrick Donnelly
> ---
> drivers/tty/tty_io.c | 8 +++-
> 1 file changed, 7
On Sat, Jun 27, 2015 at 05:17:02PM -0400, Patrick Donnelly wrote:
> Signed-off-by: Patrick Donnelly
No changelog text? Sorry, it's required.
--
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
Hello Fabio,
W dniu 28.06.2015 01:06, Fabio Estevam pisze:
> Hi Maciej,
>
> On Sat, Jun 27, 2015 at 7:51 PM, Maciej S. Szmigiero
> wrote:
>> Currently the AC'97 mode in fsl_ssi driver isn't functional.
>
> Thanks for the fix. I look forward to test it on my udoo board.
Thanks.
>> This patch
On Sat, Jun 27, 2015 at 7:51 PM, Maciej S. Szmigiero
wrote:
> +
> + ret = clk_prepare_enable(fsl_ac97_data->clk);
> + if (ret) {
> + pr_err("ac97 read clk_prepare_enable failed: %d\n",
> + ret);
> + return -1;
'return ret' would be
Hi Maciej,
On Sat, Jun 27, 2015 at 7:51 PM, Maciej S. Szmigiero
wrote:
> Currently the AC'97 mode in fsl_ssi driver isn't functional.
Thanks for the fix. I look forward to test it on my udoo board.
> This patch implements the following changes to make it work
> properly:
> * IPG clock have to
Currently the AC'97 mode in fsl_ssi driver isn't functional.
This patch implements the following changes to make it work
properly:
* IPG clock have to be enabled during AC'97 CODEC
register access,
* AC'97 DAI driver struct need the same probe method as
I2S one to setup DMA params,
* AC'97 bus
Hi Alan,
On Tue, Jun 23, 2015 at 5:08 PM, Alan Stern wrote:
> On Tue, 23 Jun 2015, Ruslan Bilovol wrote:
>
>> Change behavior during registration of gadgets and
>> gadget drivers in udc-core. Instead of previous
>> approach when for successful probe of usb gadget driver
>> at least one usb
On 06/27/2015 02:34 PM, Constantine Shulyupin wrote:
From: const
0, 3 - Temperature attributes are hidden
1 - Current mode
2 - Thermistor mode
Reference:
Nuvoton Hardware Monitoring IC NCT7802Y
7.2.32 Mode Selection Register
Location : Index 22h
Signed-off-by: Constantine Shulyupin
Hi
Hi Constantine,
On 06/27/2015 02:23 PM, Constantine Shulyupin wrote:
From: const
0, 3 - Temperature attributes are hidden
Not really per your code (though they should be hidden).
1 - Current mode
2 - Thermistor mode
Wrong - that should be 3 for current (diode) mode and 4 for thermistor
From: const
0, 3 - Temperature attributes are hidden
1 - Current mode
2 - Thermistor mode
Reference:
Nuvoton Hardware Monitoring IC NCT7802Y
7.2.32 Mode Selection Register
Location : Index 22h
Signed-off-by: Constantine Shulyupin
---
drivers/hwmon/nct7802.c | 53
From: const
0, 3 - Temperature attributes are hidden
1 - Current mode
2 - Thermistor mode
Reference:
Nuvoton Hardware Monitoring IC NCT7802Y
7.2.32 Mode Selection Register
Location : Index 22h
Signed-off-by: Constantine Shulyupin
---
drivers/hwmon/nct7802.c | 53
From: Markus Elfring
Date: Sat, 27 Jun 2015 22:23:28 +0200
The dsi_destroy() function was called in two cases by the dsi_init() function
during error handling even if the passed variable contained a null pointer.
* This implementation detail could be improved by adjustments for jump
targets
From: Markus Elfring
Date: Sat, 27 Jun 2015 22:05:31 +0200
The dsi_destroy() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
On Sat, Jun 27, 2015 at 6:11 PM, Philippe Reynes wrote:
> The clocksource imx27 wasn't defined in timer-imx-gpt.c,
> so the kernel no longer boot on imx27. Just define
> clocksource imx27 as an imx21.
>
> Signed-off-by: Philippe Reynes
Reviewed-by: Fabio Estevam
--
To unsubscribe from this
This fixes a bug where a process can set the foreground process group to its
pid even if its pid is not a valid pgrp.
Signed-off-by: Patrick Donnelly
---
drivers/tty/tty_io.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
Signed-off-by: Patrick Donnelly
---
drivers/tty/tty_io.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 57fc6ee..401d05e 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -388,33 +388,40 @@
From: Markus Elfring
Further update suggestions were taken into account after a patch was applied
from static source code analysis.
Markus Elfring (2):
Delete an unnecessary check before the function call "dsi_destroy"
One function call less in dsi_init() after error detection
The clocksource imx27 wasn't defined in timer-imx-gpt.c,
so the kernel no longer boot on imx27. Just define
clocksource imx27 as an imx21.
Signed-off-by: Philippe Reynes
---
drivers/clocksource/timer-imx-gpt.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
On Sat, 27 Jun 2015, Mike Galbraith wrote:
> > > BIOS setting "Limit CPUID Maximum" upsets new fpu code mightily.
>
> That BIOS setting is annotated with the helpful text "Disabled for
> Windows XP". It makes box say interesting things during boot, like...
>
> x86/fpu: XSTATE_CPUID
Hi Philippe,
On Sat, Jun 27, 2015 at 5:38 PM, Philippe Reynes wrote:
> I've tested this change, and it works fine.
> In the file drivers/clocksource/timer-imx-gpt.c, there is :
> #define imx21_gpt_irq_disable imx1_gpt_irq_disable
> #define imx21_gpt_irq_enable imx1_gpt_irq_enable
> So I think
Hi Fabio,
On 27/06/15 21:17, Fabio Estevam wrote:
Philippe,
On Sat, Jun 27, 2015 at 2:34 PM, Fabio Estevam wrote:
Yes, please submit a formal patch.
I thought it was imx1_timer_init_dt because in imx27.dtsi we have:
compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
So I am wondering if this
Hi,
[no In-Reply-To header - lkml.org "headers" is broken ATM]
> +
> +static bool i8042_debug_kbd;
> +module_param_named(debug_kbd, i8042_debug_kbd, bool, 0600);
> +MODULE_PARM_DESC(i8042_kbd, "Turn i8042 kbd debugging output on or off
> (requires i8042.debug=1)");
seems inconsistent:
Toralf Förster писал в своём письме Sat, 27 Jun
2015 22:16:27 +0300:
The casts are safe, since those conditions are only evaluated when sz
>= 0.
Wouldn't in this case the condition "sz < 0" be superfluously ?
No, sz can be negative. I meant that if sz < 0, then the second halves
Philippe,
On Sat, Jun 27, 2015 at 2:34 PM, Fabio Estevam wrote:
> Yes, please submit a formal patch.
>
> I thought it was imx1_timer_init_dt because in imx27.dtsi we have:
>
> compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
>
> So I am wondering if this is correct or it should be
>
> compatible =
>The casts are safe, since those conditions are only evaluated when sz >= 0.
Wouldn't in this case the condition "sz < 0" be superfluously ?
--
Toralf
pgp key: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 0076 E94E
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Hello Andy,
2015-06-28 0:39 GMT+06:00 Andy Shevchenko :
> P.S. I guess you may try to submit first something a bit more trivial
> that this to train your skills in open source community. You already
> have 13 versions of the patch series with some stylistic issues. And
> some of them might be due
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a new Laptop, a Medion E4214, with a standard xubuntu LTS 14.04
installed.
My problem is, that the notebook does neither reboot nor powerdown. It hangs
late
in the powerdown/reboot sequence, with no error message shown on the console,
From: Markus Elfring
Date: Sat, 27 Jun 2015 20:44:49 +0200
The backlight_device_unregister() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus
On Sat, Jun 27, 2015 at 4:48 PM, Alexander Kuleshov
wrote:
> The earlyprintk is usable only after the setup_early_printk will
You might use the standard form of the function representation in the
text, i.e. 'setup_early_printk()' (notice parens at the end of token).
> be executed. We pass
On Sat, Jun 27, 2015 at 4:54 PM, Alexander Kuleshov
wrote:
> sorry, forgot to add version to this patch, please skip this patch.
You may, for example, supply --subject-prefix="PATCH v13" to git
format-patch command to create a nice version token.
One comment below.
>
> 2015-06-27 19:46
On Sat, Jun 27, 2015 at 7:32 PM, Andreas Hartmann
wrote:
> Hello!
>
> Given is a module like the following snippet running fine w/ Linux 4.0
> and ext4 fs - but doesn't work w/ Linux 4.1 because f->f_op->read is not
> defined any more (= NULL). Is this the intended behavior now?
See
> There is no way for a human being to remember the complete list of
> functions with sanity checks and which don't have sanity checks.
I understand also this software development challenge.
> Markus has introduced quite a few bugs as well
I have only found other opinions about specific update
Hello!
Given is a module like the following snippet running fine w/ Linux 4.0
and ext4 fs - but doesn't work w/ Linux 4.1 because f->f_op->read is not
defined any more (= NULL). Is this the intended behavior now?
vfs_read(f, buf, 128, >f_pos) works fine.
module.c
On Sat, Jun 27, 2015 at 4:12 PM, Borislav Petkov wrote:
> On Sat, Jun 27, 2015 at 03:52:56PM +0200, Daniel Vetter wrote:
>> Hm, what do you mean by fixing this in the allocator? I've made some
>> rough sketch of the problem space in
>> http://www.x.org/wiki/DRMJanitors/ under "Make panic handling
On 06/23/2015 06:33 PM, Konrad Rzeszutek Wilk wrote:
Hey Jens,
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.2
in your 'for-4.2/drivers' branch. It is late - for which I am terrible
sorry! The patches have been sitting in
On 06/26/2015 05:58 AM, Geert Uytterhoeven wrote:
With gcc 3.4.6/4.1.2/4.2.4 (not with 4.4.7/4.6.4/4.8.4):
CC fs/block_dev.o
include/linux/fs.h:804: warning: ‘I_BDEV’ declared inline after being
called
include/linux/fs.h:804: warning: previous declaration of ‘I_BDEV’ was
On 06/26/2015 03:44 AM, Paolo Bonzini wrote:
Whenever blk_fill_sghdr_rq fails, its errno code is ignored and changed to
EFAULT. This can cause very confusing errors:
$ sg_persist -k /dev/sda
persistent reservation in: pass through os error: Bad address
The fix is trivial, just propagate
On 06/26/2015 03:20 PM, Davidlohr Bueso wrote:
On Thu, 2015-06-25 at 08:37 -0600, Jens Axboe wrote:
- Code consolidation and cleanups from Christoph.
Andrew, it seems your fix for gcc never went in. I am hitting it in
Linus' tree.
On Sat, Jun 27, 2015 at 2:26 PM, Philippe Reynes wrote:
> I've looked the code in drivers/clocksource/timer-imx-gpt.c, in the
> definition
> of imx_gpt_type, there is :
> GPT_TYPE_IMX21, /* i.MX21/27 */
>
> So I've done a little change in your patch, I've used imx21_timer_init_dt
Hi Fabio,
On 27/06/15 19:05, Fabio Estevam wrote:
Hi Philippe,
On Sat, Jun 27, 2015 at 10:21 AM, Philippe Reynes wrote:
Hi all,
I've tested the lastest linus git kernel, and this kernel
no longer boot on my armadeus apf27. The last line of the
log are (after, the kernel is stalled) :
[
>> From: Markus Elfring
>> Date: Wed, 4 Feb 2015 21:54:45 +0100
>>
>> The functions phy_power_on() and vunmap() perform also input
>> parameter validation. Thus the test around their calls is not needed.
>>
>> This issue was detected by using the Coccinelle software.
>>
>> Signed-off-by: Markus
Hi Philippe,
On Sat, Jun 27, 2015 at 10:21 AM, Philippe Reynes wrote:
> Hi all,
>
> I've tested the lastest linus git kernel, and this kernel
> no longer boot on my armadeus apf27. The last line of the
> log are (after, the kernel is stalled) :
>
> [0.00] CPU identified as i.MX27,
The casts are safe, since those conditions are only evaluated when sz >= 0.
Signed-off-by: Роман Донченко
---
arch/x86/include/asm/uaccess.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/uaccess.h b/arch/x86/include/asm/uaccess.h
index
On Fri, Jun 26, 2015 at 11:56 PM, Herbert Xu
wrote:
>
> So I think Tadeusz's patch is the simplest fix for 4.2. Could you
> please test it to see if it makes your warning go away?
Seems to silence it here.
I get the feeling that the patch is still wrong - why are not the
*tests* run at late
> From: Markus Elfring
> Date: Wed, 19 Nov 2014 14:24:20 +0100
>
> The pci_dev_put() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus
Let me try to summarize some of the approaches with their pros and cons:
--- percpu segment ---
This is probably the simplest and might make sense regardless.
cmpxchg can be used to do an atomic push onto a linked list. I think
that unlocked cmpxchg16b can be used to get an atomic pop. (You'd
On Sat, 27 Jun 2015, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jun 2015 16:00:59 +0200
>
> The kfree() function was called in two cases by the mac_ioctl() function
> during error handling even if the passed variable did not contain a pointer
> for a valid data item.
>
> *
On Sat, Jun 27, 2015 at 10:09:28AM +0200, Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Fri, Jun 26, 2015 at 9:01 AM, Tejun Heo wrote:
> > >
> > > Ooh, it isn't in mainline yet but pulling rcu tree will cause a silent
> > > conflict with this pull request which leads to build
On Saturday 27 June 2015 16:39:09 Guenter Roeck wrote:
> On 06/27/2015 06:22 AM, Gabriele Mazzotta wrote:
> > As per Documentation/hwmon/sysfs-interface, hwmon name attributes
> > must not include '-', so replace 'dell-smm' with 'dell_smm'.
> >
> > Fixes: 039ae58503f3 ("hwmon: Allow to compile
From: Markus Elfring
Date: Sat, 27 Jun 2015 18:12:14 +0200
The cleanup_one_si() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
On 06/22/2015 01:43 PM, Vivien Didelot wrote:
Hi Guenter,
On Jun 22, 2015, at 12:53 PM, Guenter Roeck li...@roeck-us.net wrote:
On Wed, Jun 17, 2015 at 06:58:59PM -0400, Vivien Didelot wrote:
Introduce a new struct max63xx_platform_data to support MAX63xx watchdog
chips connected via GPIO. A
On Sat, Jun 27, 2015 at 02:35:56PM +1000, Stephen Rothwell wrote:
> Hi Linus,
>
> On Fri, 26 Jun 2015 20:18:10 -0700 Linus Torvalds
> wrote:
> >
> > On Fri, Jun 26, 2015 at 9:01 AM, Tejun Heo wrote:
> > >
> > > Ooh, it isn't in mainline yet but pulling rcu tree will cause a silent
> > >
Salve
moto, mac Laptop, Kamera, Telefon
samsung 6, € 320
w eb: isgayre. com
N�r��yb�X��ǧv�^�){.n�+{zX����ܨ}���Ơz�:+v���zZ+��+zf���h���~i���z� �w���?�&�)ߢf��^jǫy�m��@A�a���
0��h���i
On Sat, Jun 27, 2015 at 1:14 AM, Akinobu Mita wrote:
> Akinobu Mita wrote:
>> 2015-06-26 0:40 GMT+09:00 Ming Lei :
>> > On Thu, 25 Jun 2015 21:49:43 +0900
>> > Akinobu Mita wrote:
>> >> For example, there is a single hw queue (hctx) and two CPU queues
>> >> (ctx0 for CPU0, and ctx1 for CPU1).
On Sat, Jun 27, 2015 at 1:39 AM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>> So what's wrong with exposing them as a simplified PMU driver?
>>
>> That way we only expose the ones we want to - plus tooling can use all the
>> rich
>> perf features that can be used around this. (sampling,
On Sat, 27 Jun 2015, Jan Kiszka wrote:
> > Please explain _in detail_ what you mean with "changing a power button to a
> > reset button by acessing the SSMS ACPI method in a X121e".
> >
> > Are we trigering a bug somewhere that crashes the x121e and causes it to
> > reboot?
>
> Well, there
Hi Peter,
On 06/25/2015 12:30 AM, Peter Hung wrote:
Add New Fintek SuperIO F81866(0x1010) & F71868(0x1106)
with H/W Monitor functions.
Signed-off-by: Peter Hung
---
drivers/hwmon/f71882fg.c | 50 ++--
1 file changed, 36 insertions(+), 14
On Fri, Jun 26, 2015 at 11:29 PM, Fengguang Wu wrote:
> Ah it has been reported, sorry for the duplicated report!
No problem. It was a good catch -- this bug seems to be quite
dependent on kernel config.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
1 - 100 of 384 matches
Mail list logo
