On 5/25/25 12:26, Harshal Wadhwa wrote:
On Fri, 23 May 2025 at 03:49, Shuah Khan wrote:
On 5/16/25 09:39, Harshal wrote:
Specify details in logs of failed cases
Use die() instead of exit() when write to
sys_path fails
Please explain why this change is needed?
Signed-off-by: Harshal
On Fri, 23 May 2025 at 03:49, Shuah Khan wrote:
>
> On 5/16/25 09:39, Harshal wrote:
> > Specify details in logs of failed cases
> >
> > Use die() instead of exit() when write to
> > sys_path fails
>
> Please explain why this change is needed?
>
> >
&g
On 5/16/25 09:39, Harshal wrote:
Specify details in logs of failed cases
Use die() instead of exit() when write to
sys_path fails
Please explain why this change is needed?
Signed-off-by: Harshal
---
tools/testing/selftests/firmware/fw_namespace.c | 17 +
1 file changed
Specify details in logs of failed cases
Use die() instead of exit() when write to
sys_path fails
Signed-off-by: Harshal
---
tools/testing/selftests/firmware/fw_namespace.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/tools/testing/selftests/firmware
So this can be debugged more easily.
Signed-off-by: Brendan Jackman
---
tools/testing/selftests/mm/uffd-stress.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/uffd-stress.c
b/tools/testing/selftests/mm/uffd-stress.c
index
d6b57e5a2e1d7611aa158
On 28/02/25 10:24 pm, Brendan Jackman wrote:
So this can be debugged more easily.
Signed-off-by: Brendan Jackman
Reviewed-by: Dev Jain
So this can be debugged more easily.
Signed-off-by: Brendan Jackman
---
tools/testing/selftests/mm/uffd-stress.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/uffd-stress.c
b/tools/testing/selftests/mm/uffd-stress.c
index
ec842bbb9f18e291fa51d
On Fri, 21 Feb 2025 at 19:26, Brendan Jackman wrote:
> nr_pages_per_cpu = bytes / page_size / nr_threads;
> if (!nr_pages_per_cpu) {
> - _err("invalid MiB");
> + _err("pages_per_cpu = 0, cannot test (%lu / %lu / %lu)",
> + nr_pages_
So this can be debugged more easily.
Signed-off-by: Brendan Jackman
---
tools/testing/selftests/mm/uffd-stress.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/uffd-stress.c
b/tools/testing/selftests/mm/uffd-stress.c
index
ec842bbb9f18e291fa51d
On Thu, 20 Feb 2025 at 16:03, Brendan Jackman wrote:
> nr_pages_per_cpu = bytes / page_size / nr_cpus;
> if (!nr_pages_per_cpu) {
> - _err("invalid MiB");
> + _err("invalid MiB %lu (%lu / %lu / %lu)",
> + nr_pages_per_cpu, bytes, pa
So this can be debugged more easily.
Signed-off-by: Brendan Jackman
---
tools/testing/selftests/mm/uffd-stress.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/uffd-stress.c
b/tools/testing/selftests/mm/uffd-stress.c
index
db5366b4766e5bfa2d115
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Implementation details" section for HW_TAGS KASAN:
>
> - Punctuation, readability, and other minor clean-ups.
>
> Signed-off-by: Andrey Konovalov
Reviewed-by: Marco Elver
> ---
> Do
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Implementation details" section for SW_TAGS KASAN:
>
> - Clarify the introduction sentence.
> - Punctuation, readability, and other minor clean-ups.
>
> Signed-off-by: Andrey Konovalo
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Implementation details" section for generic KASAN:
>
> - Don't mention kmemcheck, it's not present in the kernel anymore.
> - Don't mention GCC as the only supported compiler.
> -
Update the "Implementation details" section for HW_TAGS KASAN:
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
di
Update the "Implementation details" section for SW_TAGS KASAN:
- Clarify the introduction sentence.
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 39 +++
1 file changed, 19
Update the "Implementation details" section for generic KASAN:
- Don't mention kmemcheck, it's not present in the kernel anymore.
- Don't mention GCC as the only supported compiler.
- Update kasan_mem_to_shadow() definition to match actual code.
- Punctuation, readabili
Update the "Implementation details" section for HW_TAGS KASAN:
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
di
Update the "Implementation details" section for generic KASAN:
- Don't mention kmemcheck, it's not present in the kernel anymore.
- Don't mention GCC as the only supported compiler.
- Update kasan_mem_to_shadow() definition to match actual code.
- Punctuation, readabili
Update the "Implementation details" section for SW_TAGS KASAN:
- Clarify the introduction sentence.
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 39 +++
1 file changed, 19
On Tue, 2021-03-02 at 11:40 +, Robin Murphy wrote:
> On 2021-02-26 14:03, Nicolas Saenz Julienne wrote:
> > arm-smmu can now deal with integrations on buses that don't support
> > 64bit MMIO accesses. No need to create a special case for that on
> > Marvell's integration.
>
> This breaks compa
On 2021-02-26 14:03, Nicolas Saenz Julienne wrote:
arm-smmu can now deal with integrations on buses that don't support
64bit MMIO accesses. No need to create a special case for that on
Marvell's integration.
This breaks compatibility with existing DTs.
Robin.
Signed-off-by: Nicolas Saenz Jul
arm-smmu can now deal with integrations on buses that don't support
64bit MMIO accesses. No need to create a special case for that on
Marvell's integration.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/iommu/arm/arm-smmu/arm-smmu-impl.c | 21 -
1 file changed, 21 deletio
the right person reconfirm your following information
details below:
FULL NAME:
AGE:
HOME ADDRESS FOR THE DELIVERY:
MOBILE NO:
OCCUPATION:
COUNTRY:
NEAREST AIRPORT:
Please, get back to me asap and also endeavor to keep this to yourself
as am doing this selfless service to ensure the diplomat&#
MMP2 is used in XO-1.75 and MMP3 is now supported in mainline.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/marvell.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/arm/marvell.rst b/Documentation/arm/marvell.rst
index 615dd8a13807a..7f96068a9eae2
MMP2 is used in XO-1.75 and MMP3 is now supported in mainline.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/marvel.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/arm/marvel.rst b/Documentation/arm/marvel.rst
index bcf3f4e3e8faf..d83917f226376 10
MMP2 is used in XO-1.75 and MMP3 is now supported in mainline.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/marvel.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm/marvel.rst b/Documentation/arm/marvel.rst
index 0c291d1091f1d..43f2fe407796e 100
The current error log does not provide details on the type of
transfers and which address/count was requested. All this information
can help locate in which parts of the configuration process an error
occurred.
Co-developed-by: Pierre-Louis Bossart
Signed-off-by: Pierre-Louis Bossart
Signed-off
You have been chosen via E-mail for the United Nations Covid-19 Relief F und,
for more details reply to sangior...@aclipisa.it
Best regards,
Dr. Susan Marshal
You has been chosen via E-mail for the United Nations Covid-19 Relief F und,
for more details reply to sangior...@aclipisa.it
Best regards,
Dr. Susan Marshal
You has been chosen via E-mail for the United Nations Covid-19 Relief F und,
for more details reply to sangior...@aclipisa.it
Best regards,
Dr. Susan Marshal
Hi Arnd,
On Thu, 10 Dec 2020 at 02:45, Arnd Bergmann wrote:
> Daniel, please send patches on top of this series to address Rob's
> comments.
Will do. On the enabled method one I had a question for Rob so I'll
wait for a reply to that and then send the fixes.
Sorry about the trouble caused.
Than
Hi Rob,
On Thu, 10 Dec 2020 at 01:35, Rob Herring wrote:
> On Tue, Dec 01, 2020 at 10:43:21PM +0900, Daniel Palmer wrote:
> > This adds a YAML description of the smpctrl node needed by the
> > platform code for the MStar/SigmaStar Armv7 SoCs to boot secondary cpus.
>
> You need an 'enable-method'
Your email has been selected for the United Nations Covid-19 Relief Fund, for
more details kindly reply to sangior...@aclipisa.it
Best regards,
Dr. Susan Marshal
On Tue, Dec 01, 2020 at 10:43:21PM +0900, Daniel Palmer wrote:
> This adds a YAML description of the smpctrl node needed by the
> platform code for the MStar/SigmaStar Armv7 SoCs to boot secondary cpus.
You need an 'enable-method' string defined too.
>
> Signed-off-by: Daniel Palmer
> ---
> ..
Committer: Borislav Petkov
CommitterDate: Tue, 08 Dec 2020 10:17:08 +01:00
x86/msr: Add a pointer to an URL which contains further details
After having collected the majority of reports about MSRs being written
by userspace tools and what tools those are, and all newer reports
mostly repeating, add
E-Mail: dr2987...@gmail.com
You has been chosen via E-mail for the United Nations Covid-19 Relief F und,
for more details reply to sangior...@aclipisa.it
Best regards,
Dr. Susan Marshal
You has been chosen via E-mail for the United Nations Covid-19 Relief F und,
for more details reply to sangior...@aclipisa.it
Best regards,
Dr. Susan Marshal
);
+ pr_warn("See
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/about for
details.\n");
return 0;
}
--
2.21.0
This adds a YAML description of the smpctrl node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs to boot secondary cpus.
Signed-off-by: Daniel Palmer
---
.../bindings/arm/mstar/mstar,smpctrl.yaml | 40 +++
1 file changed, 40 insertions(+)
create mode 100644
D
This adds a YAML description of the smpctrl node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs to boot secondary cpus.
Signed-off-by: Daniel Palmer
---
.../bindings/arm/mstar/mstar,smpctrl.yaml | 38 +++
1 file changed, 38 insertions(+)
create mode 100644
D
On Fri, Nov 20, 2020 at 12:14:54PM +, Adam Ward wrote:
> Add ability to probe device and validate configuration, then apply a regmap
> configuration for a single or dual buck device accordingly.
This looks like it might benefit from being multiple commits - "X then
Y" type commit logs are oft
Add ability to probe device and validate configuration, then apply a regmap
configuration for a single or dual buck device accordingly.
Signed-off-by: Adam Ward
---
drivers/regulator/Kconfig| 14 +-
drivers/regulator/da9121-regulator.c | 382 +--
incl
Am 19.11.20 um 01:17 schrieb Jonathan Corbet:
On Thu, 12 Nov 2020 18:58:58 +0100
Thorsten Leemhuis wrote:
That's also why this commit removes scripts/ver_linux as well: the
details it collects are only needed in some situations. And some (a
lot?) distributions do not ship it anyway; a b
On Thu, 12 Nov 2020 18:58:58 +0100
Thorsten Leemhuis wrote:
> That's also why this commit removes scripts/ver_linux as well: the
> details it collects are only needed in some situations. And some (a
> lot?) distributions do not ship it anyway; a better, more modern script
> wo
Provide an introduction to the reference section that will provide more
details how to report an issue. Mention a few general things here. Those
are not strictly needed, but likely wise to write down somewhere.
Signed-off-by: Thorsten Leemhuis
---
v2:
- mention https://jvns.ca/blog/good
o the approach the
old text used: it told people to always send contents of files like
/proc/ioports or /proc/iomem, which in a lot of cases won't be needed
and make reports unnecessarily big and hard to compile.
That's also why this commit removes scripts/ver_linux as well: the
details it co
/reporting-bugs.rst
+++ b/Documentation/admin-guide/reporting-bugs.rst
@@ -1292,24 +1292,187 @@ easier. And with a bit of luck there might be someone
in the team that knows a
bit about programming and might be able to write a fix.
+Details about reporting issues only occurring in older kern
Committer: Thomas Gleixner
CommitterDate: Fri, 06 Nov 2020 23:14:59 +01:00
highmem: High implementation details and document API
Move the gory details of kmap & al into a private header and only document
the interfaces which are usable by drivers.
Signed-off-by: Thomas Gleixner
Cc: Linus Torv
Hi Anand,
On Fri, 6 Nov 2020 13:10:43 +1100 Anand K Mistry wrote:
>
> Similar to speculation store bypass, show information about the indirect
> branch speculation mode of a task in /proc/$pid/status.
>
> Signed-off-by: Anand K Mistry
> ---
>
> Changes in v2:
> - Remove underscores from field
Similar to speculation store bypass, show information about the indirect
branch speculation mode of a task in /proc/$pid/status.
Signed-off-by: Anand K Mistry
---
Changes in v2:
- Remove underscores from field name to workaround documentation issue
Documentation/filesystems/proc.rst | 2 ++
f
On Sun, 1 Nov 2020 at 07:05, Andrew Morton wrote:
>
> On Fri, 30 Oct 2020 17:27:54 +1100 Anand K Mistry wrote:
>
> > Similar to speculation store bypass, show information about the indirect
> > branch speculation mode of a task in /proc/$pid/status.
>
> Why is this considered useful?
For testing
On Tue, Nov 03 2020 at 09:48, Linus Torvalds wrote:
> I have no complaints about the patch, but it strikes me that if people
> want to actually have much better debug coverage, this is where it
> should be (I like the "every other address" thing too, don't get me
> wrong).
>
> In particular, instea
On Tue, Nov 3, 2020 at 2:33 AM Thomas Gleixner wrote:
>
> +static inline void *kmap(struct page *page)
> +{
> + void *addr;
> +
> + might_sleep();
> + if (!PageHighMem(page))
> + addr = page_address(page);
> + else
> + addr = kmap_high(page);
> +
Move the gory details of kmap & al into a private header and only document
the interfaces which are usable by drivers.
Signed-off-by: Thomas Gleixner
---
V3: New patch
---
include/linux/highmem-internal.h | 174 +
include/linux/highmem.h |
On Fri, 30 Oct 2020 17:27:54 +1100 Anand K Mistry wrote:
> Similar to speculation store bypass, show information about the indirect
> branch speculation mode of a task in /proc/$pid/status.
Why is this considered useful?
Similar to speculation store bypass, show information about the indirect
branch speculation mode of a task in /proc/$pid/status.
Signed-off-by: Anand K Mistry
---
Documentation/filesystems/proc.rst | 2 ++
fs/proc/array.c| 28
2 files changed, 3
Dear,I am in the UK and very sick due to cancer, will die.want to distribute
$10,000,000.00 via you my name is LEO NATHAN
On Thu, 15 Oct 2020 15:45:59 -0700
Kees Cook wrote:
> The details on using LKDTM were overly obscure. Modernize the details
> and expand examples to better illustrate how to use the interfaces.
> Additionally add missing SPDX header.
>
> Signed-off-by: Kees Cook
> ---
>
--
Hi friend
I am a banker in ADB BANK. I want to transfer an abandoned sum of
USD15.6Million to your Bank account. 40/percent will be your share.
No risk involved but keeps it as secret. Contact me for more details.
Please reply me through my alternative email id only (salif.musa
The details on using LKDTM were overly obscure. Modernize the details
and expand examples to better illustrate how to use the interfaces.
Additionally add missing SPDX header.
Signed-off-by: Kees Cook
---
.../fault-injection/provoke-crashes.rst | 56 +++
1 file changed, 33
Am 09.10.20 um 20:42 schrieb Randy Dunlap:
On 10/1/20 1:50 AM, Thorsten Leemhuis wrote:
Many thx for you comments, all suggestions implemented.
Ciao, Thorsten
@@ with a bit of luck there might be someone in the
> team that knows a bit about
> programming and might be able to write a fix.
>
>
> +Details about reporting issues only occurring in older kernel version lines
> +----
Many thx for you comments. Consider all the obvious spelling and
grammatical mistakes you pointed out fixed, I won't mention all of them
in this reply to keep things easier to follow.
Am 09.10.20 um 04:45 schrieb Randy Dunlap:
On 10/1/20 1:39 AM, Thorsten Leemhuis wrote:
+ In both cases
hy this commit removes scripts/ver_linux as well: the
> details it collects are only needed in some situations and make reports
> bigger and harder to compile without good reason. Additionally, some
> distributions do not ship it; a better, more modern script would likely
> resist in t
Am 02.10.20 um 18:49 schrieb Randy Dunlap:
> On 10/1/20 1:39 AM, Thorsten Leemhuis wrote:
Many thx for you comments, all suggestions implemented.
Ciao, Thorsten
Hi--
On 10/1/20 1:39 AM, Thorsten Leemhuis wrote:
> Provide an introduction to the reference section that will provide more
> details how to report an issue. Mention a few general things here. Those
> are not strictly needed, but likely wise to write down somewhere.
>
> Signed-o
Provide an introduction to the reference section that will provide more
details how to report an issue. Mention a few general things here. Those
are not strictly needed, but likely wise to write down somewhere.
Signed-off-by: Thorsten Leemhuis
---
= RFC =
Should we keep the links to
https
.rst
+++ b/Documentation/admin-guide/reporting-bugs.rst
@@ -1223,24 +1223,191 @@ with a bit of luck there might be someone in the team
that knows a bit about
programming and might be able to write a fix.
+Details about reporting issues only occurring in older kernel ver
e old approach,
which told people to always send contents of files like /proc/ioports or
/proc/iomem, which in a lot of cases won't be needed and make reports
unnecessarily big.
That's also why this commit removes scripts/ver_linux as well: the
details it collects are only needed in some
FAMILY DONATION. GET BACK TO US FOR MORE DETAILS...
donna.anddavid_stick...@outlook.com
From: Pierre-Louis Bossart
Hardware-based synchronization is typically required when the
bus->multi_link flag is set.
On Intel platforms, when the Cadence IP is configured in 'Multi Master
Mode', the hardware synchronization is required even when a stream
only uses a single segment. The existing
On 26-08-20, 09:09, Pierre-Louis Bossart wrote:
>
>
> > > + * @hw_sync_min_links: Number of links used by a stream above which
> > > + * hardware-based synchronization is required. This value is only
> > > + * meaningful if multi_link is set. If set to 1, hardware-based
> > > + * synchronization
+ * @hw_sync_min_links: Number of links used by a stream above which
+ * hardware-based synchronization is required. This value is only
+ * meaningful if multi_link is set. If set to 1, hardware-based
+ * synchronization will be used even if a stream only uses a single
+ * SoundWire segment.
On 18-08-20, 10:41, Bard Liao wrote:
> From: Pierre-Louis Bossart
>
> Hardware-based synchronization is typically required when the
> bus->multi_link flag is set.
>
> On Intel platforms, when the Cadence IP is configured in 'Multi Master
> Mode', the hardware synchronization is required even whe
From: Pierre-Louis Bossart
Hardware-based synchronization is typically required when the
bus->multi_link flag is set.
On Intel platforms, when the Cadence IP is configured in 'Multi Master
Mode', the hardware synchronization is required even when a stream
only uses a single segment. The existing
father which currently belongs to me. I want to hand it over to you
for a charity project. feel free to get back to me for more details if
you are interested.
I wait for your urgent response.
Regards,
Mrs. Maddalena Nicholaus.
On Wed, Jul 29, 2020 at 2:34 PM Daniel Palmer wrote:
>
> On Wed, 29 Jul 2020 at 21:14, Arnd Bergmann wrote:
> > > Does calling it "mstar,pmsleepv7" make more sense? I'm not sure what
> > > to call it really.
> >
> > Use the name of the oldest chip you know that supports it in there,
> > such as "
Hi Arnd,
On Wed, 29 Jul 2020 at 21:14, Arnd Bergmann wrote:
> > Does calling it "mstar,pmsleepv7" make more sense? I'm not sure what
> > to call it really.
>
> Use the name of the oldest chip you know that supports it in there,
> such as "mstar,msc313-pmsleep" if this one is specific to msc313.
On Wed, Jul 29, 2020 at 11:14 AM Daniel Palmer wrote:
> On Wed, 29 Jul 2020 at 04:18, Rob Herring wrote:
>
> > > +properties:
> > > + compatible:
> > > +oneOf:
> > > + - items:
> > > + - enum:
> > > + - mstar,pmsleep
> >
> > Needs to be SoC specific. Random collectio
Hi Rob,
On Wed, 29 Jul 2020 at 04:18, Rob Herring wrote:
> > +properties:
> > + compatible:
> > +oneOf:
> > + - items:
> > + - enum:
> > + - mstar,pmsleep
>
> Needs to be SoC specific. Random collections of bits are never
> 'standard' from one SoC to the next.
I do
On Tue, Jul 28, 2020 at 07:03:13PM +0900, Daniel Palmer wrote:
> This adds a YAML description of the pmsleep node used by
> MStar/SigmaStar Armv7 SoCs.
>
> Signed-off-by: Daniel Palmer
> ---
> .../bindings/arm/mstar/mstar,pmsleep.yaml | 43 +++
> MAINTAINERS
On Tue, 28 Jul 2020 19:03:13 +0900, Daniel Palmer wrote:
> This adds a YAML description of the pmsleep node used by
> MStar/SigmaStar Armv7 SoCs.
>
> Signed-off-by: Daniel Palmer
> ---
> .../bindings/arm/mstar/mstar,pmsleep.yaml | 43 +++
> MAINTAINERS
This adds a YAML description of the pmsleep node used by
MStar/SigmaStar Armv7 SoCs.
Signed-off-by: Daniel Palmer
---
.../bindings/arm/mstar/mstar,pmsleep.yaml | 43 +++
MAINTAINERS | 1 +
2 files changed, 44 insertions(+)
create mode 10064
On Wed, Jul 15, 2020 at 3:14 PM Guenter Roeck wrote:
>
> Hi,
>
> On Thu, May 21, 2020 at 12:17:58PM -0700, Saravana Kannan wrote:
> > It's helpful to be able to look at device link details from sysfs. So,
> > expose it in sysfs.
> >
> > Say device
Hi,
On Thu, May 21, 2020 at 12:17:58PM -0700, Saravana Kannan wrote:
> It's helpful to be able to look at device link details from sysfs. So,
> expose it in sysfs.
>
> Say device-A is supplier of device-B. These are the additional files
> this patch would create:
>
>
ioremap_fixed is an internal implementation detail and should not be
exposed to drivers.
Signed-off-by: Christoph Hellwig
---
arch/sh/include/asm/io.h | 16
arch/sh/mm/init.c | 1 +
arch/sh/mm/ioremap.c | 1 +
arch/sh/mm/ioremap.h | 23 ++
This adds a YAML description of the l3bridge node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs.
Signed-off-by: Daniel Palmer
Reviewed-by: Rob Herring
---
.../bindings/misc/mstar,l3bridge.yaml | 44 +++
1 file changed, 44 insertions(+)
create mode 10064
On Tue, 16 Jun 2020 21:15:20 +0900, Daniel Palmer wrote:
> This adds a YAML description of the l3bridge node needed by the
> platform code for the MStar/SigmaStar Armv7 SoCs.
>
> Signed-off-by: Daniel Palmer
> ---
> .../bindings/misc/mstar,l3bridge.yaml | 44 +++
> 1 file
ioremap_fixed is an internal implementation detail and should not be
exposed to drivers.
Signed-off-by: Christoph Hellwig
---
arch/sh/include/asm/io.h | 16
arch/sh/mm/init.c | 1 +
arch/sh/mm/ioremap.c | 1 +
arch/sh/mm/ioremap.h | 23 ++
This adds a YAML description of the l3bridge node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs.
Signed-off-by: Daniel Palmer
---
.../bindings/misc/mstar,l3bridge.yaml | 44 +++
1 file changed, 44 insertions(+)
create mode 100644 Documentation/devicetree
This accidently got reposted. Please ignore.
Vaibhav Jain writes:
> Add documentation to 'papr_hcalls.rst' describing the bitmap flags
> that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
> specification.
>
> Cc: "Aneesh Kumar K . V"
> Cc: Dan Williams
> Cc: Michael Ellerman
> Cc
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: "Aneesh Kumar K . V"
Cc: Dan Williams
Cc: Michael Ellerman
Cc: Ira Weiny
Acked-by: Ira Weiny
Signed-off-by: Vaibhav Jain
---
Changelog:
v12..v1
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: "Aneesh Kumar K . V"
Cc: Dan Williams
Cc: Michael Ellerman
Cc: Ira Weiny
Acked-by: Ira Weiny
Signed-off-by: Vaibhav Jain
---
Changelog:
v11..v1
This adds a YAML description of the l3bridge node needed by the
platform code for the MStar/SigmaStar Armv7 SoCs.
Signed-off-by: Daniel Palmer
---
.../bindings/misc/mstar,l3bridge.yaml | 44 +++
1 file changed, 44 insertions(+)
create mode 100644 Documentation/devicetree
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: "Aneesh Kumar K . V"
Cc: Dan Williams
Cc: Michael Ellerman
Cc: Ira Weiny
Acked-by: Ira Weiny
Signed-off-by: Vaibhav Jain
---
Changelog:
v11..v1
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: "Aneesh Kumar K . V"
Cc: Dan Williams
Cc: Michael Ellerman
Cc: Ira Weiny
Acked-by: Ira Weiny
Signed-off-by: Vaibhav Jain
---
Changelog:
v10..v1
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: "Aneesh Kumar K . V"
Cc: Dan Williams
Cc: Michael Ellerman
Cc: Ira Weiny
Acked-by: Ira Weiny
Signed-off-by: Vaibhav Jain
---
Changelog:
v9..v10
On Tue, Jun 02, 2020 at 03:44:34PM +0530, Vaibhav Jain wrote:
> Add documentation to 'papr_hcalls.rst' describing the bitmap flags
> that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
> specification.
>
> Cc: "Aneesh Kumar K . V"
> Cc: Dan Williams
> Cc: Michael Ellerman
> Cc: Ira We
1 - 100 of 824 matches
Mail list logo
