From: "Romer, Benjamin M" <Benjamin.Romer@unisys.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"Arfvidson, Erik" <Erik.Arfvidson@unisys.com>,
*S-Par-Maintainer <SParMaintainer@unisys.com>
Subject: Re: [PATCH 2/2] staging: unisys: added virtpci info entry
Date: Fri, 11 Jul 2014 08:00:57 -0500 [thread overview]
Message-ID: <C97001BC43954D438ACB059713BA5CDFA481E1B349@USEA-EXCH7.na.uis.unisys.com> (raw)
In-Reply-To: <20140710145140.GA18412@kroah.com>
On Thu, 2014-07-10 at 07:51 -0700, Greg KH wrote:
> On Thu, Jul 10, 2014 at 10:34:14AM -0400, Erik Arfvidson wrote:
> > This patch adds the virtpci debugfs directory and the info entry
> > inside of it.
> >
> > Signed-off-by: Erik Arfvidson <erik.arfvidson@unisys.com>
> > Signed-off-by: Benjamin Romer <benjamin.romer@unisys.com>
>
> 2/2? Where is patch 1/2?
>
> Please resend this correctly, and properly version your patches (this is
> what, version 10 or something?).
>
> Your subsystem maintainer has a short-term memory of a gnat, you need to
> be explicit otherwise I'll ignore it...
>
> greg k-h
I mistakenly clicked reply instead of reply all the first time. :(
Anyhow, I'm really sorry Greg, this patch was the second of a two part
set and you'd already taken the first one, so I thought we should only
resend the corrected patch and I told Erik to do that, so it's my fault.
Should we send you this as a [1/1 version 4] or resend the entire set
despite one patch already being in?
--
Ben Romer | Software Engineer |
Virtual Systems Development
Unisys Corporation | 2476
Swedesford Rd | Malvern, PA 19355
| 610-648-7140
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2014-07-11 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 14:34 [PATCH 2/2] staging: unisys: added virtpci info entry Erik Arfvidson
2014-07-10 14:51 ` Greg KH
2014-07-11 13:00 ` Romer, Benjamin M [this message]
2014-07-11 13:29 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2014-07-09 20:22 Erik Arfvidson
2014-07-09 20:40 ` Greg KH
2014-07-09 20:41 ` Greg KH
2014-07-08 17:21 [PATCH 1/2] staging: unisys: remove all proc entries from virtpci Erik Arfvidson
2014-07-08 17:21 ` [PATCH 2/2] staging: unisys: added virtpci info entry Erik Arfvidson
2014-07-08 17:34 ` Greg KH
2014-07-08 17:52 ` Dan Carpenter
2014-07-08 19:22 ` Erik Arfvidson
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=C97001BC43954D438ACB059713BA5CDFA481E1B349@USEA-EXCH7.na.uis.unisys.com \
--to=benjamin.romer@unisys.com \
--cc=Erik.Arfvidson@unisys.com \
--cc=SParMaintainer@unisys.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.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.