All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Anholt <eric@anholt.net>, Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Stefan Wahren <stefan.wahren@i2se.com>,
	bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL] bcm2835-dt-next-fixes-2017-11-15
Date: Mon, 27 Nov 2017 11:29:32 -0800	[thread overview]
Message-ID: <e1641746-1443-9a25-1d1c-b3477cf5de1f@gmail.com> (raw)
In-Reply-To: <20171116203936.23633-1-eric@anholt.net>

On 11/16/2017 12:39 PM, Eric Anholt wrote:
> Hi Florian,
> 
> This is a little fix from Stefan for a warning that popped up when our
> -next and dtc's -next got merged.  Hopefully it can get pulled for
> 4.15 soon.
> 
> The following changes since commit fd3372db18d3d44ae4579243a8eacb5247d8c03a:
> 
>   ARM: dts: bcm2837-rpi-3-b: Add bcm43438 serial slave (2017-10-06 13:07:21 -0700)
> 
> are available in the Git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-dt-next-fixes-2017-11-15
> 
> for you to fetch changes up to 014d6da6cb2525d7f48fb08c705cb130cc7b5f4a:
> 
>   ARM: dts: bcm283x: Fix DTC warnings about missing phy-cells (2017-11-15 10:57:47 -0800)
> 
> ----------------------------------------------------------------
> This pull request brings in a fix for a warning that started occuring
> when dtc from -next got merged.
> 
> ----------------------------------------------------------------

Merged, thanks Eric.
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] bcm2835-dt-next-fixes-2017-11-15
Date: Mon, 27 Nov 2017 11:29:32 -0800	[thread overview]
Message-ID: <e1641746-1443-9a25-1d1c-b3477cf5de1f@gmail.com> (raw)
In-Reply-To: <20171116203936.23633-1-eric@anholt.net>

On 11/16/2017 12:39 PM, Eric Anholt wrote:
> Hi Florian,
> 
> This is a little fix from Stefan for a warning that popped up when our
> -next and dtc's -next got merged.  Hopefully it can get pulled for
> 4.15 soon.
> 
> The following changes since commit fd3372db18d3d44ae4579243a8eacb5247d8c03a:
> 
>   ARM: dts: bcm2837-rpi-3-b: Add bcm43438 serial slave (2017-10-06 13:07:21 -0700)
> 
> are available in the Git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-dt-next-fixes-2017-11-15
> 
> for you to fetch changes up to 014d6da6cb2525d7f48fb08c705cb130cc7b5f4a:
> 
>   ARM: dts: bcm283x: Fix DTC warnings about missing phy-cells (2017-11-15 10:57:47 -0800)
> 
> ----------------------------------------------------------------
> This pull request brings in a fix for a warning that started occuring
> when dtc from -next got merged.
> 
> ----------------------------------------------------------------

Merged, thanks Eric.
-- 
Florian

  reply	other threads:[~2017-11-27 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 20:39 [GIT PULL] bcm2835-dt-next-fixes-2017-11-15 Eric Anholt
2017-11-16 20:39 ` Eric Anholt
2017-11-27 19:29 ` Florian Fainelli [this message]
2017-11-27 19:29   ` Florian Fainelli

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=e1641746-1443-9a25-1d1c-b3477cf5de1f@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=stefan.wahren@i2se.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 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.