The new driver fails to build without INPUT_POLLDEV
drivers/platform/x86/peaq-wmi.o: In function `peaq_wmi_exit':
peaq-wmi.c:(.exit.text+0x1c): undefined reference to
`input_unregister_polled_device'
drivers/platform/x86/peaq-wmi.o: In function `peaq_wmi_init':
peaq-wmi.c:(.init.text+0x23): undef
gcc points out a possible format string overflow for a large value of 'zone':
drivers/platform/x86/alienware-wmi.c: In function 'alienware_wmi_init':
drivers/platform/x86/alienware-wmi.c:461:24: error: '%02X' directive writing
between 2 and 8 bytes into a region of size 6 [-Werror=format-overflow
On Thu, Jul 20, 2017 at 04:19:40PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 20, 2017 at 05:50:54AM -0700, Paul E. McKenney wrote:
> > >
> > > static void cpuidle_idle_call()
> > > {
> > > rcu_idle_enter()
> > > ..
> > > rcu_idle_exit()
> > > }
> > >
> > > I want
> > >
> > > static vo
When enabling lockdep debugging on Juno platform with HDLCD and TDA998x
I get the following warning from the system:
[ 25.990733] ==
[ 25.998637] WARNING: possible circular locking dependency detected
[ 26.006531] 4.13.0-rc1-00284-g28c0a682
On Thu Jul 20 17:49:27 2017 Arnd Bergmann wrote:
> Just like ARCH_MULTIPLATFORM, we want to use ARM_PATCH_PHYS_VIRT
> when possible, but that fails for NOMMU or XIP_KERNEL configurations.
> Using 'imply' instead of 'select' gets this right and only uses
> the symbol when we don't have to hardcode
Explain better when the drm_modeset_acquire_ctx parameter can
be skipped for drm_modeset_lock() call.
Signed-off-by: Liviu Dudau
Cc: Daniel Vetter
---
drivers/gpu/drm/drm_modeset_lock.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_modeset
On 07/20/2017 06:29 AM, Keerthy wrote:
> Push the request_irq function to the end of probe so as
> to ensure all the required fields are populated in the event
> of an ISR getting executed right after requesting the irq.
>
> Currently while loading the crash kernel a crash was seen as
> soon as
2017-07-07 10:54 GMT+09:00 Kunihiko Hayashi :
> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
> monitoring unit implemented on UniPhier SoCs. This driver supports
> temperature monitoring and alert function.
>
> Signed-off-by: Kunihiko Hayashi
Sparse reports several war
Hi!
> This is fourth version of the patch series adding support for Thunderbolt
> security levels and NVM firmware upgrade.
While prototyping the user-space bits for GNOME, I stumbled upon an
oops on the Lenovo T470s (see below) when attaching a Dell TB16
thunderbolt 3 dock. As a result /sys/bus/
On Thu, Jul 20, 2017 at 09:55:31PM +0900, Akira Yokosawa wrote:
> On 2017/07/20 14:47, Paul E. McKenney wrote:
> > On Thu, Jul 20, 2017 at 09:31:41AM +0800, Boqun Feng wrote:
> >> On Wed, Jul 19, 2017 at 02:56:02PM -0700, Paul E. McKenney wrote:
> >>> On Thu, Jul 20, 2017 at 06:33:26AM +0900, Akira
staging: rts5208: Fix coding style issue caught by checkpatch.pl related to
function name in debug print
Signed-off-by: Gaurav Pathak
---
drivers/staging/rts5208/ms.c| 5 +++--
drivers/staging/rts5208/rtsx.c | 4 ++--
drivers/staging/rts5208/rtsx_chip.c | 4 ++--
drivers/staging/
> -Original Message-
> From: Christian Kellner [mailto:ckell...@redhat.com]
> Sent: Thursday, July 20, 2017 11:12 AM
> To: Mika Westerberg
> Cc: Andreas Noever ; Greg Kroah-Hartman
> ; Michael Jamet ;
> Yehezkel Bernat ; Lukas Wunner
> ; Amir Levy ; Andy Lutomirski
> ; Limonciello, Mario ;
On 07/18, Eric W. Biederman wrote:
>
> - BUG_ON((reason & __SI_MASK) != __SI_POLL);
> + BUG_ON((reason < POLL_IN) || (reason > NSIGPOLL));
^
looks obviously wrong? Say, POLL_IN is obviously
On Thu, Jul 20, 2017 at 02:58:35PM +0200, Andrea Arcangeli wrote:
> but if zap_pte in a fremap fails to drop the anon page that was under
> memory migration/compaction the exact same thing will happen. Either
... except it is ok to clear a migration entry, it will be migration
that will free the n
On Thursday 20 July 2017 09:02:20 kernel test robot wrote:
> commit: bff589be59c50924a9715951160578e570cba5c6 ("platform/x86: dell-wmi:
> Convert to the WMI bus infrastructure")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> caused below changes (please refer to atta
This helper function is useful for the nvme subsystem, and maybe
others.
Signed-off-by: Martin Wilck
---
include/linux/string.h | 30 ++
1 file changed, 30 insertions(+)
diff --git a/include/linux/string.h b/include/linux/string.h
index a467e617eeb08..0bec4151b0eb9 1
The NVME standard mandates that the SN, MN, and FR fields of
the Indentify Controller Data Structure be "ASCII strings".
That means that they may not contain 0-bytes, not even string
terminators.
Signed-off-by: Martin Wilck
---
drivers/nvme/target/admin-cmd.c | 13 ++---
1 file changed,
Some broken targets (such as the current Linux target) pad
model or serial fields with 0-bytes rather than spaces. The
NVME spec disallows 0 bytes in "ASCII" fields.
Thus strip trailing 0-bytes, too. Also make sure that we get no
underflow for pathological input.
Signed-off-by: Martin Wilck
Revie
With the current implementation, the default "fallback" WWID generation
code (if no nguid, euid etc. are defined) for Linux NVME host and target
results in the following WWID format:
nvme.-3163653363666438366239656630386200-4c696e7578
On Thu, Jul 20, 2017 at 1:29 AM, Ingo Molnar wrote:
>
> * kbuild test robot wrote:
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> master
>> head: c981f0b3fb08ee58aacb208fe7f45628af420bba
>> commit: 79e6b917e69a34d45e83e72f1e9bb7487d5f5832 [1341/1811] x86/bu
ping ;)
On 07/10, Oleg Nesterov wrote:
>
> Documentation/admin-guide/kernel-parameters.txt says:
>
> norandmaps Don't use address space randomization. Equivalent
> to echo 0 > /proc/sys/kernel/randomize_va_space
>
> but it doesn't work because arch_rnd() which is used to ran
On Thu, Jul 20, 2017 at 1:27 AM, Daniel Vetter wrote:
> On Wed, Jul 19, 2017 at 10:39:28AM -0700, Matthias Kaehlcke wrote:
>> Commit a21960339c8c ("drm/i915: Consistently use enum pipe for PCH
>> transcoders") misses some pieces, due to a problem with the patch
>> format, this patch adds the remai
Hi,
Did you by chance boot with the dock "plugged in"? Or was this the
result of
plugging in after boot?
Dock was plugged in after boot. I included another dmesg output,
where I marked the time point that I plugged the device in.
There is a known issue that Mika is tracking regarding some p
On Thu, 2017-07-20 at 20:54 +1000, Michael Ellerman wrote:
> Joe Perches writes:
>
> > On Wed, 2017-07-19 at 21:24 -0700, Linus Torvalds wrote:
> > > On Wed, Jul 19, 2017 at 6:05 PM, Joe Perches wrote:
> > > >
> > > > Just for ease of manipulation and not breaking the script much,
> > > > I'd s
On 7/20/2017 3:28 AM, Håkon Bugge wrote:
cp->cp_send_gen is treated as a normal variable, although it may be
used by different threads.
This is fixed by using {READ,WRITE}_ONCE when it is incremented and
READ_ONCE when it is read outside the {acquire,release}_in_xmit
protection.
There is expli
2017-07-21 1:08 GMT+09:00 Masahiro Yamada :
> 2017-07-07 10:54 GMT+09:00 Kunihiko Hayashi :
>> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
>> monitoring unit implemented on UniPhier SoCs. This driver supports
>> temperature monitoring and alert function.
>>
>> Signed-off
On 07/20/2017 12:24 AM, walter harms wrote:
>
>
> Am 20.07.2017 00:16, schrieb Christophe JAILLET:
>> If the 'memcmp' fails, free allocated resources as done in all other
>> error handling paths.
>>
>> Signed-off-by: Christophe JAILLET
>> ---
>> Please review carefully, this patch looks "too o
>> Yes, the following message is shown on HP systems. Please note that
>> WHEA is a Windows-defined interface.
>
> Ok, so let's couple ghes_edac loading to that and see how far we could
> go. I guess we should add checks for that to the major x86 EDAC drivers
> to not load and this way ghes_edac w
Implemented default hugepage size verification (default_hugepagesz=)
in order to allow allocation of defined number of pages (hugepages=)
only for supported hugepage sizes.
Signed-off-by: Victor Aoqui
---
v2:
- Renamed default_hugepage_setup_sz function to hugetlb_default_size_setup;
- Added po
On Thu, Jul 20, 2017 at 05:50:04PM +0200, Petr Mladek wrote:
> On Wed 2017-07-19 23:17:23, Josh Poimboeuf wrote:
> > - patching otherwise unpatchable code (i.e., assembly)
> >
> > In many/most cases, it seems like stop_machine() would be very useful
> > to avoid concurrency issues.
>
> I am
On Thu, Jul 20, 2017 at 04:55:59PM +, Luck, Tony wrote:
> Add a module parameter to those edac drivers that can override the check
> and let them load anyway. I'm not paranoid, I just assume that there is a
> BIOS
> out there that sets the OSC/WHEA bits, but isn't generating useful GHES logs.
On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
> Alternatively, if you've got a fairly recent git repo with all the
> patches merged I can build a test kernel and give it a shot for you,
> although fair warning it may take a day or two for me to get to it.
Hurm, I think this will take quite a
2017-07-21 1:53 GMT+09:00 Masahiro Yamada :
> 2017-07-21 1:08 GMT+09:00 Masahiro Yamada :
>> 2017-07-07 10:54 GMT+09:00 Kunihiko Hayashi :
>>> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
>>> monitoring unit implemented on UniPhier SoCs. This driver supports
>>> temperatu
> Or add that parameter to edac_core.ko and let it control which EDAC
> driver gets loaded? Something like
>
> edac=ignore_ghes
>
> or so. And then the other EDAC drivers query it.
Sure ... one central place is better than adding code to each
driver.
-Tony
n:
> patch:145: CHECK: Alignment should match open parenthesis
> patch:148: CHECK: Alignment should match open parenthesis
>
> Signed-off-by: Richard Leitner
Running linux-next-20170720 on a imx53-qsb I get the following issue:
root@imx53qsb:~# reboot
Broadcast message from root@
On Thu, Jul 20, 2017 at 2:11 AM, Ingo Molnar wrote:
> Could you please also create a tabulated quick-comparison of the three
> variants,
> of all key properties, about behavior, feature and tradeoff differences?
>
> Something like:
>
> !ARCH_HAS_REFCOUNT ARCH_
On Wed, Jul 19, 2017 at 07:48:08PM +0800, Yisheng Xie wrote:
> Hi Jérôme
>
> On 2017/6/29 2:00, Jérôme Glisse wrote:
> >
> > Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i
> > test same kernel as kbuild system, git branch:
> >
> > https://cgit.freedesktop.org/~glisse/linux/log/
Hi Fabio,
thanks for the testing/reporting!
On 07/20/2017 07:11 PM, Fabio Estevam wrote:
Running linux-next-20170720 on a imx53-qsb I get the following issue:
root@imx53qsb:~# reboot
...
ALSA: Storing mixer settings...
[ 20.031604] Unable to handle kernel paging request at virtual
address
Replaced __this_cpu_read function call by raw_cpu_read in
iommu_range_alloc function.
Preemption doesn't need to be disabled since any CPU can safely
use IOMMU pool.
Signed-off-by: Victor Aoqui
---
arch/powerpc/kernel/iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ar
On Thu, Jul 20, 2017 at 8:07 AM, Paul Moore wrote:
>
> git://git.infradead.org/users/pcmoore/audit stable-4.13
Pulled.
However, I'm gently poking people towards please using signed tags - I
prefer it even for kernel.org trees (and the security is pretty tight
there), and I _require_ it for publ
Hi Richard,
On Thu, Jul 20, 2017 at 2:25 PM, Richard Leitner wrote:
> Does this occur only on reboot or everytime the driver tries to read the AVC
> threshold (avc_get_threshold)?
> Are you able to set the AVC threshold (using amixer)?
I am not even using the codec. I just run 'reboot' and the
On 20 July 2017 at 09:56, Ard Biesheuvel wrote:
> On 20 July 2017 at 09:36, James Morse wrote:
>> Hi Ard,
>>
>> On 20/07/17 06:35, Ard Biesheuvel wrote:
>>> On 20 July 2017 at 00:32, Laura Abbott wrote:
I didn't notice any performance impact but I also wasn't trying that
hard. I did tr
On 07/20/2017 07:27 PM, Fabio Estevam wrote:
Hi Richard,
On Thu, Jul 20, 2017 at 2:25 PM, Richard Leitner wrote:
Does this occur only on reboot or everytime the driver tries to read the AVC
threshold (avc_get_threshold)?
Are you able to set the AVC threshold (using amixer)?
I am not even u
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
197095024 32 2476560bd video/fbdev/a
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
51551312 406507196b drivers/video
On Thu, Jul 20, 2017 at 2:38 PM, Richard Leitner wrote:
> Thank you for spotting this! That works of course.
>
> I'm sorry, it seems I messed something up during copy/paste for my own
> backport version of this patch. Seems like I tested and sent a different
> version of the patch... That definit
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
199161240 8 2116452ac fbdev/savage/
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/video/fbdev/skeletonfb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
31902704 245918171e video/fbdev/k
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
132852080 3 153683c08 video/fbdev/r
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
84321456 16990426b0 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
12149 768 36 129533299 video/fbdev/n
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
26431616 16427510b3 video/fbdev/g
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
117901913 0 137033587 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
6736 856 075921da8 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
198843036 96 2301659e8 fbdev/matrox/
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
10332 596 16 109442ac0 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
127661064 21 13851361b drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
209942440 8 234425b92 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
11940 660 16 126163148 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
170 488 0 658 292 drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
73261320 0864621c6 fbdev/mb862xx
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
7953 568 96861721a9 fbdev/vermili
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
13132 520 56 13708358c video/fbdev/i
On 07/20, Jisheng Zhang wrote:
> Hi all,
>
> I notice there's one regulator driver for NCP6335D in android-msm repo:
>
> https://android.googlesource.com/kernel/msm/+log/android-msm-dory-3.10-kitkat-wear/drivers/regulator/onsemi-ncp6335d.c
>
> Is there anyone want to make it mainlined?
>
You'r
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
125111920 0 14431385f drivers/video
On 07/20/2017 07:40 PM, Fabio Estevam wrote:
Do you want to send that patch or should I?
I have just sent the patch.
Thanks!
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
3856 968 12849521358 video/fbdev/v
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
132061232 40 14478388e video/fbdev/t
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
11749 896 24 12669317d video/fbdev/i
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
390 552 0 942 3ae drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
175341824 48 194064bce video/fbdev/a
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
4703 512 05215145f drivers/video
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
115252048 8 13581350d video/fbdev/a
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as const.
Arvind Yadav (28):
[PATCH 01/28] video: fbdev: radeon: constify pci_device_id.
[PATCH 02/28] video: fbdev: atyfb: co
Hi Borislav/Mark,
> On Wed, Jul 19, 2017 at 04:05:21PM -0400, Mark Salter wrote:
> > Yes, I should have included Boris. The last time this came up, Boris
> > said it was up to you. :)
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/401772.html
>
> /me goes back and reads
On 07/19/2017 06:38 PM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
Regardless of whether or not debug messages from the core system
suspend/hibernation code are enabled, it is useful to know when
system-wide transitions start and finish (or fail), so print "info"
messages at these points.
Borislav Petkov writes:
> On Thu, Jul 20, 2017 at 01:29:17PM +0100, Punit Agrawal wrote:
>> I agree that where there is a genuine problem, relevant messages can
>> help to diagnose the problem. But what's printed now doesn't fit the
>> criteria.
>
> So make it fit the criteria. Change the code to
On 07/20, Masahiro Yamada wrote:
> Hi Stephen, Rob,
>
> 2017-07-01 8:59 GMT+09:00 Rob Clark :
> > On Fri, Jun 30, 2017 at 6:58 PM, Stephen Boyd wrote:
> >> If we have a structure that's marked const it will be placed
> >> into the .rodata section but it could reference an init section
> >> functi
On 07/20/2017 01:26 AM, Pavel Machek wrote:
+#if defined(CONFIG_RTC_SHOW_TIME_RTC)
+ {
+ struct rtc_time tm;
+
+ rtc_time64_to_tm(ts.tv_sec, &tm);
+ pr_info("%s %d-%02d-%02d %02d:%02d:%02d.%09lu UTC\n",
+ prefix_msg ? prefix_ms
On 07/20/2017 03:33 AM, Andy Shevchenko wrote:
On Tue, 2017-07-18 at 12:57 -0700, Mark Salyzyn wrote:
On 07/18/2017 10:50 AM, Joe Perches wrote:
On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote:
Recently I have noticed too many users of struct rtc_time that
printing
its content field b
When CONFIG_PREEMPT=y, the following warning shows up:
BUG: using smp_processor_id() in preemptible [] code: swapper/0/1
caller is pseries_processor_idle_init+0x58/0x21c
This warning shows up because preemption cannot occur when using
get_paca(), otherwise the paca_struct it points to may
On Thu, Jul 20, 2017 at 1:25 PM, Linus Torvalds
wrote:
> On Thu, Jul 20, 2017 at 8:07 AM, Paul Moore wrote:
>>
>> git://git.infradead.org/users/pcmoore/audit stable-4.13
>
> Pulled.
Thanks.
> However, I'm gently poking people towards please using signed tags - I
> prefer it even for kernel.org
On Thu, Jul 20, 2017 at 10:49:08AM -0700, Loc Ho wrote:
> Tuan and I both worked on the APEI side for X-Gene and for this one,
> we both sign off.
There's no such thing as "both sign off". See the document I mentioned
before.
> If you required, I can re-post another version.
Yes please.
--
Reg
On Thu, Jul 20, 2017 at 9:48 AM, Joe Perches wrote:
>
> Same general concept, but then an expectation would be
> relative paths for filename patterns.
No, I actually think we really should require the filename patterns to
be absolute, even if the MAINTAINERS file might be deep in the
hierarchy.
Commit 7cc119f29b19 ("dt-bindings: Add TI SCI PM Domains") introduced a
number of K2G_DEV_x macros to represent each device ID available on the
K2G platform for use by the genpd, clock, and reset drivers. Rather than
use these macros, which are only used in the device tree for property
values and n
On Thu, Jul 20, 2017 at 02:36:33PM +0200, Sam Ravnborg wrote:
> On Thu, Jul 20, 2017 at 07:00:55AM +0200, Krzysztof Kozlowski wrote:
> > Remove old, dead Kconfig options (in order appearing in this commit):
> > - EXPERIMENTAL is gone since v3.9;
> > - INET_LRO: commit 7bbf3cae65b6 ("ipv4: Remove
The prefixlen maps used here are identical, and have been since
introduction. It seems to make sense to use a single large map,
that the preprocessor will fill appropriately.
Signed-off-by: Aaron Conole
---
net/netfilter/ipset/pfxlen.c | 395 +++
1 file c
Em Thu, 20 Jul 2017 19:05:04 +0200
Borislav Petkov escreveu:
> On Thu, Jul 20, 2017 at 04:55:59PM +, Luck, Tony wrote:
> > Add a module parameter to those edac drivers that can override the check
> > and let them load anyway. I'm not paranoid, I just assume that there is a
> > BIOS
> > out
Primary purpose of pr_info_show_time() is to provide a marker used for
post-mortem Battery and Power analysis. These markers are to be
placed at major discontinuities of time and power level. An optional
timestamp is added to aid the post-mortem or delayed analysis. This
function is to be called
How did this two-year old thread get resurrected?
Anyway, it got resurrected without even answering one core question:
On Thu, Jul 20, 2017 at 4:24 AM, Peter Zijlstra wrote:
> On Mon, Feb 02, 2015 at 11:13:44AM -0800, Linus Torvalds wrote:
On Mon, Feb 2, 2015 at 11:00 AM, Linus Torvalds
>>
On Thu, Jul 20, 2017 at 9:23 AM, Pali Rohár wrote:
> On Thursday 20 July 2017 09:02:20 kernel test robot wrote:
>> commit: bff589be59c50924a9715951160578e570cba5c6 ("platform/x86: dell-wmi:
>> Convert to the WMI bus infrastructure")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g
On Thu, Jul 20, 2017 at 05:07:48PM +0100, Liviu Dudau wrote:
> Explain better when the drm_modeset_acquire_ctx parameter can
> be skipped for drm_modeset_lock() call.
>
> Signed-off-by: Liviu Dudau
> Cc: Daniel Vetter
Applied, thanks.
-Daniel
> ---
> drivers/gpu/drm/drm_modeset_lock.c | 12 ++
On Thu, Jul 20, 2017 at 8:51 AM, Masami Hiramatsu wrote:
>
> Acked-by: Masami Hiramatsu
> Tested-by: Masami Hiramatsu
Ok, I committed that patch as-is.
Other architectures may end up with the same issue, unless they really
happen to have just a single instruction that fits in their
kprobe_opco
I've run into a problem where I have a driver C file and a header
file for that driver that are in the same directory. The C file
has an include like
#include
instead of
#include "driver.h"
and building this in tree fails, but building it out of tree with
the O= option doesn't fail. I
From: Matthew Wilcox
Signed-off-by: Matthew Wilcox
---
lib/Kconfig | 3 ++
lib/string.c | 130 +++
2 files changed, 133 insertions(+)
diff --git a/lib/Kconfig b/lib/Kconfig
index 6762529ad9e4..40b114a11d7c 100644
--- a/lib/Kconfig
+++
From: Matthew Wilcox
Where possible, call memset16(), memmove() or memcpy() instead of using
open-coded loops. I don't like the calling convention that uses a byte
count instead of a count of u16s, but it's a little late to change that.
Reduces code size of fbcon.o by almost 400 bytes on my lapt
On Thu, Jul 20, 2017 at 03:01:16PM +0200, Maxime Ripard wrote:
> The current drm_atomic_helper_commit_tail helper works only if the CRTC is
> accessible, and documents an alternative implementation that is supposed to
> be used if that happens.
>
> That implementation is then duplicated by some dr
From: Matthew Wilcox
These are single instructions on x86. There's no 64-bit instruction
for x86-32, but we don't yet have any user for memset64() on 32-bit
architectures, so don't bother to implement it.
Signed-off-by: Matthew Wilcox
---
arch/x86/include/asm/string_32.h | 24
From: Matthew Wilcox
Alpha already had an optimised fill-memory-with-16-bit-quantity assembler
routine called memsetw(). It has a slightly different calling convention
from memset16() in that it takes a byte count, not a count of words.
That's the same convention used by ARM's __memset routines,
601 - 700 of 969 matches
Mail list logo
