From: dev@michaelmera.com (Michael Mera)
To: kernelnewbies@lists.kernelnewbies.org
Subject: question on patch submission
Date: Fri, 28 Apr 2017 23:52:18 +0900 [thread overview]
Message-ID: <87o9vgy47x.fsf@michaelmera.com> (raw)
In-Reply-To: <20170428130131.GA11647@kroah.com>
Greg KH <greg@kroah.com> writes:
> Look at other patches on the mailing list and in your editor, all should
> be fine when you create it using git.
Ok. I indeed created it with git.
> Yes, make it a new version, as the version is the combination of both.
> Make it trivially easy for a maintainer to know which version to accept.
> Marking it as "RESEND" implies that either patch submission could be
> accepted, but marking it with a version is explicit as to which you
> should use.
Ok, I submitted a new version which I hope will be more appropriate.
> thanks,
>
> greg k-h
Thank you for taking the time to review these. Hopefully it will be less
painful for the futur patches.
Michael Mera
prev parent reply other threads:[~2017-04-28 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 12:49 question on patch submission Michael Mera
2017-04-28 13:01 ` Greg KH
2017-04-28 14:52 ` Michael Mera [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=87o9vgy47x.fsf@michaelmera.com \
--to=dev@michaelmera.com \
--cc=kernelnewbies@lists.kernelnewbies.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).