On 1/11/2025 3:20 AM, Pratik Rajesh Sampat wrote:
> Hi Nikunj,
>
> On 1/9/25 11:21 PM, Nikunj A. Dadhania wrote:
>>
>>
>> On 11/15/2024 5:10 AM, Pratik R. Sampat wrote:
>>> On incompatible firmware versions, SEV-SNP support is pulled and the
>>> setup is not performed. However, the platform and
On 1/9/25 11:52 PM, Nikunj A. Dadhania wrote:
>
>
> On 11/15/2024 5:10 AM, Pratik R. Sampat wrote:
>> Add the X86_FEATURE_SNP CPU feature to the architectural definition for
>> the SEV-SNP VM type to exercise the KVM_SEV_INIT2 call. Ensure that the
>> SNP test is skipped in scenarios where CPU
Hi Nikunj,
On 1/9/25 11:21 PM, Nikunj A. Dadhania wrote:
>
>
> On 11/15/2024 5:10 AM, Pratik R. Sampat wrote:
>> On incompatible firmware versions, SEV-SNP support is pulled and the
>> setup is not performed. However, the platform and subsequently the KVM
>> capability may continue to advertize
On 1/10/2025 11:22 AM, Nikunj A. Dadhania wrote:
>
>
> On 11/15/2024 5:10 AM, Pratik R. Sampat wrote:
>> Add the X86_FEATURE_SNP CPU feature to the architectural definition for
>> the SEV-SNP VM type to exercise the KVM_SEV_INIT2 call. Ensure that the
>> SNP test is skipped in scenarios where
On 11/15/2024 5:10 AM, Pratik R. Sampat wrote:
> Add the X86_FEATURE_SNP CPU feature to the architectural definition for
> the SEV-SNP VM type to exercise the KVM_SEV_INIT2 call. Ensure that the
> SNP test is skipped in scenarios where CPUID supports it but KVM does
> not, so that a failure is n
On 11/15/2024 5:10 AM, Pratik R. Sampat wrote:
> On incompatible firmware versions, SEV-SNP support is pulled and the
> setup is not performed. However, the platform and subsequently the KVM
> capability may continue to advertize support for it. Disable support for
> SEV-SNP if the FW version va
> I am currently working on this and would rework as soon as possible.
> The feedback that you provided is highly helpful and I will remodel the
> implementation with these points in mind.
> Hopefully you can see that in the next version.
Great.
Don't worry too much about link speeds you cannot
> >
> > Thank you for your review comments.
> >
> > > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > > know the content is safe
> > >
> > > On Wed, Sep 04, 2024 at 03:45:46AM +0530, Mohan Prasad J wrote:
> > >
24 at 03:45:46AM +0530, Mohan Prasad J wrote:
> > > This series of patches are for testing the lan743x network driver.
> > > Testing comprises autonegotiation, speed, duplex and throughput checks.
> > > Tools such as ethtool, iperf3 are used in the testing process.
>
Hello Andrew,
Thank you for your review comments.
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On Wed, Sep 04, 2024 at 03:45:46AM +0530, Mohan Prasad J wrote:
> > This series of patches are for testing the lan743x network d
On Wed, Sep 04, 2024 at 03:45:46AM +0530, Mohan Prasad J wrote:
> This series of patches are for testing the lan743x network driver.
> Testing comprises autonegotiation, speed, duplex and throughput checks.
> Tools such as ethtool, iperf3 are used in the testing process.
> Performance
This series of patches are for testing the lan743x network driver.
Testing comprises autonegotiation, speed, duplex and throughput checks.
Tools such as ethtool, iperf3 are used in the testing process.
Performance test is done for TCP streams at different speeds.
Signed-off-by: Mohan Prasad J
On Fri, Jul 19, 2024 at 04:36:10PM +0800, Peng Fan (OSS) wrote:
> This patchset is to upstream a few patches that in NXP downstream for
> quite sometime. For patches directly cherry-picked from NXP downstream,
> I keep the R-b tags.
>
> Patch 1 is a minor fix to DDR alias.
> Pa
On Fri, Jul 19, 2024 at 11:27 AM Peng Fan (OSS) wrote:
>
> This patchset is to upstream a few patches that in NXP downstream for
> quite sometime. For patches directly cherry-picked from NXP downstream,
> I keep the R-b tags.
>
> Patch 1 is a minor fix to DDR alias.
> Patch
This patchset is to upstream a few patches that in NXP downstream for
quite sometime. For patches directly cherry-picked from NXP downstream,
I keep the R-b tags.
Patch 1 is a minor fix to DDR alias.
Patch 2 was sent out before,
https://patchwork.kernel.org/project/linux-remoteproc/patch
This patchset is to upstream a few patches that in NXP downstream for
quite sometime. For patches directly cherry-picked from NXP downstream,
I keep the R-b tags.
Patch 1 is a minor fix to DDR alias.
Patch 2 was sent out before,
https://patchwork.kernel.org/project/linux-remoteproc/patch
This series introduce new ICC drivers for some legacy socs
while at it also updates a bit of qcs404 driver which seems
to not receive much attention lately.
Please take in consideration i do not own any qcs404 board
so i cannot test anything else than if it compiles.
Changes since v2
=
is supposed to be specific.
>
> BTW, you use here odd email address, so:
>
>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC (and consider --no-git-fallback argument). It might
> happen, that command when run on an older kernel, gives yo
ers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Tools like b4 or scripts/get_maintai
This series introduce new ICC drivers for some legacy socs
while at it also updates a bit of qcs404 driver which seems
to not receive much attention lately.
Please take in consideration i do not own any qcs404 board
so i cannot test anything else than if it compiles.
Changes since v1
=
This series introduce new ICC drivers for some legacy socs
while at it also updates a bit of qcs404 driver which seems
to not receive much attention lately.
Please take in consideration i do not own any qcs404 board
so i cannot test anything else than if it compiles.
Adam Skladowski (7):
dt-bind
This series are based on 5.12-rc2 and we provide three i2c patches
to fix some historical issues.
Qii Wang (3):
i2c: mediatek: Fix send master code at more than 1MHz
i2c: mediatek: Fix wrong dma sync flag
i2c: mediatek: Use scl_int_delay_ns to compensate clock-stretching
drivers/i2c
On Thu, 8 Apr 2021 20:56:31 +0800, Luo Jiaxing wrote:
> Several error is reported by checkpatch.pl, here are two patches to clean
> them up.
Applied to 5.13/scsi-queue, thanks!
[1/2] scsi: pm8001: clean up for white space
https://git.kernel.org/mkp/scsi/c/8a23dbc60089
[2/2] scsi:
On Tue, Apr 13, 2021 at 02:11:54PM +0200, Anders Roxell wrote:
> Hi,
>
> Can these patches be backported to linux-5.4.y, I've tried to build
> perf on arm and it failed without these patches.
> fc8c0a992233 ("perf tools: Use %define api.pure full instead of %pure-parse
ainline from
there. It's still good practice to Cc the x86 maintainers on
x86-specific KVM and XEN patches.
Some x86 subsystems have their own maintainers in addition to the
overall x86 maintainers. Please Cc the overall x86 maintainers on
patches touching files in arch
-- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -346,6 +346,16 @@ that you have sent your patches to the right place.
> Wait for a minimum of
> one week before resubmitting or pinging reviewers - possibly longer during
>
Hi,
Can these patches be backported to linux-5.4.y, I've tried to build
perf on arm and it failed without these patches.
fc8c0a992233 ("perf tools: Use %define api.pure full instead of %pure-parser")
20befbb10803 ("perf tools: Use %zd for size_t printf formats on 32-bit"
)
diff --git a/Documentation/process/submitting-patches.rst
b/Documentation/process/submitting-patches.rst
index ab92d9ccd39a..9284735e0b34 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -346,6 +346,16 @@ that you have sent your patches to
On Thu, 25 Mar 2021 20:29:54 +0800, Luo Jiaxing wrote:
> Two types of errors are detected by the checkpatch.
> 1. Alignment between switches and cases
> 2. Improper use of some spaces
>
> Here are the clean up patches.
>
> Luo Jiaxing (2):
> scsi: libsas: make swi
Luo,
> Several error is reported by checkpatch.pl, here are two patches to clean
> them up.
Applied to 5.13/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
There are several kinds of error are reported by checkpatch.pl.
So fix them together.
Luo Jiaxing (8):
scsi: megaraid: clean up for white space
scsi: megaraid_sas: use parentheses to enclose macros with complex
values
scsi: megaraid: clean up for blank lines
scsi: megaraid: clean up f
This patch series is to fix a few issues found during patch review and
testing on Linux, also including a patch to explictly disable CET support
in nested guest over Hyper-V(s).
change in v5:
- Changed condition to snapshot CET state to vmcs01 per Sean's feedback.
- Remove mixed fix code for MPX.
their L1D cache (mitigation mechanism suggested in [2]). The previous
> > posts of these patches were sent for inclusion (see [3]) and were not
> > included due to the concern for the need for additional checks,
> > those checks were:
> >
> > 1. Implement this mec
kindly ping
Hi, jejb, martin, would you mind to take a look for these tiny clean up
patches.
Thanks
Jiaxing
On 2021/3/25 20:29, Luo Jiaxing wrote:
Two types of errors are detected by the checkpatch.
1. Alignment between switches and cases
2. Improper use of some spaces
Here are the
Several error is reported by checkpatch.pl, here are two patches to clean
them up.
---
v1->v2:
1. modify AAP1_MEMMAP() to inline function
2. set flash_command_table and flash_error_table as const
v2->v3:
1. use lower case names for AAP1_MEMMAP
---
Luo J
A reply to v1 cause v2 code need to be modified, so please ignore this,
and directly check v3 later.
Thanks
Jiaxing
On 2021/4/7 18:07, Luo Jiaxing wrote:
Several error is reported by checkpatch.pl, here are two patches to clean
them up.
---
v1->v2:
1. modify AAP1_MEMMAP()
Hi Greg,
These are the coresight patches I'd like you to consider for
the v5.13 cycle. There is only 4, the other ones will go
go through Marc's kvmarm tree as previously agreed.
I may have another (big) set coming later this week or early
next week but it may be on the late side for
Several error is reported by checkpatch.pl, here are two patches to clean
them up.
---
v1->v2:
1. modify AAP1_MEMMAP() to inline function
2. set flash_command_table and flash_error_table as const
---
Luo Jiaxing (2):
scsi: pm8001: clean up for white space
scsi: pm8
Several error is reported by checkpatch.pl, here are two patches to clean
them up.
Luo Jiaxing (2):
scsi: pm8001: clean up for white space
scsi: pm8001: clean up for open brace
drivers/scsi/pm8001/pm8001_ctl.c | 8 +++-
drivers/scsi/pm8001/pm8001_hwi.c | 14 +++---
drivers/scsi
On Mon, 22 Mar 2021 09:51:29 +0200, Tudor Ambarus wrote:
> Various cleanup patches done while reviewing contributions.
>
> Tudor Ambarus (2):
> mtd: spi-nor: Move Software Write Protection logic out of the core
> mtd: spi-nor: swp: Improve code around spi_nor_check
Hi Greg,
Here are some nvmem patches for 5.13 which includes
- adding support to new Broadcom NVRAM, MediaTek mt8192,
Qualcomm sc7280 nvmem provider
- Add new function to make numbers reading easy
- Update qfprom to support fuse blowing!
- few minor fixes.
Can you please queue them up for 5.13
To make soundwire driver more decent and less Cppcheck complaint.
Pierre-Louis Bossart (11):
soundwire: bus: use correct driver name in error messages
soundwire: bus: test read status
soundwire: bus: use consistent tests for return values
soundwire: bus: demote clock stop prepare log to de
On 3/4/21 10:46 AM, Paolo Valente wrote:
> Hi,
> this is the V2 for the third and last batches of patches that I
> proposed recently [1].
>
> I've tried to address all issues raised in [1].
>
> In more detail, main changes for V1 are:
> 1. I've improved code
Two types of errors are detected by the checkpatch.
1. Alignment between switches and cases
2. Improper use of some spaces
Here are the clean up patches.
Luo Jiaxing (2):
scsi: libsas: make switch and case at the same indent in
sas_to_ata_err()
scsi: libsas: clean up for white spaces
Hello.
On Thu, Mar 04, 2021 at 06:46:21PM +0100, Paolo Valente wrote:
> Hi,
> this is the V2 for the third and last batches of patches that I
> proposed recently [1].
>
> I've tried to address all issues raised in [1].
>
> In more detail, main changes for V1 are:
Core-Scheduling (resend based on peter's queue.git sched/core-sched branch).
===
Enclosed is interface related core scheduling patches and one for migration.
The main core scheduling patches were already pulled in by Peter with these
bits left.
Main changes are the simplificati
On 07:40 Mon 22 Mar 2021, Jonathan Corbet wrote:
Bhaskar Chowdhury writes:
On 03:44 Mon 22 Mar 2021, Matthew Wilcox wrote:
On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
s/mesages/messages/
did you test the build afterwards? you forgot to do something.
What are you
On Sat, Mar 20, 2021 at 04:40:20PM +0100, Peter Zijlstra wrote:
> On Fri, Mar 19, 2021 at 04:32:47PM -0400, Joel Fernandes (Google) wrote:
> > Enclosed is interface related core scheduling patches and one for migration.
> > The main core scheduling patches were already pulled i
Bhaskar Chowdhury writes:
> On 03:44 Mon 22 Mar 2021, Matthew Wilcox wrote:
>>On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
>>>
>>> s/mesages/messages/
>>
>>did you test the build afterwards? you forgot to do something.
>>
> What are you talking about??? It is going over my
Various cleanup patches done while reviewing contributions.
Tudor Ambarus (2):
mtd: spi-nor: Move Software Write Protection logic out of the core
mtd: spi-nor: swp: Improve code around spi_nor_check_lock_status_sr()
drivers/mtd/spi-nor/Makefile | 2 +-
drivers/mtd/spi-nor/core.c | 406
On 04:02 Mon 22 Mar 2021, Matthew Wilcox wrote:
On Mon, Mar 22, 2021 at 09:18:34AM +0530, Bhaskar Chowdhury wrote:
On 03:44 Mon 22 Mar 2021, Matthew Wilcox wrote:
> On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
> >
> > s/mesages/messages/
>
> did you test the build afterward
On Mon, Mar 22, 2021 at 09:18:34AM +0530, Bhaskar Chowdhury wrote:
> On 03:44 Mon 22 Mar 2021, Matthew Wilcox wrote:
> > On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
> > >
> > > s/mesages/messages/
> >
> > did you test the build afterwards? you forgot to do something.
> >
On 03:44 Mon 22 Mar 2021, Matthew Wilcox wrote:
On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
s/mesages/messages/
did you test the build afterwards? you forgot to do something.
What are you talking about??? It is going over my head...why the build
reqired?? A spello ne
On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
>
> s/mesages/messages/
did you test the build afterwards? you forgot to do something.
> Signed-off-by: Bhaskar Chowdhury
> ---
> Documentation/process/submitting-patches.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletio
s/mesages/messages/
Signed-off-by: Bhaskar Chowdhury
---
Documentation/process/submitting-patches.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/submitting-patches.rst
b/Documentation/process/submitting-patches.rst
index 91de63b201c1..8b2676527b7
> Il giorno 4 mar 2021, alle ore 18:46, Paolo Valente
> ha scritto:
>
> Hi,
> this is the V2 for the third and last batches of patches that I
> proposed recently [1].
>
> I've tried to address all issues raised in [1].
>
> In more detail, main changes for
On Fri, Mar 19, 2021 at 04:32:47PM -0400, Joel Fernandes (Google) wrote:
> Enclosed is interface related core scheduling patches and one for migration.
> The main core scheduling patches were already pulled in by Peter with these
> bits left.
Funny thing, they don't appear to app
On Sat, Mar 20, 2021 at 12:16:24PM +0800, Nicolas Boichat wrote:
> Backport 2 patches that are required to make KASAN+LKDTM work
> with recent clang (patch 2/2 has a complete description).
> Tested on our chromeos-4.19 branch.
> Also compile tested on x86-64 and arm64 with gcc this t
Backport 2 patches that are required to make KASAN+LKDTM work
with recent clang (patch 2/2 has a complete description).
Tested on our chromeos-4.19 branch.
Also compile tested on x86-64 and arm64 with gcc this time
around.
Patch 1/2 adds a guard around noinstr that matches upstream,
to prevent a
From: Joel Fernandes
Core-Scheduling
===
Enclosed is interface related core scheduling patches and one for migration.
The main core scheduling patches were already pulled in by Peter with these
bits left.
Main changes are the simplification of the core cookie scheme,
new prctl code
On Fri, Mar 19, 2021 at 07:54:14AM +0800, Nicolas Boichat wrote:
>
> Backport 2 patches that are required to make KASAN+LKDTM work
> with recent clang (patch 2/2 has a complete description).
> Tested on our chromeos-4.19 branch.
>
> Patch 1/2 is context conflict only, and 2/2 i
Backport 2 patches that are required to make KASAN+LKDTM work
with recent clang (patch 2/2 has a complete description).
Tested on our chromeos-4.19 branch.
Patch 1/2 is context conflict only, and 2/2 is a clean backport.
These patches have been merged to 5.4 stable already. We might
need to
On Sat, 6 Mar 2021 11:49:57 +0200, Tudor Ambarus wrote:
> Various cleanup patches done while reviewing contributions.
>
> Tudor Ambarus (5):
> mtd: spi-nor: core: Advance erase after the erase cmd has been
> completed
> mtd: spi-nor: core: Add vdbg msg for spi_nor_e
Geert Uytterhoeven writes:
> Reword the subsystem bindings section to make sense, from a grammatical
> point of view.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
This patch series is to fix a few issues found during patch review and
testing on Linux, also including a patch to explictly disable CET support
in nested guest over Hyper-V(s).
change in v4:
- Added guest CET cpuid check before sync vmcs02 CET state to vmcs12.
- Opportunistically added similar fi
Hi all,
Here are few clean-up patches after we are dropping the legacy data for
omap4/5 and dra7. These are against my omap-for-v5.13/genpd-drop-legacy
branch at [0].
Regards,
Tony
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v5.13/genpd-drop
On Thu, Mar 11, 2021 at 2:01 AM Doug Anderson wrote:
> If you happen to feel in an applying mood one other patch to
> simple-panel I think is OK to land is at:
>
> https://lore.kernel.org/r/20210222081716.1.I1a45aece5d2ac6a2e73bbec50da2086e43e0862b@changeid
I applied and pushed this as well.
Yo
On Fri, Jan 15, 2021 at 11:44 PM Douglas Anderson wrote:
> This series is to get the N116BCA-EA1 panel working. Most of the
> patches are simple, but on hardware I have in front of me the panel
> sometimes doesn't come up. I'm still working with the hardware
> manufacture
tries, if it is needed outside of the "simple" (hm)
> panel driver then we can certainly factor it out as a helper or
> library.
>
> I looked at the patches at lore.
> Reviewed-by: Linus Walleij
> I see also Stephen has reviewed some patches.
>
> Tell me if you need me
the retries are necessary and people still don't want the retries
> in simple panel, I can fork a special panel driver just for it then.
I'm fine with the retries, if it is needed outside of the "simple" (hm)
panel driver then we can certainly factor it out as a helper or
li
HPD") new for v2.
>
> I couldn't find these patches in my inbox
Doh! Sorry about that. I think get_maintainer tagged you only on the
patches that had the explicit "fixes" in them on something you were
involved in. I tend to rely on get_maintainer heavily unless I think
so
On Fri, Jan 15, 2021 at 11:44 PM Douglas Anderson wrote:
> - ("drm/panel-simple: Don't wait longer for HPD...") new for v2.
> - ("drm/panel-simple: Retry if we timeout waiting for HPD") new for v2.
I couldn't find these patches in my inbox but my concern woul
On 3/9/21 5:06 AM, Geert Uytterhoeven wrote:
> Reword the subsystem bindings section to make sense, from a grammatical
> point of view.
>
> Signed-off-by: Geert Uytterhoeven
Acked-by: Randy Dunlap
Thanks.
> ---
> Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
> 1 file cha
Reword the subsystem bindings section to make sense, from a grammatical
point of view.
Signed-off-by: Geert Uytterhoeven
---
Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/submitti
Various cleanup patches done while reviewing contributions.
Tudor Ambarus (5):
mtd: spi-nor: core: Advance erase after the erase cmd has been
completed
mtd: spi-nor: core: Add vdbg msg for spi_nor_erase_multi_sectors()
mtd: spi-nor: Get rid of duplicated argument in spi_nor_parse_sfdp
Hi folks,
On Fri, Jan 15, 2021 at 2:44 PM Douglas Anderson wrote:
>
> This series is to get the N116BCA-EA1 panel working. Most of the
> patches are simple, but on hardware I have in front of me the panel
> sometimes doesn't come up. I'm still working with the hardware
&g
Hi,
this is the V2 for the third and last batches of patches that I
proposed recently [1].
I've tried to address all issues raised in [1].
In more detail, main changes for V1 are:
1. I've improved code as requested in "block, bfq: merge bursts of
newly-created queues"
2. I&
This patch series is to fix a few issues found during nested guest
testing on Linux, also including a patch to explictly disable CET
support in nested guest over Hyper-V(s).
Yang Weijiang (3):
KVM: nVMX: Sync L2 guest CET states between L1/L2
KVM: nVMX: Set X86_CR4_CET in cr4_fixed1_bits if CE
a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
83bf6fb8b076c72f perf vendor events power9: Remove unsupported
> >metrics
> >> > 34968b9327c83589 perf buildid-cache: Add test for PE executable
> >> > 9bb8b74bdb186bd3 perf docs: Add man pages to see also
> >> > d9fd5a718977702f perf tools: Generate mips
rier escreveu:
> > > > I noticed there is a couple of patchsets [1][2] that haven't made it
> > > > to your tree for the coming v5.12 cycle. Do you think that can still
> > > > be done?
>
> > > > I tallied the patches here to make it
wrote:
> > > > Em Wed, Feb 24, 2021 at 09:48:29AM -0700, Mathieu Poirier escreveu:
> > > > > I noticed there is a couple of patchsets [1][2] that haven't made it
> > > > > to your tree for the coming v5.12 cycle. Do you think that can still
> > &
: Add man pages to see also
>> > d9fd5a718977702f perf tools: Generate mips syscalls_n64.c syscall
>table
>> > $
>>
>> As far as I can tell you have all 6 patches.
>>
>
>Agreed - [1] I was trying is in fact:
>42b2b570b34afb5f perf cs-etm: Update ETM metadata format
>in the above list.
Ok, I misunderstood, good that's all already in, thanks for checking!
- Arnaldo
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > > to your tree for the coming v5.12 cycle. Do you think that can still
> > > be done?
> > > I tallied the patches here to make it easier for you to pick up.
> > > Applies cleanly on perf/core (84b7725536d8)
> > > [1].
> > > https:
ree for the coming v5.12 cycle. Do you think that can still
> > be done?
> >
> > I tallied the patches here to make it easier for you to pick up.
> >
> > Applies cleanly on perf/core (84b7725536d8)
> >
> > Thanks,
> > Mathieu
> >
> &
the window is closed and I missed
processing these in time, so it'll make v5.13, sorry.
- Arnaldo
> I tallied the patches here to make it easier for you to pick up.
>
> Applies cleanly on perf/core (84b7725536d8)
>
> Thanks,
> Mathieu
>
> [1].
> https:/
Hi Mark,
This patchset involves changes in NXP Flexspi driver.
Patch1 adds support for disabling AHB and enabling IP read only using a
quirk which is later used by patch3 and patch4.
Patch3 and Patch4 are not related to each and are rather dependent on
patch1 and that's why I kept them in series.
Em Wed, Feb 24, 2021 at 09:48:29AM -0700, Mathieu Poirier escreveu:
> Good day Arnaldo,
>
> I noticed there is a couple of patchsets [1][2] that haven't made it
> to your tree for the coming v5.12 cycle. Do you think that can still
> be done?
>
> I tallied the patc
Borislav Petkov writes:
> From: Borislav Petkov
> Subject: [PATCH] Documentation/submitting-patches: Extend commit message
> layout description
>
> Add more blurb about the level of detail that should be contained in a
> patch's commit message. Extend and make more ex
Hi Mark,
This patchset involves changes in NXP Flexspi driver.
Please note, though all patches might not be related to each other, I
have clubbed them so as to make easy application of series.
Patch2 is dependent on dt-bindings
https://patchwork.kernel.org/project/spi-devel-general/patch
Hi Michael,
I see that you did not include these in your latest pull request.
https://lkml.org/lkml/2021/2/10/1386
https://lkml.org/lkml/2021/2/10/1383
https://lkml.org/lkml/2021/2/18/124
Are you going to merge them?
The pull request you sent on Sat, 27 Feb 2021 12:28:39 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
> tags/riscv-for-linus-5.12-mw1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7d19ea5e99731f5346b047003bbe65117a86d12d
Thank you!
--
-----
RISC-V Patches for the 5.12 Merge Window, Part 2
I have a pair of patches that slipped through the cracks:
* CPU hotplug has been enabled in the defconfigs
* Some cleanups to setup_bootmem.
There's also a single fix
* Force NUMA to depend on SMP. This fixes some ra
The pull request you sent on Fri, 26 Feb 2021 21:02:08 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.12-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e7270e47a09e83051da7b2bee71be00741860ec4
Thank you!
--
Deet-doot-dot, I am a
Hello Linus,
please pull the second round of s390 fixes and features for 5.12.
Thank you,
Vasily
The following changes since commit df24212a493afda0d4de42176bea10d45825e9a0:
Merge tag 's390-5.12-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux (2021-02-21 13:40:06
-0800)
are
The pull request you sent on Fri, 26 Feb 2021 07:39:42 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
> tags/riscv-for-linus-5.12-mw0
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8b83369ddcb3fb9cab5c1088987ce477565bb630
Thank you!
--
d7fbcf40df86bb67193d9faf52138fc1202decb2:
riscv: Improve kasan population by using hugepages when possible (2021-02-22
18:54:17 -0800)
RISC-V Patches for the 5.12 Merge Window
I have a handful of new RISC-V related patches for this
The pull request you sent on Thu, 25 Feb 2021 15:35:17 +0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
> tags/nds32-for-linux-5.12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6c15f9e805f22566d7547551f359aba04b611f9d
Thank you!
--
Deet-
On 15.02.21 15:19:49, Borislav Petkov wrote:
> From: Borislav Petkov
> Subject: [PATCH] Documentation/submitting-patches: Extend commit message
> layout description
>
> Add more blurb about the level of detail that should be contained in a
> patch's commit message. Extend
/linux.git
tags/nds32-for-linux-5.12
for you to fetch changes up to 40e0dd851e7b7afe219820fb270b09016e41d4fc:
nds32: Fix bogus reference to (2021-02-25 14:31:49 +0800)
nds32 patches for 5.12
Here is the nds32 patchset based on 5.11
1 - 100 of 5467 matches
Mail list logo
