LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: <linuxppc-dev@ozlabs.org>
Subject: [PATCH 0/3] Patches for consideration for 2.6.23.
Date: Wed, 04 Jul 2007 14:04:31 +1000	[thread overview]
Message-ID: <1183521871.36329.499255149967.qpush@thor> (raw)

This is set of 3 patches that have been sent through the list as RFCs.  I
believe that I've addressed any feedback that was raised.  Each of the patches
is independant of the other and order is not important.

More feedback is always welcome.

Yours Tony

  linux.conf.au        http://linux.conf.au/ || http://lca2008.linux.org.au/
  Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!

             reply	other threads:[~2007-07-04  4:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  4:04 Tony Breeds [this message]
2007-07-04  4:04 ` [PATCH 3/3] Initial cut to add __read_mostly support for powerpc Tony Breeds
2007-07-04  4:04 ` [PATCH 2/3] Modify sched_clock() to make CONFIG_PRINTK_TIME more sane Tony Breeds
2007-07-04  4:27   ` Michael Ellerman
2007-07-04  4:40     ` Tony Breeds
2007-07-04  4:04 ` [PATCH 1/3] Create a dummy zImage if no valid platform has been selected Tony Breeds

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=1183521871.36329.499255149967.qpush@thor \
    --to=tony@bakeyournoodle.com \
    --cc=linuxppc-dev@ozlabs.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