linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: narmstrong@baylibre.com (Neil Armstrong)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OXNAS SoC update for 4.12
Date: Thu, 30 Mar 2017 17:04:25 +0200	[thread overview]
Message-ID: <1f3fc8db-d87b-57e9-3eee-a21c969c6b54@baylibre.com> (raw)
In-Reply-To: <CAK8P3a0uexaSYw_Wnim3-00=Zn8Bn85nfpTrKzgRoBY+NUhr+w@mail.gmail.com>

On 03/30/2017 05:03 PM, Arnd Bergmann wrote:
> On Thu, Mar 30, 2017 at 4:40 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Monday, March 20, 2017 10:39:56 AM CEST Neil Armstrong wrote:
>>> Dear arm-soc maintainers,
>>>
>>> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>>>
>>>   Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>>>
>>> are available in the git repository at:
>>>
>>>   https://github.com/OXNAS/linux.git tags/oxnas-arm-soc-for-4.12
>>>
>>> for you to fetch changes up to b44327d198b4f1bbebaf83f714cde450471de644:
>>>
>>>   ARM: oxnas: remove redundant select CPU_V6K (2017-03-20 10:13:45 +0100)
>>>
>>> ----------------------------------------------------------------
>>> - Fix OX820 Kconfig
>>>
>>
>> I've merged this into next/fixes-non-critical. Thanks,
> 
> BTW, it took 20 minutes to pull this branch from github.com, possibly they
> had moved this to cold storage. Are you able to migrate your git tree to
> kernel.org or host it yourself on baylibre.com in the future?
> 
> It's not urgent, but the delay was rather annoying and I had already
> given up and applied the patch manually when the pull finally succeeded.
> 
>        Arnd
> 

Hi Arnd,

Sorry for the inconvenience, I'll request an account on kernel.org to avoid further
issues.

Thanks,
Neil

      reply	other threads:[~2017-03-30 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20  9:39 [GIT PULL] ARM: OXNAS SoC update for 4.12 Neil Armstrong
2017-03-30 14:40 ` Arnd Bergmann
2017-03-30 15:03   ` Arnd Bergmann
2017-03-30 15:04     ` Neil Armstrong [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=1f3fc8db-d87b-57e9-3eee-a21c969c6b54@baylibre.com \
    --to=narmstrong@baylibre.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).