linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: sched: correct update_sched_clock()
Date: Fri, 8 Feb 2013 13:40:10 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1302081331000.6300@xanadu.home> (raw)
In-Reply-To: <20130208150317.GT17833@n2100.arm.linux.org.uk>

On Fri, 8 Feb 2013, Russell King - ARM Linux wrote:

> On Fri, Feb 08, 2013 at 03:51:25PM +0900, Joonsoo Kim wrote:
> > I try to put it into patch tracker, but I fail to put it.
> > I use following command.
> > 
> > git send-email --to patches at arm.linux.org.uk 0001-ARM-sched-correct~~~~~
> > 
> > Am I wrong?
> > Could you teach me how to put patch into your patch tracker?
> > I already read "help" on your website, but I can't find any stuff for
> > "git send-email".
> 
> I've never used git to send email, so I'm afraid I can't help with that.
> Maybe someone with more experience with sending email from git can
> comment?

The commit text for the patch needs to contain the following 2 lines at 
the very bottom in order to match the patch system's expectations:

PATCH FOLLOWS
KernelVersion: v3.8

The KernelVersion value needs to be adjusted of course.

Note: I never tried it myself but it ought to work.

Nicolas

  reply	other threads:[~2013-02-08 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  5:21 [PATCH RESEND] ARM: sched: correct update_sched_clock() Joonsoo Kim
2013-02-06  9:33 ` Linus Walleij
2013-02-06 15:08   ` JoonSoo Kim
2013-02-06 16:33   ` Russell King - ARM Linux
2013-02-08  6:51     ` Joonsoo Kim
2013-02-08 15:03       ` Russell King - ARM Linux
2013-02-08 18:40         ` Nicolas Pitre [this message]
2013-02-09  4:57           ` JoonSoo Kim

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.02.1302081331000.6300@xanadu.home \
    --to=nicolas.pitre@linaro.org \
    --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).