From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcus Wolf <marcus.wolf@smarthome-wolf.de>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: staging: pi433: Possible bug in rf69.c
Date: Sat, 11 Nov 2017 11:40:48 +0300 [thread overview]
Message-ID: <20171111084048.j4htvf67jb2cuqpt@mwanda> (raw)
In-Reply-To: <a8d75f3c-b7b1-19eb-4ecb-54b9a003d34c@smarthome-wolf.de>
On Sat, Nov 11, 2017 at 08:55:30AM +0100, Marcus Wolf wrote:
> Shortly befor I fell ill, you proposed me to use Gregs staging for my
> further development. But Colin yesterday was working on a repo, called
> linux-next.
>
> Can you (or anyone else) please tell me, when (or for which kind of
> patches) to use the Gregs staging and wehen (or for which kind of
> patches) to use the linux-next? Sorry for not being familiar with that
> stuff!
>
linux-next is a collection of staging-next and slightly over 100 other
devel trees. You can either using staging-next or linux-next, it's the
same thing basically.
regards,
dan carpenter
next prev parent reply other threads:[~2017-11-11 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 17:23 staging: pi433: Possible bug in rf69.c Marcus Wolf
2017-11-10 19:32 ` Dan Carpenter
2017-11-11 7:55 ` Marcus Wolf
2017-11-11 8:40 ` Dan Carpenter [this message]
2017-11-11 8:45 ` Dan Carpenter
2017-11-11 9:42 ` Marcus Wolf
2017-11-11 11:18 ` Greg Kroah-Hartman
2017-11-11 11:42 ` Marcus Wolf
2017-11-11 11:49 ` Greg Kroah-Hartman
2017-11-11 11:51 ` Marcus Wolf
2017-11-11 12:33 ` Greg Kroah-Hartman
2017-11-11 12:10 ` Dan Carpenter
2017-11-11 16:02 ` Joe Perches
2017-11-11 16:40 ` Marcus Wolf
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=20171111084048.j4htvf67jb2cuqpt@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.wolf@smarthome-wolf.de \
/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).