From: Johannes Berg
Using vmalloc() in gcov is really quite wasteful, many of the
objects allocated are really small (e.g. I've seen 24 bytes.)
Use kvmalloc() to automatically pick the better of kmalloc()
or vmalloc() depending on the size.
Signed-off-by: Johannes Berg
---
kernel/gcov/clang.c
On Mon, Mar 15, 2021 at 02:49:04PM -0700, Doug Anderson wrote:
> Hi,
>
> On Fri, Mar 12, 2021 at 10:32 AM Matthias Kaehlcke wrote:
> >
> > CoachZ rev3 uses a 100k NTC thermistor for the charger temperatures,
> > instead of the 47k NTC that is stuffed in earlier revisions. Add .dts
> > files for
On Mon, Mar 15, 2021 at 02:48:55PM -0700, Doug Anderson wrote:
> Hi,
>
> On Fri, Mar 12, 2021 at 10:32 AM Matthias Kaehlcke wrote:
> >
> > + linux,keymap = <
> > + MATRIX_KEY(0x00, 0x02, KEY_BACK)
> > + MATRIX_KEY(0x03, 0x02, KEY_REFRESH)
> > +
On Mon, Mar 15, 2021 at 02:48:46PM -0700, Doug Anderson wrote:
> Hi,
>
> On Fri, Mar 12, 2021 at 10:32 AM Matthias Kaehlcke wrote:
> >
> > Commit f73558cc83d1 ("arm64: dts: qcom: sc7180: Disable charger
> > thermal zone for lazor") disables the charger thermal zone for
> > specific lazor
Hi Bikash,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1e28eed17697bcf343c6743f0028cc3b5dd88bf0
commit: a04658594399e1fa25f984601b77ee840e6aaf01 scsi: qla2xxx: Wait for ABTS
response on I/O timeouts for NVMe
Hi Vitaly,
I believe, it is responsibility of each guest code to set
X86_FEATURE_TSC_KNOWN_FREQ cap.
Regarding VMware guest, there is a case where vmware_tsc_khz is zero (not
provided by hypervisor)
and TSC frequency should be calculated.
Sorry for late response.
Regards,
—Alexey
> On Jan 5,
On 3/15/21 10:32 AM, Aditya Srivastava wrote:
> The opening comment mark '/**' is used for highlighting the beginning of
> kernel-doc comments.
> There are some files in drivers/net/wireless/rsi which follow this syntax
> in their file headers, i.e. start with '/**' like comments, which causes
>
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 05:30:28PM +0100, Jacopo Mondi wrote:
> From: Kieran Bingham
>
> Include the eagle-gmsl.dtsi to enable GMSL camera support on the
> Eagle-V3M platform.
>
> Signed-off-by: Kieran Bingham
> Signed-off-by: Jacopo Mondi
> ---
>
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 05:30:27PM +0100, Jacopo Mondi wrote:
> From: Kieran Bingham
>
> Describe the FAKRA connector available on Eagle board that allows
> connecting GMSL camera modules such as IMI RDACM20 and RDACM21.
>
> Signed-off-by: Kieran Bingham
>
On Mon, Mar 15, 2021 at 07:40:14PM +, Matthew Wilcox wrote:
> I would agree that the conversion is both straightforward and noisy.
> There are some minor things that crop up, like noticing that we get
> the accounting wrong for writeback of compound pages. That's not
> entirely unexpected
On Mon, Mar 15, 2021, Ben Gardon wrote:
> Fix a missing rcu_dereference in tdp_mmu_zap_spte_atomic.
>
> Reported-by: kernel test robot
> Signed-off-by: Ben Gardon
> ---
Reviewed-by: Sean Christopherson
On Mon, Mar 15, 2021 at 01:39:31PM -0700, Douglas Anderson wrote:
> Match what's downstream for this board.
>
> Cc: Srinivasa Rao Mandadapu
> Cc: Ajit Pandey
> Cc: Judy Hsiao
> Cc: Cheng-Yi Chiang
> Cc: Stephen Boyd
> Cc: Matthias Kaehlcke
> Signed-off-by: Douglas Anderson
Reviewed-by:
On Mon, Mar 15, 2021, Ben Gardon wrote:
> In tdp_mmu_iter_cond_resched there is a call to tdp_iter_start which
> causes the iterator to continue its walk over the paging structure from
> the root. This is needed after a yield as paging structure could have
> been freed in the interim.
>
> The
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 05:30:26PM +0100, Jacopo Mondi wrote:
> From: Kieran Bingham
>
> Enable the MAX9286 GMSL deserializer on the Eagle-V3M board.
>
> Connected cameras should be defined in a device-tree overlay or included
> after these definitions.
>
On Mon, Mar 15, 2021, Ben Gardon wrote:
Missing "From: Sean Christopherson ", i.e. the commit in your
local tree needs "git commit --amend --author="Sean Christopherson
".
Alternatively, you could just erase my SOB ;-)
> Store the address space ID in the TDP iterator so that it can be
>
On Mon, Mar 15, 2021 at 01:39:30PM -0700, Douglas Anderson wrote:
> This was present downstream. Add upstream too. NOTE: upstream I
> managed to get some sort of halfway state and got one pinctrl entry in
> the coachz-r1 device tree. Remove that as part of this since it's now
> in the dtsi.
>
>
On 3/14/2021 1:11 AM, Adrian Hunter wrote:
On 10/03/21 5:04 am, Asutosh Das (asd) wrote:
On 3/9/2021 7:56 AM, Asutosh Das (asd) wrote:
On 3/8/2021 9:17 AM, Rafael J. Wysocki wrote:
On Mon, Mar 8, 2021 at 5:21 PM Rafael J. Wysocki wrote:
On Sat, Mar 6, 2021 at 5:17 PM Alan Stern wrote:
Hi,
On 01.02.21 10:01, Kurt Garloff wrote:
> Issue persists on Ryzen in 5.11-rc6:
>
> kvmadmin@KurtSrv2018(//):~ [0]$ sudo
> /casa/src/linux-stable/tools/power/x86/turbostat/turbostat
> [...]
> kvmadmin@KurtSrv2018(//):~ [243]$
>
> ^^^ Exit code
>
> With the patch:
On Mon, Mar 15, 2021 at 3:03 PM Kees Cook wrote:
>
> On Wed, Mar 10, 2021 at 01:01:28PM +0100, Alexey Gladkov wrote:
> > The current implementation of the ucounts reference counter requires the
> > use of spin_lock. We're going to use get_ucounts() in more performance
> > critical areas like a
Hello,
On Mon, Mar 15, 2021 at 03:11:55PM -0700, Jacob Pan wrote:
> > Migration itself doesn't have restrictions but all resources are
> > distributed on the same hierarchy, so the controllers are supposed to
> > follow the same conventions that can be implemented by all controllers.
> >
> Got
On Mon, Mar 15, 2021 at 11:02:25AM -0700, Kees Cook wrote:
> diff --git a/mm/slab.h b/mm/slab.h
> index 076582f58f68..b0977d525c06 100644
> --- a/mm/slab.h
> +++ b/mm/slab.h
> @@ -601,7 +601,8 @@ static inline void cache_random_seq_destroy(struct
> kmem_cache *cachep) { }
>
> static inline
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 05:30:25PM +0100, Jacopo Mondi wrote:
> The MAX9286 GMSL deserializer features gpio controller capabilities,
> as it provides 2 GPIO lines.
>
> As establishing a regulator that uses one of the GPIO lines and
> enabling/disabling it at
From: Voon Weifeng
Enabled EST related interrupts as below:
1) Constant Gate Control Error (CGCE)
2) Head-of-Line Blocking due to Scheduling (HLBS)
3) Head-of-Line Blocking due to Frame Size (HLBF).
4) Base Time Register error (BTRE)
5) Switch to S/W owned list Complete (SWLC)
For HLBS, the
From: Ong Boon Leong
Below EST errors are added into ethtool statistic:
1) Constant Gate Control Error (CGCE):
The counter "mtl_est_cgce" increases everytime CGCE interrupt is
triggered.
2) Head-of-Line Blocking due to Scheduling (HLBS):
The counter "mtl_est_hlbs" increases everytime
From: Mohammad Athari Bin Ismail
This patchset adds support for handling EST interrupts and reporting EST
errors. Additionally, the errors are added into ethtool statistic.
Ong Boon Leong (1):
net: stmmac: Add EST errors into ethtool statistic
Voon Weifeng (1):
net: stmmac: EST interrupts
On Mon, Mar 15, 2021 at 07:23:29PM +0100, Sedat Dilek wrote:
> You mean something like that ^^?
>
> - Sedat -
>
> [1]
> https://git.zx2c4.com/laptop-kernel/commit/?id=116badbe0a18bc36ba90acb8b80cff41f9ab0686
*shudder*, I was more thinking you'd simply add it to you CFLAGS when
building. I
Hi Yamada-san,
On Tue, Mar 16, 2021 at 02:43:45AM +0900, Masahiro Yamada wrote:
> On Mon, Mar 15, 2021 at 3:40 PM Viresh Kumar wrote:
> > On 14-03-21, 20:16, Frank Rowand wrote:
> > > On 3/12/21 11:11 PM, Frank Rowand wrote:
> > > > On 3/12/21 1:13 AM, Viresh Kumar wrote:
> > > >> On 12-03-21,
Add a new debug module param 'debug_intercept_exceptions' which will allow the
KVM to intercept any guest exception, and forward it to the guest.
This can be very useful for guest debugging and/or KVM debugging with kvm trace.
This is not intended to be used on production systems.
This is based
This change greatly helps with two issues:
* Resuming from a breakpoint is much more reliable.
When resuming execution from a breakpoint, with interrupts enabled, more often
than not, KVM would inject an interrupt and make the CPU jump immediately to
the interrupt handler and eventually
Hi!
I would like to publish two debug features which were needed for other stuff
I work on.
One is the reworked lx-symbols script which now actually works on at least
gdb 9.1 (gdb 9.2 was reported to fail to load the debug symbols from the kernel
for some reason, not related to this patch) and
Fix several issues that are present in lx-symbols script:
* Track module unloads by placing another software breakpoint at 'free_module'
(force uninline this symbol just in case), and use remove-symbol-file
gdb command to unload the symobls of the module that is unloading.
That gives the
Hi Tejun,
On Sat, 13 Mar 2021 13:05:36 -0500, Tejun Heo wrote:
> Hello,
>
> On Sat, Mar 13, 2021 at 08:57:01AM -0800, Jacob Pan wrote:
> > Isn't PIDs controller doing the charge/uncharge? I was under the
> > impression that each resource can be independently charged/uncharged,
> > why it
On Mon, Mar 15, 2021 at 11:59:12AM -0700, Linus Torvalds wrote:
> Is it only the static_call_sites entry itself that needs the
> alignment? Or do we end up depending on the static call function being
> at least 4-byte aligned too? The way it plays games with the key makes
> me worry.
The only
Hi Alex,
On Mon, 15 Mar 2021 at 08:28, Alexandre Courbot wrote:
>
> Hi Ezequiel,
>
> On Thu, Mar 4, 2021 at 6:47 AM Ezequiel Garcia
> wrote:
> >
> > Hi Alex,
> >
> > Thanks for the patch.
> >
> > On Fri, 26 Feb 2021 at 07:06, Alexandre Courbot
> > wrote:
> > >
> > > From: Yunfei Dong
> > >
On Tue, 9 Mar 2021 14:47:19 +0100, Heiko Schocher wrote:
> The datasheet for the rv3028 says the weekday has exact 3 bits
> and in chapter 3.4.0 for the "3h–Weekday" register it says:
> """
> This register holds the current day of the week. Each value represents
> one weekday that is assigned by
On Wed, Mar 10, 2021 at 01:01:28PM +0100, Alexey Gladkov wrote:
> The current implementation of the ucounts reference counter requires the
> use of spin_lock. We're going to use get_ucounts() in more performance
> critical areas like a handling of RLIMIT_SIGPENDING.
This really looks like it
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 15 Mar 2021 17:19:26 +0300 you wrote:
> Add basic support for the Marvell 88X multi-speed ethernet
> transceiver.
>
> This PHY provides data transmission over fiber-optic as well as Twinax
> copper links. The
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 15 Mar 2021 10:01:18 -0500 you wrote:
> In review, Alexander Duyck suggested that ipa_table_hash_support()
> was trivial enough that it could be implemented as a static inline
> function in the header file. But
On 15/03/2021 22.33, Andrew Morton wrote:
> On Sat, 13 Mar 2021 22:25:27 +0100 Rasmus Villemoes
> wrote:
>
>> Most of the boot process doesn't actually need anything from the
>> initramfs, until of course PID1 is to be executed. So instead of doing
>> the decompressing and populating of the
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:15:12PM +0100, Jacopo Mondi wrote:
> Re-phrase a comment in .bound() callback to make it clear we register
s/Re-phrase/Rephrase/
> a subdev notifier and remove a redundant comment about disabling i2c
> auto-ack.
>
> No functional
Hi all,
In commit
7233da86697e ("tcp: relookup sock for RST+ACK packets handled by obsolete req
sock")
Fixes tag
Fixes: e0f9759f530 ("tcp: try to keep packet if SYN_RCV race is lost")
has these problem(s):
- SHA1 should be at least 12 digits long
This is not worth rebasing for, but
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:15:10PM +0100, Jacopo Mondi wrote:
> The init() subdev core operation is deemed to be deprecated for new
> subdevice drivers. However it could prove useful for complex
> architectures to defer operation that require access to the
>
Hi,
On Fri, Mar 12, 2021 at 10:32 AM Matthias Kaehlcke wrote:
>
> CoachZ rev3 uses a 100k NTC thermistor for the charger temperatures,
> instead of the 47k NTC that is stuffed in earlier revisions. Add .dts
> files for rev3.
>
> The 47k NTC currently isn't supported by the PM6150 ADC driver.
>
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:15:06PM +0100, Jacopo Mondi wrote:
> It has been observed through repeated testing (250 boots) that in the
> 10% of the cases the RDACM21 initialization sequence errors out due a
> timeout waiting for the OV490 firmware to complete
Am 2021-02-01 23:20, schrieb Bjorn Helgaas:
On Mon, Feb 01, 2021 at 08:49:16PM +0100, Michael Walle wrote:
Am 2021-01-17 20:27, schrieb Michael Walle:
> Am 2021-01-16 00:57, schrieb Bjorn Helgaas:
> > On Wed, Jan 13, 2021 at 12:32:32AM +0100, Michael Walle wrote:
> > > Am 2021-01-12 23:58,
Replace the use of C bit-fields in the rmnet_map_ul_csum_header
structure with a single two-byte (big endian) structure member,
and use masks to encode or get values within it. The content of
these fields can be accessed using simple bitwise AND and OR
operations on the (host byte order) value of
Replace the use of C bit-fields in the rmnet_map_dl_csum_trailer
structure with a single one-byte field, using constant field masks
to encode or get at embedded values.
Signed-off-by: Alex Elder
Reviewed-by: Bjorn Andersson
Reviewed-by: Alexander Duyck
---
v3: - Use BIT(x) and don't use
In rmnet_map_ipv4_ul_csum_header() and rmnet_map_ipv6_ul_csum_header()
the offset within a packet at which checksumming should commence is
calculated. This calculation involves byte swapping and a forced type
conversion that makes it hard to understand.
Simplify this by computing the offset in
The following macros, defined in "rmnet_map.h", assume a socket
buffer is provided as an argument without any real indication this
is the case.
RMNET_MAP_GET_MUX_ID()
RMNET_MAP_GET_CD_BIT()
RMNET_MAP_GET_PAD()
RMNET_MAP_GET_CMD_START()
RMNET_MAP_GET_LENGTH()
What they hide is
The actual layout of bits defined in C bit-fields (e.g. int foo : 3)
is implementation-defined. Structures defined in
address this by specifying all bit-fields twice, to cover two
possible layouts.
I think this pattern is repetitive and noisy, and I find the whole
notion of compiler "bitfield
The fields in the checksum trailer structure used for QMAP protocol
RX packets are all big-endian format, so define them that way.
It turns out these fields are never actually used by the RMNet code.
The start offset is always assumed to be zero, and the length is
taken from the other packet
Version 6 is the same as version 5, but has been rebased on updated
net-next/master. With any luck, the patches I'm sending out this
time won't contain garbage.
Version 5 of this series responds to a suggestion made by Alexander
Duyck, to determine the offset to the checksummed range of a packet
On Tue, Mar 16, 2021 at 01:01:44AM +0800, LGA1150 wrote:
> From: DENG Qingfang
>
> Use port isolation registers to configure bridge offloading.
> Remove the VLAN init, as we have proper CPU tag and bridge offloading
> support now.
>
> Signed-off-by: DENG Qingfang
> ---
> Changes since RFC:
>
Hi,
On Fri, Mar 12, 2021 at 10:32 AM Matthias Kaehlcke wrote:
>
> + linux,keymap = <
> + MATRIX_KEY(0x00, 0x02, KEY_BACK)
> + MATRIX_KEY(0x03, 0x02, KEY_REFRESH)
> + MATRIX_KEY(0x02, 0x02, KEY_ZOOM)
> + MATRIX_KEY(0x01, 0x02,
On 05/03/2021 15:27:52+0200, Ville Syrjälä wrote:
> > which breaks S3-resume on fi-kbl-soraka presumably as that's slow enough
> > to trigger the alarm during the suspend.
> >
> > Fixes: 6950d046eb6e ("rtc: cmos: Replace spin_lock_irqsave with spin_lock
> > in hard IRQ")
>
> Sigh. I wish people
Hi,
On Fri, Mar 12, 2021 at 10:32 AM Matthias Kaehlcke wrote:
>
> Commit f73558cc83d1 ("arm64: dts: qcom: sc7180: Disable charger
> thermal zone for lazor") disables the charger thermal zone for
> specific lazor revisions due to an unsupported thermistor type.
> The initial idea was to disable
Both add_slot_store() and remove_slot_store() try to fix up the drc_name
copied from the store buffer by placing a NULL terminator at nbyte + 1
or in place of a '\n' if present. However, the static buffer that we
copy the drc_name data into is not zeored and can contain anything past
the n-th
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on net-next/master net/master v5.12-rc3 next-20210315]
[cannot apply to sparc-next/master]
[If your patch is applied to the wrong git tree, kindly drop us a note
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:15:05PM +0100, Jacopo Mondi wrote:
> The OV10640 image sensor powerdown signal is controlled by the first
> line of the OV490 GPIO pad #1, but the pad #0 identifier
> OV490_GPIO_OUTPUT_VALUE0 was erroneously used. As a result the
Hi Alexandre,
On Mon, 15 Mar 2021 at 08:28, Alexandre Courbot wrote:
>
> Hi Ezequiel, thanks for the feedback!
>
> On Thu, Mar 4, 2021 at 6:30 AM Ezequiel Garcia
> wrote:
> >
> > Hello Alex,
> >
> > Thanks for the patch.
> >
> > On Fri, 26 Feb 2021 at 07:06, Alexandre Courbot
> > wrote:
> > >
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:15:03PM +0100, Jacopo Mondi wrote:
> The MAX9271 chip manual prescribes a delay of 5 milliseconds
> after the chip exists from low power state.
I don't think we'll ever try to access the chip within 5ms of the
beginning of its
On 15.03.21 09:02, Dmitry Vyukov wrote:
static notrace unsigned long canonicalize_ip(unsigned long ip)
@@ -191,18 +192,26 @@ void notrace __sanitizer_cov_trace_pc(void)
struct task_struct *t;
unsigned long *area;
unsigned long ip =
Hi all,
On Mon, 8 Mar 2021 18:57:41 +1100 Stephen Rothwell
wrote:
>
> Fetching the arm-soc-fixes tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#arm/fixes)
> produces this error:
>
> fatal: couldn't find remote ref refs/heads/arm/fixes
Ping?
--
Cheers,
Stephen Rothwell
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1e28eed17697bcf343c6743f0028cc3b5dd88bf0
commit: eb5c2d4b45e3d2d5d052ea6b8f1463976b1020d5 compiler.h: Move
compiletime_assert() macros into compiler_types.h
-Original Message-
From: Mathieu Poirier
Date: Monday, March 15, 2021 at 10:26 AM
To: Ben Levinsky
Cc: "devicet...@vger.kernel.org" ,
"linux-remotep...@vger.kernel.org" ,
"linux-kernel@vger.kernel.org" ,
"linux-arm-ker...@lists.infradead.org" ,
Michal Simek , "Ed T. Mooring"
On Fri, 5 Mar 2021 12:21:40 +, Chris Wilson wrote:
> As previously noted in commit 66e4f4a9cc38 ("rtc: cmos: Use
> spin_lock_irqsave() in cmos_interrupt()"):
>
> <4>[ 254.192378] WARNING: inconsistent lock state
> <4>[ 254.192384] 5.12.0-rc1-CI-CI_DRM_9834+ #1 Not tainted
> <4>[
On Sun, Mar 14, 2021 at 03:00:21PM -0700, Linus Torvalds wrote:
> So rc3 is pretty big this time around, but that's entirely artificial,
> and due to how I released rc2 early. So I'm not going to read anything
> more into this, 5.12 still seems to actually be on the smaller side
> overall. Also,
Hi!
> This is the start of the stable review cycle for the 5.10.24 release.
> There are 290 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
CIP testing did not find any kernel problems here:
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:15:00PM +0100, Jacopo Mondi wrote:
> Check the return value of the max9271_write() function in the
> max9271 library driver.
>
> While at it, modify an existing condition to be made identical
> to other checks.
>
> Signed-off-by:
On Thu, 25 Feb 2021 14:42:04 +0100, Arnd Bergmann wrote:
> The added device_property_present() call causes a build
> failure in some configurations because of the missing header:
>
> drivers/rtc/rtc-tps65910.c:422:7: error: implicit declaration of function
> 'device_property_present'
From: Cristian Ciocaltea
Date: Mon, 15 Mar 2021 13:29:17 +0200
> +
> +#define DEFAULT_MSG_ENABLE (NETIF_MSG_DRV | NETIF_MSG_PROBE | NETIF_MSG_LINK)
> +static int debug = -1;
> +module_param(debug, int, 0);
> +MODULE_PARM_DESC(debug, "Debug level (0=none,...,16=all)");
Module parameters are
On 13/03/2021 07:20, Dmitry Vyukov wrote:
On Fri, Mar 12, 2021 at 9:12 PM Ben Dooks wrote:
On 12/03/2021 16:25, Alex Ghiti wrote:
Le 3/12/21 à 10:12 AM, Dmitry Vyukov a écrit :
On Fri, Mar 12, 2021 at 2:50 PM Ben Dooks
wrote:
On 10/03/2021 17:16, Dmitry Vyukov wrote:
On Wed, Mar 10,
Hi!
> This is the start of the stable review cycle for the 4.19.181 release.
> There are 120 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
CIP testing did not find any kernel problems here:
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:14:56PM +0100, Jacopo Mondi wrote:
> Enable the noise immunity threshold at the end of the rdacm20
> initialization routine.
>
> The rdacm20 camera module has been so far tested with a startup
> delay that allowed the embedded MCU
Hi Jacopo,
Thank you for the patch.
On Mon, Mar 15, 2021 at 02:14:55PM +0100, Jacopo Mondi wrote:
> Sparse reports a warning on a cast to u8 of a 16 bits constant.
>
> drivers/media/i2c/rdacm21.c:348:62: warning: cast truncates bits
> from constant value (300a becomes a)
>
> Even if the
On Sat, 13 Mar 2021 22:25:27 +0100 Rasmus Villemoes
wrote:
> Most of the boot process doesn't actually need anything from the
> initramfs, until of course PID1 is to be executed. So instead of doing
> the decompressing and populating of the initramfs synchronously in
> populate_rootfs() itself,
Michal Hocko writes:
> bikeshedding) because it hasn't really resonated with the udnerlying
> concept. Maybe just me as a non native speaker... page_head would have
> been so much more straightforward but not something I really care
> about.
Yes. page_head explains exactly what it is.
But
-Original Message-
From: Mathieu Poirier
Date: Monday, March 15, 2021 at 10:37 AM
To: Ben Levinsky
Cc: "devicet...@vger.kernel.org" ,
"linux-remotep...@vger.kernel.org" ,
"linux-kernel@vger.kernel.org" ,
"linux-arm-ker...@lists.infradead.org" ,
Michal Simek , "Ed T. Mooring"
On Mo, 15.03.21 21:04, Matthew Wilcox (wi...@infradead.org) wrote:
> On Mon, Mar 15, 2021 at 08:18:24PM +, Matthew Wilcox wrote:
> > On Mon, Mar 15, 2021 at 09:02:38PM +0100, Matteo Croce wrote:
> > > From: Matteo Croce
> > >
> > > Add a sequence number to the disk devices. This number is
On Mon, Mar 15, 2021 at 10:11 PM Jason Ekstrand wrote:
>
> On Wed, Sep 30, 2020 at 4:55 AM Daniel Vetter wrote:
> >
> > On Wed, Sep 30, 2020 at 11:39:06AM +0200, Michel Dänzer wrote:
> > > On 2020-03-17 10:21 p.m., Jason Ekstrand wrote:
> > > > Explicit synchronization is the future. At least,
On Mon, Mar 15, 2021 at 02:56:30PM +0100, gre...@linuxfoundation.org wrote:
> From: Greg Kroah-Hartman
>
> This is the start of the stable review cycle for the 4.14.226 release.
> There are 95 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with
On Mon, Mar 15, 2021 at 02:51:23PM +0100, gre...@linuxfoundation.org wrote:
> From: Greg Kroah-Hartman
>
> This is the start of the stable review cycle for the 4.9.262 release.
> There are 78 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with
On Mon, Mar 15, 2021 at 02:51:14PM +0100, gre...@linuxfoundation.org wrote:
> From: Greg Kroah-Hartman
>
> This is the start of the stable review cycle for the 4.4.262 release.
> There are 75 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with
On Mon, Mar 15, 2021 at 03:27:35PM +0100, Álvaro Fernández Rojas wrote:
> Add support for legacy Broadcom tags, which are similar to DSA_TAG_PROTO_BRCM.
> These tags are used on BCM5325, BCM5365 and BCM63xx switches.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> include/net/dsa.h | 2 +
>
Fixed in 5.12-rc3. Thanks.
RG.
On Thu, Mar 11, 2021 at 11:52:42AM +0100, Mickaël Salaün wrote:
> [...]
> This change may not impact systems relying on other permission models
> than POSIX capabilities (e.g. Tomoyo). Being able to use chroot(2) on
> such systems may require to update their security policies.
>
> Only the
The old document for usbip protocol is misleading and hard to read:
* Some fields in header are incorrect
* Explanation of some fields are unclear or even wrong
* Padding of header (namely all headers have the same length) is
not explicitly pointed out, which is crucial for stream
On Mon, Mar 15, 2021 at 01:44:02PM -0700, Florian Fainelli wrote:
> On 3/15/2021 1:09 PM, Vladimir Oltean wrote:
> > On Mon, Mar 15, 2021 at 01:03:10PM -0700, Florian Fainelli wrote:
> >>
> >>
> >> On 3/15/2021 10:09 AM, DENG Qingfang wrote:
> >>> Support port MDB and bridge flag operations.
> >>>
On Wed, Sep 30, 2020 at 4:55 AM Daniel Vetter wrote:
>
> On Wed, Sep 30, 2020 at 11:39:06AM +0200, Michel Dänzer wrote:
> > On 2020-03-17 10:21 p.m., Jason Ekstrand wrote:
> > > Explicit synchronization is the future. At least, that seems to be what
> > > most userspace APIs are agreeing on at
Hi Jerome,
I love your patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on next-20210315]
[cannot apply to wireless-drivers-next/master wireless-drivers/master v5.12-rc3]
[If your patch is applied to the wrong git tree, kindly
its/Jerome-Pouiller/wfx-get-out-from-the-staging-area/20210315-212855
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
b828324bba8f575fde487a91fec07303789dda8a
bus_sdio.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/drivers/net/wireless/silabs/wfx/
On Mon, Mar 15, 2021 at 07:56:02PM +, Vladimir Oltean wrote:
Signed-off-by: Vladimir Oltean
Tested-by: Christian Eggers # For tail taggers only
Tested-by: Kurt Kanzenbach
Reviewed-by: Florian Fainelli
Signed-off-by: Jakub Kicinski
Signed-off-by: Sasha Levin
---
For context, Sasha
Hi!
> This is the start of the stable review cycle for the 4.4.262 release.
> There are 75 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
CIP testing did not find any problems here:
On Mon, Mar 15, 2021 at 08:18:24PM +, Matthew Wilcox wrote:
> On Mon, Mar 15, 2021 at 09:02:38PM +0100, Matteo Croce wrote:
> > From: Matteo Croce
> >
> > Add a sequence number to the disk devices. This number is put in the
> > uevent so userspace can correlate events when a driver reuses a
Hi Lukas,
> -Original Message-
> From: Lukas Bulwahn [mailto:lukas.bulw...@gmail.com]
> Sent: Tuesday, March 16, 2021 1:05 AM
> To: Rob Herring ; devicet...@vger.kernel.org
> Cc: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) ; Yu
> Chen ;
> Anitha Chrisanthus ; Jonathan Cameron
> ; Joe Perches
> ;
The K3 PRUs are 32-bit processors and in general have some limitations
in using the standard ARMv8 memcpy function for loading firmware segments,
so the driver already uses a custom memcpy implementation. This added
logic however is limited to only IRAMs at the moment, but the loading
into Data
On Mon, Mar 15, 2021 at 1:32 PM Jamie Heilman
wrote:
>
> fwiw, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850202
Yup, that seems to be the exact same thing from 4 years ago.
But it looks like nothing ever came out of it. It probably stayed
within the Debian bugzilla, and didn't go to
Hi Kuldeep,
On Mon, Mar 15, 2021 at 05:45:18PM +0530, Kuldeep Singh wrote:
> Convert the Freescale DSPI binding to DT schema format using json-schema.
>
> Signed-off-by: Kuldeep Singh
> ---
> Hi Rob,
> This patch is checked with following commands with no warnings observed.
> make distclean;
> It seems sensible the more CPU we get in the cluster, the more
> we need the kernel to be aware of its existence.
>
> Tim, it is possible for you to bring up the cpu_cluster_mask and
> cluster_sibling for x86 so that the topology can be represented
> in sysfs and be used by scheduler? It
On Mon, 15 Mar 2021 15:51:17 +0200 Jarkko Sakkinen wrote:
> On Mon, Mar 15, 2021 at 03:04:59PM +0200, Jarkko Sakkinen wrote:
> > On Mon, Mar 15, 2021 at 04:13:17PM +1300, Kai Huang wrote:
> > > On Sun, 14 Mar 2021 17:27:18 +0200 Jarkko Sakkinen wrote:
> > > > On Sun, Mar 14, 2021 at 05:25:26PM
301 - 400 of 2814 matches
Mail list logo
