From: Gerd Hoffmann <kraxel@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-fbdev@vger.kernel.org, gregkh@linuxfoundation.org,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
tomi.valkeinen@ti.com,
"open list:Hyper-V CORE AND..." <devel@linuxdriverproject.org>,
haiyangz@microsoft.com
Subject: Re: [PATCH v2 2/5] vmbus: add missing breaks
Date: Mon, 24 Feb 2014 10:55:43 +0000 [thread overview]
Message-ID: <1393239343.28750.3.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <20140224104207.GG26722@mwanda>
On Mo, 2014-02-24 at 13:42 +0300, Dan Carpenter wrote:
> I'm sorry, I know it sucks to not get credit for fixes, but please just
> fold this into [patch 1/5]. We really should have a tag for this kind
> of thing.
It's not because of the credits, but because Greg picked up #1 into one
of his branches already (cover letter explains this). I'll happily
submit a v3 with 1+2 squashed together if that doesn't ruin the patch
workflow. Greg?
cheers,
Gerd
next prev parent reply other threads:[~2014-02-24 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 10:25 [PATCH v2 0/5] hyperv-fb: add support for generation 2 virtual machines Gerd Hoffmann
2014-02-24 10:25 ` [PATCH v2 1/5] Drivers: hv: vmbus: Extract the mmio information from DSDT Gerd Hoffmann
2014-02-24 10:36 ` Dan Carpenter
2014-02-24 10:25 ` [PATCH v2 2/5] vmbus: add missing breaks Gerd Hoffmann
2014-02-24 10:42 ` Dan Carpenter
2014-02-24 10:55 ` Gerd Hoffmann [this message]
2014-02-24 11:07 ` Dan Carpenter
2014-02-24 10:25 ` [PATCH v2 3/5] vmbus: use resource for hyperv mmio region Gerd Hoffmann
2014-02-24 10:25 ` [PATCH v2 4/5] hyperv-fb: add support for generation 2 virtual machines Gerd Hoffmann
2014-02-24 10:25 ` [PATCH v2 5/5] hyperv-fb: kick off efifb early Gerd Hoffmann
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=1393239343.28750.3.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).