From: Greg KH <gregkh@linuxfoundation.org>
To: "sudheer.v" <open.sudheer@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
sudheer.veliseti@aspeedtech.com, linux-aspeed@lists.ozlabs.org,
andrew@aj.id.au, benh@kernel.crashing.org,
shivahshankar.shankarnarayanrao@aspeedtech.com,
robh+dt@kernel.org, joel@jms.id.au, linux-serial@vger.kernel.org,
jslaby@suse.com, mchehab+samsung@kernel.org,
linux-arm-kernel@lists.infradead.org,
sudheer Kumar veliseti <sudheer.open@gmail.com>
Subject: Re: [patch 1/5] AST2500 DMA UART driver
Date: Mon, 10 Jun 2019 18:49:30 +0200 [thread overview]
Message-ID: <20190610164930.GA32085@kroah.com> (raw)
In-Reply-To: <1559737395-28542-2-git-send-email-open.sudheer@gmail.com>
On Wed, Jun 05, 2019 at 05:53:11PM +0530, sudheer.v wrote:
> From: sudheer Kumar veliseti <sudheer.open@gmail.com>
>
> Signed-off-by: sudheer veliseti <sudheer.open@gmail.com>
> ---
I can not take a patch without any changelog text at all, especially for
one that is 1928 lines long :(
Please provide a proper changelog and I will be glad to review it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-10 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:23 [patch 0/5] *** Cover Letter: patch submission for AST2500 UART driver *** sudheer.v
2019-06-05 12:23 ` [patch 1/5] AST2500 DMA UART driver sudheer.v
2019-06-10 16:49 ` Greg KH [this message]
2019-06-10 16:50 ` Greg KH
2019-06-05 12:23 ` [patch 2/5] build configuration for " sudheer.v
2019-06-05 12:23 ` [patch 3/5] DT nodes " sudheer.v
2019-06-05 12:23 ` [patch 4/5] defconfig and MAINTAINERS updated " sudheer.v
2019-06-05 12:23 ` [patch 5/5] Documentation: DT bindings " sudheer.v
-- strict thread matches above, loose matches on Subject: below --
2019-06-21 11:17 [patch 0/5] *** DMA based UART driver for AST2500 *** sudheer.v
2019-06-21 11:17 ` [patch 1/5] AST2500 DMA UART driver sudheer.v
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=20190610164930.GA32085@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=open.sudheer@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shivahshankar.shankarnarayanrao@aspeedtech.com \
--cc=sudheer.open@gmail.com \
--cc=sudheer.veliseti@aspeedtech.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;
as well as URLs for NNTP newsgroup(s).