From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] ARM: tegra: Core code changes for v3.19
Date: Mon, 1 Dec 2014 14:19:43 +0100 [thread overview]
Message-ID: <20141201131942.GA11943@ulmo.nvidia.com> (raw)
In-Reply-To: <201411282249.58149.arnd@arndb.de>
On Fri, Nov 28, 2014 at 10:49:57PM +0100, Arnd Bergmann wrote:
> On Friday 21 November 2014, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Hi ARM SoC maintainers,
> >
> > The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
> >
> > Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-3.19-soc
> >
> > for you to fetch changes up to e4a680099a6e97ecdbb81081cff9e4a489a4dc44:
> >
> > ARM: tegra: Re-add removed SoC id macro to tegra_resume() (2014-11-17 11:43:21 +0100)
> >
>
> Hmm, I guess this should have been part of 3.18, but I just sent out
> a pull request for fixes today, and it may have been the last time.
>
> Pulled into next/fixes-non-critical now. I see that there is a stable
> tag on it, which means that it will find its way into 3.18.x, but it's
> really the wrong way to send a patch for the following merge window when
> there is a stable tag on it.
It didn't seem quite critical enough for it to get it into 3.18, but
perhaps it should still have gone that route. I'll try to be more
careful next time around.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141201/f567fedc/attachment.sig>
next prev parent reply other threads:[~2014-12-01 13:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 11:53 [GIT PULL 1/4] ARM: tegra: IOMMU support for v3.19 Thierry Reding
2014-11-21 11:53 ` [GIT PULL 2/4] ARM: tegra: Device tree changes " Thierry Reding
2014-11-26 9:10 ` [GIT PULL v2 " Thierry Reding
2014-11-21 11:53 ` [GIT PULL 3/4] ARM: tegra: Default configuration " Thierry Reding
2014-11-28 21:45 ` Arnd Bergmann
2014-11-21 11:53 ` [GIT PULL 4/4] ARM: tegra: Core code " Thierry Reding
2014-11-28 21:49 ` Arnd Bergmann
2014-12-01 13:19 ` Thierry Reding [this message]
2014-11-26 9:10 ` [GIT PULL v2 1/4] ARM: tegra: IOMMU support " Thierry Reding
2014-11-28 22:20 ` Arnd Bergmann
2014-12-01 15:05 ` Thierry Reding
2014-12-01 17:55 ` Arnd Bergmann
2014-12-02 11:51 ` Thierry Reding
2014-12-04 13:36 ` Arnd Bergmann
2014-12-04 14:43 ` Thierry Reding
2014-12-04 15:03 ` Arnd Bergmann
2014-12-04 15:45 ` [GIT PULL v3 " Thierry Reding
2014-12-04 15:45 ` [GIT PULL v3 2/4] ARM: tegra: Device tree changes " Thierry Reding
2014-12-04 16:24 ` Arnd Bergmann
2014-12-04 16:37 ` Thierry Reding
2014-12-04 16:21 ` [GIT PULL v3 1/4] ARM: tegra: IOMMU support " Arnd Bergmann
2014-12-04 16:36 ` Thierry Reding
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=20141201131942.GA11943@ulmo.nvidia.com \
--to=thierry.reding@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).