linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Patches for 2.6.33-rc1
Date: Wed, 09 Dec 2009 12:20:44 +0200	[thread overview]
Message-ID: <1260354044.19669.1267.camel@localhost> (raw)
In-Reply-To: <1260353349.13499.4.camel@pc1117.cambridge.arm.com>

On Wed, 2009-12-09 at 10:09 +0000, Catalin Marinas wrote:
> Hi Russell,
> 
> There are some patches which were not pulled yet and it would be nice if
> they get in during this merging window. Two of them are bug-fixes and
> the other is the earlyprintk support which many people find useful.
> 
> My for-rmk branch was rebased to 2.6.32 to check what was already merged
> but I can rebase it something earlier if you want.
> 
> Thanks.
> 
> 
> The following changes since commit 22763c5cf3690a681551162c15d34d935308c8d7:
>   Linus Torvalds (1):
>         Linux 2.6.32
> 
> are available in the git repository at:
> 
>   git://linux-arm.org/linux-2.6.git for-rmk
> 
> Catalin Marinas (2):
>       Add an earlyprintk debug console
>       RealView: Fix typo in the Kconfig enabling SPARSEMEM for RealView/PBX
> 
> Varun Swara (1):
>       Do not allow the probing of the local timer

It is so much helpful when people add proper prefixes to patches, like
ARM or something. I wander, do we have a requirement for this somewhere?
But please, consider doing this, this makes it easier surfing git-log or
gitk info.

-- 
Best Regards,
Artem Bityutskiy (????? ????????)

  reply	other threads:[~2009-12-09 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 10:09 [GIT PULL] Patches for 2.6.33-rc1 Catalin Marinas
2009-12-09 10:20 ` Artem Bityutskiy [this message]
2009-12-09 10:39   ` Catalin Marinas
2009-12-09 11:04     ` Artem Bityutskiy
2009-12-09 11:23       ` Artem Bityutskiy
2009-12-09 12:43       ` Catalin Marinas
2009-12-09 12:49     ` Mark Brown
2009-12-09 13:21       ` Catalin Marinas

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=1260354044.19669.1267.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).