From: Artur Rojek <contact@artur-rojek.eu>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
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: Sat, 08 Jul 2023 23:58:30 +0200 [thread overview]
Message-ID: <efaf034aaea3a5f7459b3c9081dc0665@artur-rojek.eu> (raw)
In-Reply-To: <62d9d61e7d085840161c06f08b7aebfd734663fa.camel@physik.fu-berlin.de>
On 2023-07-08 23:49, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On Sun, 2023-07-09 at 00:25 +0300, Sergey Shtylyov wrote:
>> > 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... :-)
>
> Most SuperH/J-Core people meet in #jcore on libera these days.
>
> Adrian
I am not sure if they welcome generic SuperH chat there, but I'm lurking
in both channels already.
Cheers,
Artur
prev parent reply other threads:[~2023-07-08 21:58 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
2023-07-08 21:49 ` John Paul Adrian Glaubitz
2023-07-08 21:58 ` Artur Rojek [this message]
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=efaf034aaea3a5f7459b3c9081dc0665@artur-rojek.eu \
--to=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=s.shtylyov@omp.ru \
--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