The following set unifies the terminology for co-developed patches
(losing the capital in Developed) and adds the rule to the
checkpatch.pl script to stop warnings.
Jorge Ramirez-Ortiz (2):
docs: fix Co-Developed-by docs
checkpatch: add Co-developed-by to signature tags
As per Documentation/process/submitting-patches, Co-developed-by is a
valid signature.
This commit removes the warning.
Signed-off-by: Jorge Ramirez-Ortiz
---
scripts/checkpatch.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index
stable-rc/linux-4.4.y boot: 93 boots: 1 failed, 91 passed with 1 offline
(v4.4.167-89-g9c558d7fe359)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.167-89-g9c558d7fe359/
Full Build Summary:
stable-rc/linux-4.14.y boot: 116 boots: 1 failed, 111 passed with 2 offline, 2
untried/unknown (v4.14.88-90-g159976987c2f)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.88-90-g159976987c2f/
Full Build Summary:
Hi Bjorn,
Thanks for the review!
On 2018-12-06 12:46, Bjorn Andersson wrote:
On Tue 20 Nov 13:02 PST 2018, Sibi Sankar wrote:
After sending a sysmon shutdown request to the SSCTL service on the
subsystem, wait for the service to send shutdown-ack interrupt or
an indication message back.
So
On Sat 15-12-18 01:13:53, kbuild test robot wrote:
> Hi Michal,
>
> I love your patch! Yet something to improve:
Could you point the bot to v3 please?
http://lkml.kernel.org/r/20181213092221.27270-1-mho...@kernel.org
--
Michal Hocko
SUSE Labs
On Fri, Dec 14, 2018 at 06:20:10PM +0100, Bartosz Golaszewski wrote:
> Hi,
>
> I'm not sure what the connection is exactly but commit dcd51305cd41
> ("ALSA: hda/realtek - fix the pop noise on headphone for lenovo
> laptops") broke the mute button LED on my Lenovo X1 Extreme laptop.
>
> I don't
On Fri, Dec 14, 2018 at 09:40:24AM +0530, Taniya Das wrote:
> The CPUfreq HW present in some QCOM chipsets offloads the steps necessary
> for changing the frequency of CPUs. The driver implements the cpufreq
> driver interface for this hardware engine.
>
> Signed-off-by: Saravana Kannan
>
Hi Masami,
On Sat, 2018-12-15 at 01:31 +0900, Masami Hiramatsu wrote:
> On Mon, 10 Dec 2018 18:01:34 -0600
> Tom Zanussi wrote:
>
> > From: Tom Zanussi
> >
> > Since every var ref for a trigger has an entry in the var_ref[]
> > array,
> > use that to destroy the var_refs, instead of piecemeal
On Fri, Dec 14, 2018 at 08:27:33AM -0800, Joe Perches wrote:
> On Fri, 2018-12-14 at 21:46 +0530, Himanshu Jha wrote:
> > On Fri, Dec 14, 2018 at 07:52:15AM -0800, Joe Perches wrote:
> > > On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
> > > > As per
This patch exposes backlight control into userspace by creating a
backlight device instead of directly accessing the PWM registers.
The backlight driver can't go on a separate file as it shares the I2C
bus & address with the panel.
Signed-off-by: Nicolas Saenz Julienne
---
On Fri, Dec 14, 2018 at 03:58:19PM +0200, Matti Vaittinen wrote:
> On Fri, Dec 07, 2018 at 01:14:18PM +, Mark Brown wrote:
> > > Then we could have chip->no_of set for the 'main irq chip' and for those
> > > chips we don't wan't to expose via DT. In my case I would leave no_of
> > > unset
Le 14/12/2018 à 02:39, Sasha Levin a écrit :
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 4de9d0b547b9 crypto: talitos - Add ablkcipher algorithms.
The bot has tested the following trees: v4.19.9, v4.14.88, v4.9.145,
On Fri, 2018-12-14 at 12:48 +0100, Enric Balletbo i Serra wrote:
> There are multiple ChromeOS EC sub-drivers spread in different
> subsystems, as all of them are related to the Chrome stuff add
> Benson and myself as a maintainers for all these sub-drivers.
[]
> Changes in v3:
> - Use a
* Roger Quadros [181214 09:42]:
> Kishon,
>
> On 05/12/18 17:03, Roger Quadros wrote:
> > If clk_get() returns -EPROBE_DEFER then we should just
> > return instead of falling back to old clock name.
> >
> > Use clk_prepare_enable() and clk_disable_unprepare() instead
> > of splitting up
Hi Linus,
Please pull the arm64 fix below. Thanks.
The following changes since commit 40e020c129cfc991e8ab4736d2665351ffd1468d:
Linux 4.20-rc6 (2018-12-09 15:31:00 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
Hi,
I'm not sure what the connection is exactly but commit dcd51305cd41
("ALSA: hda/realtek - fix the pop noise on headphone for lenovo
laptops") broke the mute button LED on my Lenovo X1 Extreme laptop.
I don't have any more info frankly and don't even know where to start
debugging. Other LEDs
On Fri, Dec 14, 2018 at 12:43 AM wrote:
>
> From: Frank Rowand
>
> Non-overlay dynamic devicetree node removal may leave the node in
> the phandle cache. Subsequent calls to of_find_node_by_phandle()
> will incorrectly find the stale entry. Remove the node from the
> cache.
>
> Add paranoia
On Tue, 2018-12-11 at 14:13 -0800, Bart Van Assche wrote:
> +/*
> + * Unregister a dynamically allocated key. Must not be called from interrupt
> + * context. The caller must ensure that freeing @key only happens after an
> RCU
> + * grace period.
> + */
> +void lockdep_unregister_key(struct
On 12/14/18 17:13, Greg KH wrote:
On Fri, Dec 14, 2018 at 07:52:15AM -0800, Joe Perches wrote:
On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
As per Documentation/process/submitting-patches, Co-developed-by is a
valid signature.
This commit removes the warning.
Your commit
Hi Masami,
On Sat, 2018-12-15 at 01:18 +0900, Masami Hiramatsu wrote:
> On Mon, 10 Dec 2018 18:01:26 -0600
> Tom Zanussi wrote:
>
> > From: Tom Zanussi
> >
> > Add a test case verifying the basic functionality of the
> > hist:onchange($var) handler.
>
> This looks good to me.
>
> Acked-by:
Quoting Abel Vesa (2018-12-14 04:41:46)
> On 18-12-14 10:22:11, Lucas Stach wrote:
> > Hi Shawn,
> >
> > Am Freitag, den 14.12.2018, 09:12 +0800 schrieb Shawn Guo:
> > > On Thu, Dec 13, 2018 at 02:51:50PM +, Abel Vesa wrote:
> > > ...
> > > > > > diff --git a/arch/arm64/Kconfig.platforms
> >
Android is adopting psi to detect and remedy memory pressure that
results in stuttering and decreased responsiveness on mobile devices.
Psi gives us the stall information, but because we're dealing with
latencies in the millisecond range, periodically reading the pressure
files to detect stalls
The psi monitoring patches will need to determine the same states as
record_times(). To avoid calculating them twice, maintain a state mask
that can be consulted cheaply. Do this in a separate patch to keep the
churn in the main feature patch at a minimum.
Signed-off-by: Suren Baghdasaryan
---
Psi monitor aims to provide a low-latency short-term pressure
detection mechanism configurable by users. It allows users to
monitor psi metrics growth and trigger events whenever a metric
raises above user-defined threshold within user-defined time window.
Time window is expressed in usecs and
Hi Masami,
On Fri, 2018-12-14 at 22:11 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> On Mon, 10 Dec 2018 18:01:17 -0600
> Tom Zanussi wrote:
>
> > From: Tom Zanussi
> >
> > Add abbreviated documentation for handlers and actions to README.
>
> This change itself is good to me, and I would
From: Johannes Weiner
psi currently stops its periodic 2s aggregation runs when there has
not been any task activity, and wakes it back up later from the
scheduler when the system returns from the idle state.
The coordination between the aggregation worker and the scheduler is
minimal: the
From: Johannes Weiner
Kernfs has a standardized poll/notification mechanism for waking all
pollers on all fds when a filesystem node changes. To allow polling
for custom events, add a .poll callback that can override the default.
This is in preparation for pollable cgroup pressure files which
From: Johannes Weiner
Cgroup has a standardized poll/notification mechanism for waking all
pollers on all fds when a filesystem node changes. To allow polling
for custom events, add a .poll callback that can override the default.
This is in preparation for pollable cgroup pressure files which
Renaming psi_group structure member fields used for calculating psi
totals and averages for clear distinction between them and trigger-related
fields that will be added next.
Signed-off-by: Suren Baghdasaryan
---
include/linux/psi_types.h | 15 ---
kernel/sched/psi.c| 26
On Fri, Dec 14, 2018 at 12:43 AM wrote:
>
> From: Frank Rowand
>
> The phandle cache contains struct device_node pointers. The refcount
> of the pointers was not incremented while in the cache, allowing use
> after free error after kfree() of the node. Add the proper increment
> and decrement
Hi Michal,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc6 next-20181214]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Thu, Dec 13, 2018 at 8:33 PM YueHaibing wrote:
> On 2018/12/14 7:42, Paul Moore wrote:
> > On Sun, Dec 9, 2018 at 1:25 AM YueHaibing wrote:
> >> Remove duplicated include.
> >>
> >> Signed-off-by: YueHaibing
> >> ---
> >> kernel/audit.c | 1 -
> >> 1 file changed, 1 deletion(-)
> >>
> >>
> On Dec 14, 2018, at 5:48 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Thu, Dec 13, 2018 at 09:48:57PM +, Song Liu escreveu:
>>
>>
>>> On Dec 13, 2018, at 10:45 AM, Peter Zijlstra wrote:
>>>
>>> On Wed, Dec 12, 2018 at 01:33:20PM -0500, Steven Rostedt wrote:
On Wed, 12 Dec 2018
> -Original Message-
> From: Schrempf Frieder
> Sent: Tuesday, December 4, 2018 8:15 AM
> To: linux-...@lists.infradead.org; boris.brezil...@bootlin.com; linux-
> s...@vger.kernel.org; Marek Vasut
> Cc: dw...@infradead.org; computersforpe...@gmail.com;
> rich...@nod.at;
On Fri, Dec 14, 2018 at 07:38:30AM -0800, Sean Christopherson wrote:
> On Fri, Dec 14, 2018 at 07:12:04AM -0800, Sean Christopherson wrote:
> > On Fri, Dec 14, 2018 at 09:55:49AM +, Jethro Beekman wrote:
> > > On 2018-12-14 03:01, Sean Christopherson wrote:
> > > >+2: pop %rbx
> > >
Hi folks,
On 11/29/18 9:12 AM, Greg Kroah-Hartman wrote:
> 4.19-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Erik Schmauss
>
> commit 4abb951b73ff0a8a979113ef185651aa3c8da19b upstream.
>
> The table load process omitted adding the
From: Jakob Wuhrer
msm8996 has 12 uarts, but the devicetree only lists 3. Add the
pinmuxing and the main devicetree entries for the others.
Signed-off-by: Jakob Wuhrer
---
arch/arm64/boot/dts/qcom/msm8996-pins.dtsi | 524 +
arch/arm64/boot/dts/qcom/msm8996.dtsi
From: Jakob Wuhrer
gpiio5 is missspelt in msm8996-pins.dtsi, fix that.
Signed-off-by: Jakob Wuhrer
---
arch/arm64/boot/dts/qcom/msm8996-pins.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8996-pins.dtsi
tch/livepatch_shadow_fix2/enabled
echo 0 > /sys/kernel/livepatch/livepatch_shadow_fix1/enabled
rmmod livepatch-shadow-fix2
rmmod livepatch-shadow-fix1
rmmod livepatch-shadow-mod
and dmesg output checked.
Patch is against 4.20-rc6 (localversion-next is next-20181214)
samples/liv
ainst 4.20-rc6 (localversion-next is next-20181214)
on top of 0001-livepatch-fix-non-static-warnings.patch
samples/livepatch/livepatch-shadow-fix1.c | 5 +
samples/livepatch/livepatch-shadow-mod.c | 4
2 files changed, 9 insertions(+)
diff --git a/samples/livepatch/livepatch-shadow
On Fri, Dec 14, 2018 at 5:53 PM Michal Hocko wrote:
>
> On Fri 14-12-18 15:31:44, Dmitry Vyukov wrote:
> > On Fri, Dec 14, 2018 at 2:54 PM Michal Hocko wrote:
> > >
> > > On Fri 14-12-18 14:42:33, Dmitry Vyukov wrote:
> > > > On Fri, Dec 14, 2018 at 2:28 PM Michal Hocko wrote:
> > > > >
> > > >
On 13.12.2018 21:14, Uwe Kleine-König wrote:> On Thu, Dec 13, 2018 at
06:00:00PM +0100, Thierry Reding wrote:
>> On Thu, Dec 13, 2018 at 09:52:13AM +0100, Uwe Kleine-König wrote:
>>> On Wed, Dec 12, 2018 at 11:54:32AM +0100, Thierry Reding wrote:
On Mon, Oct 01, 2018 at 04:19:48PM +0200,
On Thu, Dec 13, 2018 at 08:20:15PM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Fri, Dec 14, 2018 at 05:38:33PM +0100, Florian Weimer wrote:
> * Rich Felker:
>
> > This is all useless (and wrong since tv_nsec is required to have type
> > long as part of C and POSIX, regardless of ILP32-vs-LP64; that's a bug
> > in glibc's x32).
>
> We should be able to fix standards if
On Thu, Dec 13, 2018 at 08:21:11PM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Fri 14-12-18 15:31:44, Dmitry Vyukov wrote:
> On Fri, Dec 14, 2018 at 2:54 PM Michal Hocko wrote:
> >
> > On Fri 14-12-18 14:42:33, Dmitry Vyukov wrote:
> > > On Fri, Dec 14, 2018 at 2:28 PM Michal Hocko wrote:
> > > >
> > > > On Fri 14-12-18 14:11:05, Dmitry Vyukov wrote:
> > > > > On Fri,
karg.hdr.id and port are indirectly controlled by user-space, hence leading
to a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
drivers/message/fusion/mptctl.c:1360 mptctl_getiocinfo() warn: potential
spectre issue 'ioc->pfacts'
On Fri, Dec 14, 2018 at 5:56 AM Richard Weinberger
wrote:
>
> [CC'ing Kees]
>
> On Wed, Dec 12, 2018 at 1:37 PM Markus F.X.J. Oberhumer
> wrote:
> >
> > I still claim that (0xf000, 4096) is not a valid C "pointer
> > to an object" according to the C standard - please see my reply
On Fri, Dec 14, 2018 at 01:00:26PM +0100, Christian Zigotzky wrote:
> On 12 December 2018 at 3:15PM, Christoph Hellwig wrote:
> > Thanks for bisecting. I've spent some time going over the conversion
> > but can't really pinpoint it. I have three little patches that switch
> > parts of the code
On Sat, Dec 15, 2018 at 12:29:11AM +1100, Michael Ellerman wrote:
> I think the problem is that we don't want to set iommu_bypass_supported
> unless cell_iommu_fixed_mapping_init() succeeds.
>
> Yep. This makes it work for me on cell on top of your v5.
Thanks, this looks good. I've folded it
On 12.12.2018 11:51, Uwe Kleine-König wrote:
> Hello,
>
> On Mon, Oct 01, 2018 at 04:19:48PM +0200, Michal Vokáč wrote:
>> Implement the get_state() function and set the initial state to reflect
>> real state of the hardware. This allows to keep the PWM running if it was
>> enabled in bootloader.
On Thu, Dec 13, 2018 at 08:21:31PM +, Fabrizio Castro wrote:
> This patch adds bindings for the r8a774c0 (RZ/G2E).
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On 14/12/2018 15:49, Ard Biesheuvel wrote:
> On Fri, 14 Dec 2018 at 16:23, Julien Thierry wrote:
>>
>> Hi,
>>
>> On 13/12/2018 15:03, Julien Thierry wrote:
>>>
>>> Argh, not as simple as I had expected.
>>>
>>> Turns out include/linux/efi.h does not include asm/efi.h (including it
>>> at the
* Rich Felker:
> This is all useless (and wrong since tv_nsec is required to have type
> long as part of C and POSIX, regardless of ILP32-vs-LP64; that's a bug
> in glibc's x32).
We should be able to fix standards if they prove unworkable in practice.
In my opinion, if standards require complex
On Thu, Dec 13, 2018 at 08:17:54PM +, Fabrizio Castro wrote:
> RZ/G2E (R8A774C0) SoC also has the R-Car Gen3 compatible SCIF and
> HSCIF ports, so document the SoC specific bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Fri, Dec 14, 2018 at 05:09:44PM +0100, Antoine Tenart wrote:
> Hi Russell,
>
> On Fri, Dec 14, 2018 at 04:02:50PM +, Russell King - ARM Linux wrote:
> > On Fri, Dec 14, 2018 at 10:34:51AM +0100, Antoine Tenart wrote:
> > > The mvpp2_phylink_validate() function sets all modes that are
> > >
On Thu, Dec 13, 2018 at 08:25:42PM -0500, Lyude Paul wrote:
> There has been a TODO waiting for quite a long time in
> drm_dp_mst_topology.c:
>
> /* We cannot rely on port->vcpi.num_slots to update
>* topology_state->avail_slots as the port may not exist if the parent
>*
On Thu, Dec 13, 2018 at 08:19:02PM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) I2C compatibility with the relevant driver
> dt-bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Thu, Dec 13, 2018 at 08:22:27PM +, Fabrizio Castro wrote:
> From: Biju Das
>
> We need r8a774c0 to be whitelisted for SDHI to work on the RZ/G2E,
> but we don't care about the revision of the SoC, so just whitelist
> the generic part number.
>
> Signed-off-by: Biju Das
Reviewed-by:
On Thu, Dec 13, 2018 at 08:22:09PM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
Now that we allow CONFIG_PCI to be unset, remove useless code from ACPICA
too.
Signed-off-by: Sinan Kaya
---
drivers/acpi/acpica/Makefile| 2 +-
drivers/acpi/acpica/achware.h | 9 +
include/acpi/platform/aclinux.h | 4
3 files changed, 14 insertions(+), 1 deletion(-)
diff
ACPI and PCI are no longer coupled to each other. Specify requirements
for both when pulling in code.
Signed-off-by: Sinan Kaya
---
arch/arm64/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index ea2ab0330e3a..bcb6262044d8
ACPI IORT table code relies on pci_request_acs() to be present. Define
a stub function when CONFI_PCI is not set.
Signed-off-by: Sinan Kaya
---
include/linux/pci.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/linux/pci.h b/include/linux/pci.h
index 51a5a5217667..f0f2f55ea93c
Make PCI reboot conditional on PCI support being present on the kernel
configuration.
Signed-off-by: Sinan Kaya
---
drivers/acpi/reboot.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/acpi/reboot.c b/drivers/acpi/reboot.c
index 6fa9c2a4cfe9..d75e637ee36a
We are compiling PCI code today for systems with ACPI and no PCI
device present. Remove the useless code and reduce the tight
dependency.
Signed-off-by: Sinan Kaya
---
arch/x86/include/asm/pci_x86.h | 7 +++
drivers/acpi/Kconfig | 1 -
drivers/acpi/Makefile | 2 +-
Getting ready to allow CONFIG_PCI to be unset with ACPI enabled. Stub out
acpi_os_read_pci_configuration and acpi_os_write_pci_configuration
functions when CONFIG_PCI is not defined.
Signed-off-by: Sinan Kaya
---
drivers/acpi/osl.c | 14 ++
1 file changed, 14 insertions(+)
diff
--
Dear customer,
As part of annual program of IMF in the fight against global poverty,
we wish to inform you that you are a beneficiary of $1 Million.
To receive your Visa card, contact: i...@visatmonline.com
Thanks
Ann
On 14/12/2018 17:17, Rich Felker wrote:
> On Fri, Dec 14, 2018 at 03:13:10PM +0100, Bernd Petrovitsch wrote:
[..]
>> FWIW I have
>> snip
>> #if defined __x86_64__
>> # if defined __ILP32__ // x32
>> # define PRI_time_t "lld" // for time_t
>> # define PRI_nsec_t "lld"
On Fri, Dec 14, 2018 at 08:41:47AM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On 12/13/2018 11:18 PM, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Sergei Shtylyov
MBR, Sergei
On Mon, 10 Dec 2018 18:01:34 -0600
Tom Zanussi wrote:
> From: Tom Zanussi
>
> Since every var ref for a trigger has an entry in the var_ref[] array,
> use that to destroy the var_refs, instead of piecemeal via the field
> expressions.
>
> This allows us to avoid having to keep and treat
Hi Doug,
Thanks for the review!
On 2018-12-14 03:47, Doug Anderson wrote:
Hi,
On Tue, Nov 27, 2018 at 12:58 AM Sibi Sankar
wrote:
This patch adds Q6V5 MSS remoteproc node for SDM845 SoCs.
Signed-off-by: Sibi Sankar
---
The remoteproc mss node depends on the following bindings:
Le ven. 14 déc. 2018 à 17:23, Florian Westphal a écrit :
> I won't send a patch to remove your work, at least not at this time.
>
> In case I'd do this removal (thresholds, hash table, or both)
> i will make these tests to see how large the impact is.
Perfect, thanks
Christophe
On 12/14/2018 4:19 AM, Rafael J. Wysocki wrote:
On Fri, Dec 14, 2018 at 4:13 AM Sinan Kaya wrote:
We are compiling PCI code today for systems with ACPI and no PCI
device present. Remove the useless code and reduce the tight
dependency.
Signed-off-by: Sinan Kaya
Bjorn, any objections here?
On Fri, Dec 14, 2018 at 7:54 AM Christoph Paasch wrote:
> To clarify: Backport to v4.19.x is needed. The backport to v4.14 and older
> should not be needed.
Sure, but this does not cause any harm.
No further action needed :)
<<< No Message Collected >>>
On Thu, Dec 13, 2018 at 08:22:34PM +, Fabrizio Castro wrote:
> Similarly to R-Car E3, RZ/G2E doesn't come with automatic
> transmission registers, as such it is not considered compatible
> with the existing fallback bindings.
>
> Add SoC specific binding compatibility to allow for later
>
On 2018-12-12 08:03, Paul Moore wrote:
> On Fri, Nov 16, 2018 at 12:34 PM Richard Guy Briggs wrote:
> > On user and remote filesystems, a forced umount can still hang due to
> > attemting to fetch the fcaps of a mounted filesystem that is no longer
> > available.
> >
> > These two patches take
On Fri, 2018-12-14 at 21:46 +0530, Himanshu Jha wrote:
> On Fri, Dec 14, 2018 at 07:52:15AM -0800, Joe Perches wrote:
> > On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
> > > As per Documentation/process/submitting-patches, Co-developed-by is a
> > > valid signature.
> > >
> > >
Hi James,
Please pull these seccomp fixes for -next.
Thanks!
-Kees
The following changes since commit fec7b6690541b8128663a13c9586b1daf42b0a6c:
samples: add an example of seccomp user trap (2018-12-11 16:32:11 -0800)
are available in the Git repository at:
of
function 'is_module_sig_enforced' [-Werror=implicit-function-declaration]
sig_enforce = is_module_sig_enforced();
^
Needs:
---
security/integrity/ima/ima_main.c |1 +
1 file changed, 1 insertion(+)
--- linux-next-20181214.orig/security/integrity/ima/ima_main.c
+++ linux-next-20181
On Tue, Dec 11, 2018 at 04:50:34PM -0800, Kees Cook wrote:
> On Mon, Dec 10, 2018 at 7:41 PM wrote:
> >
> > From: Yulei Zhang
> >
> > Early this year we spot there may be two issues in kernel
> > kfifo.
> >
> > One is reported by Xiao Guangrong to linux kernel.
> >
On Thu, Dec 13, 2018 at 08:22:44PM +, Fabrizio Castro wrote:
> Support RZ/G2E (a.k.a. R8A774C0) IPMMU.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Thu, Dec 13, 2018 at 08:22:27PM +, Fabrizio Castro wrote:
> From: Biju Das
>
> We need r8a774c0 to be whitelisted for SDHI to work on the RZ/G2E,
> but we don't care about the revision of the SoC, so just whitelist
> the generic part number.
>
> Signed-off-by: Biju Das
Reviewed-by:
Christophe Gouault wrote:
> The main use cases I have encountered and tried to address with the
> hash-based lookup were network operator use cases:
> - a lot of dynamic /32 <=> /32 policies (protecting GTP tunnels)
> - or a lot of dynamic policies with the same prefix lengths (e.g. /16 <=> /24)
On Thu, Dec 13, 2018 at 08:23:10PM +, Fabrizio Castro wrote:
> Add thermal support for the RZ/G2E SoC (a.k.a. R8A774C0).
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
Hi,
On Thu, Dec 13, 2018 at 8:52 PM Bjorn Andersson
wrote:
>
> On Thu 13 Dec 14:17 PST 2018, Doug Anderson wrote:
> > On Tue, Nov 27, 2018 at 12:58 AM Sibi Sankar wrote:
> [..]
> > > diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> > > b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> > > index
On Mon, 10 Dec 2018 18:01:26 -0600
Tom Zanussi wrote:
> From: Tom Zanussi
>
> Add a test case verifying the basic functionality of the
> hist:onchange($var) handler.
This looks good to me.
Acked-by: Masami Hiramatsu
BTW, could you sort these test patches at the end of this series?
(or at
On Fri, Dec 14, 2018 at 03:13:10PM +0100, Bernd Petrovitsch wrote:
> On 13/12/2018 17:02, Rich Felker wrote:
> > On Tue, Dec 11, 2018 at 11:29:14AM +0100, John Paul Adrian Glaubitz wrote:
> >> I can't say anything about the syscall interface. However, what I do know
> >> is that the weird
On Thu, Dec 13, 2018 at 08:18:34PM +, Fabrizio Castro wrote:
> Document RZ/G2E (R8A774C0) SoC bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Fri, Dec 14, 2018 at 07:52:15AM -0800, Joe Perches wrote:
> On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
> > As per Documentation/process/submitting-patches, Co-developed-by is a
> > valid signature.
> >
> > This commit removes the warning.
>
> Your commit message doesn't
Paul Kocialkowski writes:
> Despite what the HVS documentation indicates, the VC4 does not actually
> support SAND tiling modes for any RGB format and only semiplanar YUV420
> formats (NV12/NV21) can be used in these tiling modes.
>
> The driver currently claims to support RGB formats for the
Hi,
On Fri, Dec 14, 2018 at 3:18 PM Torsten Duwe wrote:
>
> On Thu, Dec 13, 2018 at 11:01:38PM +0530, Amit Daniel Kachhap wrote:
> > On Fri, Nov 30, 2018 at 9:53 PM Torsten Duwe wrote:
> >
> > Hi Torsten,
> >
> > I was testing your patch and it seems to work fine for function trace.
> > However
On Mon, 10 Dec 2018 18:01:23 -0600
Tom Zanussi wrote:
> From: Tom Zanussi
>
> Add a test case verifying the basic functionality of the
> hist:snapshot() action.
>
Looks good to me.
Acked-by: Masami Hiramatsu
Thank you!
> Signed-off-by: Tom Zanussi
> ---
>
On Fri, Dec 14, 2018 at 12:42:34PM +0100, Florian Weimer wrote:
> * Rich Felker:
>
> > On Thu, Dec 13, 2018 at 05:04:59PM +0100, Florian Weimer wrote:
> >> * Rich Felker:
> >>
> >> >> If the compiler can handle the zeroing, that would be great, though not
> >> >> sure how (some
Hi Linus,
In a last-ditch attempt to use up some holiday, I'm off for the rest of
the year so here's the arm64 pull request for 4.21 well ahead of the
next merge window.
At present, there are a handful of straightforward conflicts:
* The A76 workaround for erratum #1286807 landed in mainline
On Fri, Dec 14, 2018 at 07:52:15AM -0800, Joe Perches wrote:
> On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
> > As per Documentation/process/submitting-patches, Co-developed-by is a
> > valid signature.
> >
> > This commit removes the warning.
>
> Your commit message doesn't
Hi Stephen,
Can you please add the auxdisplay tree into linux-next?
https://github.com/ojeda/linux.git auxdisplay
It is extremely low volume, but from time to time there is a patch.
Thank you!
Cheers,
Miguel
401 - 500 of 1344 matches
Mail list logo