linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juan Perez-Sanchez <lithoxs@gmail.com>
To: linux-8086 <linux-8086@vger.kernel.org>
Subject: Patch set for ELKS kernel
Date: Sun, 9 Nov 2014 12:18:23 -0600	[thread overview]
Message-ID: <CAD6VGuZj7aJKszJwXi5TTzZZJQkKNkGzuvep_167yFNDjeCYcg@mail.gmail.com> (raw)

Hi,

I will send a set of 5 patches aimed to:

   -Improve readability of kernel code,

   -Fix a potential problem with the preservation of some
    registers after a fork system call.

   -General optimization of code: removing unused functions
    and variables, place in single functions sequences of
    code repeated at several places in the source tree and
    simplifying code.

   -Reduce both code and data size.

   -Reduce amount of assembly code.

No improvement is "bcc specific".

 Patches should be applied in the correct order: starting with
elks-2a.patch and ending with elks-2e.patch

 All Images builded without errors. Every Image was tested
with QEMU emulator.

Greetings,

Juan

                 reply	other threads:[~2014-11-09 18:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAD6VGuZj7aJKszJwXi5TTzZZJQkKNkGzuvep_167yFNDjeCYcg@mail.gmail.com \
    --to=lithoxs@gmail.com \
    --cc=linux-8086@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).