From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: bcm2835: add missing mbox overscan response field
Date: Thu, 07 Nov 2013 14:30:54 -0700 [thread overview]
Message-ID: <527C068E.5010604@wwwdotorg.org> (raw)
In-Reply-To: <20131107142912.2ddbedab@lilith>
On 11/07/2013 06:29 AM, Albert ARIBAUD wrote:
> Hi Andre,
>
> On Wed, 23 Oct 2013 21:46:31 +0200, Andre Heider <a.heider@gmail.com>
> wrote:
>
>> On Wed, Oct 23, 2013 at 05:54:13PM +0100, Stephen Warren wrote:
>>> On 10/22/2013 09:27 PM, Andre Heider wrote:
>>>> Add the missing "right" field to struct bcm2835_mbox_tag_overscan.
>>>
>>> This one patch,
>>> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
>>>
>>> You need to send/cc this patch to Albert Aribauld, since he applies ARM
>>> patches. Or, perhaps just make sure the patch gets assigned to him in
>>> patchwork?
>>
>> Okay, I did the patchwork dance :)
>>
>> Thanks,
>> Andre
>
> In fact, the series could be applied as a whole by the same custodian
> -- and actually, I'd prefer it to be applied as a whole, since patch 1/2
> alone looks like dead/useless code, whereas it makes sense if applied
> along with 2/2.
So, there are 2 patches and 2 custodians. One of you has to ack the
patch for the other to merge them both through the other's subsystem,
right? I guess you want Anatolij to take both of these through the video
tree based on your comments. If so, can you ack this patch and re-assign
them both in patchwork, so he knows that?
next prev parent reply other threads:[~2013-11-07 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 20:27 [U-Boot] [PATCH 1/2] ARM: bcm2835: add missing mbox overscan response field Andre Heider
2013-10-23 16:54 ` Stephen Warren
2013-10-23 19:46 ` Andre Heider
2013-11-07 13:29 ` Albert ARIBAUD
2013-11-07 21:30 ` Stephen Warren [this message]
2013-11-08 12:16 ` Albert ARIBAUD
2013-11-08 12:13 ` Albert ARIBAUD
2013-11-09 10:11 ` Anatolij Gustschin
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=527C068E.5010604@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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.