* [PATCH] riscv: Fix compilation warning
@ 2020-09-15 9:16 Damien Le Moal
2020-09-15 19:44 ` Atish Patra
0 siblings, 1 reply; 8+ messages in thread
From: Damien Le Moal @ 2020-09-15 9:16 UTC (permalink / raw)
To: linux-riscv, Palmer Dabbelt; +Cc: Anup Patel
Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
compilation warning:
arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
[-Wunused-variable]
44 | static struct pt_alloc_ops pt_ops;
| ^~~~~~
with NO MMU builds (e.g. nommu_k210_defconfig).
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
---
arch/riscv/mm/init.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
index 32e7258da9bb..c888c4470b34 100644
--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/init.c
@@ -41,8 +41,6 @@ struct pt_alloc_ops {
#endif
};
-static struct pt_alloc_ops pt_ops;
-
static void __init zone_sizes_init(void)
{
unsigned long max_zone_pfns[MAX_NR_ZONES] = { 0, };
@@ -214,6 +212,8 @@ void __init setup_bootmem(void)
}
#ifdef CONFIG_MMU
+static struct pt_alloc_ops pt_ops;
+
unsigned long va_pa_offset;
EXPORT_SYMBOL(va_pa_offset);
unsigned long pfn_base;
--
2.26.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-15 9:16 [PATCH] riscv: Fix compilation warning Damien Le Moal
@ 2020-09-15 19:44 ` Atish Patra
2020-09-16 1:29 ` Damien Le Moal
0 siblings, 1 reply; 8+ messages in thread
From: Atish Patra @ 2020-09-15 19:44 UTC (permalink / raw)
To: Damien Le Moal; +Cc: linux-riscv, Anup Patel, Palmer Dabbelt
On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
>
> Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
> compilation warning:
>
> arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
> [-Wunused-variable]
> 44 | static struct pt_alloc_ops pt_ops;
> | ^~~~~~
>
> with NO MMU builds (e.g. nommu_k210_defconfig).
>
Thanks for the fix. pt_ops was added as a part of EFI series.
I am planning to send v8 to include some more generic EFI changes.
Do you mind if I just include this fix in my series ?
> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> ---
> arch/riscv/mm/init.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
> index 32e7258da9bb..c888c4470b34 100644
> --- a/arch/riscv/mm/init.c
> +++ b/arch/riscv/mm/init.c
> @@ -41,8 +41,6 @@ struct pt_alloc_ops {
> #endif
> };
>
> -static struct pt_alloc_ops pt_ops;
> -
> static void __init zone_sizes_init(void)
> {
> unsigned long max_zone_pfns[MAX_NR_ZONES] = { 0, };
> @@ -214,6 +212,8 @@ void __init setup_bootmem(void)
> }
>
> #ifdef CONFIG_MMU
> +static struct pt_alloc_ops pt_ops;
> +
> unsigned long va_pa_offset;
> EXPORT_SYMBOL(va_pa_offset);
> unsigned long pfn_base;
> --
> 2.26.2
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
--
Regards,
Atish
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-15 19:44 ` Atish Patra
@ 2020-09-16 1:29 ` Damien Le Moal
2020-09-16 2:02 ` Palmer Dabbelt
2020-09-16 4:52 ` Atish Patra
0 siblings, 2 replies; 8+ messages in thread
From: Damien Le Moal @ 2020-09-16 1:29 UTC (permalink / raw)
To: Atish Patra; +Cc: linux-riscv, Anup Patel, Palmer Dabbelt
On 2020/09/16 4:44, Atish Patra wrote:
> On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
>>
>> Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
>> compilation warning:
>>
>> arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
>> [-Wunused-variable]
>> 44 | static struct pt_alloc_ops pt_ops;
>> | ^~~~~~
>>
>> with NO MMU builds (e.g. nommu_k210_defconfig).
>>
>
> Thanks for the fix. pt_ops was added as a part of EFI series.
> I am planning to send v8 to include some more generic EFI changes.
>
> Do you mind if I just include this fix in my series ?
Please feel free to integrate/squash this change in your series. No need for a
separate patch for just that. But: If your EFI series is not final, what is it
doing on the for-next branch ???
Palmer,
What is going on here ? If Atish V7 series has problems and is not final, why is
it already in for-next ?
>
>> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
>> ---
>> arch/riscv/mm/init.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
>> index 32e7258da9bb..c888c4470b34 100644
>> --- a/arch/riscv/mm/init.c
>> +++ b/arch/riscv/mm/init.c
>> @@ -41,8 +41,6 @@ struct pt_alloc_ops {
>> #endif
>> };
>>
>> -static struct pt_alloc_ops pt_ops;
>> -
>> static void __init zone_sizes_init(void)
>> {
>> unsigned long max_zone_pfns[MAX_NR_ZONES] = { 0, };
>> @@ -214,6 +212,8 @@ void __init setup_bootmem(void)
>> }
>>
>> #ifdef CONFIG_MMU
>> +static struct pt_alloc_ops pt_ops;
>> +
>> unsigned long va_pa_offset;
>> EXPORT_SYMBOL(va_pa_offset);
>> unsigned long pfn_base;
>> --
>> 2.26.2
>>
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
>
>
>
--
Damien Le Moal
Western Digital Research
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-16 1:29 ` Damien Le Moal
@ 2020-09-16 2:02 ` Palmer Dabbelt
2020-09-16 3:10 ` Damien Le Moal
2020-09-16 4:59 ` Atish Patra
2020-09-16 4:52 ` Atish Patra
1 sibling, 2 replies; 8+ messages in thread
From: Palmer Dabbelt @ 2020-09-16 2:02 UTC (permalink / raw)
To: Damien Le Moal; +Cc: linux-riscv, Anup Patel, atishp
>On Tue, 15 Sep 2020 18:29:52 PDT (-0700), Damien Le Moal wrote:
>> On 2020/09/16 4:44, Atish Patra wrote:
>> On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
>>>
>>> Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
>>> compilation warning:
>>>
>>> arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
>>> [-Wunused-variable]
>>> 44 | static struct pt_alloc_ops pt_ops;
>>> | ^~~~~~
>>>
>>> with NO MMU builds (e.g. nommu_k210_defconfig).
>>>
>>
>> Thanks for the fix. pt_ops was added as a part of EFI series.
>> I am planning to send v8 to include some more generic EFI changes.
>>
>> Do you mind if I just include this fix in my series ?
>
> Please feel free to integrate/squash this change in your series. No need for a
> separate patch for just that. But: If your EFI series is not final, what is it
> doing on the for-next branch ???
>
> Palmer,
>
> What is going on here ? If Atish V7 series has problems and is not final, why is
> it already in for-next ?
I'm behind on this thread, I just saw this as I was sitting down to do
something else.
It was supposed to be ready to go, but it had to be rolled back. As far as I
understand it my for-next doesn't actually have broken stuff on it, the issue
is more that some other EFI tree changes landed that would make merging the
trees more difficult. IIRC Ard was going to an EFI tree tag for me to merge,
and I was waiting until that to show up for the rebase so we didn't juggle
things too much. I guess I'd assumed that the actual patches weren't changing
that much in the process, but if Atish is going to be sending another version
with meaningful changes then I suppose it's best to drop the EFI stuff for now.
I just rebased for-next, dropping the EFI patches.
>>> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
>>> ---
>>> arch/riscv/mm/init.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
>>> index 32e7258da9bb..c888c4470b34 100644
>>> --- a/arch/riscv/mm/init.c
>>> +++ b/arch/riscv/mm/init.c
>>> @@ -41,8 +41,6 @@ struct pt_alloc_ops {
>>> #endif
>>> };
>>>
>>> -static struct pt_alloc_ops pt_ops;
>>> -
>>> static void __init zone_sizes_init(void)
>>> {
>>> unsigned long max_zone_pfns[MAX_NR_ZONES] = { 0, };
>>> @@ -214,6 +212,8 @@ void __init setup_bootmem(void)
>>> }
>>>
>>> #ifdef CONFIG_MMU
>>> +static struct pt_alloc_ops pt_ops;
>>> +
>>> unsigned long va_pa_offset;
>>> EXPORT_SYMBOL(va_pa_offset);
>>> unsigned long pfn_base;
>>> --
>>> 2.26.2
>>>
>>>
>>> _______________________________________________
>>> linux-riscv mailing list
>>> linux-riscv@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-riscv
>>
>>
>>
>
>
>--
>Damien Le Moal
>Western Digital Research
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-16 2:02 ` Palmer Dabbelt
@ 2020-09-16 3:10 ` Damien Le Moal
2020-09-16 4:59 ` Atish Patra
1 sibling, 0 replies; 8+ messages in thread
From: Damien Le Moal @ 2020-09-16 3:10 UTC (permalink / raw)
To: Palmer Dabbelt; +Cc: linux-riscv, Anup Patel, atishp
On 2020/09/16 11:02, Palmer Dabbelt wrote:
>> On Tue, 15 Sep 2020 18:29:52 PDT (-0700), Damien Le Moal wrote:
>>> On 2020/09/16 4:44, Atish Patra wrote:
>>> On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
>>>>
>>>> Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
>>>> compilation warning:
>>>>
>>>> arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
>>>> [-Wunused-variable]
>>>> 44 | static struct pt_alloc_ops pt_ops;
>>>> | ^~~~~~
>>>>
>>>> with NO MMU builds (e.g. nommu_k210_defconfig).
>>>>
>>>
>>> Thanks for the fix. pt_ops was added as a part of EFI series.
>>> I am planning to send v8 to include some more generic EFI changes.
>>>
>>> Do you mind if I just include this fix in my series ?
>>
>> Please feel free to integrate/squash this change in your series. No need for a
>> separate patch for just that. But: If your EFI series is not final, what is it
>> doing on the for-next branch ???
>>
>> Palmer,
>>
>> What is going on here ? If Atish V7 series has problems and is not final, why is
>> it already in for-next ?
>
> I'm behind on this thread, I just saw this as I was sitting down to do
> something else.
>
> It was supposed to be ready to go, but it had to be rolled back. As far as I
> understand it my for-next doesn't actually have broken stuff on it, the issue
> is more that some other EFI tree changes landed that would make merging the
> trees more difficult. IIRC Ard was going to an EFI tree tag for me to merge,
> and I was waiting until that to show up for the rebase so we didn't juggle
> things too much. I guess I'd assumed that the actual patches weren't changing
> that much in the process, but if Atish is going to be sending another version
> with meaningful changes then I suppose it's best to drop the EFI stuff for now.
>
> I just rebased for-next, dropping the EFI patches.
OK.
Atish,
Feel free to squash the compile warning patch into yours for v8.
--
Damien Le Moal
Western Digital Research
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-16 1:29 ` Damien Le Moal
2020-09-16 2:02 ` Palmer Dabbelt
@ 2020-09-16 4:52 ` Atish Patra
2020-09-16 4:55 ` Damien Le Moal
1 sibling, 1 reply; 8+ messages in thread
From: Atish Patra @ 2020-09-16 4:52 UTC (permalink / raw)
To: Damien Le Moal; +Cc: linux-riscv, Anup Patel, Palmer Dabbelt
On Tue, Sep 15, 2020 at 6:29 PM Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
>
> On 2020/09/16 4:44, Atish Patra wrote:
> > On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
> >>
> >> Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
> >> compilation warning:
> >>
> >> arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
> >> [-Wunused-variable]
> >> 44 | static struct pt_alloc_ops pt_ops;
> >> | ^~~~~~
> >>
> >> with NO MMU builds (e.g. nommu_k210_defconfig).
> >>
> >
> > Thanks for the fix. pt_ops was added as a part of EFI series.
> > I am planning to send v8 to include some more generic EFI changes.
> >
> > Do you mind if I just include this fix in my series ?
>
> Please feel free to integrate/squash this change in your series. No need for a
> separate patch for just that. But: If your EFI series is not final, what is it
> doing on the for-next branch ???
>
> Palmer,
>
> What is going on here ? If Atish V7 series has problems and is not final, why is
> it already in for-next ?
>
UEFI support is going through a shared tree between UEFI & RISC-V. The
v7 was supposed to be the final version but
there were few patches in generic EFI code last week and Ard suggested
to rebase the RISC-V UEFI series on top of it.
Here is the thread.
https://www.spinics.net/lists/linux-efi/msg20272.html
That's why I am planning to send another series with few other improvements.
> >
> >> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> >> ---
> >> arch/riscv/mm/init.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
> >> index 32e7258da9bb..c888c4470b34 100644
> >> --- a/arch/riscv/mm/init.c
> >> +++ b/arch/riscv/mm/init.c
> >> @@ -41,8 +41,6 @@ struct pt_alloc_ops {
> >> #endif
> >> };
> >>
> >> -static struct pt_alloc_ops pt_ops;
> >> -
> >> static void __init zone_sizes_init(void)
> >> {
> >> unsigned long max_zone_pfns[MAX_NR_ZONES] = { 0, };
> >> @@ -214,6 +212,8 @@ void __init setup_bootmem(void)
> >> }
> >>
> >> #ifdef CONFIG_MMU
> >> +static struct pt_alloc_ops pt_ops;
> >> +
> >> unsigned long va_pa_offset;
> >> EXPORT_SYMBOL(va_pa_offset);
> >> unsigned long pfn_base;
> >> --
> >> 2.26.2
> >>
> >>
> >> _______________________________________________
> >> linux-riscv mailing list
> >> linux-riscv@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-riscv
> >
> >
> >
>
>
> --
> Damien Le Moal
> Western Digital Research
--
Regards,
Atish
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-16 4:52 ` Atish Patra
@ 2020-09-16 4:55 ` Damien Le Moal
0 siblings, 0 replies; 8+ messages in thread
From: Damien Le Moal @ 2020-09-16 4:55 UTC (permalink / raw)
To: atishp; +Cc: linux-riscv, Anup Patel, palmer
On Tue, 2020-09-15 at 21:52 -0700, Atish Patra wrote:
> On Tue, Sep 15, 2020 at 6:29 PM Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
> > On 2020/09/16 4:44, Atish Patra wrote:
> > > On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
> > > > Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
> > > > compilation warning:
> > > >
> > > > arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
> > > > [-Wunused-variable]
> > > > 44 | static struct pt_alloc_ops pt_ops;
> > > > | ^~~~~~
> > > >
> > > > with NO MMU builds (e.g. nommu_k210_defconfig).
> > > >
> > >
> > > Thanks for the fix. pt_ops was added as a part of EFI series.
> > > I am planning to send v8 to include some more generic EFI changes.
> > >
> > > Do you mind if I just include this fix in my series ?
> >
> > Please feel free to integrate/squash this change in your series. No need for a
> > separate patch for just that. But: If your EFI series is not final, what is it
> > doing on the for-next branch ???
> >
> > Palmer,
> >
> > What is going on here ? If Atish V7 series has problems and is not final, why is
> > it already in for-next ?
> >
>
> UEFI support is going through a shared tree between UEFI & RISC-V. The
> v7 was supposed to be the final version but
> there were few patches in generic EFI code last week and Ard suggested
> to rebase the RISC-V UEFI series on top of it.
> Here is the thread.
> https://www.spinics.net/lists/linux-efi/msg20272.html
>
> That's why I am planning to send another series with few other improvements.
OK. Thanks for the clarification.
--
Damien Le Moal
Western Digital Research
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] riscv: Fix compilation warning
2020-09-16 2:02 ` Palmer Dabbelt
2020-09-16 3:10 ` Damien Le Moal
@ 2020-09-16 4:59 ` Atish Patra
1 sibling, 0 replies; 8+ messages in thread
From: Atish Patra @ 2020-09-16 4:59 UTC (permalink / raw)
To: Palmer Dabbelt; +Cc: Damien Le Moal, Anup Patel, linux-riscv
On Tue, Sep 15, 2020 at 7:02 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> >On Tue, 15 Sep 2020 18:29:52 PDT (-0700), Damien Le Moal wrote:
> >> On 2020/09/16 4:44, Atish Patra wrote:
> >> On Tue, Sep 15, 2020 at 2:16 AM Damien Le Moal <damien.lemoal@wdc.com> wrote:
> >>>
> >>> Move the declaration of pt_ops under "#ifdef iCONFIG_MMU" to avoid the
> >>> compilation warning:
> >>>
> >>> arch/riscv/mm/init.c:44:28: warning: ‘pt_ops’ defined but not used
> >>> [-Wunused-variable]
> >>> 44 | static struct pt_alloc_ops pt_ops;
> >>> | ^~~~~~
> >>>
> >>> with NO MMU builds (e.g. nommu_k210_defconfig).
> >>>
> >>
> >> Thanks for the fix. pt_ops was added as a part of EFI series.
> >> I am planning to send v8 to include some more generic EFI changes.
> >>
> >> Do you mind if I just include this fix in my series ?
> >
> > Please feel free to integrate/squash this change in your series. No need for a
> > separate patch for just that. But: If your EFI series is not final, what is it
> > doing on the for-next branch ???
> >
> > Palmer,
> >
> > What is going on here ? If Atish V7 series has problems and is not final, why is
> > it already in for-next ?
>
> I'm behind on this thread, I just saw this as I was sitting down to do
> something else.
>
> It was supposed to be ready to go, but it had to be rolled back. As far as I
> understand it my for-next doesn't actually have broken stuff on it, the issue
> is more that some other EFI tree changes landed that would make merging the
> trees more difficult. IIRC Ard was going to an EFI tree tag for me to merge,
> and I was waiting until that to show up for the rebase so we didn't juggle
> things too much. I guess I'd assumed that the actual patches weren't changing
> that much in the process, but if Atish is going to be sending another version
> with meaningful changes then I suppose it's best to drop the EFI stuff for now.
>
The actual changes are not big but it has to be rebased on top of
Ard's tree and a few small improvements
for RV32 + this patch.
I will send the series tomorrow.
> I just rebased for-next, dropping the EFI patches.
>
Thanks. Apologies for the confusion.
Regards,
Atish
> >>> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> >>> ---
> >>> arch/riscv/mm/init.c | 4 ++--
> >>> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
> >>> index 32e7258da9bb..c888c4470b34 100644
> >>> --- a/arch/riscv/mm/init.c
> >>> +++ b/arch/riscv/mm/init.c
> >>> @@ -41,8 +41,6 @@ struct pt_alloc_ops {
> >>> #endif
> >>> };
> >>>
> >>> -static struct pt_alloc_ops pt_ops;
> >>> -
> >>> static void __init zone_sizes_init(void)
> >>> {
> >>> unsigned long max_zone_pfns[MAX_NR_ZONES] = { 0, };
> >>> @@ -214,6 +212,8 @@ void __init setup_bootmem(void)
> >>> }
> >>>
> >>> #ifdef CONFIG_MMU
> >>> +static struct pt_alloc_ops pt_ops;
> >>> +
> >>> unsigned long va_pa_offset;
> >>> EXPORT_SYMBOL(va_pa_offset);
> >>> unsigned long pfn_base;
> >>> --
> >>> 2.26.2
> >>>
> >>>
> >>> _______________________________________________
> >>> linux-riscv mailing list
> >>> linux-riscv@lists.infradead.org
> >>> http://lists.infradead.org/mailman/listinfo/linux-riscv
> >>
> >>
> >>
> >
> >
> >--
> >Damien Le Moal
> >Western Digital Research
> >
--
Regards,
Atish
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2020-09-16 4:59 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-15 9:16 [PATCH] riscv: Fix compilation warning Damien Le Moal
2020-09-15 19:44 ` Atish Patra
2020-09-16 1:29 ` Damien Le Moal
2020-09-16 2:02 ` Palmer Dabbelt
2020-09-16 3:10 ` Damien Le Moal
2020-09-16 4:59 ` Atish Patra
2020-09-16 4:52 ` Atish Patra
2020-09-16 4:55 ` Damien Le Moal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).