linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH soc/next] ARM: bcm2835: add mutual inclusion protection
Date: Mon, 26 Oct 2015 12:07:58 -0700	[thread overview]
Message-ID: <562E7A0E.1090905@gmail.com> (raw)
In-Reply-To: <87vb9t4h9s.fsf@eliezer.anholt.net>

On 26/10/15 11:27, Eric Anholt wrote:
> Alexander Aring <alex.aring@gmail.com> writes:
> 
>> This patch adds mutual inclusion protection for the rpi firmware header.
>>
>> Cc: Eric Anholt <eric@anholt.net>
>> Cc: Stephen Warren <swarren@wwwdotorg.org>
>> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
>> ---
>> This patch is for "soc/next" and depends on Eric Anholt's patch ("ARM: bcm2835:
>> Add the Raspberry Pi firmware driver"), see:
>>
>> http://lists.infradead.org/pipermail/linux-rpi-kernel/2015-October/002434.html
>>
>> I think the patch is already applied but not pushed, so please fixup use this
>> as fixup or simple apply this patch after the patch to add the firmware driver.
> 
> Looks like Florian pulled this in to his pull request and it's in the
> arm-soc tree.

Yes I did apply this, sorry for not mentioning that (I usually do).
-- 
Florian

  reply	other threads:[~2015-10-26 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 18:46 [PATCH soc/next] ARM: bcm2835: add mutual inclusion protection Alexander Aring
2015-10-26 18:27 ` Eric Anholt
2015-10-26 19:07   ` Florian Fainelli [this message]
2015-10-27 17:00 ` Lee Jones
2015-10-27 17:42   ` Alexander Aring
2015-10-28  9:45     ` Lee Jones
2015-10-29  3:59     ` Stephen Warren

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=562E7A0E.1090905@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).