devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [GIT PULL] A few more device tree changes
Date: Fri, 4 Nov 2011 00:19:43 -0400	[thread overview]
Message-ID: <CACxGe6vOqjmmoV+6pT+HM6f8hK+9UVvF10SijGSS2DKiGSwSAg@mail.gmail.com> (raw)
In-Reply-To: <CACxGe6uAKBrkxQ2puiO+hhcymXTjev3LG=0kzaSeGnsEHdeX6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Linus,

Updated pull req, this time with feeling (and the branch actually pushed out)

g.

The following changes since commit d6748066ad0e8b2514545998f8367ebb3906f299:

  Merge branch 'upstream' of
git://git.linux-mips.org/pub/scm/ralf/upstream-linus (2011-11-03
13:28:14 -0700)

are available in the git repository at:

  git://git.secretlab.ca/git/linux-2.6 devicetree/merge

Grant Likely (1):
      Merge branch 'for-grant' of
git://sources.calxeda.com/kernel/linux into devicetree/merge

Nicolas Ferre (1):
      dt: add empty of_alias_get_id() for non-dt builds

Olof Johansson (1):
      dt/platform: minor cleanup

Rob Herring (1):
      ahci: add DT binding for Calxeda AHCI controller

Stephen Warren (1):
      dt: add empty of_machine_is_compatible

 .../devicetree/bindings/ata/calxeda-sata.txt       |   17 ++++++++++++
 drivers/ata/ahci_platform.c                        |    7 +++++
 drivers/of/platform.c                              |   28 +++++++++++--------
 include/linux/of.h                                 |   10 +++++++
 4 files changed, 50 insertions(+), 12 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/ata/calxeda-sata.txt


On Fri, Nov 4, 2011 at 12:01 AM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> On Thu, Nov 3, 2011 at 11:56 PM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
>> Hi Linus,
>>
>> A few more for 3.2.  Nothing exciting here.
>>
>> g.
>>
>> The following changes since commit d6748066ad0e8b2514545998f8367ebb3906f299:
>>
>>  Merge branch 'upstream' of
>> git://git.linux-mips.org/pub/scm/ralf/upstream-linus (2011-11-03
>> 13:28:14 -0700)
>>
>> are available in the git repository at:
>>
>>  git://git.secretlab.ca/git/linux-2.6 ..BRANCH.NOT.VERIFIED..
>
> Okay, well that was stupid.  I'll push out the branch and send out a
> new pull req.
>
> g.
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      parent reply	other threads:[~2011-11-04  4:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04  3:56 [GIT PULL] A few more device tree changes Grant Likely
     [not found] ` <CACxGe6t-xaH4U9F7uGOabYD-KKSHZNyQ3Ds036FhubScqR=vGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-04  4:01   ` Grant Likely
     [not found]     ` <CACxGe6uAKBrkxQ2puiO+hhcymXTjev3LG=0kzaSeGnsEHdeX6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-04  4:19       ` Grant Likely [this message]

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=CACxGe6vOqjmmoV+6pT+HM6f8hK+9UVvF10SijGSS2DKiGSwSAg@mail.gmail.com \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).