From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to send the [PATCH 0/x] kind of emails?
Date: Sat, 13 Dec 2014 08:25:56 -0500 [thread overview]
Message-ID: <20141213132556.GA21624@kroah.com> (raw)
In-Reply-To: <CAC+QLdTYhLncM515VAbgX1PXjCvTE8QCio10NOz+zaDs7tbGEw@mail.gmail.com>
On Fri, Dec 12, 2014 at 10:36:00PM -0800, Mandeep Sandhu wrote:
> On Fri, Dec 12, 2014 at 8:02 PM, Greg KH <greg@kroah.com> wrote:
> > On Fri, Dec 12, 2014 at 02:29:22PM -0800, Mandeep Sandhu wrote:
> >> Thanks Greg!
> >>
> >> One more thing. Should the 'Tested-by:' tag be added in every commit
> >> manually, or only one of them is enough (the last patch really
> >> implements the functionality and the rest are 'preparatory' commits)?
> >
> > "Tested-by" is only for people who test the patch, not for the people
> > who wrote the patch. It is implied that the person who wrote the patch
> > also tested it, otherwise they shouldn't be sending the patch in the
> > firat place, right?
>
> Right, although in my case, I'm not the original author of this patch.
> This is the uio hotplug patch that I talked to you about on this ML a
> few days back (which somehow missed inclusion almost 4 years back).
Ok, then yes, add a tested-by on every patch that you tested.
> I'm simply following your suggestion, that is re-submitting the patch
> (after making some minor modifications to it for making it work with
> newer kernels). The original patch author is "Eric W. Biederman". I
> have tested this patch for my use-case (with a PCIE hotplug device)
> and I have also written a small "fake hotplug" driver which validates
> this patch (https://github.com/mandeepsandhu/uio-hotplug-test).
>
> Let me know if this is not the appropriate way to submit the patch (if
> only the original author should submit it instead).
Have you asked the original author about this? There has to be some
reason the patch was not accepted, right? Try asking them what happened
to see if they remember. I can't remember what happened with a specific
patch yesterday, I deal with too many patches to be able to remember
anything, but usually the author has a bit better recollection.
It's ok to submit other people's patches, but it's a nice idea to ask
them about it before doing so.
good luck,
greg k-h
next prev parent reply other threads:[~2014-12-13 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 22:05 How to send the [PATCH 0/x] kind of emails? Mandeep Sandhu
2014-12-12 22:27 ` Greg KH
2014-12-12 22:29 ` Mandeep Sandhu
2014-12-13 4:02 ` Greg KH
2014-12-13 6:36 ` Mandeep Sandhu
2014-12-13 13:25 ` Greg KH [this message]
2014-12-14 17:18 ` Mandeep Sandhu
2014-12-14 18:25 ` Greg KH
2014-12-15 1:12 ` Mandeep Sandhu
2014-12-12 22:27 ` Mandeep Sandhu
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=20141213132556.GA21624@kroah.com \
--to=greg@kroah.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).