From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cl@linux.com, penberg@kernel.org,
rdunlap@infradead.org, rientjes@google.com
Subject: Re: + mm-slab_common-commonize-slab-merge-logic.patch added to -mm tree
Date: Mon, 22 Sep 2014 17:22:03 +0900 [thread overview]
Message-ID: <20140922082203.GA11825@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20140922004841.7f1e9c60.akpm@linux-foundation.org>
On Mon, Sep 22, 2014 at 12:48:41AM -0700, Andrew Morton wrote:
> On Mon, 22 Sep 2014 09:32:45 +0900 Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
>
> > Hello, Andrew.
> >
> > This patch has build failure problem if CONFIG_SLUB.
> > Detailed information and fix is in following patch.
> >
>
> Pleeeeeze be careful with the email headers? I happened to see this
> email on lkml, wasn't cc'ed.
Opps... Sorry.
Do you want to resend?
>
> I assume there's something in the mm-commits headers which is causing
> this to happen, but I don't know what. I expect a busted email client
> is involved.
>
> This:
>
> From: akpm@linux-foundation.org
> To: iamjoonsoo.kim@lge.com, cl@linux.com, penberg@kernel.org, rdunlap@infradead.org, rientjes@google.com, mm-commits@vger.kernel.org
> Reply-To: linux-kernel@vger.kernel.org
> Subject: + mm-slab_common-commonize-slab-merge-logic.patch added to -mm tree
I think that it is caused by 'Reply-To' header. There is some
explanation about it on
https://www.gnu.org/software/emacs/manual/html_node/emacs/Mail-Headers.html
‘Reply-to’
An address to which replies should be sent, instead of ‘From’. This is
used if, for some reason, your ‘From’ address cannot receive replies.
In this case, your address in 'From' doesn't disappears in my Reply-All.
Thanks.
prev parent reply other threads:[~2014-09-22 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541cb039.GkGFlIDKO1+jpDW0%akpm@linux-foundation.org>
2014-09-22 0:32 ` Joonsoo Kim
2014-09-22 7:48 ` Andrew Morton
2014-09-22 8:22 ` Joonsoo Kim [this message]
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=20140922082203.GA11825@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
/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
all inboxes | Powered by JetHome®