Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Fri, 25 Apr 2025 14:10:14 +0700 you wrote:
> Hi everyone,
>
> This only includes the selftest for virtio-net deadlock bug. The fix
> commit has been applied already.
>
> Link:
> https://lore.kernel.org/virtuali
On Fri, Apr 25, 2025 at 02:10:14PM +0700, Bui Quang Minh wrote:
> Hi everyone,
>
> This only includes the selftest for virtio-net deadlock bug. The fix
> commit has been applied already.
>
> Link:
> https://lore.kernel.org/virtualization/174537302875.2111809.8543884098526067319.git-patchwork-not
Hi everyone,
This only includes the selftest for virtio-net deadlock bug. The fix
commit has been applied already.
Link:
https://lore.kernel.org/virtualization/174537302875.2111809.8543884098526067319.git-patchwork-not...@kernel.org/T/
Version 6 changes:
- Rebase on net-next and resolve conflic
On Tue, Mar 18, 2025 at 6:14 PM Peter Hilber wrote:
>
> On Tue, Mar 18, 2025 at 10:04:07AM +0800, Lei Yang wrote:
> > QE tested this series of patches v6 with virtio-net regression tests,
> > everything works fine.
> >
> > Tested-by: Lei Yang
> >
>
> Hi Lei,
>
Hi Peter
> thanks for the reply! Ho
QE tested this series of patches v6 with virtio-net regression tests,
everything works fine.
Tested-by: Lei Yang
On Fri, Mar 14, 2025 at 1:38 AM Peter Hilber wrote:
>
> This series implements a driver for a virtio-rtc device conforming to spec
> proposal v8 [1]. It includes a PTP clock driver a
On Tue, Mar 18, 2025 at 10:04:07AM +0800, Lei Yang wrote:
> QE tested this series of patches v6 with virtio-net regression tests,
> everything works fine.
>
> Tested-by: Lei Yang
>
Hi Lei,
thanks for the reply! However, I am not sure which virtio-net regression
tests you are referring to, and
This series implements a driver for a virtio-rtc device conforming to spec
proposal v8 [1]. It includes a PTP clock driver and an RTC class driver
with alarm.
v6 updates
==
v6 fixes the PTP clock name length, and a few style issues, some of which
resulted in warnings.
Overview
On Thu, Jan 16, 2025 at 10:46:46PM +0530, Manivannan Sadhasivam wrote:
> Hi,
>
> This series carries forward the effort to add Kselftest for PCI Endpoint
> Subsystem started by Aman Gupta [1] a while ago. I reworked the initial
> version
> based on another patch that fixes the return values of IO
Hi,
This series carries forward the effort to add Kselftest for PCI Endpoint
Subsystem started by Aman Gupta [1] a while ago. I reworked the initial version
based on another patch that fixes the return values of IOCTLs in
pci_endpoint_test driver and did many cleanups. Since the resulting work
mod
At build time, create the file modules.builtin.ranges that will hold
address range data of the built-in modules that can be used by tracers.
Especially for tracing applications, it is convenient to be able to
refer to a symbol using a pair and to be able
to translate an address into a pair. But
This series adds a common samsung-matisse dtsi and reworks
samsung-matisse-wifi to use it, and introduces samsung-matisselte. I
choose matisselte over matisse-lte as this is how most other devices
(klte, s3ve3g) do it and it is the codename that Samsung gave the
device. See individual commits for m
The DAX drivers were missing sysfs ABI documentation entirely. Add this
missing documentation for the sysfs ABI for DAX regions and Dax devices
in patch 1. Switch to guard(device) semantics for Scope Based Resource
Management for device_{lock,unlock} flows in drivers/dax/bus.c in patch
2. Export m
Tightly-Coupled Memories(TCMs) are low-latency memory that provides
predictable instruction execution and predictable data load/store
timing. Each Cortex-R5F processor contains exclusive two 64 KB memory
banks on the ATCM and BTCM ports, for a total of 128 KB of memory.
In lockstep mode, both 128KB
The following series introduces K3 M4F remoteproc driver support for
AM64x and AM62x SoC families. These SoCs have a ARM Cortex M4F core in
the MCU voltage domain. For safety oriented applications, this core is
operated independently with out any IPC to other cores on the SoC.
However, for non safe
On 2/25/22 16:41, Nageswara Sastry wrote:
>
>
> On 25/02/22 12:08 pm, kajoljain wrote:
>>
>>
>> On 2/25/22 11:25, Nageswara Sastry wrote:
>>>
>>>
>>> On 17/02/22 10:03 pm, Kajol Jain wrote:
Patchset adds performance stats reporting support for nvdimm.
Added interface includes support
On 25/02/22 12:08 pm, kajoljain wrote:
On 2/25/22 11:25, Nageswara Sastry wrote:
On 17/02/22 10:03 pm, Kajol Jain wrote:
Patchset adds performance stats reporting support for nvdimm.
Added interface includes support for pmu register/unregister
functions. A structure is added called nvdim
On 2/25/22 13:17, Aneesh Kumar K V wrote:
> On Fri, 2022-02-25 at 12:08 +0530, kajoljain wrote:
>>
>>
>> On 2/25/22 11:25, Nageswara Sastry wrote:
>>>
>>>
>>> On 17/02/22 10:03 pm, Kajol Jain wrote:
>
Changelog
>>>
>>> Tested these patches with the automated tests at
>>> avoc
On Fri, 2022-02-25 at 12:08 +0530, kajoljain wrote:
>
>
> On 2/25/22 11:25, Nageswara Sastry wrote:
> >
> >
> > On 17/02/22 10:03 pm, Kajol Jain wrote:
> > >
> > >
> > > Changelog
> >
> > Tested these patches with the automated tests at
> > avocado-misc-tests/perf/perf_nmem.py
> > URL:
On 2/25/22 11:25, Nageswara Sastry wrote:
>
>
> On 17/02/22 10:03 pm, Kajol Jain wrote:
>> Patchset adds performance stats reporting support for nvdimm.
>> Added interface includes support for pmu register/unregister
>> functions. A structure is added called nvdimm_pmu to be used for
>> adding
On 17/02/22 10:03 pm, Kajol Jain wrote:
Patchset adds performance stats reporting support for nvdimm.
Added interface includes support for pmu register/unregister
functions. A structure is added called nvdimm_pmu to be used for
adding arch/platform specific data such as cpumask, nvdimm device
On Wed, Feb 23, 2022 at 11:07 AM Dan Williams wrote:
>
> On Fri, Feb 18, 2022 at 10:06 AM Dan Williams
> wrote:
> >
> > On Thu, Feb 17, 2022 at 8:34 AM Kajol Jain wrote:
> > >
> > > Patchset adds performance stats reporting support for nvdimm.
> > > Added interface includes support for pmu regi
On Fri, Feb 18, 2022 at 10:06 AM Dan Williams wrote:
>
> On Thu, Feb 17, 2022 at 8:34 AM Kajol Jain wrote:
> >
> > Patchset adds performance stats reporting support for nvdimm.
> > Added interface includes support for pmu register/unregister
> > functions. A structure is added called nvdimm_pmu t
On Thu, Feb 17, 2022 at 8:34 AM Kajol Jain wrote:
>
> Patchset adds performance stats reporting support for nvdimm.
> Added interface includes support for pmu register/unregister
> functions. A structure is added called nvdimm_pmu to be used for
> adding arch/platform specific data such as cpumask
Patchset adds performance stats reporting support for nvdimm.
Added interface includes support for pmu register/unregister
functions. A structure is added called nvdimm_pmu to be used for
adding arch/platform specific data such as cpumask, nvdimm device
pointer and pmu event functions like event_in
ARM64 server chip Kunpeng 920 has 6 or 8 clusters in each NUMA node, and each
cluster has 4 cpus. All clusters share L3 cache data while each cluster has
local L3 tag. On the other hand, each cluster will share some internal system
bus. This means cache is much more affine inside one cluster than a
This series generalizes the aspeed-vuart driver's device tree
properties to cover all the attributes it currently exposes via sysfs.
The aspeed,sirq-polarity-sense property was a bit of a design mistake
in that it ties Aspeed VUART SIRQ polarity to SCU register bits that
aren't really inherently r
Hi,
These are the remaining four patches of the series, now rebased on top
of the latest usb-next. No other changes.
v5 cover letter:
I have to use IS_REACHABLE() instead of IS_ENABLED() also in
include/linux/usb.h. Otherwise compilation will fail if the Type-C
class is build-in while USB is a
> From: Johan Jonker
> Date: Thu, 1 Apr 2021 23:36:48 +0200
>
> The conversion of rockchip,dwc3.txt to yaml was added to linux-next,
> but the necessary changes for rk3399 are still pending.
>
> For rk3399 dwc3 usb the wrapper node for only clocks makes no sense,
> so that was removed in the YA
The conversion of rockchip,dwc3.txt to yaml was added to linux-next,
but the necessary changes for rk3399 are still pending.
For rk3399 dwc3 usb the wrapper node for only clocks makes no sense,
so that was removed in the YAML example.
Now dtbs_check still generates notifications for the compatibi
utf8data.h_shipped has a large database table which is an auto-generated
decodification trie for the unicode normalization functions and it is not
necessary to carry this large table in the kernel.
Goal is to make UTF-8 encoding loadable by converting it into a module
and adding a layer between the
On Wed, Feb 24, 2021 at 03:23:01PM -0800, Bhaumik Bhatt wrote:
> v6:
> -Add patch to improve debug message
> -Fix switch-case fall through warning for EE serialization patch
> -Address review comments and update commit text
>
> v5:
> -Update commit text for "clear devices when moving execution env
Hello,
CPPC cpufreq driver is used for ARM servers and this patch series tries
to provide counter-based frequency invariance support for them in the
absence for architecture specific counters (like AMUs).
This is tested by:
- Vincent Guittot on ThunderX2.
- Ionela Voinescu on Juno R2.
- /me with
Hi,
this series contains cleanups to remove dead code that handles
unaligned cases for 4K and 1GB pages (patch#1 and patch#2) when
removing the vemmmap range, and a fix (patch#3) to handle the case
when two vmemmap ranges intersect the same PMD.
More details can be found in the respective changel
Hi all.
I'm joyful to suggest the block-layer interposer (blk_interposer) v6.
blk_interposer allows to intercept bio requests, remap bio to another
devices or add new bios.
This series of patches adds the ability to use blk_interposer for
any dm-target using the DM_INTERPOSED_FLAG flag.
The firs
v6:
-Add patch to improve debug message
-Fix switch-case fall through warning for EE serialization patch
-Address review comments and update commit text
v5:
-Update commit text for "clear devices when moving execution environments" patch
-Added test platform details that were missed out in the cov
This series adds support for new SoC MT6873/8192 to the spmi driver.
This series is based on Weiyi's patches[1].
[1]
https://patchwork.kernel.org/project/linux-mediatek/patch/1608642587-15634-7-git-send-email-weiyi...@mediatek.com/
changes since v5:
- fix the yaml error.
- refine the spmi-mtk-pm
Changes in v6:
- Address stephen's comments from v5 which includes below
- Pad 0 in documentation example to make address 8 digit
- define macro to calculate offset in driver
- Add appended_stats_avail to prv_data instead of using entire stats_config
- make array subsystems[] as const
- Add comment
v5 --> v6:
1. Use raw_spin_lock_irqsave() instead of spin_lock_irqsave()
2. Move the macros defined in cache-kunpeng-l3.h into cache-kunpeng-l3.c, and
delete that header file.
3. In some places, replace readl()/writel() with
readl_relaxed()/writel_relaxed() to improve performance without affectin
This series of patches adds support for x509 certificates signed by a CA
that uses NIST p256 or p192 keys for signing. It also adds support for
certificates where the public key is a NIST p256 or p192 key. The math
for ECDSA signature verification is also added.
Since self-signed certificates are
On 1/22/21 1:59 PM, Vincenzo Frascino wrote:
> This patchset implements the asynchronous mode support for ARMv8.5-A
> Memory Tagging Extension (MTE), which is a debugging feature that allows
> to detect with the help of the architecture the C and C++ programmatic
> memory errors like buffer overflo
This patchset implements the asynchronous mode support for ARMv8.5-A
Memory Tagging Extension (MTE), which is a debugging feature that allows
to detect with the help of the architecture the C and C++ programmatic
memory errors like buffer overflow, use-after-free, use-after-return, etc.
MTE is bui
Changes in V6:
- Rebased patches to usb-testing.
- Renamed to PATCH series instead of RFC.
- Checking for fs_descriptors instead of ss_descriptors for determining the
endpoint count for a particular configuration.
- Re-ordered patch series to fix patch dependencies.
Changes in V5:
- Added
Scatter-gather lists (sgl_s) are frequently used as data carriers in
the block layer. For example the SCSI and NVMe subsystems interchange
data with the block layer using sgl_s. The sgl API is declared in
The author has extended these transient sgl use cases to a store (i.e.
a ramdisk) in the scs
Hi All,
In this V6 posting I have addressed comments on reworking the scmi cpufreq
driver in smaller changes.
This is to support systems where exposed cpu performance controls are more
fine-grained that the platform's ability to scale cpus independently.
Many thanks,
Nicola
[v6]
* Remove defe
Hi!
Follow-up on the v5 [1], things have gotten significantly
better in the last 9 months, thanks to the efforts on Bifrost
support by the Collabora team (and probably others I'm not
aware of).
I've been testing this series on a MT8183/kukui device, with a
chromeos-5.10 kernel [2], and got basic
This set introduces perf-stat -b option to count events for BPF programs.
This is similar to bpftool-prog-profile. But perf-stat makes it much more
flexible.
Changes v5 => v6
1. Update the name for bootstrap bpftool. (Jiri)
Changes v4 => v5:
1. Add documentation. (Jiri)
2. Silent make outpu
v5->v6:
1. Drop #size-cells and #address-cell in the hisilicon,hi3559av100-clock.yaml
2. Add discription for #reset-cells in the hisilicon,hi3559av100-clock.yaml
3. Remove #clock-cells in hisilicon,hiedmacv310.yaml
4. Merge property misc_ctrl_base and misc_regmap together for hiedmacv310 driver
v
From: g00384164
v5->v6:
1. Drop #size-cells and #address-cell in the hisilicon,hi3559av100-clock.yaml
2. Add discription for #reset-cells in the hisilicon,hi3559av100-clock.yaml
3. Remove #clock-cells in hisilicon,hiedmacv310.yaml
4. Merge property misc_ctrl_base and misc_regmap together for hie
On Wed, Dec 02, 2020 at 07:54:40AM -0800, Doug Anderson wrote:
> On Wed, Dec 2, 2020 at 7:20 AM Benjamin Tissoires
> wrote:
> > On Tue, Dec 1, 2020 at 10:12 PM Doug Anderson wrote:
> > > On Wed, Nov 11, 2020 at 4:41 PM Douglas Anderson
> > > wrote:
> > > > .../bindings/input/goodix,gt7375p.yam
Hi,
On Wed, Dec 2, 2020 at 7:20 AM Benjamin Tissoires
wrote:
>
> Hi Doug,
>
> On Tue, Dec 1, 2020 at 10:12 PM Doug Anderson wrote:
> >
> > Hi,
> >
> > On Wed, Nov 11, 2020 at 4:41 PM Douglas Anderson
> > wrote:
> > >
> > > The goal of this series is to support the Goodix GT7375P touchscreen.
>
Hi Doug,
On Tue, Dec 1, 2020 at 10:12 PM Doug Anderson wrote:
>
> Hi,
>
> On Wed, Nov 11, 2020 at 4:41 PM Douglas Anderson
> wrote:
> >
> > The goal of this series is to support the Goodix GT7375P touchscreen.
> > This touchscreen is special because it has power sequencing
> > requirements that
nux Kernel Mailing List ; Raja Subramanian,
>Lakshmi Bai ; Wan Mohamad,
>Wan Ahmad Zainie ; Mark
>Gross
>Subject: Re: [PATCH v6 0/4] mmc: sdhci-of-arasan: Enable UHS-1 support for
>Keem Bay SOC
>
>On Wed, Dec 2, 2020 at 4:10 PM Ulf Hansson
>wrote:
>> On Wed, 2 Dec 2020
On Wed, Dec 2, 2020 at 4:10 PM Ulf Hansson wrote:
> On Wed, 2 Dec 2020 at 14:09, Andy Shevchenko
> wrote:
> > On Wed, Dec 2, 2020 at 2:44 PM Ulf Hansson wrote:
...
> > My point is that it may be *not* a pin control at all.
>
> Sorry, but I don't quite follow, what is *not* a pinctrl?
>
> Acco
On Wed, 2 Dec 2020 at 14:09, Andy Shevchenko wrote:
>
> On Wed, Dec 2, 2020 at 2:44 PM Ulf Hansson wrote:
> > On Wed, 2 Dec 2020 at 13:24, Shevchenko, Andriy
> > wrote:
> > > On Wed, Dec 02, 2020 at 11:53:42AM +0100, Ulf Hansson wrote:
> > > > On Wed, 2 Dec 2020 at 08:02,
> > > > wrote:
> > >
On Wed, Dec 2, 2020 at 2:44 PM Ulf Hansson wrote:
> On Wed, 2 Dec 2020 at 13:24, Shevchenko, Andriy
> wrote:
> > On Wed, Dec 02, 2020 at 11:53:42AM +0100, Ulf Hansson wrote:
> > > On Wed, 2 Dec 2020 at 08:02, wrote:
> >
> > ...
> >
> > > > Kindly help to review this patch set.
> > >
> > > This v
Adding the Sparx5 Serdes driver
This series of patches provides the serdes driver for the Microchip Sparx5
ethernet switch.
The serdes driver supports the 10G and 25G serdes instances available in the
Sparx5.
The Sparx5 serdes support several interface modes with several speeds and also
allows t
On Wed, 2 Dec 2020 at 13:24, Shevchenko, Andriy
wrote:
>
> On Wed, Dec 02, 2020 at 11:53:42AM +0100, Ulf Hansson wrote:
> > On Wed, 2 Dec 2020 at 08:02, wrote:
>
> ...
>
> > > Kindly help to review this patch set.
> >
> > This version looks a lot better to me, but I am still requesting you
> > to
On Wed, Dec 02, 2020 at 11:53:42AM +0100, Ulf Hansson wrote:
> On Wed, 2 Dec 2020 at 08:02, wrote:
...
> > Kindly help to review this patch set.
>
> This version looks a lot better to me, but I am still requesting you
> to model the pinctrl correctly. I don't see a reason not to, but I may
> ha
On Wed, 2 Dec 2020 at 08:02, wrote:
>
> From: Muhammad Husaini Zulkifli
>
> Hello
>
> This patch series adds UHS-1 Support for Keem Bay SOC.
>
> Patch 1 : Add struct device *dev in probe func(),so that dev pointer can be
> widely use in probe to make code more readable.
> Patch 2 : Export functi
From: Muhammad Husaini Zulkifli
Hello
This patch series adds UHS-1 Support for Keem Bay SOC.
Patch 1 : Add struct device *dev in probe func(),so that dev pointer can be
widely use in probe to make code more readable.
Patch 2 : Export function to be use by device driver to configure voltage rai
Hi,
On Wed, Nov 11, 2020 at 4:41 PM Douglas Anderson wrote:
>
> The goal of this series is to support the Goodix GT7375P touchscreen.
> This touchscreen is special because it has power sequencing
> requirements that necessitate driving a reset GPIO.
>
> To do this, we totally rejigger the way i2c
Hi Vinod,
On Mon, Nov 30, 2020 at 11:48 AM Vinod Koul wrote:
>
> On 21-11-20, 16:50, Sergio Paracuellos wrote:
> > This series adds support for the PCIe PHY found in the Mediatek
> > MT7621 SoC.
> >
> > There is also a 'mt7621-pci' driver which is the controller part
> > which is still in staging
On 21-11-20, 16:50, Sergio Paracuellos wrote:
> This series adds support for the PCIe PHY found in the Mediatek
> MT7621 SoC.
>
> There is also a 'mt7621-pci' driver which is the controller part
> which is still in staging and is a client of this phy.
>
> Both drivers have been tested together in
This series adds support for the PCIe PHY found in the Mediatek
MT7621 SoC.
There is also a 'mt7621-pci' driver which is the controller part
which is still in staging and is a client of this phy.
Both drivers have been tested together in a gnubee1 board.
This series are rebased on the top of lin
This series adds support for the Embedded Controller which is found on
Acer Iconia Tab A500 (Android tablet device).
The Embedded Controller is ENE KB930 and it's running firmware customized
for the A500. The firmware interface may be reused by some other sibling
Acer tablets, although none of tho
Initial support for ROHM BD9576MUF and BD9573MUF PMICs.
These PMICs are primarily intended to be used to power the R-Car family
processors. BD9576MUF includes some additional safety features the
BD9573MUF does not have. This initial version of drivers does not
utilize these features and for now th
The goal of this series is to support the Goodix GT7375P touchscreen.
This touchscreen is special because it has power sequencing
requirements that necessitate driving a reset GPIO.
To do this, we totally rejigger the way i2c-hid is organized so that
it's easier to jam the Goodix support in ther
Oops, this one has some rebase errors, I'll send v7 soon.
Sorry for the noise.
On Mon, Nov 09, 2020 at 06:24:11PM +0200, Mike Rapoport wrote:
> From: Mike Rapoport
>
> Hi,
>
> During recent discussion about KVM protected memory, David raised a concern
> about usage of __kernel_map_pages() outsi
From: Mike Rapoport
Hi,
During recent discussion about KVM protected memory, David raised a concern
about usage of __kernel_map_pages() outside of DEBUG_PAGEALLOC scope [1].
Indeed, for architectures that define CONFIG_ARCH_HAS_SET_DIRECT_MAP it is
possible that __kernel_map_pages() would fail,
Updated patchset.
Split the patch to separate mv88e6393 changes from refactoring
serdes_get_lane.
Update Documentation before adding new mode.
> Is the 6191X part of the 6193 family? Not the 6390, like the 6191 is?
> Or do we have the 6191 in the wrong family?
>> +MV88E6193X,
> You don't ad
On Thu, 29 Oct 2020 15:40:25 +1000
Pavana Sharma wrote:
> Updated patchset.
>
> Split the patch to separate mv88e6393 changes from refactoring
> serdes_get_lane.
> Update Documentation before adding new mode.
Pavana, the patch adding support for Amethyst has to be the last in the
series. The pa
Currently a non-slab kernel page which has been charged to a memory
cgroup can't be mapped to userspace. The underlying reason is simple:
PageKmemcg flag is defined as a page type (like buddy, offline, etc),
so it takes a bit from a page->mapped counter. Pages with a type set
can't be mapped to use
This series introduces a generic pattern interface in the LED class and
a driver for the Qualcomm Light Pulse Generator.
It seems like it's been almost 3 years since I posted v3, which was hung
up on the lack of conclusion on the hw_pattern and multicolor support.
Now that those are concluded I ho
Change in v6:
1)use devm_clk_get function for required clocks
Change in v5:
1)remove Reviewed-by tag
2)use devm_clk_bulk_get_optional instead of devm_clk_get_optional
for bulk clks
Change in v4:
1)drop "vmmc" and "vqmmc" desciption in mtk-sd.yaml
2)add vmmq/vqmmc supplies and the pinctrls to re
Sometimes firmware sizes can be in tens of MB's and reading all the memory
during coredump can consume lot of time and memory.
Introducing support for mini-dumps. Mini-dump contains smallest amount of
useful information, that could help to debug subsystem crashes.
During bootup memory is allocate
On Wed, 2020-09-23 at 00:10 +0300, Maxim Levitsky wrote:
> This is the next version of this patch series.
>
> In V5 I adopted Sean Christopherson's suggestion to make .set_efer return
> a negative error (-ENOMEM in this case) which in most cases in kvm
> propagates to the userspace.
>
> I noticed
On Wed, Sep 23, 2020 at 11:22:07AM -0400, Joel Fernandes (Google) wrote:
>
> This is required for several usecases identified. One of them being tracing
> how
> the segmented callback list changes. Tracing this has identified issues in RCU
> code in the past.
>
> >From Paul:
> Another use case i
This is required for several usecases identified. One of them being tracing how
the segmented callback list changes. Tracing this has identified issues in RCU
code in the past.
>From Paul:
Another use case is of course more accurately determining whether a given CPU's
large pile of callbacks can
This is the next version of this patch series.
In V5 I adopted Sean Christopherson's suggestion to make .set_efer return
a negative error (-ENOMEM in this case) which in most cases in kvm
propagates to the userspace.
I noticed though that wrmsr emulation code doesn't do this and instead
it inject
Add support for TEE based trusted keys where TEE provides the functionality
to seal and unseal trusted keys using hardware unique key. Also, this is
an alternative in case platform doesn't possess a TPM device.
This patch-set has been tested with OP-TEE based early TA which is already
merged in up
"user space client interface driver" is a very generic and there is
absolutel no explanation in this cover letter. What is this supposed
to be?
V6:
- Moved uci.c to mhi directory.
- Updated Kconfig to add module information.
- Updated Makefile to rename uci object file name as mhi_uci
- Removed kref for open count
V5:
- Removed mhi_uci_drv structure.
- Used idr instead of creating global list of uci devices.
- Used kref instead of local r
On Mon 14 Sep 13:58 UTC 2020, satya priya wrote:
> Changes in V2:
> - As per Matthias's comment added wakeup support for all the UARTs
>of SC7180.
> - Added sleep state in sc7180-idp.dts file.
> - Modify the if check in set_mctrl API in serial driver to avoid
>making RFR high during sus
Changes in V2:
- As per Matthias's comment added wakeup support for all the UARTs
of SC7180.
- Added sleep state in sc7180-idp.dts file.
- Modify the if check in set_mctrl API in serial driver to avoid
making RFR high during suspend.
Changes in V3:
- As per Matthias's comments modify the
From: Frank Wunderlich
This Patch-Series adds missing Patches/Bugfixes to get hdmi working
on BPI-R2
v5->v6:
- drop parts already merged to mediatek-drm-next
- include lima-regulator-patch
- rebase on changes in mediatek-drm-next tree (hdmi/hdmi-phy patches)
- fix compatible of hdmi0 because
On Fri, Aug 21, 2020 at 1:05 PM Roman Gushchin wrote:
>
> On Fri, Aug 21, 2020 at 09:27:56AM -0700, Shakeel Butt wrote:
> > On Fri, Aug 21, 2020 at 9:02 AM Roman Gushchin wrote:
> > >
> > > On Fri, Aug 21, 2020 at 11:04:05AM -0400, Dan Schatzberg wrote:
> > > > On Thu, Aug 20, 2020 at 10:06:44AM
On Fri, Aug 21, 2020 at 09:27:56AM -0700, Shakeel Butt wrote:
> On Fri, Aug 21, 2020 at 9:02 AM Roman Gushchin wrote:
> >
> > On Fri, Aug 21, 2020 at 11:04:05AM -0400, Dan Schatzberg wrote:
> > > On Thu, Aug 20, 2020 at 10:06:44AM -0700, Shakeel Butt wrote:
> > > > On Thu, May 28, 2020 at 6:55 AM
On Fri, Aug 21, 2020 at 9:02 AM Roman Gushchin wrote:
>
> On Fri, Aug 21, 2020 at 11:04:05AM -0400, Dan Schatzberg wrote:
> > On Thu, Aug 20, 2020 at 10:06:44AM -0700, Shakeel Butt wrote:
> > > On Thu, May 28, 2020 at 6:55 AM Dan Schatzberg
> > > wrote:
> > > >
> > > > Much of the discussion abo
On Fri, Aug 21, 2020 at 11:04:05AM -0400, Dan Schatzberg wrote:
> On Thu, Aug 20, 2020 at 10:06:44AM -0700, Shakeel Butt wrote:
> > On Thu, May 28, 2020 at 6:55 AM Dan Schatzberg
> > wrote:
> > >
> > > Much of the discussion about this has died down. There's been a
> > > concern raised that we co
On 8/21/20 9:04 AM, Dan Schatzberg wrote:
> On Thu, Aug 20, 2020 at 10:06:44AM -0700, Shakeel Butt wrote:
>> On Thu, May 28, 2020 at 6:55 AM Dan Schatzberg
>> wrote:
>>>
>>> Much of the discussion about this has died down. There's been a
>>> concern raised that we could generalize infrastructure
On Thu, Aug 20, 2020 at 10:06:44AM -0700, Shakeel Butt wrote:
> On Thu, May 28, 2020 at 6:55 AM Dan Schatzberg
> wrote:
> >
> > Much of the discussion about this has died down. There's been a
> > concern raised that we could generalize infrastructure across loop,
> > md, etc. This may be possible
On Thu, May 28, 2020 at 6:55 AM Dan Schatzberg wrote:
>
> Much of the discussion about this has died down. There's been a
> concern raised that we could generalize infrastructure across loop,
> md, etc. This may be possible, in the future, but it isn't clear to me
> how this would look like. I'm i
On 8/5/20 11:25 AM, Casey Schaufler wrote:
I think moving away from the idea that measuring "critical" data should
be limited to LSMs, will clarify this.
Are you suggesting that instead of calling the hooks LSM_STATE and LSM_POLICY, we should
keep it more generic so that it can be utilized
From: Sandeep Singh
AMD SFH(Sensor Fusion Hub) is HID based driver.SFH FW is part of MP2
processor (MP2 which is an ARM® Cortex-M4 core based co-processor to x86)
and it runs on MP2 where in driver resides on X86.The driver
functionalities are divided into three parts:-
1: amd-mp2-pcie:- This
On 2020-08-05 09:07:48, Lakshmi Ramasubramanian wrote:
> On 8/5/20 8:45 AM, Tyler Hicks wrote:
> > On 2020-08-05 08:36:40, Casey Schaufler wrote:
> > > On 8/4/2020 6:14 PM, Lakshmi Ramasubramanian wrote:
> > > > On 8/4/20 6:04 PM, Casey Schaufler wrote:
> > > > > On 8/4/2020 5:43 PM, Lakshmi Ramasu
On 8/5/20 9:14 AM, Tyler Hicks wrote:
On 2020-08-05 09:07:48, Lakshmi Ramasubramanian wrote:
On 8/5/20 8:45 AM, Tyler Hicks wrote:
On 2020-08-05 08:36:40, Casey Schaufler wrote:
On 8/4/2020 6:14 PM, Lakshmi Ramasubramanian wrote:
On 8/4/20 6:04 PM, Casey Schaufler wrote:
On 8/4/2020 5:43 PM,
On 2020-08-05 09:21:24, Lakshmi Ramasubramanian wrote:
> On 8/5/20 9:14 AM, Tyler Hicks wrote:
> > On 2020-08-05 09:07:48, Lakshmi Ramasubramanian wrote:
> > > On 8/5/20 8:45 AM, Tyler Hicks wrote:
> > > > On 2020-08-05 08:36:40, Casey Schaufler wrote:
> > > > > On 8/4/2020 6:14 PM, Lakshmi Ramasub
On 8/5/2020 9:32 AM, Tyler Hicks wrote:
> On 2020-08-05 09:21:24, Lakshmi Ramasubramanian wrote:
>> On 8/5/20 9:14 AM, Tyler Hicks wrote:
>>> On 2020-08-05 09:07:48, Lakshmi Ramasubramanian wrote:
On 8/5/20 8:45 AM, Tyler Hicks wrote:
> On 2020-08-05 08:36:40, Casey Schaufler wrote:
>>
On 8/5/2020 10:25 AM, Lakshmi Ramasubramanian wrote:
> On 8/5/20 10:03 AM, Mimi Zohar wrote:
>> On Wed, 2020-08-05 at 10:45 -0500, Tyler Hicks wrote:
>>
>>> In addition to SELINUX_STATE and SELINUX_POLICY, we should also consider
>>> the proposed LSM_STATE and LSM_POLICY func values but require an
On 8/5/20 10:57 AM, Casey Schaufler wrote:
On 8/5/2020 10:25 AM, Lakshmi Ramasubramanian wrote:
On 8/5/20 10:03 AM, Mimi Zohar wrote:
On Wed, 2020-08-05 at 10:45 -0500, Tyler Hicks wrote:
In addition to SELINUX_STATE and SELINUX_POLICY, we should also consider
the proposed LSM_STATE and LSM_P
1 - 100 of 536 matches
Mail list logo
