All of lore.kernel.org
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Are Small Changes in kernel accepted as patches
Date: Sat, 21 Jun 2014 06:27:34 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406210627030.3230@localhost> (raw)
In-Reply-To: <CAL3LdT79CvBphkoV_CHpu9tacT0+VQ4SBd0oY-S8EUG4eenZew@mail.gmail.com>

On Sat, 21 Jun 2014, Jeff Kirsher wrote:

> On Sat, Jun 21, 2014 at 2:37 AM, karthik <karthik.188@gmail.com> wrote:
> > Hey There,
> > I was just going through the linux-next source and found a small change
> > in one of the files. (Unnecessary else)
> > Now should I make this a patch and submit it or is it too small to submit?
> > Regards
> > Karthik Nayak
>
> Any patch can never be "to small", in fact small changes/patches are
> preferred over large changes/patches.

  there is a special email address for innocuous patches --
"trivial at kernel.org".

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2014-06-21 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21  9:37 Are Small Changes in kernel accepted as patches karthik
2014-06-21 10:04 ` Jeff Kirsher
2014-06-21 10:27   ` Robert P. J. Day [this message]
2014-06-21 14:23 ` Valdis.Kletnieks at vt.edu
2014-06-21 14:42   ` karthik

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=alpine.LFD.2.11.1406210627030.3230@localhost \
    --to=rpjday@crashcourse.ca \
    --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 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.