kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: patch against linux-next
Date: Tue, 22 Nov 2016 10:58:12 +0100	[thread overview]
Message-ID: <20161122095812.GA32363@kroah.com> (raw)
In-Reply-To: <CAPTh4Ot8qx6u1FBArPhbT_XLE1-yk4EP+JfwdQui9goraqbh7g@mail.gmail.com>

On Tue, Nov 22, 2016 at 09:31:34AM +0000, Amit Kumar wrote:
> On Tue, Nov 22, 2016, 1:44 PM Greg KH <greg@kroah.com> wrote:
> 
> > On Tue, Nov 22, 2016 at 01:48:22AM +0000, Amit Kumar wrote:
> > > Hi,
> > >
> > > As far as I know that linux-next tree is a preview of patches which will
> > be
> > > merged in the mainline kernel.
> >
> > That is correct.
> >
> > > I've noticed that recently linux-next is updated with a gap.
> >
> > What do you mean by "a gap"?
> >
> Previously I've seen updates everyday except weekend.

Yes, the linux-next maintainer does not do this work every single day,
he needs breaks along with the rest of us :)

> > > Can a patch be created against linux-next tree?
> >
> > Yes, it should be made against that tree as that is the merge of all of
> > the development trees together.
> >
> > For more specifics about linux-next and how the patches flow between
> > that and Linus's releases, please see the great documentation in the
> > Linux kernel source tree at Documentation/development_process/
> >
> I've watched your video regarding patch submission, in which you have
> discussed about "built right". It means if I've knowledge of a device/board
> (without owning it)  then I can write and submit patch if it builds
> correctly.

Yes, that is correct.

thanks,

greg k-h

      reply	other threads:[~2016-11-22  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  1:48 patch against linux-next Amit Kumar
2016-11-22  3:10 ` Ruben Safir
2016-11-22  4:28   ` Amit Kumar
2016-11-22  5:19     ` Ruben Safir
2016-11-22  8:13       ` Greg KH
2016-11-22  8:14 ` Greg KH
2016-11-22  9:31   ` Amit Kumar
2016-11-22  9:58     ` Greg KH [this message]

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=20161122095812.GA32363@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).