public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Artur Rojek <contact@artur-rojek.eu>,
	Guenter Roeck <linux@roeck-us.net>, Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	<linux-sh@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sh updates for v6.5
Date: Sun, 9 Jul 2023 00:25:45 +0300	[thread overview]
Message-ID: <45f9efa9-9341-e7e4-fbe4-ec7689c714aa@omp.ru> (raw)
In-Reply-To: <5c612d0b293082352df6640ac951918bfa458181.camel@physik.fu-berlin.de>

On 7/6/23 6:23 PM, John Paul Adrian Glaubitz wrote:
[...]

>> Any chance you could do an inventoy on which arch/sh/ platforms are
>> currently working and maintained and which are just bitrot?
>>
>> sh still has a lot of platform specific code that feels іt is rotting,
>> but some of that might just have been due to the lack of active
>> maintainance.
> 
> I am slowly working towards getting everything back into shape. In particular,
> there is a patch set by Yoshinori Sato to convert arch/sh to device tree which
> I would like to eventually get upstreamed.
> 
> However, since I am still new to kernel development, it will certainly take
> me a little more time until we're there. However, there is some interest
> in the community such as the J-Core people and Artur Rojek, so there are people
> who are willing to help me.

   Maybe we could start using the #linux-sh channel (again?) -- it's there, on
Libera.chat, with couple persons hanging around... :-)

[...]

> Adrian

MBR, Sergey

  reply	other threads:[~2023-07-08 21:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 21:43 [GIT PULL] sh updates for v6.5 John Paul Adrian Glaubitz
2023-07-06  4:52 ` pr-tracker-bot
2023-07-06 14:01 ` Guenter Roeck
2023-07-06 14:04   ` John Paul Adrian Glaubitz
2023-07-06 15:08     ` Guenter Roeck
2023-07-06 15:19       ` John Paul Adrian Glaubitz
2023-07-06 15:16 ` Christoph Hellwig
2023-07-06 15:23   ` John Paul Adrian Glaubitz
2023-07-08 21:25     ` Sergey Shtylyov [this message]
2023-07-08 21:49       ` John Paul Adrian Glaubitz
2023-07-08 21:58         ` Artur Rojek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45f9efa9-9341-e7e4-fbe4-ec7689c714aa@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=contact@artur-rojek.eu \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=masahiroy@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ysato@users.sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox