This series enabled Intel FGPA SmartNIC C5000X-PL virtio-blk for vDPA.
This series requires:
Stefano's vdpa block patchset: https://lkml.org/lkml/2021/3/15/2113
my patchset to enable Intel FGPA SmartNIC C5000X-PL virtio-net for vDPA:
https://lkml.org/lkml/2021/3/17/432
changes from V1:
(1)add com
This patch series adds support for the Ethernet MAC found on the Actions
Semi Owl family of SoCs.
For the moment I have only tested the driver on RoseapplePi SBC, which is
based on the S500 SoC variant. It might work on S900 as well, but I cannot
tell for sure since the S900 datasheet I currently
Some kernel functions must not be called holding a specific lock. Doing
so could lead to locking problems. Currently these routines call
lock_is_held() to check for lock hold followed by WARN_ON.
Adding a common lockdep interface will help reduce the duplication of this
logic in the rest of the ke
This set attempts to fix a few independent issues recently found
in mlx5_vdpa driver. Please find details for each in the commit
message.
Patch 1 and patch 3 are already Ack'ed by Jason Wang. Patch 2 is
reworked to move virtio feature capability query to mlx5v_probe()
as suggested by Eli.
--
v1->
On 1/21/21 9:34 PM, Thara Gopinath wrote:
thermal_notify_framework just updates for a single trip point where as
thermal_zone_device_update does other bookkeeping like updating the
temperature of the thermal zone, running through the list of trip points
and setting the next trip point etc. Sin
On Fri, 22 Jan 2021 10:24:46 +0100,
Uwe Kleine-König wrote:
>
> Hello,
>
> changes since v1
> (https://lore.kernel.org/r/20210121204812.402589-1-...@kleine-koenig.org):
> - fix build failure, found by the kernel test robot
>(my grep missed the struct isa_driver embedded in struct
>radio_
Hello,
changes since v1
(https://lore.kernel.org/r/20210121204812.402589-1-...@kleine-koenig.org):
- fix build failure, found by the kernel test robot
(my grep missed the struct isa_driver embedded in struct
radio_isa_driver). For this I introduced patch 2 and adapted patch 3
a bit. An i
thermal_notify_framework just updates for a single trip point where as
thermal_zone_device_update does other bookkeeping like updating the
temperature of the thermal zone, running through the list of trip points
and setting the next trip point etc. Since the later is a more thorough
version of for
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 8 Jan 2021 16:53:40 -0800 you wrote:
> From: Long Li
>
> This patch set fixes issues with packet loss on VF add/remove.
>
> Long Li (3):
> hv_netvsc: Check VF datapath when sending traffic to VF
> hv_netvsc
> Subject: Re: [PATCH v2 0/3] hv_netvsc: Prevent packet loss during VF
> add/remove
>
> On Fri, 8 Jan 2021 16:53:40 -0800 Long Li wrote:
> > From: Long Li
> >
> > This patch set fixes issues with packet loss on VF add/remove.
>
> These patches are for net-ne
On Fri, 8 Jan 2021 16:53:40 -0800 Long Li wrote:
> From: Long Li
>
> This patch set fixes issues with packet loss on VF add/remove.
These patches are for net-next? They just optimize the amount of packet
loss on switch, not fix bugs, right?
From: Long Li
This patch set fixes issues with packet loss on VF add/remove.
Long Li (3):
hv_netvsc: Check VF datapath when sending traffic to VF
hv_netvsc: Wait for completion on request SWITCH_DATA_PATH
hv_netvsc: Process NETDEV_GOING_DOWN on VF hot remove
drivers/net/hyperv/netvsc.c
This is second patch series which adds workaround for broken GPON SFP
modules based on Realtek RTL8672/RTL9601C chips with broken EEPROM
emulator.
PATCH 2/4 was dropped and replaced by specific UBNT quirk in modified
PATCH v2 3/3.
hwmon interface was for these SFP modules completely disabled as E
If we know that a device has broken parity checking, then disable it.
This avoids quirks like in r8169 where on the first parity error
interrupt parity checking will be disabled if broken_parity_status
is set. Make pci_quirk_broken_parity() public so that it can be used
by platform code, e.g. for T
This patch series implements jump padding to x64 jit to cover some
corner cases that used to consume more than 20 passes and caused
failure.
v2:
- Simplify the sample code in the commit description and provide the
jit code
- Check the expected padding bytes with WARN_ONCE
- Move the 'pad
On Mon, Nov 02, 2020 at 04:14:44PM +, Dmitry Safonov wrote:
> v2: Added "Fixes" tags to the patches.
>
> WARN_ON() for XFRMA_UNSPEC translation which likely no-one except
> syzkaller uses; properly zerofy tail-padding for 64-bit attribute;
> don't use __GFP_ZERO as the memory is initialized du
This series converts the remaining drivers to use new
tasklet_setup() API.
The patches are based on wireless-drivers-next (c2568c8c9e63)
Is this series queue? I haven't seen any email. This is the last
series as part of the tasklet conversion effort.
They are queued in linux-wireless patch
Allen Pais writes:
>>
>> This series converts the remaining drivers to use new
>> tasklet_setup() API.
>>
>> The patches are based on wireless-drivers-next (c2568c8c9e63)
>
> Is this series queue? I haven't seen any email. This is the last
> series as part of the tasklet conversion effort.
They
This series converts the remaining drivers to use new
tasklet_setup() API.
The patches are based on wireless-drivers-next (c2568c8c9e63)
Is this series queue? I haven't seen any email. This is the last
series as part of the tasklet conversion effort.
Thanks.
v2:
Split mt76 and mt76
v2: Added "Fixes" tags to the patches.
WARN_ON() for XFRMA_UNSPEC translation which likely no-one except
syzkaller uses; properly zerofy tail-padding for 64-bit attribute;
don't use __GFP_ZERO as the memory is initialized during translation.
Cc: Steffen Klassert
Cc: "David S. Miller"
Cc: Jakub
This small series gets my hardware into a working state. The key points are to
make sure we don't force the link and that we ask the MAC for the link status.
I also have updated my dts to say `phy-mode = "1000base-x";` and `managed =
"in-band-status";`
I've included patch #3 in this series but I d
On Mon, 2020-10-12 at 14:18 +0300, Aleksandr Nogikh wrote:
>
> Currently we're injecting frames via mac80211_hwsim (by pretenting to
> be wmediumd -
> https://github.com/google/syzkaller/blob/4a77ae0bdc5cd75ebe88ce7c896aae6bbf457a29/executor/common_linux.h#L4922).
Ah, ok, of course that works too
On Sun, 11 Oct 2020 at 21:50, Johannes Berg wrote:
[...]
> Also, unrelated to that (but I see Dmitry CC'ed), I started wondering if
> it'd be helpful to have an easier raw 802.11 inject path on top of say
> hwsim0; I noticed some syzbot reports where it created raw sockets, but
> that only gets yo
On Fri, 2020-10-09 at 17:01 +, Aleksandr Nogikh wrote:
> From: Aleksandr Nogikh
>
> This patch series enables remote KCOV coverage collection during
> 802.11 frames processing. These changes make it possible to perform
> coverage-guided fuzzing in search of remotely triggerable bugs.
Btw, it
On 11 October 2020 12:37:29 CEST, Andrey Konovalov
wrote:
>I initially hesitated to do that, as it would multiply the number of
>kcov callbacks. But perhaps you're right and a clean API look
>outweighs the rest. I will do this in v3.
Yeah, OK, dunno. You can always make it an inline calling
On 9 October 2020 19:01:59 CEST, Aleksandr Nogikh wrote:
>This patch series conflicts with another proposed patch
>http://lkml.kernel.org/r/223901affc7bd759b2d6995c2dbfbdd0a29bc88a.1602248029.git.andreyk...@google.com
>One of these patches needs to be rebased once the other one is merged.
Ma
From: Aleksandr Nogikh
This patch series enables remote KCOV coverage collection during
802.11 frames processing. These changes make it possible to perform
coverage-guided fuzzing in search of remotely triggerable bugs.
Normally, KCOV collects coverage information for the code that is
executed i
From: Allen Pais
This series converts the remaining drivers to use new
tasklet_setup() API.
The patches are based on wireless-drivers-next (c2568c8c9e63)
v2:
Split mt76 and mt7601u
Allen Pais (3):
wireless: mt76: convert tasklets to use new tasklet_setup() API
wireless: mt7601u: convert
can: flexcan: initialize all flexcan memory for ECC function
can: flexcan: add flexcan driver for i.MX8MP
These two patches add i.MX8MP driver support.
can: flexcan: disable runtime PM if register flexcandev failed
Resend this patch as a small driver improvement.
Joakim Zhang (3):
can: flexcan:
On 9/23/20 1:12 PM, Michael Jeanson wrote:
>
> Just a final clarification, the asymmetric setup would have no return
> route in VRF 2 and only test the TTL case since the others would fail?
correct. add a statement about it representing a customer setup so it is
clear such a config is a 1-off
On 2020-09-23 14 h 46, David Ahern wrote:
On 9/23/20 11:03 AM, Michael Jeanson wrote:
On 2020-09-23 12 h 04, Michael Jeanson wrote:
It should work without asymmetric routing; adding the return route to
the second vrf as I mentioned above fixes the FRAG_NEEDED problem. It
should work for TTL as
On 9/23/20 11:03 AM, Michael Jeanson wrote:
> On 2020-09-23 12 h 04, Michael Jeanson wrote:
>>> It should work without asymmetric routing; adding the return route to
>>> the second vrf as I mentioned above fixes the FRAG_NEEDED problem. It
>>> should work for TTL as well.
>>>
>>> Adding a second pa
On 2020-09-23 12 h 04, Michael Jeanson wrote:
It should work without asymmetric routing; adding the return route to
the second vrf as I mentioned above fixes the FRAG_NEEDED problem. It
should work for TTL as well.
Adding a second pass on the tests with the return through r2 is fine,
but add a f
On 2020-09-22 21 h 59, David Ahern wrote:
On 9/22/20 7:52 AM, Michael Jeanson wrote:
the test setup is bad. You have r1 dropping the MTU in VRF red, but not
telling VRF red how to send back the ICMP. e.g., for IPv4 add:
ip -netns r1 ro add vrf red 172.16.1.0/24 dev blue
do the same for v6
On 9/22/20 7:52 AM, Michael Jeanson wrote:
>>>
>>> the test setup is bad. You have r1 dropping the MTU in VRF red, but not
>>> telling VRF red how to send back the ICMP. e.g., for IPv4 add:
>>>
>>>ip -netns r1 ro add vrf red 172.16.1.0/24 dev blue
>>>
>>> do the same for v6.
>>>
>>> Also, I do
- On 21 Sep, 2020, at 15:33, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Sep 21, 2020, at 3:11 PM, David Ahern dsah...@gmail.com wrote:
>
>> On 9/21/20 12:44 PM, Mathieu Desnoyers wrote:
>>> - On Sep 21, 2020, at 2:36 PM, David Ahern dsah...@gmail.com wrote:
>>>
>
- On Sep 21, 2020, at 3:11 PM, David Ahern dsah...@gmail.com wrote:
> On 9/21/20 12:44 PM, Mathieu Desnoyers wrote:
>> - On Sep 21, 2020, at 2:36 PM, David Ahern dsah...@gmail.com wrote:
>>
>>> On 9/18/20 12:17 PM, Mathieu Desnoyers wrote:
Hi,
Here is an updated series of f
On 9/21/20 12:44 PM, Mathieu Desnoyers wrote:
> - On Sep 21, 2020, at 2:36 PM, David Ahern dsah...@gmail.com wrote:
>
>> On 9/18/20 12:17 PM, Mathieu Desnoyers wrote:
>>> Hi,
>>>
>>> Here is an updated series of fixes for ipv4 and ipv6 which which ensure
>>> the route lookup is performed on th
- On Sep 21, 2020, at 2:36 PM, David Ahern dsah...@gmail.com wrote:
> On 9/18/20 12:17 PM, Mathieu Desnoyers wrote:
>> Hi,
>>
>> Here is an updated series of fixes for ipv4 and ipv6 which which ensure
>> the route lookup is performed on the right routing table in VRF
>> configurations when se
On 9/18/20 12:17 PM, Mathieu Desnoyers wrote:
> Hi,
>
> Here is an updated series of fixes for ipv4 and ipv6 which which ensure
> the route lookup is performed on the right routing table in VRF
> configurations when sending TTL expired icmp errors (useful for
> traceroute).
>
> It includes tests
Hi,
Here is an updated series of fixes for ipv4 and ipv6 which which ensure
the route lookup is performed on the right routing table in VRF
configurations when sending TTL expired icmp errors (useful for
traceroute).
It includes tests for both ipv4 and ipv6.
These fixes address specifically addr
Hi Abhishek,
> This series adds the suspend/resume events suggested in
> https://patchwork.kernel.org/patch/11771001/.
>
> I have tested it with some userspace changes that monitors the
> controller resumed event to trigger audio device reconnection and
> verified that the events are correctly em
Hi Marcel,
This series adds the suspend/resume events suggested in
https://patchwork.kernel.org/patch/11771001/.
I have tested it with some userspace changes that monitors the
controller resumed event to trigger audio device reconnection and
verified that the events are correctly emitted.
Patc
From: Johannes Berg
Date: Tue, 18 Aug 2020 10:17:30 +0200
> In quite a few places (perhaps particularly in wireless) we need to
> validation an NLA_BINARY attribute with both a minimum and a maximum
> length. Currently, we can do either of the two, but not both, given
> that we have NLA_MIN_LEN (
In quite a few places (perhaps particularly in wireless) we need to
validation an NLA_BINARY attribute with both a minimum and a maximum
length. Currently, we can do either of the two, but not both, given
that we have NLA_MIN_LEN (minimum length) and NLA_BINARY (maximum).
Extend the range mechanis
From: Srujana Challa
Date: Fri, 7 Aug 2020 19:39:17 +0530
> The following series adds support for Marvell Cryptographic Acceleration
> Unit(CPT) on OcteonTX2 CN96XX SoC.
> This series is tested with CRYPTO_EXTRA_TESTS enabled and
> CRYPTO_DISABLE_TESTS disabled.
net-next is closed, please do not
The following series adds support for Marvell Cryptographic Acceleration
Unit(CPT) on OcteonTX2 CN96XX SoC.
This series is tested with CRYPTO_EXTRA_TESTS enabled and
CRYPTO_DISABLE_TESTS disabled.
Changes since v1:
* Moved Makefile changes from patch4 to patch2 and patch3.
Srujana Challa (3):
.kernel.org;
>> kv...@codeaurora.org; da...@davemloft.net; k...@kernel.org;
>> netdev@vger.kernel.org
>> Subject: Re: [PATCH v2 0/3]
>>
>> On 7/31/20 11:27 AM, Rakesh Pillai wrote:
>>> The history recording will be compiled only if
>>> ATH10K_DEBUG i
rnel.org;
> netdev@vger.kernel.org
> Subject: Re: [PATCH v2 0/3]
>
> On 7/31/20 11:27 AM, Rakesh Pillai wrote:
> > The history recording will be compiled only if
> > ATH10K_DEBUG is enabled, and also enabled via
> > the module parameter. Once the history recording
> > is
On Fri, 31 Jul 2020 23:57:19 +0530 Rakesh Pillai wrote:
> The history recording will be compiled only if
> ATH10K_DEBUG is enabled, and also enabled via
> the module parameter. Once the history recording
> is enabled via module parameter, it can be enabled
> or disabled runtime via debugfs.
Have y
On 7/31/20 11:27 AM, Rakesh Pillai wrote:
> The history recording will be compiled only if
> ATH10K_DEBUG is enabled, and also enabled via
> the module parameter. Once the history recording
> is enabled via module parameter, it can be enabled
> or disabled runtime via debugfs.
Why not use trace pr
The history recording will be compiled only if
ATH10K_DEBUG is enabled, and also enabled via
the module parameter. Once the history recording
is enabled via module parameter, it can be enabled
or disabled runtime via debugfs.
---
Changes from v1:
- Add module param and debugfs to enable/disable hi
From: Chris Packham
Date: Fri, 24 Jul 2020 11:21:19 +1200
> This series connects up the mv88e6xxx switches to the dsa infrastructure for
> configuring the port MTU. The first patch is also a bug fix which might be a
> candiatate for stable.
>
> I've rebased this series on top of net-next/master
On Fri, Jul 24, 2020 at 11:21:19AM +1200, Chris Packham wrote:
> This series connects up the mv88e6xxx switches to the dsa infrastructure for
> configuring the port MTU. The first patch is also a bug fix which might be a
> candiatate for stable.
>
> I've rebased this series on top of net-next/mast
This series connects up the mv88e6xxx switches to the dsa infrastructure for
configuring the port MTU. The first patch is also a bug fix which might be a
candiatate for stable.
I've rebased this series on top of net-next/master to pick up Andrew's change
for the gigabit switches. Patch 1 and 2 are
From: Kurt Kanzenbach
Date: Mon, 20 Jul 2020 14:49:36 +0200
> as discussed [1] [2] it makes sense to add a DSA yaml binding. This is the
> second version and contains now two ways of specifying the switch ports:
> Either
> by "ports" or by "ethernet-ports". That is why the third patch also adjus
Hi,
as discussed [1] [2] it makes sense to add a DSA yaml binding. This is the
second version and contains now two ways of specifying the switch ports: Either
by "ports" or by "ethernet-ports". That is why the third patch also adjusts the
DSA core for it.
Tested in combination with the hellcreek.
This patch series provides ACPI support for dpaa2 MAC driver.
This also introduces ACPI mechanism to get PHYs registered on a
MDIO bus and provide them to be connected to MAC.
This patchset is dependent on the review patches available on:
https://git.kernel.org/pub/scm/linux/kernel/git/lpieral
Currently, VMbus drivers use pointers into guest memory as request IDs
for interactions with Hyper-V. To be more robust in the face of errors
or malicious behavior from a compromised Hyper-V, avoid exposing
guest memory addresses to Hyper-V. Also avoid Hyper-V giving back a
bad request ID that is t
On Thu, Jun 25, 2020 at 4:12 PM John Fastabend wrote:
>
> Fix a splat introduced by recent changes to avoid skipping ingress policy
> when kTLS is enabled. The RCU splat was introduced because in the non-TLS
> case the caller is wrapped in an rcu_read_lock/unlock. But, in the TLS
> case we have a
Fix a splat introduced by recent changes to avoid skipping ingress policy
when kTLS is enabled. The RCU splat was introduced because in the non-TLS
case the caller is wrapped in an rcu_read_lock/unlock. But, in the TLS
case we have a reference to the psock and the caller did not wrap its
call in rc
On Wed, 24 Jun 2020 at 09:01, David Miller wrote:
>
> From: Vaibhav Gupta
> Date: Mon, 22 Jun 2020 16:43:57 +0530
>
> > Linux Kernel Mentee: Remove Legacy Power Management.
> >
> > The purpose of this patch series is to remove legacy power management
> > callbacks
> > from amd ethernet drivers.
From: Vaibhav Gupta
Date: Mon, 22 Jun 2020 16:43:57 +0530
> Linux Kernel Mentee: Remove Legacy Power Management.
>
> The purpose of this patch series is to remove legacy power management
> callbacks
> from amd ethernet drivers.
>
> The callbacks performing suspend() and resume() operations are
Linux Kernel Mentee: Remove Legacy Power Management.
The purpose of this patch series is to remove legacy power management callbacks
from amd ethernet drivers.
The callbacks performing suspend() and resume() operations are still calling
pci_save_state(), pci_set_power_state(), etc. and handling t
Linux Kernel Mentee: Remove Legacy Power Management.
The purpose of this patch series is to remove legacy power management callbacks
from amd ethernet drivers.
The callbacks performing suspend() and resume() operations are still calling
pci_save_state(), pci_set_power_state(), etc. and handling t
This patch series provides ACPI support for xgmac_mdio driver.
Changes in v2:
- Reserve "0" to mean that no mdiobus capabilities have been declared.
- bus->id: change to appropriate printk format specifier
- clean up xgmac_acpi_match
- clariy platform_get_resource() usage with comments
Calvin Jo
This patch set is extending ethtool to make it more usable on automotive
PHYs like NXP TJA11XX.
They make use of new KAPI (currently in net-next, will go probably to the
kernel 5.8-rc1):
- PHY master-slave role configuration and status informaton. Mostly needed
for 100Base-T1 PHYs due the lack o
From: Horatiu Vultur
Date: Thu, 21 May 2020 23:19:04 +
> This patch series adds small fixes to MRP implementation.
> The following are fixed in this patch series:
> - now is not allow to add the same port to multiple MRP rings
> - remove unused variable
> - restore the port state according to
This patch series adds small fixes to MRP implementation.
The following are fixed in this patch series:
- now is not allow to add the same port to multiple MRP rings
- remove unused variable
- restore the port state according to the bridge state when the MRP instance
is deleted
v2:
- use rtnl_d
Hi,
Here is the 2nd version of the series to add nested-kprobes support
to x86, arm64 and arm. This makes kprobes to accept 1-level nesting
instead of incrementing missed count.
In this version, I fixed a mistake for the kprobes on ftrace on x86
and dump nested probes when we detect an unrecovera
Hi Rafael,
On Wed, Apr 29, 2020 at 12:26:12PM +0200, Rafael J. Wysocki wrote:
> On Wed, Apr 29, 2020 at 7:38 AM Calvin Johnson
> wrote:
> >
> > > So, yes, there's another driver using it, but the ACPI folk probably
> > > never got a look-in on that instance. Even if they had been copied,
> > >
On Mon, Apr 27, 2020 at 06:54:06PM +0530, Calvin Johnson wrote:
Hi Russell, others,
> Following functions are defined:
> phylink_fwnode_phy_connect()
> phylink_device_phy_connect()
> fwnode_phy_find_device()
> device_phy_find_device()
> fwnode_get_phy_node()
>
> First two help in conne
On Wed, Apr 29, 2020 at 7:38 AM Calvin Johnson
wrote:
>
> On Mon, Apr 27, 2020 at 03:48:07PM +0100, Russell King - ARM Linux admin
> wrote:
> > On Mon, Apr 27, 2020 at 08:02:38PM +0530, Calvin Johnson wrote:
> > > On Mon, Apr 27, 2020 at 02:58:20PM +0100, Russell King - ARM Linux admin
> > > wro
On Mon, Apr 27, 2020 at 03:48:07PM +0100, Russell King - ARM Linux admin wrote:
> On Mon, Apr 27, 2020 at 08:02:38PM +0530, Calvin Johnson wrote:
> > On Mon, Apr 27, 2020 at 02:58:20PM +0100, Russell King - ARM Linux admin
> > wrote:
> > > On Mon, Apr 27, 2020 at 06:54:06PM +0530, Calvin Johnson w
Hi Christian,
> This series adds a new compatible for the QCA9377 BT device that is found
> in many Android TV box devices, makes minor changes to allow max-speed
> values for the device to be read from device-tree, and updates bindings
> to reflect those changes.
>
> v2 changes: rebase against b
Alexander Duyck posted a series in 2018 proposing adding UDP segmentation
offload support to ixgbe and ixgbevf, but those patches were never
accepted:
https://lore.kernel.org/netdev/20180504003556.4769.11407.stgit@localhost.localdomain/
This series is a repost of his ixgbe patch along with a simi
From: Ying Xue
Date: Mon, 12 Aug 2019 15:32:39 +0800
> Ying Xue (3):
> tipc: fix memory leak issue
> tipc: fix memory leak issue
Please make the subject lines for these two patches unique. Perhaps
mention what part of the tipc code has the memory leak you are fixing.
Thanks.
In this series, try to fix two memory leak issues and another issue of
calling smp_processor_id() in preemptible context.
Changes since v1:
- Fix "Reported-by:" missing in patch #3, which was reported by Jakub
Kicinski
Ying Xue (3):
tipc: fix memory leak issue
tipc: fix memory leak issue
On 7/30/19 3:22 PM, David Miller wrote:
> From: Jens Axboe
> Date: Tue, 30 Jul 2019 20:49:09 +
>
>> Pretty appalled to see this abomination:
>>
>> net: Convert skb_frag_t to bio_vec
>>
>> There are a lot of users of frag->page_offset, so use a union
>> to avoid converting those users today.
>
From: Jens Axboe
Date: Tue, 30 Jul 2019 20:49:09 +
> Pretty appalled to see this abomination:
>
> net: Convert skb_frag_t to bio_vec
>
> There are a lot of users of frag->page_offset, so use a union
> to avoid converting those users today.
>
> Signed-off-by: Matthew Wilcox (Oracle)
> Sign
From: Jonathan Lemon
Date: Tue, 30 Jul 2019 07:40:31 -0700
> The recent conversion of skb_frag_t to bio_vec did not include
> skb_frag's page_offset. Add accessor functions for this field,
> utilize them, and remove the union, restoring the original structure.
>
> v2:
> - rename accessors
>
On 7/30/19 8:40 AM, Jonathan Lemon wrote:
> The recent conversion of skb_frag_t to bio_vec did not include
> skb_frag's page_offset. Add accessor functions for this field,
> utilize them, and remove the union, restoring the original structure.
You can add:
Reviewed-by: Jens Axboe
Pretty appall
On Tue, 30 Jul 2019 07:40:31 -0700, Jonathan Lemon wrote:
> The recent conversion of skb_frag_t to bio_vec did not include
> skb_frag's page_offset. Add accessor functions for this field,
> utilize them, and remove the union, restoring the original structure.
Reviewed-by: Jakub Kicinski
Thanks!
The recent conversion of skb_frag_t to bio_vec did not include
skb_frag's page_offset. Add accessor functions for this field,
utilize them, and remove the union, restoring the original structure.
v2:
- rename accessors
- follow kdoc conventions
Jonathan Lemon (3):
linux: Add page_offset ac
This series adds support for Microchip KSZ87xx switches, which are
slightly simpler compared to KSZ9xxx .
Signed-off-by: Marek Vasut
Cc: Andrew Lunn
Cc: David S. Miller
Cc: Florian Fainelli
Cc: Tristram Ha
Cc: Vivien Didelot
Cc: Woojung Huh
Marek Vasut (1):
dt-bindings: net: dsa: ksz: do
On 2019/6/25 0:03, David Miller wrote:
> From: luoshijie
> Date: Tue, 18 Jun 2019 15:14:02 +
>
>> From: Shijie Luo
>>
>> When enable route_localnet, route of the 127/8 address is enabled.
>> But in some situations like arp_announce=2, ARP requests or reply
>> work abnormally.
>>
>> This patc
On 2019/6/25 0:03, David Miller wrote:
> From: luoshijie
> Date: Tue, 18 Jun 2019 15:14:02 +
>
>> From: Shijie Luo
>>
>> When enable route_localnet, route of the 127/8 address is enabled.
>> But in some situations like arp_announce=2, ARP requests or reply
>> work abnormally.
>>
>> This p
From: luoshijie
Date: Tue, 18 Jun 2019 15:14:02 +
> From: Shijie Luo
>
> When enable route_localnet, route of the 127/8 address is enabled.
> But in some situations like arp_announce=2, ARP requests or reply
> work abnormally.
>
> This patchset fix some bugs when enable route_localnet.
>
On 6/22/19 6:46 AM, David Miller wrote:
> From: Zhiqiang Liu
> Date: Sat, 22 Jun 2019 16:41:49 +0800
>
>> Friendly ping ...
>
> I'm not applying this patch series without someone reviewing it.
>
I have stared at it a few times since the patches were sent and can not
find anything obviously wro
> From: Zhiqiang Liu
> Date: Sat, 22 Jun 2019 16:41:49 +0800
>
>> Friendly ping ...
>
> I'm not applying this patch series without someone reviewing it.
>
Of course, all patches should be reviewd before deciding whether to apply.
In v2, we add a couple of test for enabling route_localnet in sel
From: Zhiqiang Liu
Date: Sat, 22 Jun 2019 16:41:49 +0800
> Friendly ping ...
I'm not applying this patch series without someone reviewing it.
Friendly ping ...
> From: Shijie Luo
>
> When enable route_localnet, route of the 127/8 address is enabled.
> But in some situations like arp_announce=2, ARP requests or reply
> work abnormally.
>
> This patchset fix some bugs when enable route_localnet.
>
> Change History:
> V2:
> - Change
From: Shijie Luo
When enable route_localnet, route of the 127/8 address is enabled.
But in some situations like arp_announce=2, ARP requests or reply
work abnormally.
This patchset fix some bugs when enable route_localnet.
Change History:
V2:
- Change a single patch to a patchset.
- Add bug fi
Whoops, I was slow to test these. I'm getting failuring krb5 nfs
mounts, and the following the server's logs. Dropping the three patches
for now.
--b.
[ 40.894408] remove_proc_entry: removing non-empty directory 'net/rpc',
leaking at least 'use-gss-proxy'
[ 40.897352] WARNING: CPU: 2 PID:
On Thu, 25 Apr 2019 11:49:18 -0700, John Fastabend wrote:
> On 4/25/19 11:30 AM, Jakub Kicinski wrote:
> > On Thu, 25 Apr 2019 09:02:50 -0700, John Fastabend wrote:
> >> Series of fixes for sockmap and ktls, see patches for descriptions.
> >>
> >> v2: fix build issue for CONFIG_TLS_DEVICE and fix
On 4/25/19 11:30 AM, Jakub Kicinski wrote:
> On Thu, 25 Apr 2019 09:02:50 -0700, John Fastabend wrote:
>> Series of fixes for sockmap and ktls, see patches for descriptions.
>>
>> v2: fix build issue for CONFIG_TLS_DEVICE and fixup couple comments from
>> Jakub.
>
> Ah, right my comment about
On Thu, 25 Apr 2019 09:02:50 -0700, John Fastabend wrote:
> Series of fixes for sockmap and ktls, see patches for descriptions.
>
> v2: fix build issue for CONFIG_TLS_DEVICE and fixup couple comments from
> Jakub.
Ah, right my comment about the rx side sleeping was fairly nonsensical,
the loc
Series of fixes for sockmap and ktls, see patches for descriptions.
v2: fix build issue for CONFIG_TLS_DEVICE and fixup couple comments from
Jakub.
---
John Fastabend (3):
bpf: tls, implement unhash to avoid transition out of ESTABLISHED
bpf: sockmap remove duplicate queue free
This patchset adds support for a PHY reset driven by a reset-controller.
Currently, only GPIO driven resets are supported by the PHY subsystem.
v2:
- fixed missed rename of "reset" in at803x.c
- move initial reset to mdio_device_reset
David Bauer (3):
dt-bindings: net: add PHY reset controll
From: Michael Zhivich
Date: Mon, 8 Apr 2019 10:48:44 -0400
> This patch series addresses 2 related issues:
>
> 1. ethtool_validate_speed() triggers a "signed-unsigned comparison"
> warning due to type difference of SPEED_UNKNOWN constant (int)
> and argument to ethtool_validate_speed (__u32).
>
1 - 100 of 299 matches
Mail list logo
