From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bcusdk: fix endless recursion when opening USB backends
Date: Fri, 25 Aug 2017 22:16:17 +0200 [thread overview]
Message-ID: <20170825221617.36a5d7c1@windsurf> (raw)
In-Reply-To: <20170825193652.GA6442@airbook.vandijck-laurijssen.be>
Hello,
On Fri, 25 Aug 2017 21:36:52 +0200, Kurt Van Dijck wrote:
> > upstream project is using a Git repository, please use Git formatted
> > patches (i.e patches generated by git format-patch -N).
>
> I'm not sure what you mean with 'upstream project' here? Busybox or bcusdk?
bcusdk of course.
> bcusdk isn't in git AFAIK.
https://sourceforge.net/p/bcusdk/code/ci/master/tree/ is a Git
repository.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-25 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:26 [Buildroot] [PATCH] bcusdk: fix endless recursion when opening USB backends Kurt Van Dijck
2017-08-25 14:00 ` Thomas Petazzoni
2017-08-25 19:36 ` Kurt Van Dijck
2017-08-25 20:16 ` Thomas Petazzoni [this message]
2017-08-25 20:47 ` Kurt Van Dijck
2017-08-25 20:58 ` Thomas Petazzoni
2017-08-25 21:33 ` Kurt Van Dijck
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=20170825221617.36a5d7c1@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.