From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>,
"Hyok S. Choi" <hyok.choi@samsung.com>,
linux-kernel mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: MMUless CPU support?
Date: Sun, 16 May 2004 09:18:03 +0100 [thread overview]
Message-ID: <20040516091802.A3280@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040516085858.A15133@infradead.org>; from hch@infradead.org on Sun, May 16, 2004 at 08:58:58AM +0100
On Sun, May 16, 2004 at 08:58:58AM +0100, Christoph Hellwig wrote:
> On Fri, May 14, 2004 at 06:39:22PM +0900, Hyok S. Choi wrote:
> > >And you can use assembler/linker magic to alias sys_fork to
> > >sys_ni_syscall.
> > >
> > >Since Hyok seems to be 100% against any kind of merge, it's useless
> > >even talking about this though.
> > >
> > >
> > Hmm, I think about the clean and well structured kind of merge. His
> > comment was useful for me. :-)
> >
> > I always think almost all of tricky method to cross among codes is NO
> > good, for maintainer, code readers, porting guys and all.
> > I like Vadim's method.
>
> Where does this totally out of context post come from? Given rmk is
> Cc'ed it's probably armnommu and you're probably still arguing that
> you don't want to merge the remaining tiny nommu bitws into arch/arm?
>
> A bit more context would certainly help..
Hyok's mailer has done it _again_. The CC list randomly changed from
linux-arm-kernel to lkml, so what you saw was a reply to one of my
messages on the linux-arm-kernel list, being copied out of context
to lkml.
This is at least the third time that I've known the CC list to randomly
change for no reason when Hyok has been replying, and this is the third
time I'm complaining about it.
Hyok - unless you stop this fscking annoying behaviour, you can expect
people to start ignoring you. If its your mail client doing it, please
change your mail client to something more stable. You're just _really_
pissing people off with what's currently happening with the CC: line
and that's not helping you one bit.
Thanks.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-05-16 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405040617.42342.jeffs@fairwayacademy.org>
[not found] ` <409AC200.7020106@mailcan.com>
[not found] ` <20040507084536.A14179@flint.arm.linux.org.uk>
[not found] ` <409B97E4.8010100@snapgear.com>
[not found] ` <20040507194740.A5778@flint.arm.linux.org.uk>
[not found] ` <409E3752.3050102@snapgear.com>
[not found] ` <20040509152414.C17714@flint.arm.linux.org.uk>
[not found] ` <409EC97D.7030105@samsung.com>
[not found] ` <20040510094435.B27722@flint.arm.linux.org.uk>
[not found] ` <409F62D5.6080500@samsung.com>
[not found] ` <20040510123124.C27722@flint.arm.linux.org.uk>
[not found] ` <409F7341.4090207@samsung.com>
[not found] ` <042601c43905$beed50e0$0100a8c0@SHUTTLE>
[not found] ` <20040513174521.A10776@flint.arm.linux.org.uk>
2004-05-14 9:39 ` MMUless CPU support? Hyok S. Choi
2004-05-16 7:58 ` Christoph Hellwig
2004-05-16 8:18 ` Russell King [this message]
2004-05-17 0:35 ` Hyok S. Choi
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=20040516091802.A3280@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=hch@infradead.org \
--cc=hyok.choi@samsung.com \
--cc=linux-kernel@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