From: Greg KH <gregkh@linuxfoundation.org>
To: Insop Song <Insop.Song@gainspeed.com>
Cc: "insop.song@gmail.com" <insop.song@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] Remove warning printk
Date: Fri, 28 Mar 2014 01:46:04 -0700 [thread overview]
Message-ID: <20140328084604.GA29100@kroah.com> (raw)
In-Reply-To: <e575184bc64e46b9b5e229cec5338030@BY2PR07MB011.namprd07.prod.outlook.com>
On Fri, Mar 28, 2014 at 08:05:23AM +0000, Insop Song wrote:
> Hi Greg,
>
> Will send out a new patch mail with single patch shortly.
>
> I have not yet find a good way to reply mail and add patch yet with my mailing server/client.
>
> That's why I send out a separate email instead of replying to Arnd.
>
> Below is his email and it has his signed-off, that's why I put that in my patch you got.
But Arnd wrote the patch, not you. Why are you claiming credit for it?
You also changed the subject. Not good.
I'll just take Arnd's original patch, when my merge window opens back up
again (after 3.15-rc1), and add your signed-off-by to the patch. You
can just reply to Arnd's patch with that line, and I will add it.
Don't strip off ownership of the patch, if you are having email
problems, read Documenation/SubmittingPatches for how to get the
authorship right.
greg k-h
next prev parent reply other threads:[~2014-03-28 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 3:54 [PATCH] staging: gs_fpgaboot: remove __TIMESTAMP__ macro Insop Song
2014-03-28 3:54 ` [PATCH] Remove warning printk Insop Song
2014-03-28 6:49 ` Greg KH
2014-03-28 8:05 ` Insop Song
2014-03-28 8:46 ` Greg KH [this message]
2014-03-28 9:52 ` Insop Song
-- strict thread matches above, loose matches on Subject: below --
2014-03-28 8:09 Insop Song
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=20140328084604.GA29100@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Insop.Song@gainspeed.com \
--cc=arnd@arndb.de \
--cc=insop.song@gmail.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