From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: yuasa@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: What's happening with vr41xx_giu.c?
Date: Fri, 10 Jul 2009 08:43:49 +0900 [thread overview]
Message-ID: <4A5680B5.2090405@necel.com> (raw)
Does anyone have a similar symptom?
---
skuribay@ubuntu:linux.git$ git checkout -f master
Already on 'master'
skuribay@ubuntu:linux.git$
skuribay@ubuntu:linux.git$ git log HEAD^..
commit 4eebdebd71325d0814b1c8e093fd0d1f191da9aa
Author: Kurt Martin <kurt@mips.com>
Date: Wed Jul 8 19:22:35 2009 -0700
MIPS: SMTC: Move cross VPE writes to after a TC is assigned to VPE.
Signed-off-by: Chris Dearman <chris@mips.com>
Signed-off-by: Raghu Gandham <raghu@mips.com>
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
skuribay@ubuntu:linux.git$
skuribay@ubuntu:linux.git$ git status
# On branch master
nothing to commit (working directory clean)
skuribay@ubuntu:linux.git$
skuribay@ubuntu:linux.git$
skuribay@ubuntu:linux.git$ make distclean
skuribay@ubuntu:linux.git$
skuribay@ubuntu:linux.git$
skuribay@ubuntu:linux.git$ git status
# On branch master
# Changed but not updated:
# (use "git add/rm <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# deleted: drivers/char/vr41xx_giu.c
#
no changes added to commit (use "git add" and/or "git commit -a")
skuribay@ubuntu:linux.git$
--
Shinya Kuribayashi
NEC Electronics
next reply other threads:[~2009-07-09 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 23:43 Shinya Kuribayashi [this message]
2009-07-10 0:46 ` What's happening with vr41xx_giu.c? Wu Zhangjin
2009-07-10 3:07 ` Chris Dearman
2009-07-10 10:47 ` Ralf Baechle
2009-07-10 16:20 ` Junio C Hamano
2009-07-11 3:14 ` Junio C Hamano
2009-07-11 3:20 ` [PATCH 1/2] tm_to_time_t(): allow times in year 1969 Junio C Hamano
2009-07-11 3:20 ` [PATCH 2/2] apply: notice creation/removal patches produced by GNU diff Junio C Hamano
2009-07-11 3:32 ` Linus Torvalds
2009-07-11 3:57 ` Junio C Hamano
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=4A5680B5.2090405@necel.com \
--to=shinya.kuribayashi@necel.com \
--cc=linux-mips@linux-mips.org \
--cc=yuasa@linux-mips.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.