include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
arch/arm/mach-omap1/board-h2-mmc.c | 2 +-
arch/arm/mach-omap1/board-h2.c | 2 +-
arch/arm/mach-omap1/board-h3-mmc.c | 2 +-
It doesn't make sense to use include/linux/i2c for client drivers which may in
fact rather be hwmon or input or whatever devices. As a result, I want to
deprecate include/linux/i2c for good. This series moves the include files to a
better location, largely include/linux/platform_data because that
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
arch/x86/platform/intel-mid/device_libs/platform_tc35876x.c | 2 +-
drivers/gpu/drm/gma500/tc35876x-dsi-lvds.c | 2 +-
On Sun, May 21, 2017 at 2:37 PM, Linus Torvalds
wrote:
>
> I'm pretty sure there's a reason we added support for it on x86-32,
> because there are structures that use __u64 and fill things one entry
> at a time.
Did an "allyesconfig" build on 32-bit x86, and looked
On Fri, May 19, 2017 at 09:44:45AM +0200, Micha?? K??pie?? wrote:
> It is easier to simply store a module-wide
> pointer to the last (most likely only) FUJ02E3 ACPI device found, make
> the aforementioned API use it and cover our bases by warning the user if
> firmware exposes multiple FUJ02E3
Sorry, forget 'To' Mike, Russ and Frank
On 05/22/17 at 07:14am, Baoquan He wrote:
> On 05/21/17 at 01:38pm, Thomas Garnier wrote:
> > On Sat, May 20, 2017 at 5:02 AM, Baoquan He wrote:
> > > arch/x86/mm/kaslr.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
On 05/20/2017 08:47 AM, Jarkko Sakkinen wrote:
On Mon, May 15, 2017 at 11:56:51AM -0400, Stefan Berger wrote:
On 05/15/2017 08:41 AM, Jarkko Sakkinen wrote:
On Wed, May 10, 2017 at 07:54:22PM -0400, Stefan Berger wrote:
Implement the request_locality function. To set the locality on the
John Stultz writes:
> On Wed, May 17, 2017 at 9:54 PM, Richard Cochran
> wrote:
>> On Wed, May 17, 2017 at 04:06:07PM -0700, John Stultz wrote:
>>> On Wed, May 17, 2017 at 10:22 AM, Miroslav Lichvar
>>> wrote:
>>> > Is
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
This driver could also go via the input-tree or my tree. I don't really care
and just picked some subsystem :) Let me know if you are okay with
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
arch/blackfin/mach-bf537/boards/stamp.c| 2 +-
drivers/video/backlight/adp8860_bl.c | 2 +-
include/linux/{i2c =>
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
arch/blackfin/mach-bf537/boards/stamp.c| 2 +-
drivers/video/backlight/adp8870_bl.c | 2 +-
include/linux/{i2c =>
It doesn't make sense to use include/linux/i2c for client drivers which may in
fact rather be hwmon or input or whatever devices. As a result, I want to
deprecate include/linux/i2c for good. This series moves the include files to a
better location, largely include/linux/platform_data because that
There seems to be no need for separate ones since all users include both
files anyhow. Merge them because include/linux/i2c is to be deprecated.
Signed-off-by: Wolfram Sang
---
Only build tested (by buildbot) due to no HW.
arch/blackfin/include/asm/bfin_twi.h | 134
On 05/21/17 at 01:38pm, Thomas Garnier wrote:
> On Sat, May 20, 2017 at 5:02 AM, Baoquan He wrote:
> > arch/x86/mm/kaslr.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/mm/kaslr.c b/arch/x86/mm/kaslr.c
> > index aed2064..20b0456 100644
On Mon, May 22, 2017 at 03:16:42AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> rcu/next
> head: f1b89dcf23ef0999fae8bbc34cc9eb3fe00bc677
> commit: f1b89dcf23ef0999fae8bbc34cc9eb3fe00bc677 [91/91] rcu: Remove Tasks RCU
>
Hi Michael
On Fri, May 19, 2017 at 09:44:40AM +0200, Micha?? K??pie?? wrote:
> fujitsu-laptop registers two ACPI drivers that access each other's
> module-wide structures. To improve data encapsulation and lay the
> groundwork for separating the two aforementioned ACPI drivers into
> separate
John Stultz writes:
> CONFIG_GENERIC_TIME_VSYSCALL_OLD was introduced five years ago
> to allow a transition from the old vsyscall implementations to
> the new method (which simplified internal accounting and made
> timekeeping more precise).
I'm sure it's completely
On Thu, May 18, 2017 at 4:38 PM, Mika Westerberg
wrote:
> Intel Thunderbolt controllers support up to 16 MSI-X vectors. Using
Is that true for all generations? If so can we remove the legacy path?
> MSI-X is preferred over MSI or legacy interrupt and may bring
Hi Kees,
On 05/21/2017 07:20 AM, Kees Cook wrote:
On Sat, May 20, 2017 at 1:18 PM, wrote:
Seeing problems with programs that use semaphores. The one
that I'm getting bit by is jackd. strace says:
getuid()= 967
semget(0x282929, 0,
On Sun, May 21, 2017 at 07:57:53PM +0200, Thomas Gleixner wrote:
> On Thu, 18 May 2017, Christoph Hellwig wrote:
> > On Thu, May 18, 2017 at 10:24:48AM +0200, Christoph Hellwig wrote:
> > > > b) give the union a name (breaks any reference to timer_list->func in C
> > > > code):
> > > >
> > > >
Hello,
This mini-series adds initial support for the Amlogic S905 based
FriendlyARM NanoPi K2 SBC.
Tested with mainline U-Boot.
v2 adds USB and Wifi among others.
Regards,
Andreas
Cc: devicet...@vger.kernel.org
Cc: techsupp...@friendlyarm.com
Andreas Färber (2):
dt-bindings: arm: amlogic:
On Sun, 21 May 2017, Al Viro wrote:
>
> fix unsafe_put_user()
So here's my proposed patch on top of yours to fix unsafe_get_user() with
"long long" arguments, and to clean up the extra-long line you did.
Comments?
Linus
---
arch/x86/include/asm/uaccess.h | 5 +++--
1
Commit-ID: 84bcc1d57f634ba8a55eda9a910c159467af0aac
Gitweb: http://git.kernel.org/tip/84bcc1d57f634ba8a55eda9a910c159467af0aac
Author: Yazen Ghannam
AuthorDate: Fri, 19 May 2017 11:39:15 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 21 May
Commit-ID: 7bf130e4a0653f6cec83a387de5de0c2c9fa4dba
Gitweb: http://git.kernel.org/tip/7bf130e4a0653f6cec83a387de5de0c2c9fa4dba
Author: Shiju Jose
AuthorDate: Fri, 19 May 2017 11:39:11 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 21 May
Commit-ID: 473e90b2e8356f084dcf9c815a5170d4d4925897
Gitweb: http://git.kernel.org/tip/473e90b2e8356f084dcf9c815a5170d4d4925897
Author: Elena Reshetova
AuthorDate: Fri, 19 May 2017 11:39:13 +0200
Committer: Thomas Gleixner
CommitDate: Sun,
On Sat, 20 May 2017, Christoph Hellwig wrote:
> On Sat, May 20, 2017 at 12:52:03PM +0200, Thomas Gleixner wrote:
> > This should be rewritten proper by adding a propagate() callback to those
> > slub_attributes which must be propagated and avoid that insane conversion
> > to and from ASCII
>
>
Hi Jan,
On 21/05/17 12:46, Jan Kiszka wrote:
Hi Sudip,
why do we carry
if (pcidev->vendor != PCI_VENDOR_ID_EXAR)
return -ENODEV;
in gpio_exar_probe? This effectively prevents that
EXAR_DEVICE(COMMTECH, COMMTECH_4222PCIE, pbn_exar_XR17V35x),
On 05/21/2017 12:53 AM, Roman Penyaev wrote:
On Sun, May 21, 2017 at 5:31 AM, Andy Lutomirski wrote:
On 05/19/2017 09:14 AM, Roman Penyaev wrote:
Hi folks,
After experiencing guest double faults (sometimes triple faults) on
3.16 guest kernels with the following common
From: Markus Elfring
Date: Sun, 21 May 2017 21:50:44 +0200
A single space character should be put into a sequence.
Thus use the corresponding function "seq_putc".
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
On Tue, 16 May 2017, Arnd Bergmann wrote:
> On Tue, May 16, 2017 at 5:51 PM, Christoph Hellwig wrote:
> > Yes, that sounds useful to me as well. As you said it's an independent
> > but somewhat related change. I can add it to my series, but I'll
> > need a suggestions for a good
Fix for unsafe_put_user() (no callers currently in mainline,
but anyone starting to use it will step into that) + osf_wait4()
infoleak fix.
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git
From: Sivakumar Krishnasamy
Date: Fri, 19 May 2017 05:30:38 -0400
...
> Signed-off-by: Sivakumar Krishnasamy
Applied, thanks for the more detailed commit message.
From: Corentin Labbe
Date: Fri, 19 May 2017 09:03:32 +0200
> This patch convert new_state from int to bool since it store only 1 or 0
>
> Signed-off-by: Corentin Labbe
You must also change it to use the values "true" and "false" as well.
On Thu, 18 May 2017, Christoph Hellwig wrote:
> On Thu, May 18, 2017 at 10:24:48AM +0200, Christoph Hellwig wrote:
> > > b) give the union a name (breaks any reference to timer_list->func in C
> > > code):
> > >
> > > + union {
> > > + void(*func)(struct
On Sun, 21 May 2017, Thomas Gleixner wrote:
> On Tue, 16 May 2017, Arnd Bergmann wrote:
> > On Tue, May 16, 2017 at 5:51 PM, Christoph Hellwig wrote:
> > > Yes, that sounds useful to me as well. As you said it's an independent
> > > but somewhat related change. I can add it to my
On Sun, May 21, 2017 at 10:58:48AM +0200, Christoph Hellwig wrote:
> Btw, how well is alpha working these days? It looks like there hasn't
> been any maintainer activity for about two years.
Speaking for myself, the PWS 433au I've got continues to function
admirably as my IPv6 gateway. Debian
[Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver] On 21/05/2017
(Sun 11:51) Hans de Goede wrote:
> Hi,
>
> On 20-05-17 21:26, Paul Gortmaker wrote:
> >On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker
> > wrote:
> >>On Mon, May 15, 2017 at 2:20 PM, Hans
On Thu, May 18, 2017 at 08:36:07AM +0200, Quentin Schulz wrote:
> For the sake of DT binding stability, this IIO driver is a child of an
> MFD driver for Allwinner A10, A13 and A31 because there already exists a
> DT binding for this IP. The MFD driver has a DT node but the IIO driver
> does not.
On Thu, May 18, 2017 at 4:38 PM, Mika Westerberg
wrote:
> Organization of the capabilities in switches and ports is not so random
> after all. Rework the capability handling functionality so that it
> follows how capabilities are organized and provide two new
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: f1b89dcf23ef0999fae8bbc34cc9eb3fe00bc677
commit: f1b89dcf23ef0999fae8bbc34cc9eb3fe00bc677 [91/91] rcu: Remove Tasks RCU
config: x86_64-acpi-redef (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3)
Commit-ID: fc08a4703a418a398bbb575ac311d36d110ac786
Gitweb: http://git.kernel.org/tip/fc08a4703a418a398bbb575ac311d36d110ac786
Author: Vishal Verma
AuthorDate: Fri, 19 May 2017 11:39:10 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 21
Commit-ID: 2d1f406139ec20320bf38bcd2461aa8e358084b5
Gitweb: http://git.kernel.org/tip/2d1f406139ec20320bf38bcd2461aa8e358084b5
Author: Borislav Petkov
AuthorDate: Fri, 19 May 2017 11:39:09 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 21 May 2017
Commit-ID: 37d43acfd79f9c53289e9990c344cbd5b4db4bd4
Gitweb: http://git.kernel.org/tip/37d43acfd79f9c53289e9990c344cbd5b4db4bd4
Author: Yazen Ghannam
AuthorDate: Fri, 19 May 2017 11:39:14 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 21 May
From: Markus Elfring
Date: Sun, 21 May 2017 21:20:44 +0200
Replace the specification of four data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding
From: Markus Elfring
Date: Sun, 21 May 2017 22:09:11 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (5):
Improve a size determination in four functions
Delete an error message for a failed memory
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
drivers/hid/i2c-hid/i2c-hid.c | 2 +-
include/linux/{i2c => platform_data}/i2c-hid.h | 0
2 files changed, 1 insertion(+), 1
It doesn't make sense to use include/linux/i2c for client drivers which may in
fact rather be hwmon or input or whatever devices. As a result, I want to
deprecate include/linux/i2c for good. This series moves the include files to a
better location, largely include/platform_data because that is
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
I decided to not move it to 'platform_data' but just one level up because
'pmbus.h' sounds pretty generic to me like 'i2c.h'. And it might
It doesn't make sense to use include/linux/i2c for client drivers which may in
fact rather be hwmon or input or whatever devices. As a result, I want to
deprecate include/linux/i2c for good. This series moves the include files to a
better location, largely include/platform_data because that is
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
Documentation/hwmon/ltc4245| 2 +-
drivers/hwmon/ltc4245.c| 2 +-
include/linux/{i2c =>
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
drivers/hwmon/max6639.c| 2 +-
include/linux/{i2c => platform_data}/max6639.h | 0
2 files changed, 1 insertion(+), 1
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
Documentation/hwmon/ads1015| 2 +-
MAINTAINERS| 2 +-
drivers/hwmon/ads1015.c
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang
---
drivers/input/keyboard/lm8323.c | 2 +-
include/linux/{i2c => input}/lm8323.h | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
net/socket.c: In function 'put_ts_pktinfo':
net/socket.c:695:28: error: 'SCM_TIMESTAMPING_PKTINFO' undeclared (first use in
this function)
put_cmsg(msg, SOL_SOCKET,
Hi,
On Sat, 2017-05-20 at 21:19 +0200, Greg Kroah-Hartman wrote:
> On Sun, May 21, 2017 at 02:05:31AM +0900, Masahiro Yamada wrote:
> > The combo of list_empty() and list_first_entry() can be replaced with
> > list_first_entry_or_null().
> >
> > Signed-off-by: Masahiro Yamada
On Sat, 20 May 2017, Thomas Gleixner wrote:
> memcg_propagate_slab_attrs() abuses the sysfs attribute file functions to
> propagate settings from the root kmem_cache to a newly created
> kmem_cache. It does that with:
>
> attr->show(root, buf);
> attr->store(new, buf, strlen(bug);
>
>
Hi DT experts,
I have a question about "simple-mfd".
Documentation/devicetree/bindings/mfd/mfd.txt says as allows:
--8<-
Optional properties:
- compatible : "simple-mfd" - this signifies that the operating system should
consider all subnodes of the
On Sun, May 21, 2017 at 3:19 PM, Linus Torvalds
wrote:
>
> Did an "allyesconfig" build on 32-bit x86, and looked at who uses the
> 8-byte get_user/put_user cases:
I've done more testing.
It turns out that quite independently of all these patches, our 32-bit
x86
2017-05-21 18:44 GMT+09:00 Borislav Petkov :
> On Sun, May 21, 2017 at 06:15:53PM +0900, Masahiro Yamada wrote:
>> Could you change line 199
>>
>> $(addprefix $(obj)/,$(lxdialog)): $(obj)/dochecklxdialog
>>
>> to
>>
>> $(addprefix $(obj)/, mconf.o $(lxdialog)):
Hi Alex,
>-Original Message-
>From: Alex Williamson [mailto:alex.william...@redhat.com]
>Sent: Saturday, May 20, 2017 12:34 AM
>To: Chen, Xiaoguang
>Cc: kra...@redhat.com; intel-...@lists.freedesktop.org; linux-
>ker...@vger.kernel.org; zhen...@linux.intel.com;
Hi Arnd, Olof,
Last week, I thought I found a problem in my pull request,
but it turned out my misunderstanding.
So, my pull request I sent is OK.
I am re-sending this request mail for clarification.
Here are some ARM UniPhier SoC fixes for v4.12.
Due to the eMMC driver update, PHY parameters
This patch is used to add an obvious error message, due to
dismatch cluster names between on-disk and in the current cluster.
We can meet this case during OCFS2 cluster migration, if we can
give the user an obvious tip for why they can not mount the file
system after migration, they can quickly
On 5/19/2017 9:33 PM, Jin, Yao wrote:
On 5/19/2017 8:36 PM, Peter Zijlstra wrote:
On Fri, May 19, 2017 at 08:24:19PM +0800, Jin, Yao wrote:
Ah, I was more thinking of something like PERF_PMU_CAP_NO_SKID or
something that would skip the test and preserve current behaviour.
OK, I understand
From: Huang Ying
This patch is only a code clean up patch without functionality
changes. It moves CONFIG_THP_SWAP checking from inside swap slot
allocation to before we start swapping the THP. This makes the code
path a little easier to be followed and understood.
> -Original Message-
> From: Chen, Xiaoguang
> Sent: Thursday, May 18, 2017 7:20 PM
> To: He, Min ; alex.william...@redhat.com;
> kra...@redhat.com; intel-...@lists.freedesktop.org; linux-
> ker...@vger.kernel.org; zhen...@linux.intel.com; Lv, Zhiyuan
>
Hi Heiko,
On 2017/5/20 5:46, Heiko Stuebner wrote:
Hi Frank,
Am Mittwoch, 17. Mai 2017, 18:16:16 CEST schrieb Frank Wang:
From: Finley Xiao
This patch adds some new frequencies for rk3229 board.
Signed-off-by: Finley Xiao
Hi Paul,
Today's linux-next merge of the selinux tree got a conflict in:
include/rdma/ib_verbs.h
between commit:
2fc775726491 ("IB/opa-vnic: RDMA NETDEV interface")
from Linus' tree and commit:
89b54b4d09bd ("IB/core: Enforce PKey security on QPs")
from the selinux tree.
I fixed it
On Sat, 20 May 2017 20:33:35 -0700
Florian Fainelli wrote:
> Commit db2aa7fd15e8 ("initramfs: allow again choice of the embedded
> initram compression algorithm") introduced the possibility to select the
> initramfs compression algorithm from Kconfig and while this is a
Hi Paul,
After merging the selinux tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/infiniband/core/uverbs_cmd.c: In function 'create_qp':
drivers/infiniband/core/uverbs_cmd.c:1513:4: error: label 'err_destroy' used
but not defined
goto err_destroy;
^
On (05/20/17 11:18), Nicolas Iooss wrote:
> When compiling with -Wsuggest-attribute=format, gcc complains that some
> functions in kernel/printk/printk_safe.c transmit their argument to
> printf-like functions without having a printf attribute. Silence these
> warnings by adding relevant __printf
I'm back on the usual Sunday schedule, and everything else looks
fairly normal too. This rc2 is maybe a bit bigger than usual, but the
whole merge window was bigger than most, so maybe it's just that. And
it's not like it's huge - usually the rc2 week is fairly quiet as
people find issues.
The
John Johansen wrote:
> On 05/20/2017 09:59 PM, Tetsuo Handa wrote:
> > John Johansen wrote:
> >> On 11/22/2016 10:31 PM, Tetsuo Handa wrote:
> >>> Tetsuo Handa wrote:
> John Johansen wrote:
> >> In order to minimize the burden of reviewing, this patchset implements
> >> only
On Mon, May 15, 2017 at 06:45:32PM +0100, Okash Khawaja wrote:
> This exports tty_open_by_driver so that it can be called from other places
> inside the kernel. The checks for null file pointer are based on Alan Cox's
> patch here:
>
On Sat, May 20, 2017 at 08:59:54PM +0300, Rakesh Pandit wrote:
> While doing IO if I reset NVMe SSD (model :Samsung MZVPV512HDGL-0)
> it doesn't work as expected also results in NULL point dereference and
> system becomes unstable.
>
> Device's access is successfully disabled and reset
Looks fine,
Reviewed-by: Christoph Hellwig
On Fri, May 19, 2017 at 11:58:41AM +0100, David Howells wrote:
> Christoph Hellwig wrote:
>
> > It's not a userspace ABI, so by defintion it does not break an
> > existing user program.
>
> That's an invalid assumption. It is a de facto userspace ABI as it has been
> exposed in
On Fri, May 19, 2017 at 10:48:51AM +, David Laight wrote:
> From: Christoph Hellwig
> > Sent: 16 May 2017 12:48
> >
> > The new callback gets a pointer to the timer_list itself, which can
> > then be used to get the containing structure using container_of
> > instead of casting from and to
On Thu, May 18, 2017 at 10:57:31AM +0200, Arnd Bergmann wrote:
> How expensive would it be to add another field to timer_list and
> just have both pointers?
That would add 4/8 bytes to every structure containing a timer,
so I'd rather avoid it if possible. But one option might be to
inflict this
On Wed, May 17, 2017 at 05:32:12PM +0900, Minchan Kim wrote:
> Is block device(esp, zram which is compressed ram block device) okay to
> return garbage when ongoing overwrite IO fails?
>
> O_DIRECT write 4 block "aaa.." -> success
> read 4 block "aaa.." -> success
> O_DIRECT write 4 block
On Wed, 17 May 2017 14:33:45 +0200,
Bhumika Goyal wrote:
>
> On Wed, May 17, 2017 at 5:50 PM, Takashi Iwai wrote:
> > On Wed, 17 May 2017 13:38:56 +0200,
> > Bhumika Goyal wrote:
> >>
> >> Declare snd_kcontrol_new structures as const as they are only passed an
> >> argument to the function
On Sun, May 21, 2017 at 12:04:27AM -0700, Christoph Hellwig wrote:
> On Wed, May 17, 2017 at 05:32:12PM +0900, Minchan Kim wrote:
> > Is block device(esp, zram which is compressed ram block device) okay to
> > return garbage when ongoing overwrite IO fails?
> >
> > O_DIRECT write 4 block "aaa.."
This flag is already set in the top level Makefile of the kernel.
Also, by having set CONFIG_DRM_I915_GVT, thereby appending -Wall to
ccflags, you undo all the -Wno-* cflags previously set in the Make
variable KBUILD_CFLAGS.
For example:
cc foo.c -Wall -Wno-format -Wall
resets -Wformat.
On Fri, May 19, 2017 at 03:50:32PM -0500, Tom Lendacky wrote:
> The "worker" function would be doing the loop through the setup data,
> but since the setup data is mapped inside the loop I can't do the __init
> calling the non-init function and still hope to consolidate the code.
> Maybe I'm
Hi Dmitry,
I've updated the patch with your comments, unregistering first before
freeing the gpios.
In regards of your comment for the gpio-keys-polled update, I've just
started with kernel dev and thought moving old drivers to the new
managed api was a good start.
So I don't really know how to
On Fri, May 19, 2017 at 02:08:20PM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> commit: 75f64d68f9816a1c244b8685f056389b24d97e98 ("waitid(): switch copyout
> of siginfo to unsafe_put_user()")
> url:
>
On Sun, May 21, 2017 at 07:35:21AM +0200, Lukas Wunner wrote:
> On Sun, May 21, 2017 at 05:29:47AM +, Levy, Amir (Jer) wrote:
> > On Sun, May 21 2017, 07:47 AM, Lukas Wunner wrote:
> > > On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote:
> > > > +
> > > > + default:
> > > >
On Sat, May 20, 2017 at 11:09:02PM -0700, Christoph Hellwig wrote:
> On Mon, May 15, 2017 at 06:45:32PM +0100, Okash Khawaja wrote:
> > This exports tty_open_by_driver so that it can be called from other places
> > inside the kernel. The checks for null file pointer are based on Alan Cox's
> >
On Sun 21-05-17 00:45:46, Wei Yongjun wrote:
> From: Wei Yongjun
>
> The function get_free_pipe_id_locked() is called from
> goldfish_pipe_open() with a lock is held, so we should
> use GFP_ATOMIC instead of GFP_KERNEL.
Why is GFP_NOWAIT insufficient? Does this path needs an access to memory
On Sun, May 21, 2017 at 07:31:14AM +0200, Lukas Wunner wrote:
> On Fri, May 19, 2017 at 01:28:36PM +0300, Mika Westerberg wrote:
> > On Fri, May 19, 2017 at 12:07:10PM +0200, Lukas Wunner wrote:
> > > Apple uses 0x30 to store a
> > > serial number. Is this attribute number assigned by Intel to
On Sun, May 21, 2017 at 5:31 AM, Andy Lutomirski wrote:
> On 05/19/2017 09:14 AM, Roman Penyaev wrote:
>>
>> Hi folks,
>>
>> After experiencing guest double faults (sometimes triple faults) on
>> 3.16 guest kernels with the following common pattern:
>>
[cut]
>>
>> Further tracking of VMCB
On Sun, May 21, 2017 at 10:40:41AM +0300, Mika Westerberg wrote:
> On Sun, May 21, 2017 at 07:35:21AM +0200, Lukas Wunner wrote:
> > On Sun, May 21, 2017 at 05:29:47AM +, Levy, Amir (Jer) wrote:
> > > On Sun, May 21 2017, 07:47 AM, Lukas Wunner wrote:
> > > > On Thu, May 18, 2017 at 05:39:08PM
On Sun, May 21 2017, 11:00 AM, Mika Westerberg wrote:
> On Sun, May 21, 2017 at 10:40:41AM +0300, Mika Westerberg wrote:
> > On Sun, May 21, 2017 at 07:35:21AM +0200, Lukas Wunner wrote:
> > > On Sun, May 21, 2017 at 05:29:47AM +, Levy, Amir (Jer) wrote:
> > > > On Sun, May 21 2017, 07:47 AM,
On Sat, May 20, 2017 at 09:15:17AM +, Levy, Amir (Jer) wrote:
> > I created a udev rule that will automatically authorize the dock and cable.
> > #dell cable
> > ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0",
> > ATTR{vendor}=="0xd4", ATTR{device}=="0xb051",
From: Markus Elfring
Date: Sun, 21 May 2017 10:20:03 +0200
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation in zswap_pool_create()
Improve a size determination in
Hi James,
sorry for the late response due to recently verify and debug the
RAS solution.
2017-05-13 1:24 GMT+08:00, James Morse :
> Hi gengdongjiu,
>
> On 05/05/17 13:31, gengdongjiu wrote:
>> when guest OS happen an SEA, My current solution is shown below:
>>
>> (1) host EL3 firmware firstly
From: Markus Elfring
Date: Sat, 20 May 2017 22:33:21 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
From: Markus Elfring
Date: Sat, 20 May 2017 22:44:03 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
From: Markus Elfring
Date: Sun, 21 May 2017 09:29:25 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
> + *
> + * pci_irq_vector() below is able to handle entry differently
> + * depending on MSI vs MSI-x case
> + *
>*/
One more instance of this comment left :)
> pcie_capability_read_word(dev, PCI_EXP_FLAGS, );
>
Markus, can you please stop CCing me on every of those patches?
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Link:
>
201 - 300 of 542 matches
Mail list logo