From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 2/2] sparc: Implement and wire up vio_hotplug for vio.
Date: Sun, 01 May 2016 23:13:19 +0000 [thread overview]
Message-ID: <57268D8F.3000903@physik.fu-berlin.de> (raw)
In-Reply-To: <1460657682-12209-3-git-send-email-glaubitz@physik.fu-berlin.de>
Hi!
On 04/28/2016 11:13 AM, John Paul Adrian Glaubitz wrote:
> On Wed, Apr 27, 2016 at 10:00:32PM -0400, David Miller wrote:
>> My tree may never be rebased, as people clone and do work against it,
>> therefore any commit made there is permanent.
>>
>> Please just be careful with patches you submit in the future, thanks.
>
> Well, my patches are
>
> Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
>
> so, I think did everything correctly on my side. I don't exactly know
> my name was cut off, but I guess it's too late now -.-.
I was just wondering: Would it be possible to ask Linus to fix my name
when he pulls in the changes from the sparc tree? From what I can see,
the current changes are not in Linus' tree yet, so there might be a
chance to fix the problem.
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:[~2016-05-01 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 18:14 [PATCH 2/2] sparc: Implement and wire up vio_hotplug for vio John Paul Adrian Glaubitz
2016-04-17 19:29 ` Sam Ravnborg
2016-04-27 20:39 ` David Miller
2016-04-27 21:05 ` John Paul Adrian Glaubitz
2016-04-28 2:00 ` David Miller
2016-04-28 2:07 ` Julian Calaby
2016-04-28 2:10 ` David Miller
2016-04-28 2:30 ` Julian Calaby
2016-04-28 9:13 ` John Paul Adrian Glaubitz
2016-05-01 23:13 ` John Paul Adrian Glaubitz [this message]
2016-05-02 0:43 ` David Miller
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=57268D8F.3000903@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.