On 03/09/2018 09:37 PM, Sergei Shtylyov wrote:
>> Commit 009f766 intended to filter multicast/broadcast, however
>
>At least 12 digits needed here, and the summary line too, just like you do
> for the Fixes: tag.
>
>> the NDIS filter wasn't set properly in non-promiscuous modes,
>> which
Now we just need to get the other drivers merged and finish the style
cleanups/garbage collecting so we can get out of staging.
Signed-off-by: Eric Anholt
Acked-by: Stefan Wahren
---
v2-3: no changes
drivers/staging/vc04_services/interface/vchi/TODO |
On Fri, Mar 9, 2018 at 4:50 AM, Mark Brown wrote:
> On Thu, Mar 08, 2018 at 12:06:53PM -0800, Kees Cook wrote:
>
>> If a codec is not attached to the sound soc, a NULL deref is possible as a
>> regular user in /sys.
>
> I can't parse this, sorry. What is the "sound soc"?
This was requested by Rob Herring in DT bindings review.
Signed-off-by: Eric Anholt
Acked-by: Stefan Wahren
---
v2: new patch
v3: no changes
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 3 ++-
1 file changed, 2 insertions(+), 1
These are dead code, including in the downstream Raspberry Pi tree.
Signed-off-by: Eric Anholt
---
v2-3: no changes
.../vc04_services/interface/vchiq_arm/vchiq_arm.c| 20
.../vc04_services/interface/vchiq_arm/vchiq_if.h | 10 --
2 files
The VCHIQ communication channel can be provided by BCM283x and Capri
SoCs, to communicate with the VPU-side OS services.
Signed-off-by: Eric Anholt
---
v2: VCHI->VCHIQ, dropped firmware property, added cache-line-size
v3: Dropped cache-line-size, s/vchi@/mailbox@/
On Fri, 09 Mar 2018 10:36:44 PST (-0800), parri.and...@gmail.com wrote:
On Fri, Mar 09, 2018 at 09:56:21AM -0800, Palmer Dabbelt wrote:
On Fri, 09 Mar 2018 04:13:40 PST (-0800), parri.and...@gmail.com wrote:
>Atomics present the same issue with locking: release and acquire
>variants need to be
> This is Intel SE7520JR22S mainboard with 2 64-bit P4 xeons. Earlier
> kernels up to 4.14 have had W+X checking on but found nothing. Now I
> tried 4.15.0-rc9-00023-g1f07476ec143 and it gives a new W+X warning.
Actually, I was wrong about earlier kernels - I just did not have
CONFIG_DEBUG_WX
On Fri, Mar 9, 2018 at 10:50 AM, Linus Torvalds
wrote:
> On Fri, Mar 9, 2018 at 10:43 AM, Kees Cook wrote:
>>
>> Module loading (via kernel_read_file()) already uses
>> deny_write_access(), and so does do_open_execat(). As long as module
>>
On 3/9/2018 12:42 PM, Peter Zijlstra wrote:
On Fri, Mar 09, 2018 at 09:31:11AM -0500, Vince Weaver wrote:
On Fri, 9 Mar 2018, tip-bot for Kan Liang wrote:
Commit-ID: 1af22eba248efe2de25658041a80a3d40fb3e92e
Gitweb: https://git.kernel.org/tip/1af22eba248efe2de25658041a80a3d40fb3e92e
From: Bjorn Helgaas
7570a333d8b0 ("PCI: Add pcie_hp=nomsi to disable MSI/MSI-X for pciehp
driver") added the "pcie_hp=nomsi" kernel parameter to work around this
error on shutdown:
irq 16: nobody cared (try booting with the "irqpoll" option)
Pid: 1081, comm: reboot Not
From: Bjorn Helgaas
The platform may restrict the OS's use of PCIe services, e.g., via the ACPI
_OSC method. The user may use "pcie_ports=native" to force the port driver
to use PCIe services even if the platform asked us not to.
The "pcie_ports=native" parameter
From: Bjorn Helgaas
No driver registers for PCIE_PORT_SERVICE_VC, so remove it.
This removes the VC "service" files from /sys/bus/pci_express/devices,
e.g., :07:00.0:pcie108, :08:04.0:pcie208 (all the files that
contained "8" as the last digit of the "pcieXXX"
From: Bjorn Helgaas
The "pcie_ports=compat" kernel parameter sets pcie_ports_disabled, which is
intended to disable the PCIe port driver. But even when it was disabled,
we registered pcie_portdriver so we could work around a BIOS PME issue (see
fe31e69740ed ("PCI/PCIe:
From: Bjorn Helgaas
Some PCIe features (AER, DPC, hotplug, PME) can be managed by either the
platform firmware or the OS, so the host bridge driver may have to request
permission from the platform before using them. On ACPI systems, this is
done by negotiate_os_control() in
On Fri, 9 Mar 2018, Peter Zijlstra wrote:
> On Fri, Mar 09, 2018 at 09:31:11AM -0500, Vince Weaver wrote:
> > On Fri, 9 Mar 2018, tip-bot for Kan Liang wrote:
> >
> > > Commit-ID: 1af22eba248efe2de25658041a80a3d40fb3e92e
> > > Gitweb:
> > >
On Fri 2018-03-09 10:45:16, Kees Cook wrote:
> On Fri, Mar 9, 2018 at 4:50 AM, Mark Brown wrote:
> > On Thu, Mar 08, 2018 at 12:06:53PM -0800, Kees Cook wrote:
> >
> >> If a codec is not attached to the sound soc, a NULL deref is possible as a
> >> regular user in /sys.
> >
>
Thanks.
I replied to your message with additional information.
I will update the commit message and resubmit the patch.
MV
On 03/09/18 14:29, Arnaldo Carvalho de Melo wrote:
Em Fri, Mar 09, 2018 at 01:49:50PM -0500, Martin Vuille escreveu:
Hi,
I made two other submissions that may also
On Fri, Mar 9, 2018 at 7:38 PM, Linus Torvalds
wrote:
> On Fri, Mar 9, 2018 at 11:12 AM, Linus Torvalds
> wrote:
>>
>> How are you going to handle five processes doing the same setup concurrently?
>
> Side note: it's not just
From: Markus Elfring
Date: Fri, 9 Mar 2018 21:00:12 +0100
Adjust jump targets so that a bit of exception handling can be better
reused at the end of these functions.
This issue was partly detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
Add documentation for the interconnect consumer bindings, that will allow
to link a device node (consumer) to its interconnect controller hardware.
Tha aim is to enable drivers to request a framework API to configure an
interconnect path by providing their struct device pointer and a name.
On Fri, Mar 9, 2018 at 12:05 PM, Kees Cook wrote:
> When max() is used in stack array size calculations from literal values
> (e.g. "char foo[max(sizeof(struct1), sizeof(struct2))]", the compiler
> thinks this is a dynamic calculation due to the single-eval logic, which
>
Use the newly exposed VSP1 interface to enable interlaced frame support
through the VSP1 lif pipelines.
Signed-off-by: Kieran Bingham
---
drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 1 +
drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 3 +++
2 files changed, 4
Calculate the top and bottom fields for the interlaced frames and
utilise the extended display list command feature to implement the
auto-field operations. This allows the DU to update the VSP2 registers
dynamically based upon the currently processing field.
Signed-off-by: Kieran Bingham
On Fri, Mar 09, 2018 at 03:58:19PM -0600, Eddie James wrote:
> From: Milton Miller
>
> Assert RESET_SYSTEM bit for any reset and set MODE field from reset
> type.
>
> The watchdog control register has a RESET_SYSTEM bit that is really
> closer to activate a reset, and
VSPD and VSP-DL devices can provide extended display lists supporting
extended command display list objects.
These extended commands require their own dma memory areas for a header
and body specific to the command type.
Implement a command pool to allocate all necessary memory in a single
DMA
Hi Milan,
Yes, that is correct that the attacks it protects against is when the
underlying storage is offline. We have discussed if we should reset the bitmap
at certain events but decided against it.
Cheers,
Patrik
On Thu, Mar 08, 2018 at 01:35:05PM +0100, Milan Broz wrote:
> On 03/07/2018
Hi,
I sent this to the wrong maintainers, sorry — you’ll find the original patch
on https://patchwork.kernel.org/patch/10269257/
Regards,
Stephen
On Thu, 8 Mar 2018 13:43:07 -0800, Kees Cook wrote:
> On Thu, Mar 8, 2018 at 1:38 PM, Stephen Kitt wrote:
>
On Fri, Mar 9, 2018 at 10:43 AM, Kees Cook wrote:
>
> Module loading (via kernel_read_file()) already uses
> deny_write_access(), and so does do_open_execat(). As long as module
> loading doesn't call allow_write_access() before the execve() has
> started in the new
From: Bjorn Helgaas
The "pcie_ports=auto" parameter set pcie_ports_disabled and pcie_ports_auto
to their compiled-in defaults, so specifying the parameter is the same as
not using it at all.
Remove the "pcie_ports=auto" parameter and update the documentation.
From: Bjorn Helgaas
"pcie_ports_auto" is only used inside the PCIe port driver itself, so
move it from include/linux/pci.h to portdrv.h so it's not visible to the
whole kernel.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/pcie/portdrv.h |2 ++
From: Bjorn Helgaas
The pcie_port_bus_type must be registered before drivers that depend on it
can be registered. Those drivers include:
pcied_init()# PCIe native hotplug driver
aer_service_init() # AER driver
dpc_service_init() #
From: Bjorn Helgaas
portdrv_pci.c doesn't use anything from . Remove the
include of it. No functional change intended.
Signed-off-by: Bjorn Helgaas
Reviewed-by: Rafael J. Wysocki
---
drivers/pci/pcie/portdrv_pci.c |1
> -Original Message-
> From: Dexuan Cui
> Sent: Tuesday, March 6, 2018 1:22 PM
> To: bhelg...@google.com; linux-...@vger.kernel.org; KY Srinivasan
> ; Stephen Hemminger ;
> o...@aepfle.de; a...@canonical.com; jasow...@redhat.com
> Cc:
> -Original Message-
> From: Dexuan Cui
> Sent: Tuesday, March 6, 2018 1:22 PM
> To: bhelg...@google.com; linux-...@vger.kernel.org; KY Srinivasan
> ; Stephen Hemminger ;
> o...@aepfle.de; a...@canonical.com; jasow...@redhat.com
> Cc:
On Fri, Mar 9, 2018 at 11:12 AM, Linus Torvalds
wrote:
>
> How are you going to handle five processes doing the same setup concurrently?
Side note: it's not just serialization. It's also "is it actually up
and running".
The rule for "request_module()" (for a real
On Fri, Mar 9, 2018 at 6:55 PM, David Miller wrote:
> From: Alexei Starovoitov
> Date: Fri, 9 Mar 2018 10:50:49 -0800
>
>> On 3/9/18 10:23 AM, Andy Lutomirski wrote:
>>> It might not be totally crazy to back it by tmpfs.
>>
>> interesting. how do you propose to
On Fri, Mar 09, 2018 at 09:19:53PM +1100, Michael Ellerman wrote:
> Ram Pai writes:
>
> > Once an address range is associated with an allocated pkey, it cannot be
> > reverted back to key-0. There is no valid reason for the above behavior. On
> > the contrary applications
From: Yuqiong Sun
Add new CONFIG_IMA_NS config option. Let clone() create a new IMA
namespace upon CLONE_NEWNS flag. Add ima_ns data structure in nsproxy.
ima_ns is allocated and freed upon IMA namespace creation and exit.
Currently, the ima_ns contains no useful IMA data but
On Wed, 07 Mar 2018 13:46:24 -0800
Dave Hansen wrote:
> From: Dave Hansen
>
> I think we need to soften the language a bit. It might scare folks
> off, especially the:
>
>We prefer to fully disclose the bug as soon as
If it was interrupted by a signal, the 9p client may need to send some
more requests to the server for cleanup before returning to userspace.
To avoid such a last minute request to be interrupted right away, the
client memorizes if a signal is pending, clears TIF_SIGPENDING, handles
the request
Retraining MST is rather difficult. In order to do it properly while
guaranteeing that we'll never run into a spot where we commit a
physically impossible configuration, we have to do a lot of checks on
atomic commits which affect MST topologies. All of this work is going to
need to be repeated
On 03/09/2018 11:46 AM, Peter Zijlstra wrote:
On Fri, Mar 09, 2018 at 12:04:18PM +0100, Sebastian Andrzej Siewior wrote:
+void swake_add_all_wq(struct swait_queue_head *q, struct wake_q_head *wq)
{
struct swait_queue *curr;
while (!list_empty(>task_list)) {
curr =
One MC command structure got away with using uXX fields instead
of __leXX. Fix it.
Signed-off-by: Ioana Radulescu
---
v2: new patch
drivers/staging/fsl-dpaa2/ethernet/dpni-cmd.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Drop dependency on ARCH_LAYERSCAPE (which in turn depends on ARM64),
thus allowing this driver to compile on all architectures supported
by the fsl-mc bus driver.
This was compile tested on:
- powerpc (corenet_basic_defconfig, ppc64_defconfig)
- x86 (i386_defconfig, x86_64_defconfig, needs
On Wed, Mar 7, 2018 at 6:36 AM, Mark Brown wrote:
> On Tue, Mar 06, 2018 at 06:57:49AM -0800, Tony Lindgren wrote:
>
>> > By using regmap_irq_update_bits to ACK the interrupts we use the masked
>> > status bits so we take care not to affect any other bits then use
>> >
On 3/9/18 10:23 AM, Andy Lutomirski wrote:
On Mar 9, 2018, at 10:15 AM, Greg KH wrote:
Oh, and for the record, I like Andy's proposal as well as dumping this
into a kernel module "blob" with the exception that this now would take
up unswapable memory, which
Le vendredi 09 mars 2018 à 14:49 -0300, Gustavo Padovan a écrit :
> From: Gustavo Padovan
>
> In preparation to have full support to explicit fence we are
> marking codec as non-ordered preventively. It is easier and safer from an
The usage of "codec" is soso
The LSM check should happen after the file has been confirmed to be
unchanging. Without this, we could have a ToCToU issue between the
LSM verification and the actual contents of the file later.
Signed-off-by: Kees Cook
---
Only loadpin and SELinux implement this hook.
On Wed, 7 Mar 2018 20:33:56 +0900, musashino.o...@gmail.com wrote:
> From: INAGAKI Hiroshi
>
> Buffalo WZR-900DHP has 8 LEDs, but there is not LED definitions in the
> dts and cannot configure these LEDs.
> I Added missing LED definitions for WZR-900DHP.
>
>
Hi Stephen,
Thanks for the review.
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: Friday, March 09, 2018 10:25 AM
> To: Rajan Vaja ; mturque...@baylibre.com
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Jolly Shah
>
dso__build_id_filename calls build_id_cache__linkname
build_id_cache__linkname uses buildid_dir
symbol__config_symfs includes the symfs directory in buildid_dir
So it's not necessary to prepend it again.
Should've included those notes in the original submission.
Will do better next time.
On Fri, 2018-03-09 at 13:20 -0500, Waiman Long wrote:
> On 03/09/2018 01:17 PM, Mike Galbraith wrote:
> > On Fri, 2018-03-09 at 12:45 -0500, Waiman Long wrote:
> >> On 03/09/2018 11:34 AM, Mike Galbraith wrote:
> >>> On Fri, 2018-03-09 at 10:35 -0500, Waiman Long wrote:
> Given the fact that
Am Dienstag, 27. Februar 2018, 17:37:45 CET schrieb Stephan Mueller:
Hi Jiri, Dimity, Henrik,
> Am Sonntag, 21. Januar 2018, 23:06:55 CET schrieb Stephan Müller:
>
> Hi Jiri, Dimity, Henrik,
>
> > Hi,
> >
> > Changes v3:
> > * port to 4.15-rc8
> > * small code cleanups (isolation of type
From: Mehmet Kayaalp
The iint cache stores whether the file is measured, appraised, audited
etc. This patch moves the IMA_AUDITED flag into the per-namespace
ns_status, enabling IMA audit mechanism to audit the same file each time
it is accessed in a new namespace.
From: Mehmet Kayaalp
This patch adds an rbtree to the IMA namespace structure that stores a
namespaced version of iint->flags in ns_status struct. Similar to the
integrity_iint_cache, both the iint ns_struct are looked up using the
inode pointer value. The lookup,
This patch set implements an IMA namespace data structure that gets
created alongside a mount namespace with CLONE_NEWNS, and lays down the
foundation for namespacing the different aspects of IMA (eg. IMA-audit,
IMA-measurement, IMA-appraisal).
The original PoC patches [1] created a new
Add driver for the Qualcomm interconnect buses found in msm8916 based
platforms.
Signed-off-by: Georgi Djakov
---
drivers/interconnect/Kconfig| 5 +
drivers/interconnect/Makefile | 1 +
drivers/interconnect/qcom/Kconfig | 11 +
On some Qualcomm SoCs, there is a remote processor, which controls some of
the Network-On-Chip interconnect resources. Other CPUs express their needs
by communicating with this processor. Add a driver to handle comminication
with this remote processor.
Signed-off-by: Georgi Djakov
This binding is intended to represent the interconnect hardware present
in some of the modern SoCs. Currently it consists only of a binding for
the interconnect hardware devices (provider).
Signed-off-by: Georgi Djakov
---
.../bindings/interconnect/interconnect.txt
Add a functionality to provide information about the current constraints
per each node and provider.
Signed-off-by: Georgi Djakov
---
drivers/interconnect/core.c | 70 +
1 file changed, 70 insertions(+)
diff --git
Currently we support only platform data for specifying the interconnect
endpoints. As now the endpoints are hard-coded into the consumer driver
this may leed to complications when a single driver is used by multiple
SoCs, which may have different interconnect topology.
To avoid cluttering the
On Fri, Mar 9, 2018 at 1:33 PM, Lina Iyer wrote:
> Hi Stephen,
>
> I will address all the comments in the next spin of the patch. Here are
> some responses to the questions.
>
> On Tue, Mar 06 2018 at 12:45 -0700, Stephen Boyd wrote:
>>
>> Quoting Lina Iyer (2018-03-02
On Fri, Mar 9, 2018 at 1:10 PM, Linus Torvalds
wrote:
> On Fri, Mar 9, 2018 at 12:05 PM, Kees Cook wrote:
>> When max() is used in stack array size calculations from literal values
>> (e.g. "char foo[max(sizeof(struct1), sizeof(struct2))]",
On Fri, Mar 09, 2018 at 03:58:20PM -0600, Eddie James wrote:
> From: Milton Miller
>
> Allow the device tree to specify a watchdog to fallover to
> the alternate boot source.
>
> The aspeeed watchdog can set a latch directing flash chip select 0 to
> chip select 1, allowing
The VSP1 devices define their specific capabilities through features
marked in their device info structure. Various parts of the code read
this info structure to infer if the features are available.
Wrap this into a more readable vsp1_feature(vsp1, f) macro to ensure
that usage is consistent
The pixel format is 'unsupported'. Fix the small debug message which
incorrectly declares this.
Signed-off-by: Kieran Bingham
---
drivers/media/platform/vsp1/vsp1_drm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Currently the firmware loader only exposes one silent path for querying
optional firmware, and that is request_firmware_direct(). This function
also disables the usermodehelper fallback which might not always be the
desired behaviour.
This patch introduces request_firmware_optional(), which will
On Fri, 09 Mar 2018 21:41:38 +0100 Greg Kurz wrote:
> If it was interrupted by a signal, the 9p client may need to send some
> more requests to the server for cleanup before returning to userspace.
>
> To avoid such a last minute request to be interrupted right away, the
>
Hi Everyone,
Wanted to inquire your opinions about the following matter.
We are experiencing some end user confusion regarding the following messages
being printed to dmesg:
[0.571324] amdgpu :01:00.0: Direct firmware load for
amdgpu/polaris10_pfp_2.bin failed with error -2
[
Hi!
Hmm. Looks like there's a lot of fun to be had with sysfs.
Pavel
pavel@n900:~$ uname -a
Linux n900 4.16.0-rc4-59690-g7f84626-dirty #543 Thu Mar 8 19:53:30 CET
2018 armv7l GNU/Linux
[ 306.402496] bq2415x: command Timer reset
From: zain wang
It's too early to detect fast link training, if other step after it
failed, we will set fast_link flag to 1, and retry set_bridge again. In
this case we will power down and power up panel power supply, and we
will do fast link training since we have set
On Fri, Mar 09, 2018 at 11:12:21PM +0100, Pavel Machek wrote:
> Hi!
>
> Hmm. Looks like there's a lot of fun to be had with sysfs.
>
> Pavel
>
>
> pavel@n900:~$ uname -a
> Linux n900 4.16.0-rc4-59690-g7f84626-dirty #543 Thu Mar 8
On 03/08/2018 03:08 PM, miny...@acm.org wrote:
From: Corey Minyard
The IPMI spec states:
The purpose of the SPMI Table is to provide a mechanism that can
be used by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management”
From: Douglas Anderson
The comments in analogix_dp_init_aux() claim that we're disabling aux
channel retries, but then right below it for Rockchip it sets them to
3. If we actually need 3 retries for Rockchip then we could adjust
the comment, but it seems more likely that
From: Douglas Anderson
Some of the platform-specific stuff in rockchip_dp_poweron() needs to
happen before the generic code. Some needs to happen after. Let's
split the callback in two.
Specifically we can't start doing PSR work until _after_ the whole
controller is up,
From: Miroslav Lichvar
When the timekeeping multiplier is changed, the NTP error is updated to
correct the clock for the delay between the tick and the update of the
clock. This error is corrected in later updates and the clock appears as
if the frequency was changed exactly
This patch adds high-level documentation about the Generic Counter
interface.
Signed-off-by: William Breathitt Gray
---
Documentation/driver-api/generic-counter.rst | 321 +++
Documentation/driver-api/index.rst | 1 +
MAINTAINERS
From: Benjamin Gaignard
rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they
rely on 32bits variables and that will make rtc break in y2038/2016.
Stop using those two functions to safer 64bits ones.
Cc: Arnd Bergmann
Cc: Thomas Gleixner
This is an attempt to move a few things out of the port driver.
I added these new patches since v1:
Merge pcieport_if.h into portdrv.h
Merge pcieport_if.h and portdrv.h to reduce clutter
Remove unnecessary "pcie_ports=auto" parameter
This is the default setting anyway, so specifying
From: Bjorn Helgaas
fe31e69740ed ("PCI/PCIe: Clear Root PME Status bits early during system
resume") added a .resume_noirq() callback to the PCIe port driver to clear
the PME Status bit during resume to work around a BIOS issue.
The BIOS evidently enabled PME interrupts for
From: Bjorn Helgaas
pcieport_if.h contained the interfaces to register port service driver,
e.g., pcie_port_service_register(). portdrv.h contained internal data
structures of the port driver.
I don't think it's worth keeping those files separate, since both headers
and
From: Bjorn Helgaas
Per PCIe r4.0, sec 6.1.6, Root Complex Event Collectors can generate PME
interrupts on behalf of Root Complex Integrated Endpoints.
Linux does not currently enable PME interrupts from RC Event Collectors,
but fe31e69740ed ("PCI/PCIe: Clear Root PME
From: Bjorn Helgaas
Move pcie_clear_root_pme_status() from the port driver to the PCI core so
it will be available even when the port driver isn't present. No
functional change intended.
Signed-off-by: Bjorn Helgaas
Reviewed-by: Rafael J. Wysocki
Hi Vivek,
On 03/02/2018 11:41 AM, Vivek Unune wrote:
> Hardware Info
> -
>
> Processor - Broadcom BCM4709C0KFEBG dual-core @ 1.4 GHz
> Switch- BCM53012 in BCM4709C0KFEBG & external BCM53125
> DDR3 RAM - 256 MB
> Flash - 128 MB (Toshiba
Yes, thought of doing that.
Unfortunately it was sent directly from git, so I do not have a copy of the
message that was sent.
MV
On 03/09/18 14:15, Kim Phillips wrote:
On Fri, 9 Mar 2018 13:49:50 -0500
Martin Vuille wrote:
For
The LSM check should happen after the file has been confirmed to be
unchanging. Without this, we could have a race between the Time of Check
(the call to security_kernel_read_file() which could read the file and
make access policy decisions) and the Time of Use (starting with
kernel_read_file()'s
Hi Eric,
> Eric Anholt hat am 9. März 2018 um 19:44 geschrieben:
>
>
> The VCHIQ communication channel can be provided by BCM283x and Capri
> SoCs, to communicate with the VPU-side OS services.
>
> Signed-off-by: Eric Anholt
> ---
>
> v2: VCHI->VCHIQ,
On Fri 2018-03-09 16:13:36, Suman Anna wrote:
> On 03/09/2018 06:08 AM, Robin Murphy wrote:
> > On 08/03/18 18:50, Pavel Machek wrote:
> >> Hi!
> >>
> * Pavel Machek [180308 14:31]:
> > Hi!
> >
> > I'm getting this warning... Has anyone seen/debugged that before?
>
On Fri, Mar 09, 2018 at 09:25:50PM +0100, Sebastian Andrzej Siewior wrote:
> Is it just about the irqsave() usage or something else? I doubt it is
> the list walk. It is still unbound if not called from irq-off region.
The current list walk is preemptible. You put the entire iteration (of
unbound
As soon as register_filesystem() exits, filesystem can be mounted.
It is better to present fully operational /proc.
Of course it doesn't matter because /proc is not modular
but do it anyway.
Drop error check, it should be handled by panicking.
Signed-off-by: Alexey Dobriyan
From: Tomasz Figa
It looks like the driver subsystem detaches devices from power domains
at shutdown without consent of the drivers. This means that we might have
our power domain turned off behind our back and the only way to avoid
problems is to stop doing any hardware
From: Tomasz Figa
It is not used anymore after last changes and it was not even correct to
begin with as it assumed a 1:1 relation between a CRTC and encoder,
while in fact a CRTC can be attached to multiple encoders.
Signed-off-by: Tomasz Figa
From: Tomasz Figa
If we change the state first and reschedule later, we might have the
work executed according to previous scheduled time and end up with PSR
re-enabled instantly. Let's cancel the work before changing the state.
While at it, consolidate psr_disable_handler()
From: Mark Yao
Some encoder have a crc verification check, crc check fail if
input and output data is not equal.
That means encoder input and output need use same color depth,
vop can output 10bit data to encoder, but some panel only support
8bit depth, that would make
From: Douglas Anderson
The current user of the analogix power_off is "analogix_dp-rockchip".
That driver does this:
- deactivate PSR
- turn off a clock
Both of these things (especially deactive PSR) should be done before
we turn the PHY power off and turn off analog
From: Tomasz Figa
Driver callbacks, such as system suspend or resume can be called any
time, specifically they can be called before the component bind
callback. Let's use dp->adp pointer as a safeguard and skip calling
Analogix entry points if it is an ERR_PTR().
Hey Thomas,
Just wanted to send along my timekeeping queue for 4.17.
Its a bit short, and I want to apologize as I've not had much
time for maintanance and review work. I worry if my current
workload levels persist, I might need to downgrade my status
in the maintainers file, as I'm not
This patch adds standard documentation for the Generic Counter interface
userspace sysfs attributes of the 104-QUAD-8 driver.
Signed-off-by: William Breathitt Gray
---
.../ABI/testing/sysfs-bus-counter-104-quad-8 | 115 +
MAINTAINERS
From: Miroslav Lichvar
When the length of the NTP tick changes significantly, e.g. when an
NTP/PTP application is correcting the initial offset of the clock, a
large value may accumulate in the NTP error before the multiplier
converges to the correct value. It may then take
1 - 100 of 2416 matches
Mail list logo