On Wed, 27 Feb 2019 10:45:44 -0800
Florian Fainelli wrote:
> On 2/27/19 10:40 AM, Stephen Hemminger wrote:
> > On Wed, 27 Feb 2019 17:24:03 +0530
> > Harini Katakam wrote:
> >
> >> Hi,
> >>
> >> We've had some users requesting control over net device name order
> >> when multiple ethernet
On Tue, 26 Feb 2019 12:17:43 +0100
Joerg Roedel wrote:
> Hi Jean-Philippe,
>
> Thanks for the patch! I think this is getting close to be applied
> after the next merge window.
>
> On Wed, Feb 20, 2019 at 02:27:59PM +, Jean-Philippe Brucker wrote:
> > +int iommu_sva_bind_device(struct
Hi Marcel,
On Tue, Feb 26, 2019 at 11:53 PM Marcel Holtmann wrote:
> > We may need to specify a GPIO wake pin for this device, so add a
> > compatible property for it.
> >
> > There are at least to USB PID/VID variations of this chip: one with a
> > Lite-On ID and one with an Atheros ID.
> >
> >
On Wed, Feb 27, 2019 at 04:41:04PM +0900, Masami Hiramatsu wrote:
> On Tue, 26 Feb 2019 16:38:50 -0500
> Joel Fernandes wrote:
>
> > On Mon, Feb 25, 2019 at 11:04:42PM +0900, Masami Hiramatsu wrote:
>
> > > Note that kprobe event provides these methods, but it doesn't
> > > change it from
On Tue, Feb 26, 2019 at 02:04:28PM -0800, Andrew Morton wrote:
> How is this going to affect existing userspace which is aware of the
> current behaviour?
Well, current behavior is not really predictable.
Our customer was "surprised" that the call to mremap() failed, but the regions
got unmapped
On Wed, 27 Feb 2019, Joe Lawrence wrote:
> The ppc64le implementation of save_stack_trace_tsk_reliable() is
> exported, so do the same with x86.
And what's the in tree module user of this? I can't find one and just
because PPC has an export with no user is not a convincing argument to add
In the past there were some issues resulting from additions to
XSAVE/XSAVES. Introduce a few tests to help detect issues early.
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Dave Hansen
Cc: Ingo Molnar
Cc: Shuah Khan
Signed-off-by: Yu-cheng Yu
---
tools/testing/selftests/x86/Makefile
On Wed, Feb 27, 2019 at 07:36:50PM +0100, David Sterba wrote:
> On Wed, Feb 27, 2019 at 01:29:16PM -0500, Dennis Zhou wrote:
> > > I've noticed while reading the code, why do you use the indirect call
> > > here? The wsm.ops points to btrfs_zstd_compress so free_workspace is
> > > always
While calling functions inside zstd, we don't need to use the
indirection provided by the workspace_manager. Forward declarations are
added to maintain the function order of btrfs_compress_op.
Signed-off-by: Dennis Zhou
---
fs/btrfs/zstd.c | 11 +++
1 file changed, 7 insertions(+), 4
The ppc64le implementation of save_stack_trace_tsk_reliable() is
exported, so do the same with x86.
Signed-off-by: Joe Lawrence
---
arch/x86/kernel/stacktrace.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/stacktrace.c b/arch/x86/kernel/stacktrace.c
index
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
size = sizeof(struct foo) +
Hi,
On Tue, Feb 26, 2019 at 3:54 PM Doug Anderson wrote:
>
> Hi,
>
> On Tue, Feb 5, 2019 at 9:13 PM Bjorn Andersson
> wrote:
> >
> > From: Sibi Sankar
> >
> > This patch adds Q6V5 MSS remoteproc node for SDM845 SoCs.
> >
> > Signed-off-by: Sibi Sankar
> > Reviewed-by: Douglas Anderson
> >
Hi Bjorn,
Commit
a048671aa0c8 ("PCI: qcom: Don't deassert reset GPIO during probe")
is missing a Signed-off-by from its committer.
-
Cheers,
Stephen Rothwell
pgpULlZ3JRtgs.pgp
Description: OpenPGP digital signature
Hijacking an old thread,
On 11/10/17 5:30 PM, Chris Packham wrote:
> On 11/10/17 16:42, Guenter Roeck wrote:
>> On 10/10/2017 07:29 PM, Chris Packham wrote:
>>> The orion_wdt_irq invokes panic() so we are going to reset the CPU
>>> regardless. By not setting this bit we get a chance to gather
A warning is generated when a PCIe device is probed with a degraded
link, but there was no similar mechanism to warn when the link becomes
degraded after probing. The Link Bandwidth Notification provides this
mechanism.
Use the link bandwidth notification interrupt to detect bandwidth
changes,
Hi Ard,
On Wed, Feb 27, 2019 at 11:16:12AM +0100, Ard Biesheuvel wrote:
> On Wed, 27 Feb 2019 at 11:02, Marc Zyngier wrote:
> > On 26/02/2019 23:28, Brian Norris wrote:
> > > You're not the first person to notice this. All the motivations are not
> > > necessarily painted clearly in their cover
Le mercredi 27 février 2019 à 11:01 +0100, Maxime Ripard a écrit :
> > Also regarding the pixel formats. I still think we should have two
> > pixel formats: V4L2_PIX_FMT_H264_SLICE_RAW and
> > V4L2_PIX_FMT_H264_SLICE_ANNEX_B, to properly represent "raw" NALUs
> > and "annex B" formatted NALUs.
>
On Wed, 27 Feb 2019, Yoshihiro Shimoda wrote:
> Hello,
>
> > From: Julia Lawall, Sent: Wednesday, February 27, 2019 5:25 PM
> >
> > On Wed, 27 Feb 2019, Yoshihiro Shimoda wrote:
> >
> > > This patch fixes memory leak at error paths of the probe function.
> > > In for_each_child_of_node, if the
016a0880() GS:8880ae80()
> >> knlGS:
> >> CS: 0010 DS: ES: CR0: 80050033
> >> CR2: 20f50f90 CR3: 97b89000 CR4: 001406f0
> >>
> >>
> >> ---
> >> This bug i
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this when assigning a APID or a APQI to the mediated device
and
x7fc7001ba207
> > > Code: Bad RIP value.
> > > RSP: 002b:7ffe06aa13b8 EFLAGS: 0206 ORIG_RAX: 003b
> > > RAX: ffda RBX: RCX: 00007fc7001ba207
> > > RDX: 01fd5fd0 RSI: 7ffe06aa14b0 RDI: 7ffe06aa2
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/video/fbdev/xen-fbfront.c: In function ‘xenfb_backend_changed’:
drivers/video/fbdev/xen-fbfront.c:678:6: warning: this statement may fall
Miss a star.
Signed-off-by: Qian Cai
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index af7f18b32389..d4b96dc4bd8a 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -5747,7 +5747,7 @@ struct cgroup_subsys
Hi arm-soc maintainers,
Since we are having a -rc8 for v5.0, please help to merge a few additional
patches for the upcoming merge window. Thanks
Regards,
Leo
The following changes since commit bd3bd3b36df725645036748e58a8c35c8d2cbf91:
soc: fsl: dpio: fix memory leak of a struct qbman on
Hi Marc,
On Wed, Feb 27, 2019 at 10:02:16AM +, Marc Zyngier wrote:
> On 26/02/2019 23:28, Brian Norris wrote:
> > On Sun, Feb 24, 2019 at 02:04:22PM +, Marc Zyngier wrote:
> >> Note how the interrupt is part of the properties directly attached to the
> >> PCI node. And yet, this interrupt
From: Rajan Vaja
Clock description is part of firmware doc. Move clock description
in separate doc.
Signed-off-by: Rajan Vaja
Signed-off-by: Jolly Shah
---
.../devicetree/bindings/clock/xlnx,zynqmp-clk.txt | 63 ++
.../firmware/xilinx/xlnx,zynqmp-firmware.txt | 54
Rename file name of ZynqMP clk dt-bindings to align with
file name of reset and power dt-bindings.
Signed-off-by: Rajan Vaja
Signed-off-by: Jolly Shah
---
.../firmware/xilinx/xlnx,zynqmp-firmware.txt | 2 +-
include/dt-bindings/clock/xlnx,zynqmp-clk.h| 116 ---
This patchset renames clock dt include file to align with other incldues.
Other patch moves clock binding to a separate file under clock directory to
align with other firmware child binding documenetation.
Jolly Shah (1):
include: dt-binding: clock: Rename zynqmp header file
Rajan Vaja (1):
From: Yue Haibing
Date: Fri, 22 Feb 2019 15:37:58 +0800
> From: YueHaibing
>
> KASAN report this:
. ..
> nfc_llcp_build_tlv will return NULL on fails, caller should check it,
> otherwise will trigger a NULL dereference.
>
> Reported-by: Hulk Robot
> Fixes: eda21f16a5ed ("NFC: Set MIU and RW
On 21/02/2019 08:42, Marek Szyprowski wrote:
> Dear All,
>
> On 2019-02-15 12:13, Ming Lei wrote:
>> This patch pulls the trigger for multi-page bvecs.
>>
>> Reviewed-by: Omar Sandoval
>> Signed-off-by: Ming Lei
>
> Since Linux next-20190218 I've observed problems with block layer on one
>
Hi,
Comments inline.
On Sun, Feb 24, 2019 at 12:34:51PM -0800, Robert Eshleman wrote:
> This patch adds support for the ap3216c ambient light and proximity
> sensor.
>
> Supported features include:
>
> * Illuminance (lux)
> * Proximity (raw)
> * IR (raw)
> *
From: Florian Fainelli
Date: Wed, 27 Feb 2019 11:44:24 -0800
> This patch series completes the removal of the switchdev_ops by
> converting switchdev_port_attr_set() to use either the blocking
> (process) or non-blocking (atomic) notifier since we typically need to
> deal with both depending on
Hi Marcel,
On Wed, Feb 27, 2019 at 08:48:31AM +0100, Marcel Holtmann wrote:
> Hi Matthias,
>
> > The current 300ms delay after a baudrate change is extremely long.
> > For WCM3990 it is sufficient to wait 10ms after the baudrate change
> > request has been sent over the wire.
> >
> > Also use
On 2/27/19 3:40 AM, Pierre Morel wrote:
On 26/02/2019 17:10, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
The AP interruptions are assigned on a queue basis and
the GISA structure is handled on a VM basis, so that
we need to add a structure we can retrieve from both side
Hi Boris,
On 2/27/19 2:13 AM, Boris Brezillon wrote:
> On Tue, 26 Feb 2019 21:53:16 -0600
> "Gustavo A. R. Silva" wrote:
>
>> Hi all,
>>
>> Friendly ping:
>>
>> Who can ack or review this, please?
>
> Will be queued for the next release. Please be patient.
>
Great. Good to know. :)
Sure
Enumeration P2P_PROTO_WK_ID is not used in the driver code,
so remove it from wifi.h.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/include/wifi.h | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/staging/rtl8188eu/include/wifi.h
Defined P2P_PRIVATE_IOCTL_SET_LEN is not used in the driver code,
so remove it from wifi.h.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/include/wifi.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/rtl8188eu/include/wifi.h
From: Matthew Garrett
UEFI systems provide a boot services protocol for obtaining the TPM
event log, but this is unusable after ExitBootServices() is called.
Unfortunately ExitBootServices() itself triggers additional TPM events
that then can't be obtained using this protocol. The platform
From: Matthew Garrett
Any events that are logged after GetEventsLog() is called are logged to
the EFI Final Events table. These events are defined as being in the
crypto agile log format, so we can just append them directly to the
existing log if it's in the same format. In theory we can also
From: Matthew Garrett
Right now we only attempt to obtain the SHA1-only event log. The
protocol also supports a crypto agile log format, which contains digests
for all algorithms in use. Attempt to obtain this first, and fall back
to obtaining the older format if the system doesn't support it.
From: Matthew Garrett
We need to calculate the size of crypto agile events in multiple
locations, including in the EFI boot stub. The easiest way to do this is
to put it in a header file as an inline and leave a wrapper to ensure we
don't end up with multiple copies of it embedded in the
Identical to V4, but based on tpmdd-next
On 27-02-2019 21:05, Mark Brown wrote:
> On Wed, Feb 27, 2019 at 08:41:46PM +0100, Olliver Schinagl wrote:
>> On 25-02-2019 18:25, Mark Brown wrote:
>>> If you find you need to describe what the fields are it would be much
>>> more constructive to add a comment at the top of the table saying what
When compiling with -Wformat, clang emits the following warnings:
fs/cifs/smb1ops.c:312:20: warning: format specifies type 'unsigned
short' but the argument has type 'unsigned int' [-Wformat]
tgt_total_cnt, total_in_tgt);
Add ECC support for Mellanox BlueField SoC DDR controller.
This requires SMC to the running Arm Trusted Firmware to report
what is the current memory configuration.
Signed-off-by: Junhan Zhou
---
drivers/edac/Kconfig | 7 +
drivers/edac/Makefile | 1 +
On 2/24/19 8:29 PM, Lukas Wunner wrote:
> On Fri, Dec 07, 2018 at 12:20:00PM -0600, Alexandru Gagniuc wrote:
>
>
>> Q: Why is this unconditionally compiled in?
>> A: The symmetrical check in pci probe() is also always compiled in.
>
> Hm, it looks like the convention is to provide a separate
On Wed, Feb 27, 2019 at 11:44:24AM -0800, Florian Fainelli wrote:
> Hi all,
>
> This patch series completes the removal of the switchdev_ops by
> converting switchdev_port_attr_set() to use either the blocking
> (process) or non-blocking (atomic) notifier since we typically need to
> deal with
On Wed, Feb 27, 2019 at 11:44:32AM -0800, Florian Fainelli wrote:
> Now that we have converted all possible callers to using a switchdev
> notifier for attributes we do not have a need for implementing
> switchdev_ops anymore, and this can be removed from all drivers the
> net_device structure.
>
On Wed, Feb 27, 2019 at 11:44:31AM -0800, Florian Fainelli wrote:
> Drop switchdev_ops.switchdev_port_attr_set. Drop the uses of this field
> from all clients, which were migrated to use switchdev notification in
> the previous patches.
>
> Add a new function switchdev_port_attr_notify() that
On 2/27/19 4:29 AM, Pierre Morel wrote:
On 26/02/2019 19:14, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to
Hi Alexandre.
Nice patch, good to clean out unused code.
On Mon, Feb 25, 2019 at 10:25:33PM +0100, Alexandre Belloni wrote:
> Make the driver OF only as since AVR32 has been removed from the kernel,
> there are only OF enabled platform using it.
>
> Signed-off-by: Alexandre Belloni
Reviewed-by:
On Wed, 2019-02-27 at 09:09 -0500, Qian Cai wrote:
> On Mon, 2019-02-25 at 16:07 -0800, Linus Torvalds wrote:
> > On Mon, Feb 25, 2019 at 4:03 PM Qian Cai wrote:
> > > >
> > > > Of course, that's just gcc. I have no idea what llvm ends up doing.
> > >
> > > Clang 7.0:
> > >
> > > # clang -O2
On 2/27/2019 11:56 AM, Bolen, Austin wrote:
>
> BTW, this patch in particular is complaining about an error for a
> removed device. The Dell servers referenced in this chain will check if
> the device is removed and if so it will suppress the error so I don't
> think they are susceptible to this
On 2/27/19 8:33 AM, Martin K. Petersen wrote:
>
> Gustavo,
>
>> Add missing break statement and fix identation issue.
>
> So much bad indentation in this driver. Tried various tab widths and it
> is still all over the place.
>
> Anyway. After staring at the firmware header I have convinced
On Wed, Feb 27, 2019 at 08:41:46PM +0100, Olliver Schinagl wrote:
> On 25-02-2019 18:25, Mark Brown wrote:
> > If you find you need to describe what the fields are it would be much
> > more constructive to add a comment at the top of the table saying what
> > they are. As things are this isn't
Hi Borislav, Russell,
This seems to have fallen off the radar. Is there anything stopping this
series from being merged?
On 22/11/18 1:12 PM, Chris Packham wrote:
> The current plan is for these to go in via the ARM tree once appropriate
> Reviews/Acks have been given
>
>
Hi Masahiro.
On Thu, Jan 31, 2019 at 12:56:39PM +0900, Masahiro Yamada wrote:
> Currently, the Kbuild core manipulates header search paths in a crazy
> way [1].
>
> To fix this mess, I want all Makefiles to add explicit $(srctree)/ to
> the search paths in the srctree. Some Makefiles are already
This adds an x86-specific test for pinned cr4 bits. A successful test
will validate pinning and check the ROP-style call-middle-of-function
defense, if needed. For example, in the case of native_write_cr4()
looking like this:
8171bce0 :
8171bce0: 48 8b 35 79 46 f2 00mov
With sensitive CR4 bits pinned now, it's possible that the WP bit for CR0
might become a target as well. Following the same reasoning for the CR4
pinning, this pins CR0's WP bit (but this can be done with a static value).
As before, to convince the compiler to not optimize away the check for the
This adds CR0 pinning (for WP), and cleans up the CR4 pin to avoid
taking an exception from WARN before fixing up the desired pin.
Additionally adds lkdtm test (which depends on the CR4 patch, otherwise
I'd send it via Greg's tree).
v2:
- include brown-paper-bag fix to lkdtm test in v1
- clean up
Instead of taking a full WARN() exception before restoring a potentially
missed CR4 bit, this retains the missing bit for later reporting. This
matches the logic done for the CR0 pinning. Additionally updates the
comments to note the required use of "volatile".
Suggested-by: Solar Designer
On Wed, Feb 27, 2019 at 8:39 AM Bjorn Andersson
wrote:
>
> This adds an initial dts for the Dragonboard 845. Supported
> functionality includes Debug UART, UFS, USB-C (peripheral), USB-A
> (host), Ethernet, microSD-card and Bluetooth.
>
> Initializing the SMMU is clearing the mapping used for the
As it's now perfectly possible that a PM domain managed by genpd contains
devices belonging to CPUs, we should start to take into account the
residency values for the idle states during the state selection process.
The residency value specifies the minimum duration of time, the CPU or a
group of
Let's add a data pointer to the genpd_power_state struct, to allow a genpd
backend driver to store per state specific data. To introduce the pointer,
we need to change the way genpd deals with freeing of the corresponding
allocated data.
More precisely, let's clarify the responsibility of whom
To be able to predict the sleep duration for a CPU that is entering idle,
knowing when the next timer/tick is going to expire, is extremely useful.
Both the teo and the menu cpuidle governors already makes use of this
information, while selecting an idle state.
Moving forward, the similar
To enable a device belonging to a CPU to be attached to a PM domain managed
by genpd, let's do a few changes to it, as to make it convenient to manage
the specifics around CPUs.
To be able to quickly find out what CPUs that are attached to a genpd,
which typically becomes useful from a genpd
Changes in v12:
- Drop the patches for restructuring tick_nohz_get_sleep_length(). Instead
replace them all with a new timer/cpuidle patch, according to suggestions by
Rafael.
- The entire v12 series, including the PSCI/ARM changes are available in a
git branch [2].
Changes in v11:
- This
On Wed, Feb 27, 2019 at 6:03 AM Jarkko Sakkinen
wrote:
> My guess is that your patches are based a later 5.0-rcX. Unfortunately I
> cannot update my master at this point because my 5.1 PR was taken to
> security tree and rebasing would change the commit IDs of 5.1 content
> because
On Wed, Feb 27, 2019 at 7:08 AM Anson Huang wrote:
> diff --git a/arch/arm/boot/dts/imx7ulp.dtsi b/arch/arm/boot/dts/imx7ulp.dtsi
> index fca6e50..fca4a01 100644
> --- a/arch/arm/boot/dts/imx7ulp.dtsi
> +++ b/arch/arm/boot/dts/imx7ulp.dtsi
> @@ -286,6 +286,12 @@
> status
Hi Anson,
On Wed, Feb 27, 2019 at 7:08 AM Anson Huang wrote:
> +Example :
> + mmdc0: mmdc@21b { /* MMDC0 */
Node names should be generic, so:
memory-controller@21b
Following patches will change the way we communicate setting a port's
attribute and use notifiers towards that goal.
Prepare rocker to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_SET from both atomic and process context and use a
small helper to translate the event notifier
Following patches will change the way we communicate setting a port's
attribute and use a blocking notifier to perform those tasks.
Prepare ethsw to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_SET and simply translate that into the existing
swdev_port_attr_set() call.
Drop switchdev_ops.switchdev_port_attr_set. Drop the uses of this field
from all clients, which were migrated to use switchdev notification in
the previous patches.
Add a new function switchdev_port_attr_notify() that sends the switchdev
notifications SWITCHDEV_PORT_ATTR_SET and calls the
Following patches will change the way we communicate setting a port's
attribute and use notifiers to perform those tasks.
Ocelot does not currently have an atomic notifier registered for
switchdev events, so we need to register one in order to deal with
atomic context SWITCHDEV_PORT_ATTR_SET
Now that we have converted all possible callers to using a switchdev
notifier for attributes we do not have a need for implementing
switchdev_ops anymore, and this can be removed from all drivers the
net_device structure.
Signed-off-by: Florian Fainelli
---
Following patches will change the way we communicate setting a port's
attribute and use a notifier to perform those tasks.
Prepare mlxsw to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_SET and utilize the switchdev_handle_port_attr_set()
to handle stacking of devices.
Hi all,
This patch series completes the removal of the switchdev_ops by
converting switchdev_port_attr_set() to use either the blocking
(process) or non-blocking (atomic) notifier since we typically need to
deal with both depending on where in the bridge code we get called from.
This was tested
On Wed, Feb 27, 2019 at 2:44 AM Solar Designer wrote:
>
> On Tue, Feb 26, 2019 at 03:36:45PM -0800, Kees Cook wrote:
> > static inline void native_write_cr0(unsigned long val)
> > {
> > - asm volatile("mov %0,%%cr0": : "r" (val), "m" (__force_order));
> > + bool warn = false;
> > +
> >
In preparation for allowing switchdev enabled drivers to veto specific
attribute settings from within the context of the caller, introduce a
new switchdev notifier type for port attributes.
Suggested-by: Ido Schimmel
Reviewed-by: Ido Schimmel
Signed-off-by: Florian Fainelli
---
Following patches will change the way we communicate setting a port's
attribute and use notifiers towards that goal.
Prepare DSA to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_SET from both atomic and process context and use a
small helper to translate the event notifier into
On Wed, Feb 27, 2019 at 3:08 AM Louis Taylor wrote:
>
> When building with -Wformat, clang warns:
>
> drivers/hid/hid-quirks.c:1075:27: warning: format specifies type
> 'unsigned short' but the argument has type '__u32' (aka 'unsigned int')
> [-Wformat]
> bl_entry->driver_data,
On Wed, Feb 27, 2019 at 9:57 AM Nadav Amit wrote:
>
> I’ll have a look at some specific function assembly, but overall, the “+m”
> approach might prevent even more code optimizations than the “volatile” one.
Ok, that being the case, let's forget that patch.
I still wonder about the added
On 25-02-2019 18:25, Mark Brown wrote:
> On Sat, Feb 23, 2019 at 09:37:01PM +0100, Olliver Schinagl wrote:
>
>> In any case, you seem like a smart person that reads and writes hex and
>> bits often enough. This is not true for everyone. I can just as easily
>> reverse your arguments of course, for
ср, 27 февр. 2019 г. в 09:54, Sasha Levin :
>
> On Fri, Feb 15, 2019 at 08:10:47PM +, Pavel Shilovskiy wrote:
> >чт, 14 февр. 2019 г. в 18:40, Sasha Levin :
> >>
> >> From: Pavel Shilovsky
> >>
> >> [ Upstream commit 0fd1d37b0501efc6e295f56ab55cdaff784aa50c ]
> >>
> >> If we don't receive a
Introduce in-kernel headers and other artifacts which are made available
as an archive through proc (/proc/kheaders.tar.xz file). This archive makes
it possible to build kernel modules, run eBPF programs, and other
tracing programs that need to extend the kernel for tracing purposes
without any
This test tries to build a module successfully using the in-kernel
headers found in /proc/kheaders.tar.xz.
Verified pass and fail scenarios by running:
make -C tools/testing/selftests TARGETS=kheaders run_tests
Signed-off-by: Joel Fernandes (Google)
---
tools/testing/selftests/Makefile
On 01/01/2019 04:51, Yong Wu wrote:
MediaTek IOMMU don't have its power-domain. all the consumer connect
with smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-
| |...
| |
larb1 larb2
| |
vdec
Fix unused function warning when compiled with CONFIG_PCI_PASID
disabled.
Fixes: e5567f5f6762 ("PCI/ATS: Add pci_prg_resp_pasid_required() interface.")
Signed-off-by: Kuppuswamy Sathyanarayanan
---
include/linux/pci-ats.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Steven,
On Wed, Feb 27, 2019 at 6:07 PM Steven Price wrote:
> walk_page_range() is going to be allowed to walk page tables other than
> those of user space. For this it needs to know when it has reached a
> 'leaf' entry in the page tables. This information is provided by the
> p?d_large()
On Tue, Feb 19, 2019 at 09:30:33PM -0800, 'Ira Weiny' wrote:
> From: Ira Weiny
>
> Resending these as I had only 1 minor comment which I believe we have covered
> in this series. I was anticipating these going through the mm tree as they
> depend on a cleanup patch there and the IB changes are
On Wed, Feb 27, 2019 at 12:04 PM Johan Jonker wrote:
>
> Thanks for your advice.
>
> On 2/25/19 5:59 PM, Rob Herring wrote:> On Fri, Feb 01, 2019 at
> 01:32:35PM +0100, Johan Jonker wrote:
> >> This patch adds a binding that describes the HDMI controller for
> >> rk3066.
> >
> > This is not using
On 27.02.2019 10:20, Maxime Ripard wrote:
On Sun, Feb 24, 2019 at 09:04:57AM +0100, Gerhard Wiesinger wrote:
Hello,
I've 3 Banana Pi R1, one running with self compiled kernel
4.7.4-200.BPiR1.fc24.armv7hl and old Fedora 25 which is VERY STABLE, the 2
others are running with Fedora 29 latest,
> On Feb 27, 2019, at 9:57 AM, Nadav Amit wrote:
>
>> On Feb 27, 2019, at 8:14 AM, Linus Torvalds
>> wrote:
>>
>> On Wed, Feb 27, 2019 at 2:16 AM Peter Zijlstra wrote:
>>> Nadav Amit reported that commit:
>>>
>>> b59167ac7baf ("x86/percpu: Fix this_cpu_read()")
>>>
>>> added a bunch of
On 27.02.19 18:05, Steven Price wrote:
> walk_page_range() is going to be allowed to walk page tables other than
> those of user space. For this it needs to know when it has reached a
> 'leaf' entry in the page tables. This information is provided by the
> p?d_large() functions/macros.
>
> For
From: Randy Dunlap Sent: Wednesday, February 27, 2019
9:25 AM
>
> on i386:
>
> ../arch/x86/kernel/cpu/mshyperv.c: In function 'ms_hyperv_init_platform':
> ../arch/x86/kernel/cpu/mshyperv.c:339:3: error: 'x2apic_phys' undeclared
> (first use in this
> function)
>x2apic_phys = 1;
>^
Hi,
On 2/26/19 6:20 PM, Stephen Rothwell wrote:
Hi Joerg,
After merging the iommu tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from drivers/pci/pci.c:32:
include/linux/pci-ats.h:70:12: warning: 'pci_prg_resp_pasid_required' defined
but not
On Wed, Feb 27 2019 at 12:38pm -0500,
Sasha Levin wrote:
> On Thu, Feb 14, 2019 at 10:49:09PM -0500, Mike Snitzer wrote:
> >On Thu, Feb 14 2019 at 9:08pm -0500,
> >Sasha Levin wrote:
> >
> >>From: Mike Snitzer
> >>
> >>[ Upstream commit 57c36519e4b949f89381053f7283f5d605595b42 ]
> >>
> >>DM's
On 2/27/19 10:40 AM, Stephen Hemminger wrote:
> On Wed, 27 Feb 2019 17:24:03 +0530
> Harini Katakam wrote:
>
>> Hi,
>>
>> We've had some users requesting control over net device name order
>> when multiple ethernet devices are present on a system. I've tried a
>> few solutions to this and looked
On Wed, 27 Feb 2019 17:24:03 +0530
Harini Katakam wrote:
> Hi,
>
> We've had some users requesting control over net device name order
> when multiple ethernet devices are present on a system. I've tried a
> few solutions to this and looked it up on forums. But I apologize if
> I have missed
From: Steven Price
Date: Wed, 27 Feb 2019 17:05:54 +
> walk_page_range() is going to be allowed to walk page tables other than
> those of user space. For this it needs to know when it has reached a
> 'leaf' entry in the page tables. This information is provided by the
> p?d_large()
301 - 400 of 898 matches
Mail list logo
