From: Greg KH <gregkh@linuxfoundation.org>
To: Amitesh Singh <singh.amitesh@gmail.com>
Cc: linux-kernel@vger.kernel.org,
thomas.petazzoni@free-electrons.com,
"Noralf Trønnes" <noralf@tronnes.org>
Subject: Re: [PATCH] staging: fbtft: remove duplicate entries of ili9225
Date: Thu, 1 Dec 2016 08:28:52 +0100 [thread overview]
Message-ID: <20161201072852.GA17164@kroah.com> (raw)
In-Reply-To: <CABKcAmUYcuD-4iyotodhe1yzZ70bOyiZQJaOm8tNbuPP9PbdQg@mail.gmail.com>
On Wed, Nov 30, 2016 at 11:10:41PM +0530, Amitesh Singh wrote:
> On Nov 30, 2016 02:26, "Greg KH" <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Nov 28, 2016 at 05:55:29PM +0530, Amitesh Singh wrote:
> > > Signed-off-by: Amitesh Singh <singh.amitesh@gmail.com>
> > > ---
> >
> > I can't take patches without a changelog text :(
>
> did you mean the text after the commit heading?
Yes, please read Documentation/SubmittingPatches for what you should be
putting into a changelog text.
next prev parent reply other threads:[~2016-12-01 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 12:25 [PATCH] staging: fbtft: remove duplicate entries of ili9225 Amitesh Singh
2016-11-29 20:56 ` Greg KH
2016-11-30 17:40 ` Amitesh Singh
2016-12-01 7:28 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-24 17:46 Amitesh Singh
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=20161201072852.GA17164@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=singh.amitesh@gmail.com \
--cc=thomas.petazzoni@free-electrons.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 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.