Hi Steve!
On Mon, 2023-02-06 at 10:08 +1100, Stephen Rothwell wrote:
> Hi,
>
> On Fri, 3 Feb 2023 09:30:37 +0100 Christoph Hellwig wrote:
> >
> > On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
> > > Since this is my very first time stepping up as a kernel
On Wed, 2023-02-08 at 21:09 -0600, Rob Landley wrote:
> > Geert has suggested to wait with adding a tree source to the entry until I
> > get my
> > own kernel.org account. I have enough GPG signatures from multiple kernel
> > developers
> > on my GPG key, so I think it shouldn't be too difficult
On 2/8/23 06:13, John Paul Adrian Glaubitz wrote:
> Hi Randy!
>
> On Tue, 2023-02-07 at 17:31 -0800, Randy Dunlap wrote:
>>
>> On 2/7/23 01:06, John Paul Adrian Glaubitz wrote:
>> > Hello Christoph!
>> >
>> > On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
>> > > On Mon, Jan 16,
On 2/3/23 09:57, Randy Dunlap wrote:
> Hi--
>
> On 2/3/23 02:33, Geert Uytterhoeven wrote:
>> Hi Adrian,
>>
>> On Fri, Feb 3, 2023 at 11:29 AM John Paul Adrian Glaubitz
>> wrote:
>>> On Fri, 2023-02-03 at 09:30 +0100, Christoph Hellwig wrote:
On Fri, Feb 03, 2023 at 09:24:46AM +0100, John
> Yes, that's the plan. We're collecting the various patches people have sent
> in for arch/sh, review and test them and apply them.
>
> My test board is running the latest kernel now, so I can test new patches,
> too.
I am just witnessing this development, but I want to say thanks for your
Hi Huacei!
On Wed, 2023-02-08 at 20:24 +0800, Huacai Chen wrote:
> Emm, maybe this patch has its chance to be merged now. :)
>
> https://lore.kernel.org/linux-sh/caahv-h6siotvkzpks4aabejgzcqtwp3tiha0+0hgz1+mu3x...@mail.gmail.com/T/#u
Yes, that's the plan. We're collecting the various patches
Emm, maybe this patch has its chance to be merged now. :)
https://lore.kernel.org/linux-sh/caahv-h6siotvkzpks4aabejgzcqtwp3tiha0+0hgz1+mu3x...@mail.gmail.com/T/#u
Huacai
On Wed, Feb 8, 2023 at 8:14 PM John Paul Adrian Glaubitz
wrote:
>
> Hi Randy!
>
> On Tue, 2023-02-07 at 17:31 -0800, Randy
Hi Randy!
On Tue, 2023-02-07 at 17:31 -0800, Randy Dunlap wrote:
>
> On 2/7/23 01:06, John Paul Adrian Glaubitz wrote:
> > Hello Christoph!
> >
> > On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
> > > On Mon, Jan 16, 2023 at 09:52:10AM +0100, John Paul Adrian Glaubitz wrote:
> > >
On 2/7/23 01:06, John Paul Adrian Glaubitz wrote:
> Hello Christoph!
>
> On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
>> On Mon, Jan 16, 2023 at 09:52:10AM +0100, John Paul Adrian Glaubitz wrote:
>>> We have had a discussion between multiple people invested in the SuperH
>>>
Hello Christoph!
On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
> On Mon, Jan 16, 2023 at 09:52:10AM +0100, John Paul Adrian Glaubitz wrote:
> > We have had a discussion between multiple people invested in the SuperH
> > port and
> > I have decided to volunteer as a co-maintainer of
Hi Stephen!
On Mon, 2023-02-06 at 10:08 +1100, Stephen Rothwell wrote:
> Hi,
>
> On Fri, 3 Feb 2023 09:30:37 +0100 Christoph Hellwig wrote:
> >
> > On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
> > > Since this is my very first time stepping up as a kernel
Hi,
On Fri, 3 Feb 2023 09:30:37 +0100 Christoph Hellwig wrote:
>
> On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
> > Since this is my very first time stepping up as a kernel maintainer, I was
> > hoping
> > to get some pointers on what to do to make this happen.
> >
Hi Randy,
On Fri, Feb 3, 2023 at 4:57 PM Randy Dunlap wrote:
> Is this "sh64" still accurate and applicable? from
> Documentation/kbuild/kbuild.rst:
>
> But some architectures such as x86 and sparc have aliases.
>
> - x86: i386 for 32 bit, x86_64 for 64 bit
> - sh: sh for 32 bit, sh64 for 64
Hi--
On 2/3/23 02:33, Geert Uytterhoeven wrote:
> Hi Adrian,
>
> On Fri, Feb 3, 2023 at 11:29 AM John Paul Adrian Glaubitz
> wrote:
>> On Fri, 2023-02-03 at 09:30 +0100, Christoph Hellwig wrote:
>>> On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
Since this is my
Hi Geert!
On Fri, 2023-02-03 at 11:33 +0100, Geert Uytterhoeven wrote:
> Hi Adrian,
>
> On Fri, Feb 3, 2023 at 11:29 AM John Paul Adrian Glaubitz
> wrote:
> > On Fri, 2023-02-03 at 09:30 +0100, Christoph Hellwig wrote:
> > > On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz
Hi Adrian,
On Fri, Feb 3, 2023 at 11:29 AM John Paul Adrian Glaubitz
wrote:
> On Fri, 2023-02-03 at 09:30 +0100, Christoph Hellwig wrote:
> > On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
> > > Since this is my very first time stepping up as a kernel maintainer, I
>
Hi Christoph!
On Fri, 2023-02-03 at 09:30 +0100, Christoph Hellwig wrote:
> On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote:
> > Since this is my very first time stepping up as a kernel maintainer, I was
> > hoping
> > to get some pointers on what to do to make this
Hello Christoph!
On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
> On Mon, Jan 16, 2023 at 09:52:10AM +0100, John Paul Adrian Glaubitz wrote:
> > We have had a discussion between multiple people invested in the SuperH
> > port and
> > I have decided to volunteer as a co-maintainer of
On 1/18/23 01:46, Geert Uytterhoeven wrote:
> Again, I think you're talking about something different.
> Does kexec work for you?
Sorry, got woken up several hours early by sirens and flashy lights this morning
(duplex on the corner caught fire, Austin has a LOT of emergency vehicles), been
a bit
> Since there are people around with real hardware is sh in big endian mode
> (sheb) real ? Its qemu support is quite limited; most PCI devices don't work
> due to endianness issues. It would be interesting to know if this works better
> with real hardware.
Hi Guenter,
SH big endian works
Hi Rob,
On Wed, Jan 18, 2023 at 5:50 AM Rob Landley wrote:
> On 1/17/23 14:26, Geert Uytterhoeven wrote:
> > On Tue, Jan 17, 2023 at 8:01 PM Rob Landley wrote:
> >> I'm lazy and mostly test each new sh4 build under qemu -M r2d because it's
> >> really convenient: neither of my physical boards
On 1/17/23 14:26, Geert Uytterhoeven wrote:
> Hi Rob,
>
> On Tue, Jan 17, 2023 at 8:01 PM Rob Landley wrote:
>> On 1/16/23 01:13, Christoph Hellwig wrote:
>> > On Fri, Jan 13, 2023 at 09:09:52AM +0100, John Paul Adrian Glaubitz wrote:
>> >> I'm still maintaining and using this port in Debian.
On 1/17/23 12:26, Geert Uytterhoeven wrote:
Hi Rob,
On Tue, Jan 17, 2023 at 8:01 PM Rob Landley wrote:
On 1/16/23 01:13, Christoph Hellwig wrote:
On Fri, Jan 13, 2023 at 09:09:52AM +0100, John Paul Adrian Glaubitz wrote:
I'm still maintaining and using this port in Debian.
It's a bit
Hi Rob,
On Tue, Jan 17, 2023 at 8:01 PM Rob Landley wrote:
> On 1/16/23 01:13, Christoph Hellwig wrote:
> > On Fri, Jan 13, 2023 at 09:09:52AM +0100, John Paul Adrian Glaubitz wrote:
> >> I'm still maintaining and using this port in Debian.
> >>
> >> It's a bit disappointing that people keep
On 1/16/23 01:13, Christoph Hellwig wrote:
> On Fri, Jan 13, 2023 at 09:09:52AM +0100, John Paul Adrian Glaubitz wrote:
>> I'm still maintaining and using this port in Debian.
>>
>> It's a bit disappointing that people keep hammering on it. It works fine for
>> me.
>
> What platforms do you (or
Hello Christoph!
On 1/16/23 08:13, Christoph Hellwig wrote:
On Fri, Jan 13, 2023 at 09:09:52AM +0100, John Paul Adrian Glaubitz wrote:
I'm still maintaining and using this port in Debian.
It's a bit disappointing that people keep hammering on it. It works fine for me.
What platforms do you
On 1/13/23 13:05, John Paul Adrian Glaubitz wrote:
> Hi Rob!
>
> On 1/13/23 20:11, Rob Landley wrote:
>> There is definitely interest in this architecture. I'm aware Rich hasn't been
>> the most responsive maintainer. (I'm told he's on vacation with his family at
>> the moment, according to the
On 1/13/23 02:52, John Paul Adrian Glaubitz wrote:
> Hi Geert!
>
> On 1/13/23 09:26, Geert Uytterhoeven wrote:
>> Indeed. The main issue is not the lack of people sending patches and
>> fixes, but those patches never being applied by the maintainers.
>> Perhaps someone is willing to stand up to
Hi Rob!
On 1/13/23 20:11, Rob Landley wrote:
I actually would be willing to do it but I'm a bit hesitant as I'm not 100%
sure my skills are sufficient. Maybe if someone can assist me?
My skills aren't sufficient and I dunno how much time I have, but I can
certainly assist. I test sh4
On Fri, Jan 13, 2023 at 07:23:17AM +0100, Christoph Hellwig wrote:
> Hi all,
>
> arch/sh has been a long drag because it supports a lot of SOCs, and most
> of them haven't even been converted to device tree infrastructure. These
> SOCs are generally obsolete as well, and all of the support has
Hi Geert!
On 1/13/23 09:26, Geert Uytterhoeven wrote:
Indeed. The main issue is not the lack of people sending patches and
fixes, but those patches never being applied by the maintainers.
Perhaps someone is willing to stand up to take over maintainership?
I actually would be willing to do it
On Fri, Jan 13, 2023 at 9:10 AM John Paul Adrian Glaubitz
wrote:
> On 1/13/23 07:23, Christoph Hellwig wrote:
> > arch/sh has been a long drag because it supports a lot of SOCs, and most
> > of them haven't even been converted to device tree infrastructure. These
> > SOCs are generally obsolete
Hello!
On 1/13/23 07:23, Christoph Hellwig wrote:
arch/sh has been a long drag because it supports a lot of SOCs, and most
of them haven't even been converted to device tree infrastructure. These
SOCs are generally obsolete as well, and all of the support has been barely
maintained for almost
33 matches
Mail list logo
