kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Contribute
Date: Sat, 22 Jul 2017 15:13:17 +0200	[thread overview]
Message-ID: <20170722131317.GA16446@kroah.com> (raw)
In-Reply-To: <9948e517-6eda-9f7b-6309-d40366fff9fa@gmail.com>

On Sat, Jul 22, 2017 at 12:21:15PM +0200, nunojsa wrote:
> On 22.07.2017 11:56, Greg KH wrote:
> > On Sat, Jul 22, 2017 at 11:39:45AM +0200, nunojsa wrote:
> >> Hi all,
> >>
> >> Im fairly new to linux kernel and would like to start with some staging work (seems like the best way to start).
> >> Basically what i would like to know is which tree should i clone for this? My understanding is that one should never work directly on top of the mainline tree, instead (for this case) on top of the linux staging tree. The same goes, for example, for USB subsystem development in which case i should just clone the usb development tree (and the same for all subsystems).
> >>
> >> Is my understanding correct?
> > 
> > Yes it is, make sure you work off of the correct branch as well.  For> the staging tree, working off of the staging-next is best.
> 
> This would be my next question. Regarding the linux-next tree, the
> same as i wrote before also applies? So, I should not work directly in
> the linux-next tree but instead in the correspondent branch
> (subsystem-next) of the specific subsystem I'm working on? 

You can use linux-next just fine, as it includes the staging-next
branch, along with all other subsystem's development trees.

Just be careful, linux-next rebases every day, you might have a harder
time doing development on it if you don't really know what you are doing
with git.

hope this helps,

greg k-h

  reply	other threads:[~2017-07-22 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22  9:39 Contribute nunojsa
2017-07-22  9:56 ` Contribute Greg KH
2017-07-22 10:21   ` Contribute nunojsa
2017-07-22 13:13     ` Greg KH [this message]
2017-07-24  0:22 ` Contribute Tobin C. Harding

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=20170722131317.GA16446@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).