From: Brian Norris
These error messages don't give much information about what went wrong.
It would be nice, for one, to see what invalid temperature was being
requested when conversion fails. It's also good to return an error when
we can't handle a conversion properly.
While we're at it, fix th
There are five patches posted for upstream.
89267b5 thermal: rockchip: improve conversion error messages
a0b5649 thermal: rockchip: don't pass table structs by value
bceed92 thermal: rockchip: fixes invalid temperature case
30be6d0 thermal: rockchip: optimize the conversion table
35636e9 thermal: r
In some cases, some sensors didn't need the trip points, the
set_trips will pass {-INT_MAX, INT_MAX} to trigger tsadc alarm in the end,
ignore this case and disable the high temperature interrupt.
Signed-off-by: Caesar Wang
Reviewed-by: Brian Norris
---
Changes in v4: None
Changes in v3:
- chan
In order to support the valid temperature can conver to analog value.
The rockchip thermal driver has not supported the all valid temperature
to convert the analog value. (e.g.: 61C, 62C, 63C)
For example:
In some cases, we need adjust the trip point.
$cd /sys/class/thermal/thermal_zone*
$echo
Hello all,
I think should be use to "WARN_ON" and checkpatch script give to error, I fixed
and I think should don't use "BUG_ON".
Regards,
Signed-off-by: Ozgur Karatas
---
drivers/net/ethernet/mellanox/mlx4/icm.c | 4 ++--
diff --git a/drivers/net/ethernet/mellanox/mlx4/icm.c
b/drivers/net/e
The temp_to_code function will return 0 when we set the temperature to a
invalid value (e.g. 61C, 62C, 63C), that's unpractical. This patch
will prevent this case happening. That will return the max analog value to
indicate the temperature is invalid or over table temperature range.
Signed-off
Init field must be cleared in driver probe as this structure is not dinamically
allocated. If not, wrong flags can be passed to core.
Signed-off-by: Jose Abreu
Cc: Carlos Palminha
Cc: Stephen Boyd
Cc: Michael Turquette
Cc: linux-...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
driver
Hello.
On 12/12/16 11:58, Ozgur Karatas wrote:
Hello all,
I think should be use to "WARN_ON" and checkpatch script give to error, I fixed and I
think should don't use "BUG_ON".
Regards,
Signed-off-by: Ozgur Karatas
I pointed you already before to the Documentation how to prepare a
commit
Hi Linus,
Please pull LED updates for 4.10 merge cycle.
>From the things that need to be highlighted there are:
- userspace LED class driver - it can be useful for testing triggers
and can also be used to implement virtual LEDs,
- LED class driver for NIC78bx device,
- LED core fixes for preven
Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it
only gives VGA resolution on screen. Use the same chipset as nv134
then it shows FullHD. This commit copies fields from nv134_chipset
to nv136_chipset for GTX 1060.
Signed-off-by: Chris Chiu
---
drivers/gpu/drm/nouveau/nvkm/engi
The Linux man-pages maintainer proudly announces:
man-pages-4.09 - man pages for Linux
This release resulted from patches, bug reports, reviews, and
comments from 44 contributors. This is one of the more substantial
releases in recent times, with more than 500 commits changing
around 190 p
Hi Rob,
On 2016/12/10 6:35, Rob Herring wrote:
> On Mon, Dec 05, 2016 at 09:27:58PM +0800, Dongpo Li wrote:
>> The "hix5hd2" is SoC name, add the generic ethernet driver name.
>> The "hisi-gemac-v1" is the basic version and "hisi-gemac-v2" adds
>> the SG/TXCSUM/TSO/UFO features.
>>
>> Signed-off-b
On Sun, Dec 11, 2016 at 03:50:55AM +0300, Alexander Popov wrote:
> Introduce kaslr_offset() similarly to x86_64 for fixing kcov.
>
> Signed-off-by: Alexander Popov
> ---
> arch/arm64/include/asm/setup.h | 19 +++
> arch/arm64/include/uapi/asm/setup.h | 4 ++--
> arch/arm64/
Dear Stefan;
I'm reading to Documentation/SubmittingPatches and I still apologized for
misrepresentations my patches.
I will add a next time good commit message and commit subjects.
Sorry,
Regards
Ozgur Karatas
12.12.2016, 13:20, "Stefan Schmidt" :
> Hello.
>
> On 12/12/16 11:58, Ozgur Karat
If several parallel bq24735 chargers have their ac-detect gpios wired
together (or if only one of the parallel bq24735 chargers have its
ac-detect pin wired to a gpio, and the others are assumed to react the
same), then all driver instances need to check the same gpio. But the
gpio subsystem does n
On 2016/10/17 20:07, Pan Wen wrote:
> Add dts files for Hi3516CV300 demo board.
>
> Signed-off-by: Pan Wen
> ---
Could you help to review this patch, please?
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/hi3516cv300-demb.dts | 148
> arch/arm/boot/dts/hi35
Hi Sakari
On 12/7/2016 11:01 PM, Sakari Ailus wrote:
> Hi Ramiro,
>
> On Mon, Dec 05, 2016 at 05:36:34PM +, Ramiro Oliveira wrote:
>> Add support for OV5647 sensor.
>>
>> Modes supported:
>> - 640x480 RAW 8
>>
>> Signed-off-by: Ramiro Oliveira
>> ---
>> MAINTAINERS| 7 +
>
Hi Sakari,
Thank you for the feedback.
On 12/7/2016 10:33 PM, Sakari Ailus wrote:
> Hi Ramiro,
>
> Thank you for the patch.
>
> On Mon, Dec 05, 2016 at 05:36:33PM +, Ramiro Oliveira wrote:
>> Add device tree documentation.
>>
>> Signed-off-by: Ramiro Oliveira
>> ---
>> .../devicetree/bind
+Cc folks who may know about timer stuff on epoll.
Dmitry Banschikov wrote:
> Hi!
>
> I have a problem caused by inaccurate timeouts in epoll_wait(2).
> Here are some parts of strace -tt output:
Which kernel version are you using?
> 22578 09:33:46.959791 epoll_wait(5,
> 22578 09:33:50.010794
On 12/12/2016 09:26 PM, Chris Chiu wrote:
> Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it
> only gives VGA resolution on screen. Use the same chipset as nv134
> then it shows FullHD. This commit copies fields from nv134_chipset
> to nv136_chipset for GTX 1060.
I have one of th
On Fri, Dec 09, 2016 at 02:59:00PM +0100, Peter Zijlstra wrote:
> On Wed, Dec 07, 2016 at 07:34:55PM +0100, Peter Zijlstra wrote:
>
> > @@ -2352,6 +2357,28 @@ perf_install_in_context(struct perf_event_context
> > *ctx,
> > return;
> > }
> > raw_spin_unlock_irq(&ctx->lock);
> >
Rafał Miłecki writes:
> On 12 December 2016 at 09:12, Johannes Berg wrote:
>> On Sat, 2016-12-10 at 16:54 +0100, Rafał Miłecki wrote:
>>> In brcmfmac we use request_firmware_nowait and if fetching firmware
>>> with NVRAM variables fails then we try to fallback to the platform
>>> one (see brcmf_
Hi Ramiro,
On Mon, Dec 12, 2016 at 11:39:31AM +, Ramiro Oliveira wrote:
> Hi Sakari,
>
> Thank you for the feedback.
>
> On 12/7/2016 10:33 PM, Sakari Ailus wrote:
> > Hi Ramiro,
> >
> > Thank you for the patch.
> >
> > On Mon, Dec 05, 2016 at 05:36:33PM +, Ramiro Oliveira wrote:
> >>
Hi Ramiro,
On Mon, Dec 12, 2016 at 11:39:13AM +, Ramiro Oliveira wrote:
> Hi Sakari
>
> On 12/7/2016 11:01 PM, Sakari Ailus wrote:
> > Hi Ramiro,
> >
> > On Mon, Dec 05, 2016 at 05:36:34PM +, Ramiro Oliveira wrote:
> >> Add support for OV5647 sensor.
> >>
> >> Modes supported:
> >> - 64
Adding support to avoid regmap bulk write for the
devices which are not supported register bulk write.
Max77620 RTC device does not support register bulk write
so disabling regmap bulk write for max77620 rtc device
and enabling only for max77683.
Signed-off-by: Venkat Reddy Talla
---
drivers/rtc
On 9 December 2016 at 14:52, Robert Richter wrote:
> On 09.12.16 21:15:12, Yisheng Xie wrote:
>> For invalid pages, their zone and node information is not initialized, and it
>> do have risk to trigger the BUG_ON, so I have a silly question,
>> why not just change the BUG_ON:
>
> We need to get th
Hi,
>>> Do you actually hit an issue with image size? In what context?
>>> Do you use inline/outline instrumentation? Does switching to the other
>>> option help?
>>
>> Memory access with KASAN enabled Image has overhead in terms of cpu
>> execution.
>> Sometimes we are not able to reproduce race
Hi,
>A PC24 relocation has a range of +/-32MB. This means that where-ever
>the module is placed, it must be capable of reaching any function
>within the kernel text, which may itself be quite large (eg, 8MB, or
>possibly larger). The module area exists to allow modules to be
>located in an area
Hi,
On 12/09/2016 10:40 PM, Shuah Khan wrote:
> Hi Krzysztof,
>
> Thanks for getting to this so quickly. Couple of comments below:
>
> On 12/09/2016 10:15 AM, Krzysztof Opasiak wrote:
>> Add some simple script which creates a USB gadget using ConfigFS
>> and then exports it using vUDC.
>>
>> Th
This patch series builds atop:
ec988ad78ed6d184a7f4ca6b8e962b0e8f1de461 ("phy: Don't increment MDIO bus
refcount unless it's a different owner")
I have checked all the hisilicon ethernet driver and found only two drivers
need to be fixed to make sure set dev->dev.parent before PHY connect.
Dongpo
The hisi_femac driver calls into PHYLIB which now checks for
net_device->dev.parent, so make sure we do set it before calling into
any MDIO/PHYLIB related function.
Fixes: ec988ad78ed6 ("phy: Don't increment MDIO bus refcount unless it's a
different owner")
Signed-off-by: Dongpo Li
---
drivers/
The hip04 driver calls into PHYLIB which now checks for
net_device->dev.parent, so make sure we do set it before calling into
any MDIO/PHYLIB related function.
Fixes: ec988ad78ed6 ("phy: Don't increment MDIO bus refcount unless it's a
different owner")
Signed-off-by: Dongpo Li
---
drivers/net/e
Hi,
On Saturday, December 10, 2016 10:46:23 AM Robert Jarzmik wrote:
> Bartlomiej Zolnierkiewicz writes:
>
> > Replace [lpd270,lubbock,mainstone,pxa255-idp]_defconfig-s with
> > a Makefile target using merge_config.
> >
> > The patch was verified with doing:
> >
> > $ make [lpd270,...]_defc
Hi Sakari
On 12/12/2016 11:49 AM, Sakari Ailus wrote:
> Hi Ramiro,
>
> On Mon, Dec 12, 2016 at 11:39:31AM +, Ramiro Oliveira wrote:
>> Hi Sakari,
>>
>> Thank you for the feedback.
>>
>> On 12/7/2016 10:33 PM, Sakari Ailus wrote:
>>> Hi Ramiro,
>>>
>>> Thank you for the patch.
>>>
>>> On Mon,
Hi Ramiro,
On Mon, Dec 12, 2016 at 12:15:04PM +, Ramiro Oliveira wrote:
> Hi Sakari
>
> On 12/12/2016 11:49 AM, Sakari Ailus wrote:
> > Hi Ramiro,
> >
> > On Mon, Dec 12, 2016 at 11:39:31AM +, Ramiro Oliveira wrote:
> >> Hi Sakari,
> >>
> >> Thank you for the feedback.
> >>
> >> On 12/7/
On Mon, Dec 12, 2016 at 10:12:53AM +0100, Paolo Bonzini wrote:
> Introduce a new mutex to avoid an AB-BA deadlock between kvm->lock and
> vcpu->mutex. Protect accesses in kvm_hv_setup_tsc_page too, as suggested
> by Roman.
>
> Reported-by: Dmitry Vyukov
> Cc: Roman Kagan
> Signed-off-by: Paolo
In preparation to using a generic API in the DRM core for continuous CRC
generation, move the related code out of i915_debugfs.c into a new file.
Eventually, only the Intel-specific code will remain in this new file.
v2: Rebased.
v6: Rebased.
v7: Fix whitespace issue.
v9: Have intel_display_cr
On 2016-12-10 19:21, Jonathan Cameron wrote:
> On 06/12/16 09:18, Peter Rosin wrote:
>> On 2016-12-06 00:26, Rob Herring wrote:
>>> On Wed, Nov 30, 2016 at 09:16:58AM +0100, Peter Rosin wrote:
Signed-off-by: Peter Rosin
---
.../bindings/iio/multiplexer/iio-mux.txt | 40
>
On Mon, Sep 05, 2016 at 03:22:45PM +0100, Juri Lelli wrote:
[...]
> +===
> +5 - References
> +===
> +
> +[1] ARM Linux Kernel documentation - CPUs bindings
> +Documentation/devicetree/bindings/arm/cpus.txt
> diff
On Mon, Dec 12, 2016 at 12:58:59PM +0200, Ozgur Karatas wrote:
> Hello all,
> I think should be use to "WARN_ON" and checkpatch script give to error, I
> fixed and I think should don't use "BUG_ON".
> Regards,
>
> Signed-off-by: Ozgur Karatas
NAK, Leon Romanovsky
If we put aside commit messag
On Mon, Dec 12, 2016 at 11:46:40AM +, Will Deacon wrote:
> > @@ -2331,13 +2330,36 @@ perf_install_in_context(struct perf_event_context
> > *ctx,
> > /*
> > * Installing events is tricky because we cannot rely on ctx->is_active
> > * to be set in case this is the nr_events 0 -> 1
ROG means ASUS "Republic of Gamers" laptops. The input device info
also represents itself as "ASASTeK COMPUTER INC. ROG MacroKey". It
uses special HID_USAGE code for function keys. This commit remap the
special code to standard keycode for function keys handling. It's
verified on GL553VD/VE, GL753V
-u32/20161212-001614
base: git://linux-nfs.org/~bfields/linux.git nfsd-next
config: x86_64-kexec (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by
Hi,
On Monday, July 18, 2016 08:15:08 PM Sekhar Nori wrote:
> On Friday 15 July 2016 08:45 PM, Kevin Hilman wrote:
> > Arnd Bergmann writes:
> >
> >> On Wednesday, July 13, 2016 12:59:23 PM CEST Bartlomiej Zolnierkiewicz
> >> wrote:
> >>>
> >>> On Friday, July 08, 2016 10:23:48 PM Arnd Bergman
On Mon, Dec 12, 2016 at 11:22:30AM +, Vaneet Narang wrote:
> Hi,
>
> >A PC24 relocation has a range of +/-32MB. This means that where-ever
> >the module is placed, it must be capable of reaching any function
> >within the kernel text, which may itself be quite large (eg, 8MB, or
> >possibly l
On 12.12.2016 06:00, Thang Q. Nguyen wrote:
On Sat, Dec 10, 2016 at 4:36 AM, Rob Herring wrote:
On Sun, Dec 04, 2016 at 07:42:01PM +0700, Thang Q. Nguyen wrote:
From: Thang Nguyen
As per USB 2.0 link power management addendum ECN, table 1-2, page 4,
device or host initiated via resume signal
Dmitry
On 12/11/2016 12:59 AM, Dmitry Torokhov wrote:
> We were accidentally initializing haptics->rated_voltage twice, and did not
> initialize overdrive voltage.
>
> Signed-off-by: Dmitry Torokhov
> ---
> drivers/input/misc/drv260x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
Dear Romanovsky;
I'm trying to learn english and I apologize for my mistake words and phrases.
So, I think the code when call to "sg_set_buf" and next time set memory and
buffer. For example, isn't to call "WARN_ON" function, get a error to implicit
declaration, right?
Because, you will use to
At maximum CPU frequency of 300 MHz the maximum pixel clock frequency
is 37.5 MHz[1]. We must filter out any mode for which the calculated
pixel clock rate would exceed this value.
Specify the max-pixelclock property for the display node for
da850-lcdk.
[1]
http://processors.wiki.ti.com/index.ph
The tilcdc node name is 'display' as per the ePAPR 1.1 recommendation.
The label is also 'display', but change it to 'lcdc' to make it clear
what the underlying hardware is.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/boot/dts/da850.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Add the vga-bridge node to the board DT together with corresponding
ports and vga connector. This allows to retrieve the edid info from
the display automatically.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Laurent Pinchart
---
arch/arm/boot/dts/da850-lcdk.dts | 67 +
THS8135 is a configurable video DAC. Add DT bindings for this chip.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Laurent Pinchart
---
.../bindings/display/bridge/ti,ths8135.txt | 52 ++
1 file changed, 52 insertions(+)
create mode 100644
Documentation/devicetree
This series contains the last DT changes required for LCDC support
on da850-lcdk. The first one adds the dumb-vga-dac nodes, the second
limits the maximum pixel clock rate.
v1 -> v2:
- drop patch 3/3 (already merged)
- use max-pixelclock instead of max-bandwidth for display mode limiting
v2 -> v3
THS8135 is a configurable video DAC, but no configuration is actually
necessary to make it work.
For now use the dumb-vga-dac driver to support it.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/dumb-vga-dac.c | 1 +
1 file changed, 1 insertion(+)
Hi Sakari
On 12/12/2016 12:19 PM, Sakari Ailus wrote:
> Hi Ramiro,
>
> On Mon, Dec 12, 2016 at 12:15:04PM +, Ramiro Oliveira wrote:
>> Hi Sakari
>>
>> On 12/12/2016 11:49 AM, Sakari Ailus wrote:
>>> Hi Ramiro,
>>>
>>> On Mon, Dec 12, 2016 at 11:39:31AM +, Ramiro Oliveira wrote:
Hi Sa
On 2016-12-12 12:00, Peter Rosin wrote:
> If several parallel bq24735 chargers have their ac-detect gpios wired
> together (or if only one of the parallel bq24735 chargers have its
> ac-detect pin wired to a gpio, and the others are assumed to react the
> same), then all driver instances need to ch
Linus,
The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6:
Linux 4.9-rc5 (2016-11-13 10:32:32 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to f673b5b2a66332da5358def524dbfb33
Hi,
On Monday, December 12, 2016 05:14:45 PM Venkat Reddy Talla wrote:
> Adding support to avoid regmap bulk write for the
> devices which are not supported register bulk write.
What about register bulk reads done by the driver?
Do they also need a fixup?
> Max77620 RTC device does not support
Hi Ying,
On 12 December 2016 at 06:43, kernel test robot
wrote:
> Greeting,
>
> FYI, we noticed a 149% regression of ftq.noise.50% due to commit:
>
>
> commit: 4e5160766fcc9f41bbd38bac11f92dce993644aa ("sched/fair: Propagate
> asynchrous detach")
> https://git.kernel.org/pub/scm/linux/kernel/git
On 12/12/16 12:40, Lorenzo Pieralisi wrote:
> On Mon, Sep 05, 2016 at 03:22:45PM +0100, Juri Lelli wrote:
>
> [...]
>
> > +===
> > +5 - References
> > +===
> > +
> > +[1] ARM Linux Kernel documentation - CPUs bindings
Hi,
On Saturday, December 10, 2016 11:51:11 AM Krzysztof Kozlowski wrote:
> The driver was checking for non-NULL address of struct's members:
> - s3c_audio_pdata->type (union),
> - s3c_audio_pdata->type.i2s (embedded struct).
>
> This is pointless as these will be always non-NULL. The 's3c_au
On Sun, Dec 04, 2016 at 11:57:07AM -0800, Omar Sandoval wrote:
> On Sun, Dec 04, 2016 at 12:51:53PM +0800, Pan Bian wrote:
> > In function btrfs_uuid_tree_iterate(), errno is assigned to variable ret
> > on errors. However, it directly returns 0. It may be better to return
> > ret. This patch also
Hi,
On Saturday, December 10, 2016 03:47:32 PM Krzysztof Kozlowski wrote:
> The list of retention registers (release_ret_regs field of struct
> exynos_pm_data and arrays with values) are not modified and can be made
> const to improve the const safeness.
>
> Signed-off-by: Krzysztof Kozlowski
Em Mon, Dec 12, 2016 at 11:35:39AM +0100, Jiri Olsa escreveu:
> Removing extra '--' prefix.
Please add a Fixes: tag in such cases, as this helps backporters to
figure out what affects packages they published, in this case I'm
adding:
Fixes: ad16511b0e40 ("perf mem: Add -U/-K (--all-user/--all-ker
On Mon, Dec 12, 2016 at 10:43:11AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Dec 12, 2016 at 11:35:39AM +0100, Jiri Olsa escreveu:
> > Removing extra '--' prefix.
>
> Please add a Fixes: tag in such cases, as this helps backporters to
> figure out what affects packages they published, in th
Hi,
I have 2 solutions(high level design) came to me, please see if they are
acceptable, or which one is acceptable. Also have some questions.
1. block guest access during host recovery
add new field error_recovering in struct vfio_pci_device to
indicate host recovery status. aer driver in
On Mon, Dec 12, 2016 at 2:43 PM, Dmitry Vyukov wrote:
>
> On Mon, Dec 12, 2016 at 12:12 PM, Vaneet Narang wrote:
>>
>> Hi,
>>
>> >>> Do you actually hit an issue with image size? In what context?
>> >>> Do you use inline/outline instrumentation? Does switching to the other
>> >>> option help?
>>
On 12/10, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > On 12/09, EunTaik Lee wrote:
> >>
> >> There is a use-after-free case with below call stack.
> >>
> >> pid_nr_ns+0x10/0x38
> >> cgroup_pidlist_start+0x144/0x400
> >> cgroup_seqfile_start+0x1c/0x24
> >> kernfs_seq_start+0x54/0x90
>
On 12/12/16 4:53 AM, Ozgur Karatas wrote:
>
> Hello,
>
> I have error to use uuid and I think the functions should be used when -i'm
> eye-catching- "(* uuid)".
> I tested it.
>
> Regards,
>
> Signed-off-by: Ozgur Karatas
NAK
This doesn't fix code style at all; there is no need and no
prece
On Sat 2016-12-10 12:10:22, Sergey Senozhatsky wrote:
> On (12/09/16 17:46), Petr Mladek wrote:
> > > -/*
> > > - * Safe printk() for NMI context. It uses a per-CPU buffer to
> > > - * store the message. NMIs are not nested, so there is always only
> > > - * one writer running. But the buffer might
Hey Linus!
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git
stable/for-linus-4.9
which has:
- Minor fixes (rate limiting), remove certain functions.
- Support for DMA_ATTR_SKIP_CPU_SYNC which is an optimization in the
DMA API
That is
Hi Bartlomiej,
On Monday 12 December 2016 06:15 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Monday, July 18, 2016 08:15:08 PM Sekhar Nori wrote:
>> On Friday 15 July 2016 08:45 PM, Kevin Hilman wrote:
>>> Arnd Bergmann writes:
>>>
On Wednesday, July 13, 2016 12:59:23 PM CEST Bartlo
There's no users that wants sync_global_pgd(.remove=1) sinc af2cf278ef4f
("x86/mm/hotplug: Don't remove PGD entries in remove_pagetable()").
Let's drop 'remove'.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/pgtable_64.h | 3 +--
arch/x86/mm/fault.c | 2 +-
arch/x86
v4l2_subdev_{core/video}_ops structures are stored in the
fields of the v4l2_subdev_ops structure which are of type const.
Also, v4l2_subdev_ops structure is passed to a function
having its argument of type const. As these structures are never
modified, so declare them as const.
Done using Coccinel
Removed trailing whitespace.
Signed-off-by: Manoj Sawai
---
drivers/staging/ks7010/ks7010_sdio.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ks7010/ks7010_sdio.h
b/drivers/staging/ks7010/ks7010_sdio.h
index 5820b5c9b684..0165994605ac 100644
--- a/drivers/
Fixed coding style error. Complex macro not inside parentheses.
Signed-off-by: Manoj Sawai
---
drivers/staging/ks7010/ks7010_sdio.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ks7010/ks7010_sdio.h
b/drivers/staging/ks7010/ks7010_sdio.h
index 0f5fd848e23d.
On Sun, Dec 11, 2016 at 01:08:33PM +1100, Balbir Singh wrote:
>
>
> On 11/12/16 04:17, Josh Poimboeuf wrote:
> > On Sat, Dec 10, 2016 at 04:46:17PM +1100, Balbir Singh wrote:
> >> On Thu, 2016-12-08 at 12:08 -0600, Josh Poimboeuf wrote:
> >>> Dusting the cobwebs off the consistency model again.
On Mon, Dec 12, 2016 at 10:53:38AM +0100, Rafał Miłecki wrote:
> On 12 December 2016 at 10:26, Arend Van Spriel
> wrote:
> > On 12-12-2016 9:32, Rafał Miłecki wrote:
> >> On 12 December 2016 at 09:12, Johannes Berg
> >> wrote:
> >>> On Sat, 2016-12-10 at 16:54 +0100, Rafał Miłecki wrote:
>
On (12/12/16 14:54), Petr Mladek wrote:
> On Sat 2016-12-10 12:10:22, Sergey Senozhatsky wrote:
> > On (12/09/16 17:46), Petr Mladek wrote:
> > > > -/*
> > > > - * Safe printk() for NMI context. It uses a per-CPU buffer to
> > > > - * store the message. NMIs are not nested, so there is always only
On Sat, Dec 10, 2016 at 04:54:41PM +0100, Rafał Miłecki wrote:
> So it would be nice to have version of request_firmware_nowait with
> FW_OPT_NO_WARN. If requesting firmware NVRAM fails *and* getting
> platform NVRAM fails, then I could to print error on my own.
> Does it make sense? Can you see a
On 12 December 2016 at 15:07, Luis R. Rodriguez wrote:
> On Mon, Dec 12, 2016 at 10:53:38AM +0100, Rafał Miłecki wrote:
>> On 12 December 2016 at 10:26, Arend Van Spriel
>> wrote:
>> > On 12-12-2016 9:32, Rafał Miłecki wrote:
>> >> On 12 December 2016 at 09:12, Johannes Berg
>> >> wrote:
>> >>>
On Mon, Dec 12, 2016 at 5:16 AM, Dongpo Li wrote:
> Hi Rob,
>
> On 2016/12/10 6:35, Rob Herring wrote:
>> On Mon, Dec 05, 2016 at 09:27:58PM +0800, Dongpo Li wrote:
>>> The "hix5hd2" is SoC name, add the generic ethernet driver name.
>>> The "hisi-gemac-v1" is the basic version and "hisi-gemac-v2"
On Thu, Dec 08, 2016 at 10:40:41AM -0800, Andy Lutomirski wrote:
> On Thu, Dec 8, 2016 at 8:21 AM, Kirill A. Shutemov
> wrote:
> > XXX: how to test this?
>
> tools/testing/selftests/x86/sigreturn_{32,64}
Hm. They fail on non-patched kernel with QEMU, but not KVM. :-/
I guess I'd need to fix QEMU
>
> In order to provide access to locality registers, this commits adds mapping of
> the head of the CRB registers, which are located right before the control
> area.
>
> Signed-off-by: Jarkko Sakkinen
> ---
> drivers/char/tpm/tpm_crb.c | 89 +
> -
>
On Fri, 09 Dec 2016 21:57:37 +0100,
Dmitry Torokhov wrote:
>
> Hi,
>
> Historically we did not trust PNP data regarding keyboard controllers on
> X86, but more and more boards get upset with us if they try to tell us that
> there is no keyboard controller and we still go and try to poke at where
When processing KVM_REQ_EVENT, apic_update_ppr is called which may set
KVM_REQ_EVENT again if the recalculated value of PPR becomes smaller
than the previous one. This results in cancelling the guest entry and
reiterating in vcpu_enter_guest.
However this is unnecessary because at this point KVM_R
Em Mon, Dec 12, 2016 at 11:35:42AM +0100, Jiri Olsa escreveu:
> Adding perf_evsel::ignore_missing_cpu_thread bool.
>
> When set true, it allows perf to ignore error of missing
> pid of perf event syscall.
>
> We remove missing thread id from the thread_map, so the
> rest of the processing like io
Em Mon, Dec 12, 2016 at 11:32:09AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Dec 12, 2016 at 11:35:42AM +0100, Jiri Olsa escreveu:
> > Adding perf_evsel::ignore_missing_cpu_thread bool.
> >
> > When set true, it allows perf to ignore error of missing
> > pid of perf event syscall.
> >
>
Hi Linus,
Please pull the below, highlights include:
_ This is my first pull request as the new OpenRISC architecture
maintainer. I hope I have things in order.
- Changes to MAINTAINER for openrisc
- Probably biggest actual change is the move to memblock from bootmem
- Plus several bug and
On Sun, Dec 11, 2016 at 12:35:32AM -0500, Nayna Jain wrote:
> Physical TPMs use Open Firmware Device Tree bindings that are similar
> to the IBM Power virtual TPM to support event log. However, these
> properties store the values in different endianness for Physical
> and Virtual TPM.
>
> This pat
On 12/12/2016 01:48 AM, Rasmus Villemoes wrote:
A bootloader may start the watchdog device before handing control to
the kernel - in that case, we should tell the kernel about it so the
watchdog framework can keep it alive until userspace opens
/dev/watchdog0.
Signed-off-by: Rasmus Villemoes
On Mon, Dec 12, 2016 at 4:01 AM, Benjamin Tissoires
wrote:
> On Dec 12 2016 or thereabouts, Jiri Kosina wrote:
>> Given the timing (merge window being open) and given then NACK given by
>> Rob, I've now unapplied the patches (the for-4.10/i2c-hid branch is now
>> obsolete, and has been superseded
Em Fri, Dec 09, 2016 at 09:51:09AM -0800, Joe Stringer escreveu:
> Commit f72179ef11db ("samples/bpf: Switch over to libbpf") added these
> two makefile changes that were unnecessary for switching samples to use
> libbpf. The extra make is already handled by the build dependency, and
> libbpf targe
-Platform-Driver/20161212-220228
config: alpha-allyesconfig (attached as .config)
compiler: alpha-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin
This was done to conform to the Lustre Coding Guidelines.
-Ben
On 12/10/16, 1:14 PM, "Greg Kroah-Hartman"
wrote:
>On Sat, Dec 10, 2016 at 01:05:59PM -0500, James Simmons wrote:
>> From: Ben Evans
>>
>> It was found if you sort the headers alphabetically
>> that it reduced patch conflicts. Thi
On Thu, Dec 08, 2016 at 01:25:37PM -0500, Jérémy Lefaure wrote:
> On Thu, 8 Dec 2016 13:50:11 +0300
> "Kirill A. Shutemov" wrote:
>
> > On Wed, Dec 07, 2016 at 11:38:33PM -0500, Jérémy Lefaure wrote:
> > > When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op
> > > stub. In such
On Mon, Dec 12, 2016 at 11:32:09AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Dec 12, 2016 at 11:35:42AM +0100, Jiri Olsa escreveu:
> > Adding perf_evsel::ignore_missing_cpu_thread bool.
> >
> > When set true, it allows perf to ignore error of missing
> > pid of perf event syscall.
> >
> >
> I really would prefer to move the thing to its own PMU.
The patch as below creates a new PMU to fix the issue.
Jirka, could you please try the patch on your machine?
Thanks,
Kan
---
>From 2de8b2eda6b54734e08a608b5fc8c367b94369d3 Mon Sep 17 00:00:00 2001
From: Kan Liang
Date: Mon, 12 De
On Fri, Dec 02, 2016 at 05:51:36PM -0800, Maxim Patlasov wrote:
> Problem statement: unprivileged user who has read-write access to more than
> one btrfs subvolume may easily consume all kernel memory (eventually
> triggering oom-killer).
>
> Reproducer (./mkrmdir below essentially loops over mkdi
On Fri, Dec 9, 2016 at 9:49 PM, Caesar Wang wrote:
> Look likes, the BOE panel FW didn't ack the DPCD600 signal from the host
> device, that will cause the panel hang on the startup display.
> The root cause we use the fast link mode during enter and exit the psr,
> this issue is gone if switching
601 - 700 of 757 matches
Mail list logo
