From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Raag Jadav <raagjadav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: dts: am43x-epos-evm: set data pin directions for spi0 and spi1
Date: Thu, 23 Jan 2020 08:12:37 -0800 [thread overview]
Message-ID: <20200123161237.GZ5885@atomide.com> (raw)
In-Reply-To: <1579433339-10663-1-git-send-email-raagjadav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
* Raag Jadav <raagjadav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> [200119 11:30]:
> Set d0 and d1 pin directions for spi0 and spi1 as per their pinmux.
Thanks applying into fixes.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Raag Jadav <raagjadav@gmail.com>
Cc: bcousson@baylibre.com, robh+dt@kernel.org, mark.rutland@arm.com,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: am43x-epos-evm: set data pin directions for spi0 and spi1
Date: Thu, 23 Jan 2020 08:12:37 -0800 [thread overview]
Message-ID: <20200123161237.GZ5885@atomide.com> (raw)
In-Reply-To: <1579433339-10663-1-git-send-email-raagjadav@gmail.com>
* Raag Jadav <raagjadav@gmail.com> [200119 11:30]:
> Set d0 and d1 pin directions for spi0 and spi1 as per their pinmux.
Thanks applying into fixes.
Tony
next prev parent reply other threads:[~2020-01-23 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 11:28 [PATCH] ARM: dts: am43x-epos-evm: set data pin directions for spi0 and spi1 Raag Jadav
[not found] ` <1579433339-10663-1-git-send-email-raagjadav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-01-23 16:12 ` Tony Lindgren [this message]
2020-01-23 16:12 ` Tony Lindgren
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=20200123161237.GZ5885@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=raagjadav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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 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.