public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Updating sunxi tree in linux-next
Date: Fri, 31 Mar 2017 09:57:29 +0200	[thread overview]
Message-ID: <20170331075729.gsfewphm3zd45vwt@lukather> (raw)

Hi Stephen,

We've switched from my personal git tree for the Allwinner sunxi
development to a shared tree:
git://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git

The branch to be included in linux-next will still be called
sunxi/for-next as it used to be, and it will still go through the
arm-soc tree to reach Linux.

However, I'll still have the patches for our DRM drivers on my
personal git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git

Could you add the branch sunxi-drm/for-next to the list of branches
you merge?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170331/bff2dc25/attachment.sig>

             reply	other threads:[~2017-03-31  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31  7:57 Maxime Ripard [this message]
2017-04-02 23:56 ` Updating sunxi tree in linux-next Stephen Rothwell
2017-04-03  1:21   ` Chen-Yu Tsai
2017-04-03 11:45   ` Maxime Ripard
2017-04-03 21:40 ` Stephen Rothwell

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=20170331075729.gsfewphm3zd45vwt@lukather \
    --to=maxime.ripard@free-electrons.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