Writing a new value of 3 to /proc/sys/kernel/randomize_va_space
enables full randomization of memory mappings created with mmap(NULL,
...). With 2, the base of the VMA used for such mappings is random,
but the mappings are created in predictable places within the VMA and
in sequential order. With
Hi James,
would you mind adding this to the security tree? (You can cherrypick
from
https://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git/commit/?h=2020-11-29/fix-nscaps
)
thanks,
-serge
On Tue, Nov 17, 2020 at 08:09:59AM -0800, Andrew G. Morgan wrote:
> Signed-off-by: Andrew G.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: aae5ab854e38151e69f261dbf0e3b7e396403178
commit: e5fc436f06eef54ef512ea55a9db8eb9f2e76959 sparse: use static inline for
__chk_{user,io}_ptr()
date: 3 months ago
config: sh-randconfig-s032-20201130
On Sun, Nov 29, 2020 at 06:34:01PM +0100, Paolo Bonzini wrote:
On 29/11/20 05:13, Sasha Levin wrote:
Which doesn't seem to be suitable for stable either... Patch 3/5
in
Why not? It was sent as a fix to Linus.
Dunno, 120 lines of new code? Even if it's okay for an rc, I don't
see why it
On 11/25/20 7:36 AM, Vladimir Oltean wrote:
> Extend the 'bridge mdb' command for the following syntax:
> bridge mdb add dev br0 port swp0 grp 01:02:03:04:05:06 permanent
>
> Signed-off-by: Vladimir Oltean
> ---
> Changes in v3:
> - Using rt_addr_n2a_r instead of inet_ntop/ll_addr_n2a directly.
On Sun, Nov 29, 2020 at 08:45:12PM +0100, Heinrich Schuchardt wrote:
> Since commit bbc4d71d6354 ("net: phy: realtek: fix rtl8211e rx/tx
> delay config") network is broken on the NanoPi Neo Plus2.
>
> This patch changes the phy-mode to use internal delays both for RX and TX
> as has been done for
Hi!
This is neccessary for having useful Droid 4 support, so let me try to
ressurect this.
If there's newer version (I took mine from for-5.7 branch), let me
know.
On Thu 2020-05-28 11:31:02, Johan Hovold wrote:
> On Tue, May 12, 2020 at 02:47:08PM -0700, Tony Lindgren wrote:
> > I initially
On Sat, Nov 28, 2020 at 7:54 PM Andy Lutomirski wrote:
>
> On Sat, Nov 28, 2020 at 8:02 AM Nicholas Piggin wrote:
> >
> > On big systems, the mm refcount can become highly contented when doing
> > a lot of context switching with threaded applications (particularly
> > switching between the idle
Le 29/11/2020 à 20:49, Dmitry Torokhov a écrit :
Hi Christophe,
On Sun, Nov 29, 2020 at 09:45:16AM +0100, Christophe JAILLET wrote:
In case of a managed resource, 'devm_input_device_release()' already has a
'input_put_device(dev)' call.
Avoid a double reference decrement by explicitly
On Fri, Nov 27, 2020 at 07:30:03PM +0100, Enrico Weigelt, metux IT consult
wrote:
> diff --git a/include/uapi/linux/virtio_ids.h b/include/uapi/linux/virtio_ids.h
> index b052355ac7a3..85772c0bcb4b 100644
> --- a/include/uapi/linux/virtio_ids.h
> +++ b/include/uapi/linux/virtio_ids.h
> @@ -48,5
On Sun, Nov 29, 2020 at 08:43:51AM +0200, Eli Cohen wrote:
> We should not try to use the VF MAC address as that is used by the
> regular (e.g. mlx5_core) NIC implementation. Instead, use a random
> generated MAC address.
>
> Suggested by: Cindy Lu
> Fixes: 1a86b377aa21 ("vdpa/mlx5: Add VDPA
From: Arnd Bergmann
gcc warns about an out-of-bounds access when the using nonzero
values for 'plane_id' on kmb->plane_status:
drivers/gpu/drm/kmb/kmb_plane.c: In function 'kmb_plane_atomic_disable':
drivers/gpu/drm/kmb/kmb_plane.c:128:20: warning: array subscript 3 is above
array bounds of
The pull request you sent on Sun, 29 Nov 2020 13:37:59 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> irq-urgent-2020-11-29
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8b7a51ba2637ee53ce90624f5f98aaf8ec9b2bcc
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sun, 29 Nov 2020 13:38:00 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> locking-urgent-2020-11-29
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f91a3aa6bce480fe6e08df540129f4a923222419
Thank you!
--
The pull request you sent on Sun, 29 Nov 2020 11:42:09 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/efi-urgent-for-v5.10-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1214917e008bb8989747b8bf9a721f7a6db8f8d7
Thank you!
--
The pull request you sent on Sun, 29 Nov 2020 11:38:44 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.10-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7255a39d24a7960da3a55e840ca5cbed5fcb476f
Thank you!
--
Hi Christophe,
On Sun, Nov 29, 2020 at 09:45:16AM +0100, Christophe JAILLET wrote:
> In case of a managed resource, 'devm_input_device_release()' already has a
> 'input_put_device(dev)' call.
>
> Avoid a double reference decrement by explicitly calling
> 'input_put_device()' only on non-managed
Andrew,
On Sun, Nov 29, 2020 at 8:38 PM Andrew Lunn wrote:
>
> On Sun, Nov 29, 2020 at 08:34:27PM +0100, Jean Pihet wrote:
> > Hi Andrew,
> >
> > On Sun, Nov 29, 2020 at 5:56 PM Andrew Lunn wrote:
> > >
> > > On Sun, Nov 29, 2020 at 11:23:59AM +0100, Jean Pihet wrote:
> > > > Some ethernet
On Sat, Nov 28, 2020 at 01:13:50PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:56:12AM +0200, Cristian Ciocaltea wrote:
> > Add the linux-actions mailing list for the Actions Semi architecture.
> >
> > Signed-off-by: Cristian Ciocaltea
>
> There was a patch from me for this
Since commit bbc4d71d6354 ("net: phy: realtek: fix rtl8211e rx/tx
delay config") network is broken on the NanoPi Neo Plus2.
This patch changes the phy-mode to use internal delays both for RX and TX
as has been done for other boards affected by the same commit.
Fixes: bbc4d71d6354 ("net: phy:
Hi Lubomir,
On Sun, Nov 29, 2020 at 03:21:45PM +0100, Lubomir Rintel wrote:
> This adds support for the power button attached to the Embedded Controller
> on a Dell Wyse 3020 "Ariel" board.
>
> The Embedded Controller's SPI interface is actually capable sending and
> receiving the PS/2 keyboard
On Sun, Nov 29, 2020 at 08:34:27PM +0100, Jean Pihet wrote:
> Hi Andrew,
>
> On Sun, Nov 29, 2020 at 5:56 PM Andrew Lunn wrote:
> >
> > On Sun, Nov 29, 2020 at 11:23:59AM +0100, Jean Pihet wrote:
> > > Some ethernet controllers (e.g. TI CPSW) pad the frames to a minimum
> > > of 64 bytes before
On Sat, Nov 28, 2020 at 01:11:08PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:56:11AM +0200, Cristian Ciocaltea wrote:
> > Add pinctrl definitions for the I2C controllers used in RoseapplePi SBC.
> > For the moment enable only I2C0, which is used by the ATC2603C PMIC.
> >
>
Speakup exposing a line discipline allows userland to try to use it,
while it is deemed to be useless, and thus uselessly exposes potential
bugs. One of them is simply that in such a case if the line sends data,
spk_ttyio_receive_buf2 is called and crashes since spk_ttyio_synth
is NULL.
This
Andrew,
On Sun, Nov 29, 2020 at 5:57 PM Andrew Lunn wrote:
>
> Hi Jean
>
> Please also include a patch 0/X which describes the patchset as a
> whole. This will be used as the branch merge commit.
Sure, will submit a v2 asap.
Thx,
Jean
>
>Andrew
Hi Andrew,
On Sun, Nov 29, 2020 at 5:56 PM Andrew Lunn wrote:
>
> On Sun, Nov 29, 2020 at 11:23:59AM +0100, Jean Pihet wrote:
> > Some ethernet controllers (e.g. TI CPSW) pad the frames to a minimum
> > of 64 bytes before the FCS is appended. This causes an issue with the
> > KSZ tail tag which
On Sun, Nov 29, 2020 at 5:38 AM Thomas Gleixner wrote:
>
> Yet two more places which invoke tracing from RCU disabled regions in the
> idle path. Similar to the entry path the low level idle functions have to
> be non-instrumentable.
This really seems less than optimal.
In particular, lookie
Since this patchset adds support for V4L2_ENC_CMD_STOP and
VENUS_ENC_STATE_ENCODING it should also add support for
VIDIOC_TRY_ENCODER_CMD so that those commands are discoverable. I've
made an attempt at that here:
https://www.spinics.net/lists/linux-media/msg182319.html
On Wed, Nov 11, 2020 at
On Thu, Nov 26, 2020 at 01:38:53PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> from drivers/net/ethernet/ibm/ibmvnic.c:35:
> inlined from ‘handle_vpd_rsp’ at drivers/net/ethernet/ibm/ibmvnic.c:4124:3:
> drivers/net/ethernet/ibm/ibmvnic.c:1362: warning:
On Thu, Nov 26, 2020 at 01:38:52PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/toshiba/spider_net.c:263: warning: Function parameter
> or member 'hwdescr' not described in 'spider_net_get_descr_status'
>
Hello,
on STM32MP1 with almost vanilla 5.7.7 in single CPU mode. Pair of
modprobe armmmci ; rmmod armmmci
causes rmmod and kworker to hang. I should note that no MMC is detected
on the board (SDIO device on MMC bus is not responding).
On another board (where SDIO is responding) rmmod works.
It
platform_get_irq_byname already prints an error message if the requested
irq was not found. Don't print another message in the driver.
Signed-off-by: Martin Kaiser
Reviewed-by: Fabien Dessenne
---
changes in v2
- added Fabien's review tag
- reformatted the commit message such that lines are <
Now that the driver can be enabled by COMPILE_TEST, we see warnings on
64bit platforms when void pointers are cast to unsigned int (and
vice versa).
warning: cast to smaller integer type 'unsigned int' from 'void *'
unsigned int chan = (unsigned int)link->con_priv;
...
warning: cast to
This allows compiling the driver on architectures where the hardware is not
available. Most other mailbox drivers support this as well.
Signed-off-by: Martin Kaiser
Reviewed-by: Fabien Dessenne
---
changes in v2
- added Fabien's review tag
Dear all,
this has been around for some weeks now. Is
Gentle poke; did this just get missed or is there some reason not to
apply it?
On Sun, Jul 05, 2020 at 03:25:44PM +0100, Jonathan McDowell wrote:
> Add missing prng definition for ipq806x SoC
>
> Signed-off-by: Jonathan McDowell
> ---
> arch/arm/boot/dts/qcom-ipq8064.dtsi | 7 +++
> 1 file
On Mon, Nov 16, 2020 at 9:55 AM Jonathan Marek wrote:
>
> On 11/16/20 12:50 PM, Rob Clark wrote:
> > On Mon, Nov 16, 2020 at 9:33 AM Christoph Hellwig wrote:
> >>
> >> On Sat, Nov 14, 2020 at 03:07:20PM -0500, Jonathan Marek wrote:
> >>> qcom's vulkan driver has nonCoherentAtomSize=1, and it
On Thu, Nov 26, 2020 at 01:38:51PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/toshiba/ps3_gelic_net.c:1107: warning: Function
> parameter or member 'irq' not described in 'gelic_card_interrupt'
>
Hi Lee
> /**
> * build_hdr_data - creates L2/L3/L4 header data buffer
> - * @hdr_field - bitfield determining needed headers
> - * @skb - socket buffer
> - * @hdr_len - array of header lengths
> - * @tot_len - total length of data
> + * @hdr_field: bitfield determining needed headers
> + *
On Sun, Nov 29, 2020 at 10:32:31AM -0800, Linus Torvalds wrote:
> This is not a problem, it's just a note for people to try to avoid
> surprising me..
Oh, sorry, forgot to mention: he surprised me too and I asked. He said
he's updated his subkeys, yeah, perhaps because they're about to expire
and
On Thu, Nov 26, 2020 at 01:38:49PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/ti/am65-cpts.c:736: warning: Function parameter or
> member 'en' not described in 'am65_cpts_rx_enable'
> drivers/net/ethernet/ti/am65-cpts.c:736: warning:
On Thu, Nov 26, 2020 at 01:38:48PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/ti/am65-cpsw-qos.c:364: warning: Function parameter or
> member 'ndev' not described in 'am65_cpsw_timer_set'
> drivers/net/ethernet/ti/am65-cpsw-qos.c:364:
On Sat, Nov 28, 2020 at 01:08:51PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:56:10AM +0200, Cristian Ciocaltea wrote:
> > Add uSD support for RoseapplePi SBC using a fixed regulator as a
> > temporary solution until PMIC support becomes available.
> >
> > Signed-off-by:
On Thu, Nov 26, 2020 at 01:38:47PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/xen-netback/xenbus.c:419: warning: Function parameter or member
> 'dev' not described in 'frontend_changed'
> drivers/net/xen-netback/xenbus.c:419: warning: Function
On Thu, Nov 26, 2020 at 01:38:46PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/net/ethernet/smsc/smc91x.c:2200: warning: Function parameter or
> member 'dev' not described in 'try_toggle_control_gpio'
> drivers/net/ethernet/smsc/smc91x.c:2200:
On Sun, Nov 29, 2020 at 2:42 AM Borislav Petkov wrote:
>
> please pull more forwarded EFI urgent fixes.
Ard seems to be using almost random signing of his tags. Last time it
was signed with subkey 9CD2A0DA, this time it's subkey FBD9627C.
I see that it's all the same primary key, and I'm pretty
From: Andrea Parri (Microsoft) Sent: Thursday,
November 26, 2020 11:12 AM
>
> Quoting from commit 7527810573436f ("Drivers: hv: vmbus: Introduce
> the CHANNELMSG_MODIFYCHANNEL message type"),
>
> "[...] Hyper-V can *not* currently ACK CHANNELMSG_MODIFYCHANNEL
>messages with the promise
On Sat, Nov 28, 2020 at 01:06:50PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:56:09AM +0200, Cristian Ciocaltea wrote:
> > Remove the UART fixed clock for RoseapplePi SBC and switch to using
> > the clock provided by CMU.
> >
> > Signed-off-by: Cristian Ciocaltea
>
>
On Sat, Nov 28, 2020 at 01:00:45PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:55:59AM +0200, Cristian Ciocaltea wrote:
> > The DMA controller present on the Actions Semi S500 SoC is compatible
> > with the S900 variant, so add it to the list of devices supported by
> > the
Hi Rob,
On Sun, Nov 29, 2020 at 10:12:40AM -0800, Rob Clark wrote:
> From: Rob Clark
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/msm/disp/mdp5/mdp5_ctl.c:227: warning: Function parameter or
> member 'ctl' not described in 'mdp5_ctl_set_encoder_state'
>
On Sun, 2020-11-29 at 09:52 -0800, Randy Dunlap wrote:
> On 11/29/20 9:47 AM, Tom Rix wrote:
> > On 11/27/20 11:53 AM, Matthew Wilcox wrote:
> > > On Fri, Nov 27, 2020 at 11:07:07AM -0800, t...@redhat.com wrote:
> > > > +++ b/fs/fcntl.c
> > > > @@ -526,7 +526,7 @@ SYSCALL_DEFINE3(fcntl64, unsigned
On Sat, Nov 28, 2020 at 12:59:45PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:55:58AM +0200, Cristian Ciocaltea wrote:
> > Add a new compatible string corresponding to the DMA controller found
> > in the S500 variant of the Actions Semi Owl SoCs family.
> >
> >
From: Rob Clark
Fixes the following W=1 kernel build warning(s):
drivers/gpu/drm/msm/disp/mdp5/mdp5_ctl.c:227: warning: Function parameter or
member 'ctl' not described in 'mdp5_ctl_set_encoder_state'
drivers/gpu/drm/msm/disp/mdp5/mdp5_ctl.c:227: warning: Function parameter or
member
On Sat, Nov 28, 2020 at 01:02:06PM +0100, Lino Sanfilippo wrote:
> Use the newer apply function of pwm_ops instead of config, enable, disable
> and set_polarity.
>
> This guarantees atomic changes of the pwm controller configuration. It also
> reduces the size of the driver.
>
> This has been
On Sat, Nov 28, 2020 at 12:55:13PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:55:56AM +0200, Cristian Ciocaltea wrote:
> > Set Clock Management Unit clocks for the UART nodes of Actions Semi
> > S500 SoCs.
> >
> > Signed-off-by: Cristian Ciocaltea
>
> Also in this patch
On Fri, Nov 27, 2020 at 03:23:25PM +0100, Uwe Kleine-König wrote:
[...]
> I suggest for now we go for "don't provide a .get_state() callback"
> because in the only case where it is currently called there is no cached
> data to rely on anyhow.
Alright!
Thanks,
Jonathan
signature.asc
On Sat, Nov 28, 2020 at 12:52:12PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Nov 20, 2020 at 01:55:55AM +0200, Cristian Ciocaltea wrote:
> > Add Clock Management Unit for Actions Semi S500 SoC.
> >
> > Signed-off-by: Cristian Ciocaltea
>
> Reviewed-by: Manivannan Sadhasivam
Thanks for
On 11/29/20 9:47 AM, Tom Rix wrote:
>
> On 11/27/20 11:53 AM, Matthew Wilcox wrote:
>> On Fri, Nov 27, 2020 at 11:07:07AM -0800, t...@redhat.com wrote:
>>> +++ b/fs/fcntl.c
>>> @@ -526,7 +526,7 @@ SYSCALL_DEFINE3(fcntl64, unsigned int, fd, unsigned
>>> int, cmd,
>>> (dst)->l_whence =
On Fri, Nov 27, 2020 at 08:11:05AM +0100, Uwe Kleine-König wrote:
> Hello Jonathan,
>
> On Fri, Nov 27, 2020 at 12:19:31AM +0100, Jonathan Neuschäfer wrote:
> > On Tue, Nov 24, 2020 at 09:20:19AM +0100, Uwe Kleine-König wrote:
[...]
> > > state->duty_cycle and state->period are u64, so you're
On 11/27/20 11:53 AM, Matthew Wilcox wrote:
> On Fri, Nov 27, 2020 at 11:07:07AM -0800, t...@redhat.com wrote:
>> +++ b/fs/fcntl.c
>> @@ -526,7 +526,7 @@ SYSCALL_DEFINE3(fcntl64, unsigned int, fd, unsigned int,
>> cmd,
>> (dst)->l_whence = (src)->l_whence; \
>> (dst)->l_start =
Hi all,
In commit
912b341585e3 ("platform/x86: mlx-platform: Remove PSU EEPROM from MSN274x
platform configuration")
Fixes tag
Fixes: ef08e14a3 ("platform/x86: mlx-platform: Add support for new msn274x
system type")
has these problem(s):
- SHA1 should be at least 12 digits long
In
> +#define SPX5_RD_(sparx5, id, tinst, tcnt,\
> + gbase, ginst, gcnt, gwidth,\
> + raddr, rinst, rcnt, rwidth)\
> + readl(spx5_addr((sparx5)->regs, id, tinst, tcnt,\
> + gbase,
On 29/11/20 05:13, Sasha Levin wrote:
Which doesn't seem to be suitable for stable either... Patch 3/5 in
Why not? It was sent as a fix to Linus.
Dunno, 120 lines of new code? Even if it's okay for an rc, I don't see
why it is would be backported to stable releases and release it without
On 11/27/20 4:54 PM, Daniel Borkmann wrote:
> On 11/27/20 8:27 PM, t...@redhat.com wrote:
>> From: Tom Rix
>>
>> The macro use will already have a semicolon.
>>
>> Signed-off-by: Tom Rix
>> ---
>> include/trace/events/xdp.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>>
On Sun, Nov 29, 2020 at 07:53:45AM -0800, Shakeel Butt wrote:
> On Wed, Nov 25, 2020 at 1:51 AM Mike Rapoport wrote:
> >
> > From: Mike Rapoport
> >
> > Account memory consumed by secretmem to memcg. The accounting is updated
> > when the memory is actually allocated and freed.
> >
> >
> +static void sparx5_hw_lock(struct sparx5 *sparx5)
> +{
> + mutex_lock(>lock);
> +}
> +
> +static void sparx5_hw_unlock(struct sparx5 *sparx5)
> +{
> + mutex_unlock(>lock);
> +}
Why is this mutex special and gets a wrapper where as the other two
don't? If there is no reason for the
Ping for comments
> -Original Message-
> From: Ben Levinsky
> Sent: Saturday, November 14, 2020 8:49 AM
> To: mathieu.poir...@linaro.org
> Cc: devicet...@vger.kernel.org; linux-remotep...@vger.kernel.org; linux-
> ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
> Subject:
> diff --git a/drivers/net/ethernet/microchip/sparx5/sparx5_ethtool.c
> b/drivers/net/ethernet/microchip/sparx5/sparx5_ethtool.c
> new file mode 100644
> index ..a91dd9532f1c
> --- /dev/null
> +++ b/drivers/net/ethernet/microchip/sparx5/sparx5_ethtool.c
> @@ -0,0 +1,1027 @@
> +//
'--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Parshuram-Thombare/I3C-mastership-handover-support/20201129-222847
base:6174f05255e65622ff3340257879a4c0f858b0df
config: i386-randconfig-a012-20201129 (attached as .config
On 11/29/20 8:50 AM, Trond Myklebust wrote:
> On Sun, 2020-11-29 at 16:42 +, Trond Myklebust wrote:
>> Hi Tom,
>>
>> On Fri, 2020-11-27 at 11:43 -0800, t...@redhat.com wrote:
>>> From: Tom Rix
>>>
>>> The macro use will already have a semicolon.
>>>
>>> Signed-off-by: Tom Rix
>>> ---
>>>
On Sun, Nov 29, 2020 at 11:24:00AM +0100, Jean Pihet wrote:
> Add support for RGMII in 100 and 1000 Mbps.
>
> Adjust the CPU port based on the host interface settings: interface
> MII type, speed, duplex.
Please could you add some extra information here why this is needed. I
suspect you have
Hi Jean
Please also include a patch 0/X which describes the patchset as a
whole. This will be used as the branch merge commit.
Andrew
On Sun, Nov 29, 2020 at 11:23:59AM +0100, Jean Pihet wrote:
> Some ethernet controllers (e.g. TI CPSW) pad the frames to a minimum
> of 64 bytes before the FCS is appended. This causes an issue with the
> KSZ tail tag which could not be the last byte before the FCS.
> Solve this by padding the
syzbot has bisected this issue to:
commit 4d004099a668c41522242aa146a38cc4eb59cb1e
Author: Peter Zijlstra
Date: Fri Oct 2 09:04:21 2020 +
lockdep: Fix lockdep recursion
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=178c99fd50
start commit: 6174f052 Add linux-next
From: Matheus Castello Sent: Tuesday, November 24,
2020 7:29 PM
>
> Checkpatch emits WARNING: quoted string split across lines.
> To keep the code clean and with the 80 column length indentation the
> check and registration code for kmsg_dump_register has been transferred
> to a new function
On Sun, 2020-11-29 at 16:42 +, Trond Myklebust wrote:
> Hi Tom,
>
> On Fri, 2020-11-27 at 11:43 -0800, t...@redhat.com wrote:
> > From: Tom Rix
> >
> > The macro use will already have a semicolon.
> >
> > Signed-off-by: Tom Rix
> > ---
> > net/sunrpc/auth_gss/gss_generic_token.c | 2 +-
>
Am Samstag, 24. Oktober 2020, 05:53:21 CET schrieb Jonathan Liu:
> Error message incorrectly refers to grf clock instead of vpll clock.
>
> Signed-off-by: Jonathan Liu
applied to drm-misc-next
Thanks
Heiko
From: Jing Xiangfeng Sent: Thursday, November 26,
2020 7:02 PM
>
> Fix to return a error code "-ENOMEM" from the error handling case
> instead of 0.
>
> Fixes: 436ad9413353 ("scsi: storvsc: Allow only one remove lun work item to
> be issued per
> lun")
> Signed-off-by: Jing Xiangfeng
> ---
>
Hi Tom,
On Fri, 2020-11-27 at 11:43 -0800, t...@redhat.com wrote:
> From: Tom Rix
>
> The macro use will already have a semicolon.
>
> Signed-off-by: Tom Rix
> ---
> net/sunrpc/auth_gss/gss_generic_token.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On 29/11/20 9:46 pm, Greg Kroah-Hartman wrote:
> There's no more need to dynamically allocate the buffer variable here
> now, right? It can be on the stack as the change you made above allows
> that to work properly, no need to allocate the buffer twice in a row
> (once here and once in the USB
On Tue, 10 Nov 2020 21:04:30 +0100, Paul Kocialkowski wrote:
> In the Rockchip DRM LVDS component driver, the endpoint id provided to
> drm_of_find_panel_or_bridge is grabbed from the endpoint's reg property.
>
> However, the property may be missing in the case of a single endpoint.
> Initialize
setup_per_zone_lowmem_reserve() iterates through each zone setting
zone->lowmem_reserve[j] = 0 (where j is the zone's index) then
iterates backwards through all proceeding zones, setting
lower_zone->lowmem_reserve[j] = sum(managed pages of higher zones) /
lowmem_reserve_ratio[idx] for each (where
On Sun, Nov 29, 2020 at 06:28:01PM +0530, Amit Kucheria wrote:
> On Thu, Nov 26, 2020 at 2:16 AM Ansuel Smith wrote:
>
> > > > };
> > > > @@ -441,6 +442,10 @@ enum regfield_ids {
> > > > CRIT_THRESH_14,
> > > > CRIT_THRESH_15,
> > > >
> > > > + /* VER_0 MIN MAX THRESH */
>
Since commit bbc4d71d6354 ("net: phy: realtek: fix rtl8211e rx/tx
delay config") iSCSI booting fails on the Pine A64 LTS.
This patch changes the phy-mode to use internal delays both for RX and TX
as has been done for other boards affected by the same commit.
Fixes: bbc4d71d6354 ("net: phy:
Got it. Thanks again Al.
On Sat, Nov 28, 2020 at 7:28 PM Al Viro wrote:
>
> On Sat, Nov 28, 2020 at 06:19:31PM -0800, Walt Drummond wrote:
> > Thanks Al. I want to understand the nuance, so please bear with me as I
> > reason this out. The cast in stone nature of this is due to both the need
On Sun, Nov 29, 2020 at 09:36:00PM +0530, Anant Thazhemadam wrote:
> The newer usb_control_msg_{send|recv}() API are an improvement on the
> existing usb_control_msg() as it ensures that a short read/write is treated
> as an error, data can be used off the stack, and raw usb pipes need not be
>
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instances of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, instances of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, instances of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, instances of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, instances of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, instances of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, the instance of
The newer usb_control_msg_{send|recv}() API are an improvement on the
existing usb_control_msg() as it ensures that a short read/write is treated
as an error, data can be used off the stack, and raw usb pipes need not be
created in the calling functions.
For this reason, instances of
201 - 300 of 386 matches
Mail list logo
