From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Hung <hpeter@gmail.com>
Cc: jslaby@suse.cz, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix IO address calculation with Multi-Fintek PCI-to-UART Product
Date: Wed, 19 Nov 2014 10:47:39 -0800 [thread overview]
Message-ID: <20141119184739.GA28871@kroah.com> (raw)
In-Reply-To: <546C2DCC.4090507@gmail.com>
On Wed, Nov 19, 2014 at 01:42:36PM +0800, Peter Hung wrote:
> Dear Greg KH and Senior Linuxers,
>
> I had some some question, If I submited a patch, but it had rejected, how
> should I do when fix the patch?
>
> 1. send patch by reply original email ?
You can do this, with a [PATCH v2] in the subject.
> 2. direct send patch with new email again?
That works as well, but tell us what changed from the first one please.
thanks,
greg k-h
prev parent reply other threads:[~2014-11-19 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 9:48 [PATCH] Fix IO address calculation with Multi-Fintek PCI-to-UART Product Peter Hung
2014-11-18 16:58 ` Greg KH
2014-11-19 5:42 ` Peter Hung
2014-11-19 18:47 ` Greg KH [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=20141119184739.GA28871@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hpeter@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).