From: dinguyen@opensource.altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SoCFPGA updates for v4.2, part 2, version 2
Date: Wed, 10 Jun 2015 18:00:58 -0500 [thread overview]
Message-ID: <5578C1AA.3000307@opensource.altera.com> (raw)
In-Reply-To: <7hh9qfjhht.fsf@deeprootsystems.com>
On 06/10/2015 06:01 PM, Kevin Hilman wrote:
> dinh.linux at gmail.com writes:
>
>> Hi Arnd, Kevin, Olof,
>>
>> This is an updated pull request for the supend-to-ram patch that has the
>> EDAC code removed in order to avoid a merge conflict.
>>
>> Thanks,
>> Dinh
>>
>> The following changes since commit c65b99f046843d2455aa231747b5a07a999a9f3d:
>>
>> Linux 4.1-rc6 (2015-05-31 19:01:07 -0700)
>
> Why v4.1-rc6?
>
> Are there specific dependencies there? If not, we prefer these pulls to
> be on older -rc tags (typically nothing past where arm-soc/master is).
No dependency, I just saw that arm-soc/for-next was at -rc6. I remember
seeing an email that you should based to an early -rc, or the same -rc
as the for-next branch?
>
> If there are no deps, could you respin this against -rc2/-rc3, or you
> could also rebase on top of your previous socfpga_updates_for_v4.2 as
> well (which itself is based on -rc2.)
>
Yes, I can do that as, I have an additional patch to be included.
Thanks,
Dinh
next prev parent reply other threads:[~2015-06-10 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 19:39 [GIT PULL] SoCFPGA updates for v4.2, part 2, version 2 dinh.linux at gmail.com
2015-06-10 23:01 ` Kevin Hilman
2015-06-10 23:00 ` Dinh Nguyen [this message]
2015-06-11 0:10 ` Kevin Hilman
2015-06-10 23:03 ` Kevin Hilman
2015-06-10 23:01 ` Dinh Nguyen
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=5578C1AA.3000307@opensource.altera.com \
--to=dinguyen@opensource.altera.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 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.