From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: mvme147 status
Date: Mon, 19 Jun 2017 17:17:04 +0200 [thread overview]
Message-ID: <20170619151704.GC18704@physik.fu-berlin.de> (raw)
In-Reply-To: <20170619105227.GA29878@infradead.org>
Hi Christoph!
On Mon, Jun 19, 2017 at 03:52:27AM -0700, Christoph Hellwig wrote:
> > I would be very interested in doing that, probably with some assistance from
> > Geert. I'm interested in getting more involved into kernel development but I
> > have successfully submitted only two patches so far.
>
> Did yo get any chance to look into this project? My offer for help
> still stands, but I'd like to make some progress on this issue.
Sorry, it somehow fell off the table. I'll try to look at it this
weekend if that's still ok.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2017-06-19 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 17:16 mvme147 status Christoph Hellwig
[not found] ` <CACz-3rgtA0pvSZV38ezRWAxDsgcEa_+_teQ3-1dvY4Cf22hfyQ@mail.gmail.com>
2016-09-12 7:43 ` Geert Uytterhoeven
2016-09-12 7:46 ` Christoph Hellwig
2016-09-12 8:00 ` Geert Uytterhoeven
2016-09-13 20:05 ` Stephen N Chivers
2016-09-14 13:04 ` Kars de Jong
2016-09-12 7:46 ` John Paul Adrian Glaubitz
2016-09-12 7:52 ` Christoph Hellwig
2016-09-12 8:00 ` Geert Uytterhoeven
2017-06-19 10:52 ` Christoph Hellwig
2017-06-19 15:17 ` John Paul Adrian Glaubitz [this message]
2017-06-19 15:19 ` Christoph Hellwig
2017-06-29 12:26 ` John Paul Adrian Glaubitz
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=20170619151704.GC18704@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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