linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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:01:46 -0500	[thread overview]
Message-ID: <5578C1DA.6040105@opensource.altera.com> (raw)
In-Reply-To: <CAMAWPa8wiKu-zha0gUSetnenLNjBt7OGm8NU8RCbMXoDD4qYZg@mail.gmail.com>

On 06/10/2015 06:03 PM, Kevin Hilman wrote:
> On Wed, Jun 10, 2015 at 4:01 PM, Kevin Hilman <khilman@kernel.org> 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).
>>
>> 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.)
> 
> Actually, no need to respin since this is just a single patch.  I've
> picked it from your branch and applied it to socfpga/soc and merged
> into next/soc.  But please keep in mind the above for future pull
> reqs.  Thanks.
> 

Ok, will do.

Thanks,

Dinh

      reply	other threads:[~2015-06-10 23:01 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
2015-06-11  0:10     ` Kevin Hilman
2015-06-10 23:03   ` Kevin Hilman
2015-06-10 23:01     ` Dinh Nguyen [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=5578C1DA.6040105@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 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).