On Wed 01-02-17 15:48:21, Minchan Kim wrote:
> Hi Yisheng,
>
> On Tue, Jan 31, 2017 at 09:06:18PM +0800, ys...@foxmail.com wrote:
> > From: Yisheng Xie
> >
> > This patch changes the return type of isolate_movable_page()
> > from bool to int. It will return 0 when isolate movable page
> > succes
On Tue, Jan 31, 2017 at 05:00:03PM +, Marc Zyngier wrote:
> On 30/01/17 19:06, Christoffer Dall wrote:
> > On Mon, Jan 30, 2017 at 06:48:02PM +, Marc Zyngier wrote:
> >> On 30/01/17 18:41, Christoffer Dall wrote:
> >>> On Mon, Jan 30, 2017 at 05:50:03PM +, Marc Zyngier wrote:
> On
From: Omar Sandoval
put_chars() stuffs the buffer it gets into an sg, but that buffer may be
on the stack. This breaks with CONFIG_VMAP_STACK=y (for me, it
manifested as printks getting turned into NUL bytes).
Signed-off-by: Omar Sandoval
---
Patch based on v4.10-rc6.
drivers/char/virtio_cons
Could you paste your drivers/iio/pressure/mpl3115.c code into pastebin.com
and send us the result?
thanks,
Daniel.
On Wed, Feb 1, 2017 at 8:50 AM, Jonathan Cameron
wrote:
>
>
> On 1 February 2017 00:42:31 GMT+00:00, "Ken.Lin"
> wrote:
>>
>>
>>> -Original Message-
>>> From: Peter Rosin
Sorry I'm late..
I got it!
I'll send v3 with changed patches !!
Thanks,
Taeung
On 01/31/2017 10:23 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Jan 31, 2017 at 08:38:30PM +0900, Taeung Song escreveu:
Currently there are several parts not checking NULL
after allocating with zalloc() or asigning
On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote:
> On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim
> wrote:
> > Now that we maintain the EL1 physical timer register states of VMs,
> > update the physical timer interrupt level along with the virtual one.
> >
> > Note that the emulated
On 01/31/2017 10:25 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Jan 31, 2017 at 08:38:31PM +0900, Taeung Song escreveu:
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
The title of this patch is misleading, ambiguous. It leads one to have
doubt if we were not incrementing that i
On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote:
> Currently qw_sign requires UTF-8 character to set, but returns UTF-16
> when read. This isn't obvious when simply using cat since the null
> characters are not visible, but hexdump unveils the true string:
>
> # echo MSFT100 > os_de
On Tue, Jan 31, 2017 at 06:19:16PM -0800, Stefan Agner wrote:
> Currently qw_sign requires UTF-8 character to set, but returns UTF-16
> when read. This isn't obvious when simply using cat since the null
> characters are not visible, but hexdump unveils the true string:
>
> # echo MSFT100 > os_de
On Tue, Jan 31, 2017 at 06:19:17PM -0800, Stefan Agner wrote:
> Other unsigned properties return hexadecimal values, follow this
> convention when printing b_vendor_code too. Also add newlines to
> the OS Descriptor support related properties, like other sysfs
> files use.
configfs is not sysfs, s
On Mon, Jan 30, 2017 at 01:53:36PM -0800, Dan Williams wrote:
> On Mon, Jan 30, 2017 at 4:24 AM, Christoph Hellwig wrote:
> > Hi Dan,
> >
> > this looks mostly fine to me. A few code comments below, but except
> > for this there is another issue with it: We still have drivers
> > that share a si
On Wed, Feb 01, 2017 at 12:10:17AM +0100, Rafael J. Wysocki wrote:
> On Tue, Jan 3, 2017 at 7:33 AM, Peter Chen wrote:
> > We have an well-known problem that the device needs to do some power
> > sequence before it can be recognized by related host, the typical
> > example like hard-wired mmc devi
On Mon, Jan 30, 2017 at 12:57:05PM -0800, Dan Williams wrote:
>
> struct kref {
> atomic_t refcount;
> };
>
> ...so what do we gain by open coding kref_get() and kref_put()?
A much less ugly calling convention.
On Tue, Jan 31, 2017 at 10:37:14PM +0200, Jarkko Sakkinen wrote:
> On Tue, Jan 31, 2017 at 01:43:59PM -0500, Stefan Berger wrote:
> > drivers/char/tpm/tpm-sysfs.c:161:25: warning: expression using sizeof bool
> >
> > Fixes: c659af78eb7b ("tpm: Check size of response before accessing data")
> > Sig
Hi!
These two patches are needed to fix some fallout from adding the
available attribute.
I'm sending this before getting a verification that it work from Ken Lin
in the hopes that these mails will reach other recipients swifter than my
original mail appears to do [1]. It looks like my mails are
Fixes a regression triggered by a change in the layout of
struct iio_chan_spec, but the real bug is in the driver which assumed
a specific structure layout in the first place.
Fixes: 3017d90e8931 ("iio: Add Freescale MPL115A2 pressure / temperature sensor
driver")
Fixes: 51239600074b ("iio:core:
Fixes a regression triggered by a change in the layout of
struct iio_chan_spec, but the real bug is in the driver which assumed
a specific structure layout in the first place.
# cat /sys/bus/iio/devices/iio\:device1/in_pressure_scale_available
Segmentation fault
Unable to handle kernel NULL point
On 01/30/2017 09:44 PM, Steven Rostedt wrote:
On Wed, 25 Jan 2017 02:28:16 +0100
Daniel Borkmann wrote:
For upcoming tracepoint support for BPF, we want to dump the program's
tag. Format should be similar to __print_hex(), but without spacing.
Add a __print_hex_str() variant for exactly that p
On 01.02.2017 08:44, Inki Dae wrote:
>
> 2017년 02월 01일 16:34에 Andrzej Hajda 이(가) 쓴 글:
>> On 01.02.2017 08:31, Inki Dae wrote:
>>> 2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글:
In some platforms there is attached another device to the end of HDMI.
The patch adds support for it.
>>> Andrzej,
2017년 02월 01일 17:12에 Andrzej Hajda 이(가) 쓴 글:
> On 01.02.2017 08:44, Inki Dae wrote:
>>
>> 2017년 02월 01일 16:34에 Andrzej Hajda 이(가) 쓴 글:
>>> On 01.02.2017 08:31, Inki Dae wrote:
2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글:
> In some platforms there is attached another device to the end of
On Jan 31 2017 or thereabouts, Daniel Drake wrote:
> Hi Benjamin,
>
> On Tue, Dec 13, 2016 at 2:16 AM, Benjamin Tissoires
> wrote:
> > On Dec 12 2016 or thereabouts, Chris Chiu wrote:
> >> ROG means ASUS "Republic of Gamers" laptops. The input device info
> >> also represents itself as "ASASTeK C
Hi Jonathan,
On Jan 31 2017 or thereabouts, Jonathan Tomer wrote:
> These adapters allow pre-USB Sun keyboards to be connected to USB-only
> machines, but includes the wrong maximum keycode in its report
> descriptor, making most of the keys present on Sun keyboards but not
> 101-key PC keyboards
commit e2427b09ba929c2b9 (phy: Add support for Qualcomm's USB HS phy")
while using extcon API's in qcom-usb-hs failed to add
'depends on EXTCON' resulting in the following compile errors if
EXTCON is not enabled.
drivers/built-in.o: In function `qcom_usb_hs_phy_power_off':
phy-qcom-usb-hs.c:(.text+
On TM2/TM2e platforms HDMI output is connected to MHL bridge
SiI8620. To allow configure UltraHD modes on the bridge
and to eliminate unsupported modes this bridge should be
attached to drm_encoder implemented in exynos_hdmi.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_hdmi.c
On Tue, 31 Jan 2017 11:07:24 -0500
Paul Moore wrote:
> On Tue, Jan 31, 2017 at 7:36 AM, Richard Guy Briggs
> wrote:
> > On 2017-01-31 06:59, Paul Moore wrote:
> >> On Thu, Jan 26, 2017 at 4:21 PM, Richard Guy Briggs
> >> wrote:
> >> > This adds a new auxiliary record MODULE_INIT to the SYSC
On Tuesday 31 January 2017 07:59:18 Tony Lindgren wrote:
> * Kalle Valo [170130 22:36]:
> > Tony Lindgren writes:
> >
> > > * Pavel Machek [170127 11:41]:
> > >> On Fri 2017-01-27 17:23:07, Kalle Valo wrote:
> > >> > Pali Rohár writes:
> > >> >
> > >> > > On Friday 27 January 2017 14:26:22 Ka
>> At boot time, probe function of multiple connected devices
>> (proprietary devices) execute simultaneously.
>
>What exactly do you mean here? How can probe happen "simultaneously"?
>The USB core prevents this, right?
I have observed two scenarios to call probe function:
Scenario #1: Driver
On Jan 31 2017 or thereabouts, Dmitry Torokhov wrote:
> If device is supposed to send absolute events (i.e. EV_ABS bit is set in
> dev->evbit) but dev->absinfo is not allocated, then the driver has done
> something wrong, and we should not register such device. Otherwise we'll
> crash later, when d
On Fri, 27 Jan 2017, Michael Schmitz wrote:
> Am 26.01.2017 um 21:47 schrieb Finn Thain:
>
> > This would imply CPU overhead that is half of that which mac_scsi
> > incurs. That's the best case, but I see no reason to expect worse
> > performance than PDMA gets.
>
> But how much more overhead
On Wed, Feb 1, 2017 at 3:04 AM, Christoffer Dall
wrote:
> On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote:
>> On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim
>> wrote:
>> > Now that we maintain the EL1 physical timer register states of VMs,
>> > update the physical timer interrupt l
Hi Finn,
On Wed, Feb 1, 2017 at 9:40 AM, Finn Thain wrote:
> okay. (BTW, where is the IDE status register found anyway?)
In the IDE device.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversa
On Jan 31 2017 or thereabouts, Dmitry Torokhov wrote:
> If user tries to initialize uinput device mixing old and new style
> initialization (i.e. using old UI_SET_ABSBIT instead of UI_ABS_SETUP,
> we forget to allocate input->absinfo and will crash when trying to send
> absolute events:
>
>
On 02/01/2017 09:09 AM, Peter Rosin wrote:
> Hi!
>
> These two patches are needed to fix some fallout from adding the
> available attribute.
I put together a quick cocci script to check for other occurrences of this
issue and these were the only two drivers affected by the issue.
On Wed 01-02-17 13:01:24, Anshuman Khandual wrote:
[...]
> More importantly it also extends the cpuset memory restriction feature
> to the logical completion without adding any regressions for the
> existing use cases. Then why not do this ? Does it add any overhead ?
Maybe it doesn't add any over
On Tue, 31 Jan 2017, Josh Poimboeuf wrote:
> On Tue, Jan 31, 2017 at 03:31:39PM +0100, Miroslav Benes wrote:
> > On Thu, 19 Jan 2017, Josh Poimboeuf wrote:
> >
> > > Expose the per-task patch state value so users can determine which tasks
> > > are holding up completion of a patching operation.
>
* Sam Ravnborg wrote:
> > Firsty, the headers are not maintained by the user-space project, 99.999%
> > of
> > the maintenance is done by the kernel developers.
>
> In the inital mail triggering this plan was that the kernel is moving away
> from
> having uapi headers what-so-ever.
No, tha
Hi Linus,
another week another set of pin control fixes. The subsystem has seen
high patch-spot activity recently.
The majority of the patches are for Intel, I vaguely think it mostly concern
phones, tablets and maybe chromebooks and even laptops with this Intel
Atom family chips.
Please pull th
On Feb 01 2017 or thereabouts, Benjamin Tissoires wrote:
> On Jan 30 2017 or thereabouts, Todd K wrote:
> > On Mon, Jan 30, 2017 at 10:56:18AM +0100, Benjamin Tissoires wrote:
> > > Hi,
> > >
> > > On Jan 27 2017 or thereabouts, Todd Kelner wrote:
> > > > Sony's NSG-MR5U and NSG-MR7U remote contro
On Wed, Feb 01, 2017 at 07:24:44AM +, Ajay Kaher wrote:
>
> >> At boot time, probe function of multiple connected devices
> >> (proprietary devices) execute simultaneously.
> >
> >What exactly do you mean here? How can probe happen "simultaneously"?
> >The USB core prevents this, right?
>
>
Hi,
Greg KH writes:
> On Tue, Jan 31, 2017 at 06:19:17PM -0800, Stefan Agner wrote:
>> Other unsigned properties return hexadecimal values, follow this
>> convention when printing b_vendor_code too. Also add newlines to
>> the OS Descriptor support related properties, like other sysfs
>> files u
On Tue 31-01-17 16:38:10, Johannes Weiner wrote:
> On Tue, Jan 31, 2017 at 11:45:47AM -0800, Shaohua Li wrote:
> > On Tue, Jan 31, 2017 at 01:59:49PM -0500, Johannes Weiner wrote:
> > > Hi Shaohua,
> > >
> > > On Sun, Jan 29, 2017 at 09:51:17PM -0800, Shaohua Li wrote:
> > > > We are trying to use
As was done with Armada XP, add node labels to Armada 38x common and SoC
specific nodes to make them easier to reference in board device trees.
Signed-off-by: Chris Packham
---
arch/arm/boot/dts/armada-385.dtsi | 20 +---
arch/arm/boot/dts/armada-388.dtsi | 9 -
arch/arm
Hi Linus:
This push fixes a bug in CBC/CTR on ARM64 that breaks chaining
as well as a bug in the core API that causes registration failures
when a driver unloads and then reloads an algorithm.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
Ard Bies
* Nicolas Iooss wrote:
> Adding such an attribute helps to detect errors in the format string at
> build time. After doing this, the compiler complains about such issues:
>
> arch/x86/tools/relocs.c:460:5: error: format specifies type 'int'
> but the argument has type 'Elf64_Xword' (aka
On Tue 31-01-17 10:27:53, Ross Zwisler wrote:
> On Tue, Dec 27, 2016 at 7:16 AM, Sergey Senozhatsky
> wrote:
> > Use printk_safe per-CPU buffers in printk recursion-prone blocks:
> > -- around logbuf_lock protected sections in vprintk_emit() and
> >console_unlock()
> > -- around down_trylock_c
On 27 January 2017 at 10:52, Will Deacon wrote:
> On Fri, Jan 27, 2017 at 10:43:16AM +, Ard Biesheuvel wrote:
>> On 27 January 2017 at 10:40, Matthias Brugger wrote:
>> > Older compilers may not be able to detect the crc32 extended cpu type.
>>
>> What do you mean 'detect'? Could you describe
Hello,
> Fixes a regression triggered by a change in the layout of
> struct iio_chan_spec, but the real bug is in the driver which assumed
> a specific structure layout in the first place.
I don't think that this is a proper fix
maybe the driver is unique in that it uses mask_separate for INFO_S
On 2017-02-01 10:10, Peter Meerwald-Stadler wrote:
> Hello,
>
>> Fixes a regression triggered by a change in the layout of
>> struct iio_chan_spec, but the real bug is in the driver which assumed
>> a specific structure layout in the first place.
>
> I don't think that this is a proper fix
>
> m
On Wed, Feb 01, 2017 at 01:01:24PM +0530, Anshuman Khandual wrote:
> On 01/31/2017 09:30 PM, Mel Gorman wrote:
> > On Tue, Jan 31, 2017 at 07:52:37PM +0530, Anshuman Khandual wrote:
> >> At present, top_cpuset.mems_allowed is same as node_states[N_MEMORY] and it
> >> cannot be changed at the runtim
On Tue, Jan 31, 2017 at 05:54:52PM -0800, Steve Longerbeam wrote:
> On 01/31/2017 04:23 PM, Russell King - ARM Linux wrote:
> First, thank you for the explanation, it clears up a lot.
>
> But of_parse_subdev() is used to parse the OF graph starting
> from the CSI ports, to discover all the nodes t
On Wed, Feb 1, 2017 at 9:46 AM, Hoegeun Kwon wrote:
> The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected
> using MIPI-DSI interfaces.
>
> Signed-off-by: Donghwa Lee
> Signed-off-by: Hyungwon Hwang
> Signed-off-by: Hoegeun Kwon
> Reviewed-by: Andrzej Hajda
> Acked-by: Rob Herring
>
On 01/02/17 04:20, Archit Taneja wrote:
>
>
> On 01/31/2017 11:24 PM, Rob Herring wrote:
>> A few bindings snuck into bindings/video/bridge since consolidating
>> everything under bindings/display/bridge/. Move them to the correct
>> spot.
>>
>> Cc: Andrzej Hajda
>> Cc: Archit Taneja
>> Cc: E
On Tue, Jan 31, 2017 at 09:55:08PM +0100, Fabian Frederick wrote:
> Once again it's just about readability:
I feel APIs should be about common use-cases, not about sporadic weird cases.
> "add -1 unless value is zero" looks more complex in code than "dec not zero"
> but maybe it's just a matter o
Hi Liviu,
Am Dienstag, den 31.01.2017, 18:58 + schrieb Liviu Dudau:
> Commit 25d3db7600b8 ("mm, fs: reduce fault, page_mkwrite, and pfn_mkwrite
> to take only vmf") updated the etnaviv_gem_fault() function signature
> without updating the header file with the declaration.
>
There is already a
Hi,
these three patches tried to address a simple OOM victim runaways when
the oom victim can deplete the memory reserve completely. Tetsuo was able
to trigger the depletion in the write(2) path and I believe the similar
is possible for the read part. Vmalloc would be a bit harder but still
not imp
Hi All,
On Tuesday 24 January 2017 11:06 AM, Lokesh Vutla wrote:
> commit 4a9d4b024a31 ("switch fput to task_work_add") implements a
> schedule_work() for completing fput(), but did not guarantee calling
> __fput() after unpacking initramfs. Because of this, there is a
> possibility that during bo
From: Michal Hocko
Tetsuo has noticed that an OOM stress test which performs large write
requests can cause the full memory reserves depletion. He has tracked
this down to the following path
__alloc_pages_nodemask+0x436/0x4d0
alloc_pages_current+0x97/0x1b0
__page_cache_all
From: Michal Hocko
do_generic_file_read can be told to perform a large request from
userspace. If the system is under OOM and the reading task is the OOM
victim then it has an access to memory reserves and finishing the full
request can lead to the full memory depletion which is dangerous. Make
s
From: Michal Hocko
__vmalloc_area_node allocates pages to cover the requested vmalloc size.
This can be a lot of memory. If the current task is killed by the OOM
killer, and thus has an unlimited access to memory reserves, it can
consume all the memory theoretically. Fix this by checking for
fata
Hi,
these three patches tried to address a simple OOM victim runaways when
the oom victim can deplete the memory reserve completely. Tetsuo was able
to trigger the depletion in the write(2) path and I believe the similar
is possible for the read part. Vmalloc would be a bit harder but still
not imp
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
On Tue, 2017-01-31 at 19:37 +0100, Borislav Petkov wrote:
> Bah. That's wrong. Delta patch below:
> >
> > --- a/arch/x86/kernel/cpu/mcheck/mce.c
> > +++ b/arch/x86/kernel/cpu/mcheck/mce.c
> > @@ -1782,7 +1782,7 @@ static void mce_start_timer(struct timer
> > return;
> >
> > this_
On 2017-01-30 Michal Hocko wrote:
> On Sun 29-01-17 16:50:03, Trevor Cordes wrote:
> > On 2017-01-25 Michal Hocko wrote:
> > > On Wed 25-01-17 04:02:46, Trevor Cordes wrote:
> > > > OK, I patched & compiled mhocko's git tree from the other day
> > > > 4.9.0+. (To confirm, weird, but mhocko's gi
> >> Fixes a regression triggered by a change in the layout of
> >> struct iio_chan_spec, but the real bug is in the driver which assumed
> >> a specific structure layout in the first place.
> > what do you mean by 'driver which assumed a specific structure'?
>
> Look again, the two bits are not
On Tue, 2017-01-31 at 17:26 -0800, Steve Longerbeam wrote:
[...]
> > # Set pad formats
> > media-ctl --set-v4l2 "'tc358743 1-000f':0[fmt:UYVY/1920x1080]"
> > media-ctl --set-v4l2 "'imx6-mipi-csi2':1[fmt:UYVY2X8/1920x1080]"
> > media-ctl --set-v4l2 "'ipu1_csi0_mux':2[fmt:UYVY2X8/1920x1080]"
> > medi
Hi Shaohua,
the code your patching has changed a lot in Jens' tree, so I think
you'll have to respin it. But the idea looks fine.
Am Dienstag, 31. Januar 2017, 15:43:12 CET schrieb Alexander Kochetkov:
> Make all properties description in form '"rockchip,-timer",
> "rockchip,rk3288-timer"' for all chips found in linux kernel.
>
> Suggested-by: Heiko Stübner
> Signed-off-by: Alexander Kochetkov
> Acked-by: Rob Herring
loo
Am Dienstag, 31. Januar 2017, 15:43:13 CET schrieb Alexander Kochetkov:
> Property set to '"rockchip,rk3228-timer", "rockchip,rk3288-timer"'
> to match devicetree bindings.
>
> Signed-off-by: Alexander Kochetkov
> Suggested-by: Heiko Stübner
depending on who is picking that up, they can add my
> + mask = pci_irq_get_affinity(to_pci_dev(dev->dev), i);
> + if (mask) {
> + node = cpu_to_node(cpumask_first(mask));
> + node = local_memory_node(node);
> + }
Can you move this to a PCI-layer helper, e.g. something like:
On 1 February 2017 at 09:33, Pali Rohár wrote:
> On Tuesday 31 January 2017 07:59:18 Tony Lindgren wrote:
>> * Kalle Valo [170130 22:36]:
[...]
>> > * before distro updates linux-firmware create yours own deb/rpm/whatever
>> > package "wl1251-firmware" which installs your flavor of nvs file (or
On Wed, Feb 01, 2017 at 10:06:25AM +0100, Jan Kara wrote:
> Clearly scheduler code (update_load_avg) calls WARN_ON from scheduler while
> holding rq_lock which has been always forbidden. Sergey and Petr were doing
> some work to prevent similar deadlocks but I'm not sure how far they
> went...
Its
Am Dienstag, den 31.01.2017, 18:56 + schrieb Liviu Dudau:
> etnaviv_gem.h header gets included twice. Remove duplicate.
>
> Signed-off-by: Liviu Dudau
Thanks, applied to my tree.
> ---
> drivers/gpu/drm/etnaviv/etnaviv_drv.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/
Hi Dave,
here's a pull request to 4.11, more details in the signed tag below.
I forgot to mention in the tag that this includes one small change to
include/linux/soc/qcom/smem_state.h which was acked by Andy Gross in
commit 6c0b2e833f14. It was needed to fix a build problem with wcn36xx
using the
On 2017-02-01 10:31, Peter Meerwald-Stadler wrote:
>
Fixes a regression triggered by a change in the layout of
struct iio_chan_spec, but the real bug is in the driver which assumed
a specific structure layout in the first place.
>
>>> what do you mean by 'driver which assumed a spe
On 1 February 2017 at 09:07, Ard Biesheuvel wrote:
> On 27 January 2017 at 10:52, Will Deacon wrote:
>> On Fri, Jan 27, 2017 at 10:43:16AM +, Ard Biesheuvel wrote:
>>> On 27 January 2017 at 10:40, Matthias Brugger wrote:
>>> > Older compilers may not be able to detect the crc32 extended cpu
Am Dienstag, 31. Januar 2017, 15:43:15 CET schrieb Alexander Kochetkov:
> The patch add two timers to all rk3188 based boards.
>
> The first timer is from alive subsystem and it act as a backup
> for the local timers at sleep time. It act the same as other
> SoC rockchip timers already present in
Commit-ID: fff4b87e594ad3d2e4f51e8d3d86a6f9d3d8b654
Gitweb: http://git.kernel.org/tip/fff4b87e594ad3d2e4f51e8d3d86a6f9d3d8b654
Author: Thomas Gleixner
AuthorDate: Tue, 31 Jan 2017 23:58:40 +0100
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:37:27 +0100
perf/x86/intel/uncore: Ma
Commit-ID: dd86e373e09fb16b83e8adf5c48c421a4ca76468
Gitweb: http://git.kernel.org/tip/dd86e373e09fb16b83e8adf5c48c421a4ca76468
Author: Thomas Gleixner
AuthorDate: Tue, 31 Jan 2017 23:58:38 +0100
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:37:27 +0100
perf/x86/intel/rapl: Make
On 01/30/2017 10:35 PM, Jani Nikula wrote:
On Sat, 28 Jan 2017, Peter Senna Tschudin wrote:
On Thu, Jan 05, 2017 at 01:18:47PM +0530, Archit Taneja wrote:
Hi Archit,
Thank you for the comments!
[...]
+ total_size = (block[EDID_EXT_BLOCK_CNT] + 1) * EDID_LENGTH;
+ if (total_size
Commit-ID: 2bd79f30eea1a7c3082c930a91370bb68435b86d
Gitweb: http://git.kernel.org/tip/2bd79f30eea1a7c3082c930a91370bb68435b86d
Author: Lukas Wunner
AuthorDate: Tue, 31 Jan 2017 13:21:33 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:42 +0100
efi: Deduplicate efi_file_si
Commit-ID: db4545d9a7881db0a7e18599e6cd1adbcb93db33
Gitweb: http://git.kernel.org/tip/db4545d9a7881db0a7e18599e6cd1adbcb93db33
Author: Lukas Wunner
AuthorDate: Tue, 31 Jan 2017 13:21:34 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:43 +0100
x86/efi: Deduplicate efi_cha
Commit-ID: 1aa6cfd33df492939b0be15ebdbcff1f8ae5ddb6
Gitweb: http://git.kernel.org/tip/1aa6cfd33df492939b0be15ebdbcff1f8ae5ddb6
Author: Thomas Gleixner
AuthorDate: Tue, 31 Jan 2017 23:58:39 +0100
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:37:27 +0100
perf/x86/intel/uncore: Cl
On Wed, Feb 01, 2017 at 10:26:08AM +0100, Lucas Stach wrote:
> Hi Liviu,
>
> Am Dienstag, den 31.01.2017, 18:58 + schrieb Liviu Dudau:
> > Commit 25d3db7600b8 ("mm, fs: reduce fault, page_mkwrite, and pfn_mkwrite
> > to take only vmf") updated the etnaviv_gem_fault() function signature
> > wit
Commit-ID: 3a6b6c6fb23667fa383053bd5259aabc96468571
Gitweb: http://git.kernel.org/tip/3a6b6c6fb23667fa383053bd5259aabc96468571
Author: Sai Praneeth
AuthorDate: Tue, 31 Jan 2017 13:21:35 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:43 +0100
efi: Make EFI_MEMORY_ATTRIBU
On Wed, Feb 01, 2017 at 08:59:24AM +0100, Michal Hocko wrote:
> On Wed 01-02-17 15:48:21, Minchan Kim wrote:
> > Hi Yisheng,
> >
> > On Tue, Jan 31, 2017 at 09:06:18PM +0800, ys...@foxmail.com wrote:
> > > From: Yisheng Xie
> > >
> > > This patch changes the return type of isolate_movable_page()
Commit-ID: a19ebf59e20880c87dd49b6336476307559ac5ba
Gitweb: http://git.kernel.org/tip/a19ebf59e20880c87dd49b6336476307559ac5ba
Author: Sai Praneeth
AuthorDate: Tue, 31 Jan 2017 13:21:36 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:44 +0100
efi: Introduce the EFI_MEM_A
Commit-ID: 18141e89a76c58101860486fd9cc0999da2eed43
Gitweb: http://git.kernel.org/tip/18141e89a76c58101860486fd9cc0999da2eed43
Author: Sai Praneeth
AuthorDate: Tue, 31 Jan 2017 13:21:37 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:44 +0100
x86/efi: Add support for EFI
Commit-ID: c4c39c70c5fef43655019236bec8ba5e7273b868
Gitweb: http://git.kernel.org/tip/c4c39c70c5fef43655019236bec8ba5e7273b868
Author: Ard Biesheuvel
AuthorDate: Tue, 31 Jan 2017 13:21:39 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:45 +0100
efi: Use typed function po
Commit-ID: e66880808960322d8126f878d7fe315a3f1ada74
Gitweb: http://git.kernel.org/tip/e66880808960322d8126f878d7fe315a3f1ada74
Author: Colin Ian King
AuthorDate: Tue, 31 Jan 2017 13:21:38 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:45 +0100
efi/esrt: Fix typo in pr_e
Commit-ID: 7b0a911478c74ca02581d496f732c10e811e894f
Gitweb: http://git.kernel.org/tip/7b0a911478c74ca02581d496f732c10e811e894f
Author: Dave Young
AuthorDate: Tue, 31 Jan 2017 13:21:40 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:46 +0100
efi/x86: Move the EFI BGRT ini
Am Dienstag, 31. Januar 2017, 15:43:16 CET schrieb Alexander Kochetkov:
> The clocksource and the sched_clock provided by the arm_global_timer
> are quite unstable because their rates depend on the cpu frequency.
>
> On the other side, the arm_global_timer has a higher rating than the
> rockchip_t
Commit-ID: 696204faa6e8a318320ebb49d9fa69bc8275644d
Gitweb: http://git.kernel.org/tip/696204faa6e8a318320ebb49d9fa69bc8275644d
Author: Ard Biesheuvel
AuthorDate: Tue, 31 Jan 2017 13:21:42 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:47 +0100
efi/libstub: Preserve .deb
Commit-ID: 22c091d02a5422d2825a4fb1af71e5a62f9e4d0f
Gitweb: http://git.kernel.org/tip/22c091d02a5422d2825a4fb1af71e5a62f9e4d0f
Author: Dave Young
AuthorDate: Tue, 31 Jan 2017 13:21:41 +
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 08:45:46 +0100
efi/x86: Add debug code to pri
Commit-ID: 93825f2ec736f30e034ab7c9d56b42849c5b00da
Gitweb: http://git.kernel.org/tip/93825f2ec736f30e034ab7c9d56b42849c5b00da
Author: Frederic Weisbecker
AuthorDate: Tue, 31 Jan 2017 04:09:16 +0100
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 09:13:45 +0100
jiffies: Reuse TICK_N
A test-build of e820.o with -Wswitch-enum shows the following warnings:
arch/x86/kernel/e820.c: In function ‘e820_type_to_string’:
arch/x86/kernel/e820.c:965:2: warning: enumeration value ‘E820_TYPE_RESERVED’
not handled in switch [-Wswitch-enum]
switch (entry->type) {
^
arch/x86/k
This is a quick update to the original series, mostly to address Linus's
feedback.
The full tree can be found at:
git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot
Thanks,
Ingo
>
Borislav Petkov (1):
x86/boot: Fix pr_debug() API braindamage
Ingo Mol
From: Borislav Petkov
What looked like a straightforward conversion from printk(KERN_DEBUG, ...)
to pr_debug() broke the boot log output:
DMI:/M57SLI-S4, BIOS FF 01/24/2008
-e820: update [mem 0x-0x0fff] usable ==> reserved
-e820: remove [mem 0x000a-0x000f] usable
+us
Commit-ID: 07e5f5e353aaa61696c8353d87050994a0c4648a
Gitweb: http://git.kernel.org/tip/07e5f5e353aaa61696c8353d87050994a0c4648a
Author: Frederic Weisbecker
AuthorDate: Tue, 31 Jan 2017 04:09:17 +0100
Committer: Ingo Molnar
CommitDate: Wed, 1 Feb 2017 09:13:45 +0100
time: Introduce jiffi
1 - 100 of 931 matches
Mail list logo
