public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Leonid Segal <leonid.s@variscite.com>
Cc: Andy Gross <andy.gross@linaro.org>,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, will.deacon@arm.com,
	linux-kernel@vger.kernel.org,
	David Brown <david.brown@linaro.org>,
	robh+dt@kernel.org, catalin.marinas@arm.com,
	linux-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH 1/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts
Date: Fri, 25 Aug 2017 13:44:18 +0300	[thread overview]
Message-ID: <20170825104418.fb7thsfukgh3im2k@tarshish> (raw)
In-Reply-To: <CAP6K80Sj9=im4CpXTAL+oR6XLmiBQYPeNMmvpC6v2W0xOP-j4g@mail.gmail.com>

Hi Leonid,

On Wed, Aug 23, 2017 at 08:44:56PM +0300, Leonid Segal wrote:
> Thank you very much for the tips.
> I have updated the documentation and schematics of our web site.
> I also tried to implement all other fixes, but seems that I cannot file the git
> you are talking about.
> The patches i sent were done to:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> and there is no -next branch.
> I tried to check out the linaro git:
> http://git.linaro.org/landing-teams/working/qualcomm/kernel.git
> there is a -next branch, but the USB section is in old format.
> 
> I tried to complile the latest version from
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> the usb there in new format, but nothing works (even LEDS) on Dragonboard too.
> So, I think I am missing something global on the way.
> 
>    If you can help me with it, I will appreciate it.

The linux-next tree is at [1]. Stephen Rothwell generates this tree on a daily 
basis semi-automatically from subsystem maintainers branches that feed the 
-next tree. Read more about it in the linux-next web page[2]. The branch that 
feeds the arm64 changes is for-next/core[3]. See the full list in the 
Next/Trees file in the -next tree.

Hope this helps,
baruch

[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

[2] https://www.kernel.org/doc/man-pages/linux-next.html

[3] git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/core

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2017-08-25 10:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13  9:42 [RESEND PATCH 1/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts Leonid Segal
2017-08-14 22:29 ` Andy Gross
2017-08-18 20:35 ` Andy Gross
2017-08-23 17:44   ` Leonid Segal
2017-08-25 10:44     ` Baruch Siach [this message]
2017-08-27  3:46       ` Andy Gross

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=20170825104418.fb7thsfukgh3im2k@tarshish \
    --to=baruch@tkos.co.il \
    --cc=andy.gross@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=leonid.s@variscite.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.com \
    /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