Dear Friend, My present internet connection is very slow in case you
received my email in your spam
How are you today?.With due respect to your person and much sincerity
of purpose,Well it is a pleasure to contact you on this regard and i
pray that this will turn out to be everlasting
On 05/05/2020 22.38, Bruno Thomsen wrote:
> Hi Rasmus
>
> Den tir. 5. maj 2020 kl. 22.07 skrev Alexandre Belloni
> :
>>
>> On 05/05/2020 21:54:47+0200, Rasmus Villemoes wrote:
>>> Hi Bruno
>>>
>>> I just noticed your "rtc: pcf2127: add tamper detection support"
>>> (03623b4b04) from 5.4.
On Mon, May 04, 2020 at 10:15:14PM -0400, J. Bruce Fields wrote:
> Though now I'm feeling greedy: it would be nice to have both some kind
> of global flag, *and* keep kthread->data pointing to svc_rqst (as that
> would give me a simpler and quicker way to figure out which client is
> conflicting).
On 2020-05-05 22:03, Andrew Morton wrote:
On Tue, 05 May 2020 10:42:05 +0200 Roman Penyaev
wrote:
May I ask you to remove "epoll: ensure ep_poll() doesn't miss wakeup
events" from your -mm queue? Jason lately found out that the patch
does not fully solve the problem and this one patch is a
On Tue, May 5, 2020 at 6:02 PM Jürgen Groß wrote:
> On 05.05.20 17:01, Arnd Bergmann wrote:
> > On Tue, May 5, 2020 at 4:34 PM Jürgen Groß wrote:
> >> On 05.05.20 16:15, Arnd Bergmann wrote:
> >
> > I considered that as well, and don't really mind either way. I think it does
> > get a bit ugly
On Tue, 2020-05-05 at 22:40 +0200, Pali Rohár wrote:
> Hello!
>
> On Tuesday 05 May 2020 12:57:37 Joe Perches wrote:
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > > index eac40f0abd56a9f4..3355358697d9e790 100755
> > > --- a/scripts/checkpatch.pl
> > > +++
Hi Ben,
On Fri, Apr 24, 2020 at 10:36:10AM -0700, Ben Levinsky wrote:
> R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
> remotproc driver, we can boot the R5 sub-system in different
> configurations.
>
> Acked-by: Stefano Stabellini
> Acked-by: Ben Levinsky
> Reviewed-by:
On 2020-05-05 13:36, Souptick Joarder wrote:
On Wed, May 6, 2020 at 1:08 AM John Hubbard wrote:
On 2020-05-05 12:14, Souptick Joarder wrote:
Currently {get|pin}_user_pages_fast() have 3 return value 0, -errno
and no of pinned pages. The only case where these two functions will
return 0, is
On Tue, May 5, 2020 at 10:07 PM Jason A. Donenfeld wrote:
> On Tue, May 5, 2020 at 8:13 AM Arnd Bergmann wrote:
> >
> > clang points out a harmless use of uninitialized variables that
> > get passed into a local function but are ignored there:
> >
> > In file included from
On Tue, May 05, 2020 at 02:44:28PM -0500, Eric W. Biederman wrote:
>
> At least gcc 8.3 when generating code for x86_64 has a hard time
> consolidating multiple calls to current aka get_current(), and winds
> up unnecessarily rereading %gs:current_task several times in
> setup_new_exec.
>
>
When single-step triggered with KVM_SET_GUEST_DEBUG, we should fill in the pc
value with current linear RIP rather than the cached singlestep address.
Signed-off-by: Peter Xu
---
arch/x86/kvm/x86.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/x86.c
On Tue, May 05, 2020 at 02:43:25PM -0500, Eric W. Biederman wrote:
>
> The two functions are now always called one right after the
> other so merge them together to make future maintenance easier.
>
> Signed-off-by: "Eric W. Biederman"
Reviewed-by: Kees Cook
--
Kees Cook
The first two patches try to fix two issues I found (I think) with the
selftest. The 3rd patch is the test itself. Note, we need below patches to be
applied too for the test to work:
KVM: X86: Declare KVM_CAP_SET_GUEST_DEBUG properly
KVM: selftests: Fix build for evmcs.h
Please
Covers fundamental tests for KVM_SET_GUEST_DEBUG. It is very close to the debug
test in kvm-unit-test, but doing it from outside the guest.
Signed-off-by: Peter Xu
---
tools/testing/selftests/kvm/Makefile | 1 +
.../testing/selftests/kvm/include/kvm_util.h | 2 +
RTM should always been set even with KVM_EXIT_DEBUG on #DB.
Signed-off-by: Peter Xu
---
arch/x86/kvm/vmx/vmx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index c2c6335a998c..05ed3e707ec6 100644
--- a/arch/x86/kvm/vmx/vmx.c
On Tue, May 05, 2020 at 02:42:26PM -0500, Eric W. Biederman wrote:
>
> Update the comments and make the code easier to understand by
> renaming this flag.
>
> Signed-off-by: "Eric W. Biederman"
Reviewed-by: Kees Cook
--
Kees Cook
On Tue, May 05, 2020 at 10:42:58PM +0200, Christoph Hellwig wrote:
> On Tue, May 05, 2020 at 09:34:46PM +0100, Al Viro wrote:
> > Looks good. Want me to put it into vfs.git? #work.set_fs-exec, perhaps?
>
> Sounds good.
Applied, pushed and added into #for-next
On Tue, May 05, 2020 at 02:41:47PM -0500, Eric W. Biederman wrote:
>
> With install_exec_creds updated to follow immediately after
> setup_new_exec, the failure of unshare_sighand is the only
> code path where exec_update_mutex is held but not explicitly
> unlocked.
>
> Update that code path to
On Tue, May 05, 2020 at 02:41:01PM -0500, Eric W. Biederman wrote:
>
> In 2016 Linus moved install_exec_creds immediately after
> setup_new_exec, in binfmt_elf as a cleanup and as part of closing a
> potential information leak.
>
> Perform the same cleanup for the other binary formats.
>
>
On Tue, May 05, 2020 at 09:34:46PM +0100, Al Viro wrote:
> Looks good. Want me to put it into vfs.git? #work.set_fs-exec, perhaps?
Sounds good.
On Tue, May 05, 2020 at 08:34:41AM +0200, Greg KH wrote:
> On Mon, May 04, 2020 at 09:59:03PM +, Luis Chamberlain wrote:
> > On Mon, May 04, 2020 at 01:32:07PM -0700, Kees Cook wrote:
> > > On Mon, May 04, 2020 at 07:59:37PM +, Luis Chamberlain wrote:
> > > > On Mon, May 04, 2020 at
Hello!
On Tuesday 05 May 2020 12:57:37 Joe Perches wrote:
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index eac40f0abd56a9f4..3355358697d9e790 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -1057,6 +1057,10 @@ for my $filename (@ARGV) {
> >
On Tue, May 5, 2020 at 10:13 AM Thomas Gleixner wrote:
>
> The sanitizers are not really applicable to the fragile low level entry
> code. code. Entry code needs to carefully setup a normal 'runtime'
> environment.
>
> Signed-off-by: Peter Zijlstra (Intel)
> Signed-off-by: Thomas Gleixner
> ---
Hi Rasmus
Den tir. 5. maj 2020 kl. 22.07 skrev Alexandre Belloni
:
>
> On 05/05/2020 21:54:47+0200, Rasmus Villemoes wrote:
> > Hi Bruno
> >
> > I just noticed your "rtc: pcf2127: add tamper detection support"
> > (03623b4b04) from 5.4. Unfortunately, clearing the BTSE bit breaks a use
> > case
Hi.
On 1/5/20 5:22, Daniil Lunev wrote:
> Hi Prashant,
> I do not think it is present. Thinking about it, I do not think it
> shall be an issue on any released device as it will have either a
> firmware which wouldn't even trigger the typec probe or the one after
> the hierarchy fix. Likely I
On Tue, May 5, 2020 at 1:04 PM Andrew Morton wrote:
>
> On Tue, 05 May 2020 10:42:05 +0200 Roman Penyaev wrote:
>
> > May I ask you to remove "epoll: ensure ep_poll() doesn't miss wakeup
> > events" from your -mm queue? Jason lately found out that the patch
> > does not fully solve the problem
On Tue, May 05, 2020 at 12:12:49PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> this series gets rid of playing with the address limit in the exec and
> coredump code. Most of this was fairly trivial, the biggest changes are
> those to the spufs coredump code.
>
> Changes since v5:
> - fix
On Tue, 07 Apr 2020 21:21:57 +0100 David Howells wrote:
> David Howells wrote:
>
> > > if (unlikely(key_data))
> > > - __kvzfree(key_data, key_data_len);
> > > + kvfree_sensitive(key_data, key_data_len);
> >
> > I think the
On Mon, May 04, 2020 at 11:14:03PM +, Singh, Balbir wrote:
> On Mon, 2020-05-04 at 11:39 -0700, Kees Cook wrote:
> >
> > On Mon, May 04, 2020 at 02:13:42PM +1000, Balbir Singh wrote:
> > > Implement a mechanism to selectively flush the L1D cache. The goal
> > > is to
> > > allow tasks that
Linus Torvalds writes:
> On Tue, May 5, 2020 at 3:13 AM Christoph Hellwig wrote:
>>
>> this series gets rid of playing with the address limit in the exec and
>> coredump code. Most of this was fairly trivial, the biggest changes are
>> those to the spufs coredump code.
>
> Ack, nice, and looks
randconfig-b003-20200503
x86_64 randconfig-b001-20200503
i386 randconfig-b002-20200503
x86_64 randconfig-d001-20200505
i386 randconfig-d003-20200505
i386 randconfig-d001-20200505
x86_64 randconfig-d003
> Subject: RE: [PATCH net] soc: fsl: dpio: properly compute the consumer index
>
>
>
> > -Original Message-
> > From: Ioana Ciornei
> > Sent: Tuesday, May 5, 2020 3:14 PM
> > To: da...@davemloft.net; net...@vger.kernel.org; linux-
> > ker...@vger.kernel.org
> > Cc: Youri Querry ; Leo
While the ability to override or append to the boot command line has
been added, the boot messages contain no information as to whether the
cmdline was manipulated by the build-time options. This patch, for x86,
adds boot messages specifying the intital cmdline, and the final cmdline
after
On Wed, May 6, 2020 at 1:08 AM John Hubbard wrote:
>
> On 2020-05-05 12:14, Souptick Joarder wrote:
> > Currently {get|pin}_user_pages_fast() have 3 return value 0, -errno
> > and no of pinned pages. The only case where these two functions will
> > return 0, is for nr_pages <= 0, which doesn't
> -Original Message-
> From: Ioana Ciornei
> Sent: Tuesday, May 5, 2020 3:14 PM
> To: da...@davemloft.net; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Cc: Youri Querry ; Leo Li ;
> Ioana Ciornei
> Subject: [PATCH net] soc: fsl: dpio: properly compute the consumer index
>
ug it first?
> > > Which version of gcc are you using and what .config?
> > > I've tried:
> > > Linux version 5.7.0-rc2 (gcc version 10.0.1 20200505 (prerelease) (GCC)
> > > CONFIG_UNWINDER_ORC=y
> > > # CONFIG_RETPOLINE is not set
> > &
- On May 5, 2020, at 3:57 PM, ndesaulniers ndesaulni...@google.com wrote:
> On Tue, May 5, 2020 at 12:00 PM Mathieu Desnoyers
> wrote:
>>
>> - On May 5, 2020, at 2:48 PM, Linus Torvalds
>> torva...@linux-foundation.org
>> wrote:
>> [...]
>> >
>> > Your initial reaction that "you can't
From: Grygorii Strashko
Date: Tue, 5 May 2020 19:21:23 +0300
> It's possible to have build configuration which will force PTP_1588_CLOCK=m
> and so TI_K3_AM65_CPTS=m while still have TI_K3_AM65_CPSW_NUSS=y. This will
> cause build failures:
>
> aarch64-linux-gnu-ld:
On 5/1/20 2:05 PM, Dave Hansen wrote:
From: Dave Hansen
This is not a bug fix. It was found by inspection, but I believe
that it is confusing as it stands.
First, page_ref_freeze() is implemented internally with:
atomic_cmpxchg(>_refcount, expected, 0) == expected
The "cmp" part
> What do you think about changing:
> "But when nfp_nsp_has_hwinfo_lookup fail, the pointer is not released,.."
> to
…
> or
> "But when nfp_nsp_has_hwinfo_lookup fail,
I became curious about a related wording variant.
But when a call of the function “…” failed,
> NSP resource is not cleaned
From: Geert Uytterhoeven
Date: Tue, 5 May 2020 15:34:00 +0200
> There is no need to cast a typed pointer to a void pointer when calling
> a function that accepts the latter. Remove it, as the cast prevents
> further compiler checks.
>
> Signed-off-by: Geert Uytterhoeven
Applied to net-next,
On Tue, May 05, 2020 at 09:36:04PM +0200, Thomas Gleixner wrote:
> Ashok,
>
>
> > Now the second question with Interrupt Remapping Support:
> >
> > intel_ir_set_affinity->intel_ir_reconfigure_irte()-> modify_irte()
> >
> > The flush of Interrupt Entry Cache (IEC) should ensure, if any interrupts
Mask the consumer index before using it. Without this, we would be
writing frame descriptors beyond the ring size supported by the QBMAN
block.
Fixes: 3b2abda7d28c ("soc: fsl: dpio: Replace QMAN array mode with ring mode
enqueue")
Signed-off-by: Ioana Ciornei
---
I am sending this fix through
Add support for the RTC_VL_BACKUP_SWITCH flag to report battery switch over
events.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf2127.c | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-pcf2127.c b/drivers/rtc/rtc-pcf2127.c
index
There is not point in setting .ioctl to NULL when CONFIG_RTC_INTF_DEV is
not defined because it would not be called anyway.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf2127.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/rtc/rtc-pcf2127.c b/drivers/rtc/rtc-pcf2127.c
Set regmap max_register to ease debugging and enforce the register range.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf2127.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/rtc/rtc-pcf2127.c b/drivers/rtc/rtc-pcf2127.c
index 5ac996578523..039078029bd4 100644
---
Let the core handle offsetting and windowing the RTC range.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf2127.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/rtc/rtc-pcf2127.c b/drivers/rtc/rtc-pcf2127.c
index 4e50d6768f13..136709baaa88 100644
A new flag RTC_VL_BACKUP_SWITCH means that a backup switchover happened
since last flag clear.
Signed-off-by: Alexandre Belloni
---
include/uapi/linux/rtc.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/rtc.h b/include/uapi/linux/rtc.h
index 83bba58d47f4..fa9aff91cbf2
On Tue, 5 May 2020 08:21:34 +0530 Anshuman Khandual
wrote:
> >>> static inline void arch_clear_hugepage_flags(struct page *page)
> >>> {
> >>>
> >>> }
> >>> #define arch_clear_hugepage_flags arch_clear_hugepage_flags
> >>>
> >>> It's a small difference - mainly to avoid adding two variables
get_user_pages_fast() is already having a check for the same. This
double check can be removed.
Signed-off-by: Souptick Joarder
---
drivers/misc/vmw_vmci/vmci_host.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/misc/vmw_vmci/vmci_host.c
b/drivers/misc/vmw_vmci/vmci_host.c
index
Reviewed-by: Julius Werner
On 05/05/2020 21:54:47+0200, Rasmus Villemoes wrote:
> Hi Bruno
>
> I just noticed your "rtc: pcf2127: add tamper detection support"
> (03623b4b04) from 5.4. Unfortunately, clearing the BTSE bit breaks a use
> case of ours:
>
> We rely on the battery switch-over detection to distinguish a
On Tue, May 5, 2020 at 8:13 AM Arnd Bergmann wrote:
>
> clang points out a harmless use of uninitialized variables that
> get passed into a local function but are ignored there:
>
> In file included from drivers/net/wireguard/ratelimiter.c:223:
>
Hi,
On Mon, May 4, 2020 at 11:36 PM Stephen Boyd wrote:
>
> > > -static int check_for_req_inflight(struct rsc_drv *drv, struct tcs_group
> > > *tcs,
> > > - const struct tcs_request *msg)
> > > +static int check_for_req_inflight_and_find_free(struct rsc_drv *drv,
On Tue, 05 May 2020 10:42:05 +0200 Roman Penyaev wrote:
> May I ask you to remove "epoll: ensure ep_poll() doesn't miss wakeup
> events" from your -mm queue? Jason lately found out that the patch
> does not fully solve the problem and this one patch is a second
> attempt to do things correctly
This adds the SNPS FemtoPHY V2 driver used in QCOM SOCs. There
are potentially multiple instances of this UTMI PHY on the
SOC, all which can utilize this driver. The V2 driver will
have a different register map compared to V1.
Signed-off-by: Wesley Cheng
Reviewed-by: Philipp Zabel
The UFS QMP v4 PHY has a largely different register set versus USB and
PCIe. Rename the register offsets to denote that the value is specific for
the UFS PCS register.
Signed-off-by: Wesley Cheng
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 20 +--
The register map for SM8150 QMP USB SSPHY has moved
QPHY_POWER_DOWN_CONTROL to a different offset. Allow for
an offset in the register table to override default value
if it is a DP capable PHY.
Signed-off-by: Wesley Cheng
Reviewed-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 23
From: Jack Pham
Add support for SM8150 QMP USB3 PHY with the necessary
initialization sequences as well as additional QMP V4
register definitions.
Signed-off-by: Jack Pham
Signed-off-by: Wesley Cheng
Reviewed-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 153
This binding shows the descriptions and properties for the
Synopsis Femto USB PHY V2 used on QCOM platforms.
Signed-off-by: Wesley Cheng
Reviewed-by: Rob Herring
Reviewed-by: Stephen Boyd
---
.../bindings/phy/qcom,usb-snps-femto-v2.yaml | 80 ++
1 file changed, 80
This series adds support for the Synopsis 7nm HSPHY USB driver being
used in QCOM chipsets. The HSPHY register map differs compared to
other PHY revisions. In addition, modifications and updates are done
to the QMP driver to add new registers/offsets, and to update the
initialization sequence
On Tue, 2020-05-05 at 15:26 +0200, Geert Uytterhoeven wrote:
> While "git am" can apply an mbox file containing multiple patches (e.g.
> as created by b4[1], or a patch bundle downloaded from patchwork),
> checkpatch does not have proper support for that. When operating on an
> mbox, checkpatch
On Tue, May 5, 2020 at 12:00 PM Mathieu Desnoyers
wrote:
>
> - On May 5, 2020, at 2:48 PM, Linus Torvalds
> torva...@linux-foundation.org wrote:
> [...]
> >
> > Your initial reaction that "you can't compile away the read and the
> > test of NULL" was correct, I think.
>
> I suspect this
On Tue, May 5, 2020 at 3:26 PM YueHaibing wrote:
>
> Remove duplicated include.
>
> Signed-off-by: YueHaibing
Tested-by: Souptick Joarder
> ---
> mm/madvise.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/mm/madvise.c b/mm/madvise.c
> index 8fec261457a6..f8be54dd92d3 100644
> ---
Hi Bruno
I just noticed your "rtc: pcf2127: add tamper detection support"
(03623b4b04) from 5.4. Unfortunately, clearing the BTSE bit breaks a use
case of ours:
We rely on the battery switch-over detection to distinguish a powerfail
during boot from a PORESET by the external watchdog (in the
t you'd need
> > > to tell me what tests to run.
> >
> > I'd like to minimize the risk and avoid code churn,
> > so how about we step back and debug it first?
> > Which version of gcc are you using and what .config?
> > I've tried:
> > Linux version 5.7.0-
Quoting Doug Anderson (2020-05-05 11:45:05)
> On Mon, May 4, 2020 at 10:44 PM Stephen Boyd wrote:
> >
> > Quoting Douglas Anderson (2020-05-04 21:36:31)
> > > regmap_update_bits(pdata->regmap, SN_DSI_LANES_REG,
> > >CHA_DSI_LANES_MASK, val);
> > >
> > > +
From: Grygorii Strashko
Date: Tue, 5 May 2020 13:19:35 +0300
> Fix dt_binding_check fail:
> Fix Documentation/devicetree/bindings/net/ti,k3-am654-cpts.yaml: $id:
> relative path/filename doesn't match actual path or filename
> expected:
There is and has been for a very long time been a lot more going on in
flush_old_exec than just flushing the old state. After the movement
of code from setup_new_exec there is a whole lot more going on than
just flushing the old executables state.
Rename flush_old_exec to begin_new_exec to
The current idiom for the callers is:
flush_old_exec(bprm);
set_personality(...);
setup_new_exec(bprm);
In 2010 Linus split flush_old_exec into flush_old_exec and
setup_new_exec. With the intention that setup_new_exec be what is
called after the processes new personality is set.
Move the
At least gcc 8.3 when generating code for x86_64 has a hard time
consolidating multiple calls to current aka get_current(), and winds
up unnecessarily rereading %gs:current_task several times in
setup_new_exec.
Caching the value of current in the local variable of me generates
slightly better
The two functions are now always called one right after the
other so merge them together to make future maintenance easier.
Signed-off-by: "Eric W. Biederman"
---
arch/x86/ia32/ia32_aout.c | 1 -
fs/binfmt_aout.c | 1 -
fs/binfmt_elf.c | 1 -
fs/binfmt_elf_fdpic.c |
From: YueHaibing
Date: Tue, 5 May 2020 16:47:36 +0800
> There's no callers in-tree anymore since commit 5952fde10c35 ("net:
> sched: choke: remove dead filter classify code")
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:50:09 +0800
> commit 05cc5a39ddb7 ("bnx2x: add vlan filtering offload")
> left behind this, remove it.
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:51:24 +0800
> There's no callers in-tree
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:44:21 +0800
> There's no callers in-tree.
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:42:56 +0800
> There's no caller in-tree since
> commit 2af6106ae949 ("net: stmmac: Introducing support for Page Pool")
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:40:37 +0800
> commit 84411f73b884 ("net: mv643xx_eth: Avoid setting the initial TCP
> checksum")
> left behind this, remove it.
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:33:12 +0800
> There's no callers in-tree anymore.
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:31:56 +0800
> There's no callers in-tree anymore.
>
> Signed-off-by: YueHaibing
Applied.
From: YueHaibing
Date: Tue, 5 May 2020 16:43:39 +0800
> commit 4ca3221fe4b6 ("myri10ge: Convert from LRO to GRO")
> left behind this, remove it.
>
> Signed-off-by: YueHaibing
Applied.
Update the comments and make the code easier to understand by
renaming this flag.
Signed-off-by: "Eric W. Biederman"
---
fs/exec.c | 12 ++--
include/linux/binfmts.h | 6 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/fs/exec.c b/fs/exec.c
index
On Tue, May 05, 2020 at 08:35:05AM +0200, Oleksij Rempel wrote:
> This UAPI is needed for BroadR-Reach 100BASE-T1 devices. Due to lack of
> auto-negotiation support, we needed to be able to configure the
> MASTER-SLAVE role of the port manually or from an application in user
> space.
>
> The same
With install_exec_creds updated to follow immediately after
setup_new_exec, the failure of unshare_sighand is the only
code path where exec_update_mutex is held but not explicitly
unlocked.
Update that code path to explicitly unlock exec_update_mutex.
Remove the unlocking of exec_update_mutex
In 2016 Linus moved install_exec_creds immediately after
setup_new_exec, in binfmt_elf as a cleanup and as part of closing a
potential information leak.
Perform the same cleanup for the other binary formats.
Different binary formats doing the same things the same way makes exec
easier to
In the patchset that introduced exec_update_mutex there were a few last
minute discoveries and fixes that left the code in a state that can
be very easily be improved.
During the merge window we discussed the first three of these patches
and I promised I would resend them.
What the first patch
On 2020-05-05 12:14, Souptick Joarder wrote:
Currently {get|pin}_user_pages_fast() have 3 return value 0, -errno
and no of pinned pages. The only case where these two functions will
return 0, is for nr_pages <= 0, which doesn't find a valid use case.
But if at all any, then a -ERRNO will be
On 5/5/2020 6:34 AM, Rob Herring wrote:
> On Mon, 4 May 2020 16:54:23 -0700, Wesley Cheng wrote:
>> This binding shows the descriptions and properties for the
>> Synopsis Femto USB PHY V2 used on QCOM platforms.
>>
>> Signed-off-by: Wesley Cheng
>> Reviewed-by: Rob Herring
>> Reviewed-by:
Ashok,
"Raj, Ashok" writes:
> On Tue, Mar 24, 2020 at 08:03:44PM +0100, Thomas Gleixner wrote:
>> Evan Green writes:
>> Well, the point is that we don't see a spurious interrupt on any
>> CPU. We added a traceprintk into do_IRQ() and that would immediately
>> tell us where the thing goes off
The Texas Instruments K3 Multicore SoC platforms have chipid module which
is represented by CTRLMMR_xxx_JTAGID register and contains information
about SoC id and revision.
Bits:
31-28 VARIANT Device variant
27-12 PARTNO Part number
11-1 MFG Indicates TI as manufacturer (0x17)
1
Add DT binding for Texas Instruments K3 Multicore SoC platforms chipid
module which is represented by CTRLMMR_xxx_JTAGID register and contains
information about SoC id and revision.
Signed-off-by: Grygorii Strashko
Reviewed-by: Lokesh Vutla
---
.../bindings/soc/ti/k3-socinfo.yaml |
Hi All,
This series introduces TI K3 Multicore SoC platforms chipid module driver
which provides identification support of the TI K3 SoCs (family, revision)
and register this information with the SoC bus. It is available under
/sys/devices/soc0/ for user space, and can be checked, where needed,
On Tue, May 05, 2020 at 12:14:05PM -0700, Alexei Starovoitov wrote:
> >
> > Hi,
> >
> > I see the objtool warning:
> > kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x33: call without
> > frame pointer save/setup
> >
> > when using:
> > gcc (SUSE Linux) 9.3.1 20200406 [revision
> >
Quoting Christophe JAILLET (2020-05-03 12:03:27)
> s/Sypport/Support
>
> Signed-off-by: Christophe JAILLET
> ---
Applied to clk-next
Quoting YueHaibing (2020-05-05 01:30:01)
> There's no callers in-tree anymore.
>
> Signed-off-by: YueHaibing
> ---
Applied to clk-next
Elsewhere in the file, there is a list_for_each_entry with
>resv_regions as the second argument, suggesting that
>resv_regions is the list head. So exchange the
arguments on the list_add call to put the list head in the
second argument.
Fixes: 2a5a31487445 ("iommu/virtio: Add probe request")
On Tue, May 5, 2020 at 7:05 AM Bartosz Golaszewski wrote:
>
> From: Bartosz Golaszewski
>
> Provide devm_register_netdev() - a device resource managed variant
> of register_netdev(). This new helper will only work for net_device
> structs that have a parent device assigned and are devres managed
On Tue, 5 May 2020 15:26:13 +0200 Geert Uytterhoeven
wrote:
> While "git am" can apply an mbox file containing multiple patches (e.g.
> as created by b4[1], or a patch bundle downloaded from patchwork),
> checkpatch does not have proper support for that. When operating on an
> mbox,
On Fri, May 01, 2020 at 11:58:05PM +0200, Ansuel Smith wrote:
> Document dwc3 qcom phy hs and ss phy bindings needed to correctly
> inizialize and use usb on ipq806x SoC.
>
> Signed-off-by: Ansuel Smith
> ---
> v5:
> * Fix dt_binding_check error
> v4:
> * Add qcom to specific bindings
> v3:
> *
>
> Hi,
>
> I see the objtool warning:
> kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x33: call without
> frame pointer save/setup
>
> when using:
> gcc (SUSE Linux) 9.3.1 20200406 [revision
> 6db837a5288ee3ca5ec504fbd5a765817e556ac2]
>
> with the attached config file.
Thanks
301 - 400 of 1544 matches
Mail list logo
