From: Colin Ian King
Variable key_ref is being assigned a value that is never read;
key_ref is being re-assigned a few statements later. Hence this
assignment is redundant and can be removed.
Signed-off-by: Colin Ian King
---
From: Arvind Yadav
Date: Mon, 4 Dec 2017 23:18:20 +0530
> @@ -120,9 +120,10 @@ static int sni_82596_probe(struct platform_device *dev)
> netdevice->dev_addr[5] = readb(eth_addr + 0x06);
> iounmap(eth_addr);
>
> - if (!netdevice->irq) {
> + if
> On Dec 3, 2017, at 9:03 AM, Alexei Starovoitov
> wrote:
>
> On Thu, Nov 30, 2017 at 03:50:18PM -0800, Song Liu wrote:
>> Two new perf types, perf_kprobe and perf_uprobe, will be added to allow
>> creating [k,u]probe with perf_event_open. These [k,u]probe are
On Mon, Dec 4, 2017 at 6:49 AM, Arnd Bergmann wrote:
> gcc-8 warns about using strncpy() with the source size as the limit:
>
> fs/exec.c:1223:32: error: argument to 'sizeof' in 'strncpy' call is the same
> expression as the source; did you mean to use the size of the destination?
Am 04.12.2017 um 12:37 schrieb Dan Carpenter:
On Mon, Dec 04, 2017 at 01:17:37PM +0300, Dan Carpenter wrote:
Perhaps choose different function names if you want? You could do it
as several patches:
patch 1: change types to bool
patch 2: sed -e '/ == optionOn//'
patch 3: split the functions
The patch
ASoC: spdif: Add S32_LE support for S/PDIF dummy codec drivers
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
MAINTAINERS: add entries for UniPhier ASoC sound drivers
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
On Mon, 4 Dec 2017, J. Bruce Fields wrote:
On Mon, Dec 04, 2017 at 01:39:37PM -0200, Thiago Rafael Becker wrote:
On Mon, 4 Dec 2017, NeilBrown wrote:
I think you need to add groups_sort() in a few more places.
Almost anywhere that calls groups_alloc() should be considered.
Restrict which nodes are valid targets for a DT overlay.
Add a flag bit to struct device_node allowing nodes to be marked as
valid target for overlays.
A driver that is always intended to handle DT overlays can
enable overlays by calling a function for its DT node.
For individual nodes that
On Mon, 2017-12-04 at 11:06 -0800, Paul E. McKenney wrote:
> On Fri, Dec 01, 2017 at 08:45:13PM -0800, Joe Perches wrote:
> > On Fri, 2017-12-01 at 13:44 -0800, Paul E. McKenney wrote:
>
> > If you really wanted to optimize, you could make the first (smp_|)
> > become (?:smp_|) to avoid the
Am 04.12.2017 um 12:24 schrieb Dan Carpenter:
On Sun, Dec 03, 2017 at 04:17:25PM +0100, Simon Sandström wrote:
Renames enum dataMode and its values packet, continuous, continuousNoSync
to enum data_mode and PACKET, CONTINUOUS, CONTINUOUS_NO_SYNC. Fixes
checkpatch.pl warnings: "Avoid
On Mon, 4 Dec 2017 11:45:21 -0500, Prarit Bhargava wrote:
> On 12/04/2017 08:13 AM, Prarit Bhargava wrote:
> > x86: Booting SMP configuration:
> > node #0, CPUs:#1 #2 #3 #4
> > node #1, CPUs:#5 #6 #7 #8 #9
> > node #0, CPUs: #10 #11 #12 #13 #14
> > node
On Mon, Dec 04, 2017 at 03:53:32PM +0100, Rafael J. Wysocki wrote:
> Not really.
>
> This is generic code, so no thinkpad_acpi-specific stuff in this file, please,
> even under #ifdefs.
>
I have some ideas, and I want your confirmation if that would be
acceptable.
Can I do this:
Expose a new
Simple but useful message log to the user in case of module appraise is
forced and fails due to the lack of file descriptor, that might be
caused by kmod calls to compressed modules.
Signed-off-by: Bruno E. O. Meneguele
---
security/integrity/ima/ima_main.c | 6 +-
1
Commit-ID: 4ce413d1840b25b101be3c0559161db8891f3360
Gitweb: https://git.kernel.org/tip/4ce413d1840b25b101be3c0559161db8891f3360
Author: Will Deacon
AuthorDate: Fri, 1 Dec 2017 15:29:39 +
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017
On 04-12, Bruno E. O. Meneguele wrote:
> Simple but useful message log to the user in case of module appraise is
> forced and fails due to the lack of file descriptor, that might be
> caused by kmod calls to compressed modules.
>
> Signed-off-by: Bruno E. O. Meneguele
> ---
On Fri 01 Dec 14:25 PST 2017, Rob Herring wrote:
> On Wed, Nov 29, 2017 at 04:00:40PM -0800, Bjorn Andersson wrote:
> > Attempt to acquire the APCS IPC through the mailbox framework and fall
> > back to the old syscon based approach, to allow us to move away from
> > using the syscon.
> >
> >
On 12/04/2017 08:59 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.4 release.
> There are 95 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Tue, Nov 21, 2017 at 02:41:05PM +0530, Tirupathi Reddy wrote:
> This patch adds device tree bindings for Qualcomm SPMI PMIC
> clock divider module.
>
> Signed-off-by: Tirupathi Reddy
> ---
> .../bindings/clock/qcom,spmi-pmic-div.txt | 59
>
On Fri, Dec 01, 2017 at 10:23:07PM +0800, Lai Jiangshan wrote:
> Sine the cpu/hotplug refactor is done, the hotplug
> callbacks are called properly. So the workaround is
> useless.
>
> Signed-off-by: Lai Jiangshan
Applied to wq/for-4.16 w/ desc updates.
Thanks.
--
> On Dec 4, 2017, at 9:59 AM, Greg Kroah-Hartman
> wrote:
>
> This is the start of the stable review cycle for the 4.14.4 release.
> There are 95 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
>
> Kernel Page Table Isolation, prefix kpti_
>
>Linus, your call :)
I think you probably chose the right name here. The alternatives sound
intriguing, but probably not the right thing to do.
How much of this is
On Mon, Dec 4, 2017 at 4:20 PM, Gustavo A. R. Silva
wrote:
> Hi Joonas,
>
> Quoting Joonas Lahtinen :
>
>> On Mon, 2017-11-27 at 16:17 -0600, Gustavo A. R. Silva wrote:
>>>
>>> In preparation to enabling -Wimplicit-fallthrough, mark switch
On Mon, Dec 04, 2017 at 11:59:22AM +1100, James Morris wrote:
> On Fri, 1 Dec 2017, Paul E. McKenney wrote:
>
> > Now that the associative-array library properly heads dependency chains,
> > the various smp_read_barrier_depends() calls in security/keys/keyring.c
> > are no longer needed. This
From: Alexander Potapenko
As a code-size optimization, LLVM builds since r279383 may
bulk-manipulate the shadow region when (un)poisoning large memory
blocks. This requires new callbacks that simply do an uninstrumented
memset().
This fixes linking the Clang-built kernel
For now we can hard-code ASAN ABI level 5, since historical clang builds
can't build the kernel anyway. We also need to emulate gcc's
__SANITIZE_ADDRESS__ flag, or memset() calls won't be instrumented.
Signed-off-by: Greg Hackmann
Signed-off-by: Paul Lawrence
Signed-off-by: Greg Hackmann
Signed-off-by: Paul Lawrence
---
lib/test_kasan.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/lib/test_kasan.c b/lib/test_kasan.c
index ef1a3ac1397e..2724f86c4cef 100644
---
On Mon, Dec 04, 2017 at 08:59:35PM +0200, Marcus Wolf wrote:
>
> Am 04.12.2017 um 12:33 schrieb Dan Carpenter:
> > On Sun, Dec 03, 2017 at 04:17:26PM +0100, Simon Sandström wrote:
> > > diff --git a/drivers/staging/pi433/pi433_if.h
> > > b/drivers/staging/pi433/pi433_if.h
> > > index
clang's AddressSanitizer implementation adds redzones on either side of
alloca()ed buffers. These redzones are 32-byte aligned and at least 32
bytes long.
__asan_alloca_poison() is passed the size and address of the allocated
buffer, *excluding* the redzones on either side. The left redzone
On Wed, Nov 15, 2017 at 2:51 PM, Alan Tull wrote:
Gentle reminder, this patch set is pretty straightforward, could use
some reviewing.
Alan
> This patch set goes on top of v6 of the non-dt support patchset that has
> been acked and I've asked Greg KH to send upstream.
>
>
Hi,
On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> As you reported that the PLL lock failure message is not printed, the
> failure can only come from either the extra delay introduced by the
> above loop, or from reading the HDMI_PHY_STAT0 register.
>
> How many iterations of the for loop
On Mon, Dec 04, 2017 at 12:11:22PM +0100, Gomonovych, Vasyl wrote:
> Hi Christoffer
>
> It is just syntax sugar of course
> and in mentioned function context it looks harmonically because it is
> in the end of function return statement.
> But in context of around source files it is looks not so
On 12/04/2017 08:59 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.86 release.
> There are 12 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Mon, Dec 04, 2017 at 05:01:20PM +0800, andy.t...@nxp.com wrote:
> From: Yuantian Tang
>
> These PP2C and PP3C registers control the configuration of the PHY
> control OOB timing for the COMINIT/COMWAKE parameters respectively
> for sata port. Overwrite default values with
Commit-ID: 10c9a5346f7200f5150608742075470612f9eadb
Gitweb: https://git.kernel.org/tip/10c9a5346f7200f5150608742075470612f9eadb
Author: Kirill A. Shutemov
AuthorDate: Mon, 4 Dec 2017 15:40:55 +0300
Committer: Thomas Gleixner
Commit-ID: eabf2a604e0555b8f86a2c6c05c3a27496facf6d
Gitweb: https://git.kernel.org/tip/eabf2a604e0555b8f86a2c6c05c3a27496facf6d
Author: Kirill A. Shutemov
AuthorDate: Mon, 4 Dec 2017 15:40:56 +0300
Committer: Thomas Gleixner
Hello,
On Mon, Dec 04, 2017 at 10:44:49AM +0530, Prateek Sood wrote:
> Any feedback/suggestion for this patch?
Sorry about the delay. I'm a bit worried because it feels like we're
chasing a squirrel. I'll think through the recent changes and this
one and get back to you.
Thanks.
--
tejun
On 2017-12-04 08:08 AM, Arnd Bergmann wrote:
> Building the DCN 1.0 Raven display driver with CONFIG_KCOV_INSTRUMENT_ALL=y
> and CONFIG_KCOV_ENABLE_COMPARISONS=y results in warnings about many functions
> that do a comparison of floating-point variables:
>
>
==Background==
The fsl_ssi driver was designed for PPC originally and then it has
been updated to support different modes for i.MX Series, including
SDMA, I2S Master mode, AC97 and older i.MXs with FIQ, by different
contributors for different use cases in different coding styles.
Additionally, in
The name fsl_ssi_rxtx_reg_val is too long to read comfortably.
So this patch shortens it by using an array (fsl_ssi_regvals,
renamed from fsl_ssi_reg_val). To do that, it also introduces
two macros (TX and RX) to replace the wrapper structure. This
will also help for further cleanups.
Meanwhile,
Shortens the variable name to save space, useful for dev_err outputs.
Signed-off-by: Nicolin Chen
---
sound/soc/fsl/fsl_ssi.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/sound/soc/fsl/fsl_ssi.c
struct device is defined in system level header files any way.
As long as fsl_ssi.h is included after those header files, it
should be safe to remove this line.
Signed-off-by: Nicolin Chen
---
sound/soc/fsl/fsl_ssi.h | 2 --
1 file changed, 2 deletions(-)
diff --git
On Mon, Dec 4, 2017 at 9:36 PM, Deepa Dinamani wrote:
> On Mon, Dec 4, 2017 at 6:21 AM, Arnd Bergmann wrote:
>> On Mon, Dec 4, 2017 at 1:55 AM, Deepa Dinamani
>> wrote:
>>> struct timeval which is part of struct input_event to
>>>
On Mon, Dec 04, 2017 at 08:46:24PM +0530, Vijendar Mukunda wrote:
> added additional error checks in acp dma driver
> v2: printed error codes for acp init & acp deinit
> failure cases.
Don't include noise like inter-version changelogs in commit messages,
add them after the --- if they're
On Mon, 4 Dec 2017, Linus Torvalds wrote:
> On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> >
> > Kernel Page Table Isolation, prefix kpti_
> >
> >Linus, your call :)
>
> I think you probably chose the right name here. The alternatives sound
> intriguing, but
On Wed, Nov 22, 2017 at 08:43:18PM +0900, Katsuhiro Suzuki wrote:
> sound/soc/uniphier/Makefile | 4 +
> sound/soc/uniphier/aio-core.c| 368 +
> sound/soc/uniphier/aio-dma.c | 266 +++
> sound/soc/uniphier/aio-regctrl.c | 699
>
On Mon, Dec 4, 2017 at 5:44 PM, Al Viro wrote:
> On Thu, Nov 02, 2017 at 04:05:01AM -0700, syzbot wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 3a99df9a3d14cd866b5516f8cba515a3bfd554ab
>>
On Mon, Dec 04, 2017 at 03:38:56PM +, David Howells wrote:
> Paul E. McKenney wrote:
>
> > - Q = READ_ONCE(P); smp_read_barrier_depends(); D = READ_ONCE(*Q);
> > + Q = READ_ONCE(P); D = READ_ONCE(*Q);
> >
> > the CPU will issue the following memory
On Sat, Dec 02, 2017 at 12:19:27PM +, Jonathan Cameron wrote:
> > diff --git a/drivers/iio/accel/bmc150-accel.h
> > b/drivers/iio/accel/bmc150-accel.h
> > index c38754452883..7f49a09b136f 100644
> > --- a/drivers/iio/accel/bmc150-accel.h
> > +++ b/drivers/iio/accel/bmc150-accel.h
> > @@ -47,6
From: Andrey Ryabinin
LLVM doesn't understand GCC-style paramters ("--param asan-foo=bar"),
thus we currently we don't use inline/globals/stack instrumentation
when building the kernel with clang.
Add support for LLVM-style parameters ("-mllvm -asan-foo=bar") to
enable
[PATCH v3 1/5] kasan: add compiler support for clang
No change
[PATCH v3 2/5] kasan/Makefile: Support LLVM style asan parameters.
Correctly attributed
Changed to use strip to work in all environments
[PATCH v3 3/5] kasan: support alloca() poisoning
No change
[PATCH v3 4/5] kasan: Add
Hi Rob,
On Mon, Dec 4, 2017 at 8:35 PM, Rob Herring wrote:
> On Mon, Dec 4, 2017 at 9:47 AM, Geert Uytterhoeven
> wrote:
>> The special overlay mutex is taken first, hence it should be released
>> last in the error path.
>>
>> Move
Commit-ID: e085ac7a6ddbd746966083c5e13aa290c3e9a253
Gitweb: https://git.kernel.org/tip/e085ac7a6ddbd746966083c5e13aa290c3e9a253
Author: Xie XiuQi
AuthorDate: Mon, 4 Dec 2017 17:54:37 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017
On 12/04/2017 10:32 AM, Dan Carpenter wrote:
> On Sat, Dec 02, 2017 at 10:05:20PM +0100, Tomas Marek wrote:
>> @@ -578,13 +546,9 @@ static irqreturn_t DIO1_irq_handler(int irq, void
>> *dev_id)
>> SET_CHECKED(rf69_set_mode(spi, standby)); /* this clears the
>> fifo */
>>
On Mon, Nov 13, 2017 at 09:08:48PM +, Alan Cox wrote:
> On Mon, 13 Nov 2017 18:42:50 +0100
> "Luis R. Rodriguez" wrote:
>
> > On Sat, Nov 11, 2017 at 02:32:40AM +, Alan Cox wrote:
> > > > My assumption here is:
> > > > 1) there are some less important and so
On Mon, Dec 4, 2017 at 6:03 PM, Jann Horn wrote:
> As far as I can tell, commit b03c9f9fdc37 ("bpf/verifier: track signed
> and unsigned min/max values") introduced the following effectless bug
> in the BPF_RSH case of adjust_scalar_min_max_vals() (unless that's
> intentional):
Hi Chris,
Given commit
8ee5ad1d4c0b ("arch/tile: mark as orphaned")
in Linus' tree, should I remove the tile tree from linux-next?
--
Cheers,
Stephen Rothwell
On 12/04/2017 08:59 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.67 release.
> There are 38 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Wed, Nov 29, 2017 at 12:11 AM, Moritz Fischer wrote:
> Hi Hao,
>
> On Mon, Nov 27, 2017 at 02:42:09PM +0800, Wu Hao wrote:
>> This patch adds region_id to fpga_image_info data structure, it
>> allows driver to pass region id information to fpga-mgr via
>> fpga_image_info for
On Mon, Dec 4, 2017 at 8:11 AM, Andrey Smirnov wrote:
> Add a driver for RAVE Supervisory Processor, an MCU implementing
> various bits of housekeeping functionality (watchdoging, backlight
> control, LED control, etc) on RAVE family of products by Zodiac
> Inflight
This patch rewrites the mouse report fixup used for the DEFT and HUGE
ELECOM trackballs in order to make it generic enough to fix other ELECOM
mice with similar issues. This patch also uses this new report fixup
function to fix the ELECOM EX-G trackball which has 6 physical buttons
and a similar
All
After creating a new LED driver for the LM3692x device I went back to the
LP8860 driver that I authored and found some updates that need to be applied.
First the way the LP8860 retrieved the label from the DT was incorrect as the
label should have been from a child node as opposed to the
Advice about what to use as a unique identifier is no longer valid since
patch series was merged to hash pointers printed with %p. We can use
this as a unique identifier now.
Signed-off-by: Tobin C. Harding
---
Documentation/security/self-protection.rst | 4 ++--
1 file changed,
On Wed, Nov 15, 2017 at 02:51:48PM -0600, Alan Tull wrote:
> Part of patchset that changes the following fpga_*_register
> functions to not set drvdata:
> * fpga_region_register.
> * fpga_mgr_register
> * fpga_bridge_register
>
> The rationale is that setting drvdata is fine for DT based devices
On 12/4/2017 11:23 AM, Rob Herring wrote:
> On Fri, Dec 1, 2017 at 10:27 PM, Sinan Kaya wrote:
>> Now that we have a get_match_data() callback as part of the firmware node,
>> implement the OF specific piece for it.
>>
>> Signed-off-by: Sinan Kaya
>>
[+Ard]
Hi Cyrille,
On Sun, Dec 03, 2017 at 09:44:46PM +0100, Cyrille Pitchen wrote:
[...]
> >> +cdns_pci_map_bus(struct pci_bus *bus, unsigned int devfn, int where)
> >> +{
> >> + struct pci_host_bridge *bridge = pci_find_host_bridge(bus);
> >> + struct cdns_pcie_rc *rc =
To increase the readability of the register accesses, the abstraction
of the helpers was increased from simple read and write to set bit,
reset bit and read modify write bit. In addition - according to the
proposal from Walter Harms from 20.07.2017 - instead of marcros inline
functions were used.
On Mon, Dec 4, 2017 at 7:56 AM, Will Deacon wrote:
> On Fri, Dec 01, 2017 at 12:10:00PM -0800, Kees Cook wrote:
>> Distros have been shipping with CONFIG_STRICT_DEVMEM=y for years now. It
>> is probably time to flip this default for x86 and arm64.
>
> Should we be defaulting
On Mon, Dec 04, 2017 at 03:07:20PM +0100, Thomas Gleixner wrote:
> From: Andy Lutomirski
>
> This has a secondary purpose: it puts the entry stack into a region
> with a well-controlled layout. A subsequent patch will take
> advantage of this to streamline the SYSCALL entry
On 12/4/2017 10:34 AM, Kirill A. Shutemov wrote:
On Mon, Dec 04, 2017 at 04:00:26PM +, Tom Lendacky wrote:
On 12/4/2017 8:57 AM, Kirill A. Shutemov wrote:
On Mon, Dec 04, 2017 at 08:19:11AM -0600, Tom Lendacky wrote:
On 12/4/2017 5:23 AM, Kirill A. Shutemov wrote:
sme_populate_pgd()
In cases where group_info is cached (e.g. sunrpc), multiplpe
threads may call set_groups with a freshly created group_info
cache (e.g. nfsd), and attempt to sort them simultaneously,
which configures a race condition that can overwrite some
groups in the cache and lead to errors. In the case of
Reviewed-by: Vidya Sagar
On Sunday 03 December 2017 03:15 AM, Bjorn Helgaas wrote:
The PCIe active link power state is L0. ASPM defines two low-power
states: L0s and L1. The L1 PM Substates feature defines two
additional low-power states: L1.1 and L2.2.
The L1.2 state may
Disregard this. git reset --hard without a git stash. Sorry about it.
On Mon, 4 Dec 2017, Thiago Rafael Becker wrote:
The responsibility for calling groups_sort is now on the caller
of set_groups.
Signed-off-by: Thiago Rafael Becker
---
kernel/groups.c | 1
Add a flag to struct device_node marking the node as a valid target
for device tree overlays. When an overlay is submitted, if any target
in the overlay is not enabled for overlays, the overlay is rejected.
Drivers that support dynamic configuration can enable/disable their
device node with:
Allow DT nodes to be marked as valid targets for DT
overlays by the added "overlay-allowed" property.
Signed-off-by: Alan Tull
---
drivers/of/base.c | 4 ++--
drivers/of/dynamic.c| 3 +++
drivers/of/fdt.c| 3 +++
drivers/of/of_private.h | 2 ++
4 files
On 30/11/2017 at 13:17:40 -0800, Guenter Roeck wrote:
> > I think it's a bugfix; it fixes real problems where the application
> > misbehave due to faulty content when reading from an eeprom. I'm
> > expecting to make a new release for the hw in question RSN and these
> > are the only local
On Mon, Nov 27, 2017 at 9:15 PM, Wu Hao wrote:
> On Mon, Nov 27, 2017 at 10:28:04AM +, David Laight wrote:
>> From: Wu Hao
>> > Sent: 27 November 2017 06:42
>> > From: Zhang Yi
>> >
>> > The Intel FPGA device appears as a PCIe device on the system.
On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
> Add a document for Intel FPGA driver overview.
>
> Signed-off-by: Enno Luebbers
> Signed-off-by: Xiao Guangrong
> Signed-off-by: Wu Hao
>
> v2:
On Mon, Dec 04, 2017 at 09:31:06PM +0200, Marcus Wolf wrote:
> > > Then it might be, that DATAMODUL_MODE_PACKET might need an other value.
> >
> > That's future code so we can delete that sentence for now.
>
> With the rule above, you are absolutely right. But we now spend time, to
> remove an
On 12/04/2017 08:59 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.104 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Mon, Dec 4, 2017 at 6:29 AM, Arnd Bergmann wrote:
> On Mon, Dec 4, 2017 at 1:55 AM, Deepa Dinamani wrote:
>> struct timeval is not y2038 safe.
>> All usage of timeval in the kernel will be replaced by
>> y2038 safe structures.
>> The change is also
On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
Hi Hao,
mgr->status isn't used anywhere except in status_show. So we don't
need to add status to the fpga_manager struct. Also don't need the
inline function to update it. Just read the status in status_show, if
that ops
Hi Michael,
I was hoping to get a clear statement one way or another from the kernel
maintainers as to whether an EINTR from stat() is supposed to be allowed
kernel behavior (hence the RFC in the subject). If it's not, then I don't think
it should be documented, even if there is buggy filesystems
On Mon, Dec 04, 2017 at 09:29:45PM +0100, Thomas Gleixner wrote:
> On Mon, 4 Dec 2017, Kirill A. Shutemov wrote:
>
> > This patch prepare decompression code to boot-time switching between 4-
> > and 5-level paging.
>
> This is the very wrong reason for tagging this commit stable.
>
> >
> >
Add the full text of the MIT license to the kernel tree. It was copied
directly from:
https://spdx.org/licenses/MIT.html#licenseText
Add the required tags for reference and tooling.
Signed-off-by: Thomas Gleixner
Reviewed-by: Philippe Ombredanne
On Mon, Dec 4, 2017 at 1:22 PM, Tobin C. Harding wrote:
> Advice about what to use as a unique identifier is no longer valid since
> patch series was merged to hash pointers printed with %p. We can use
> this as a unique identifier now.
>
> Signed-off-by: Tobin C. Harding
The platform_get_irq() function returns negative number if an error
occurs, Zero if No irq is found and positive number if irq gets successful.
platform_get_irq() error checking only for zero is not correct.
Signed-off-by: Arvind Yadav
---
changes in v2:
On 4 December 2017 at 14:02, Jose Abreu wrote:
> On 04-12-2017 13:16, Alexey Brodkin wrote:
>> Option "kmsdev" "/dev/dri/card1"
>
> Which drm driver uses /dev/dri/card0? I'm seing drmOpen code and
> if you don't specify the busID it will fallback for the
Olof Johansson writes:
> Thanks, Stephen. I need to get a similar script going to catch these
> things in our own tree.
>
> Since this was a clean revert, I've redone it myself, carrying over
> descriptions from the pull request and keeping attribution to Kevin.
>
> Kevin; hope
This adds the devicetree bindings for the LM3692x
I2C LED string driver.
Acked-by: Pavel Machek
Signed-off-by: Dan Murphy
---
v7 - No changes - https://patchwork.kernel.org/patch/10087475/
v6 - No changes -https://patchwork.kernel.org/patch/10085567/
v5 - No
The patch
ASoC: uniphier: add DT bindings documentation for UniPhier EVEA
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: uniphier: add support for UniPhier EVEA codec
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
On 4 December 2017 at 18:20, Lorenzo Pieralisi
wrote:
> [+Ard]
>
> Hi Cyrille,
>
> On Sun, Dec 03, 2017 at 09:44:46PM +0100, Cyrille Pitchen wrote:
>
> [...]
>
>> >> +cdns_pci_map_bus(struct pci_bus *bus, unsigned int devfn, int where)
>> >> +{
>> >> + struct
The patch
ASoC: amd: added error checks in dma driver
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
ASoC: eukrea-tlv320: Remove include line of fsl_ssi.h
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
When the group_info is cached (e.g. sunrpc) there's the possibility
that threads calling set_groups will attempt to do so simultaneously.
Moving the responsibility of sorting to the caller of set_groups, or
in the case of nfsd, to the point where it is received from rpc.mountd
avoids this issue.
In preparation to move group_info sorting to the caller,
make group_sort globally visible.
Signed-off-by: Thiago Rafael Becker
---
include/linux/cred.h | 1 +
kernel/groups.c | 4 +++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git
The responsibility for calling groups_sort is now on the caller
of set_groups.
Signed-off-by: Thiago Rafael Becker
---
kernel/groups.c | 1 +
kernel/uid16.c| 1 +
net/sunrpc/svcauth_unix.c | 7 +++
3 files changed, 9 insertions(+)
diff --git
The subject is way too long.
On Mon, Dec 04, 2017 at 08:18:51PM +0200, Marcus Wolf wrote:
> To increase the readability of the register accesses, the abstraction
> of the helpers was increased from simple read and write to set bit,
> reset bit and read modify write bit. In addition - according to
On Mon, Dec 04, 2017 at 03:40:56PM +0300, Kirill A. Shutemov wrote:
> We cannot proceed booting if the machine doesn't support the paging mode
> kernel was compiled for.
>
> Getting error the usual way -- via validate_cpu() -- is not going to
> work. We need to enable appropriate paging mode
1 - 100 of 2484 matches
Mail list logo