From: Baoquan He <bhe@redhat.com>
To: Sylvain Munaut <s.munaut@whatever-company.com>
Cc: kexec@lists.infradead.org
Subject: Re: Patch merging process ?
Date: Thu, 6 Oct 2016 13:04:43 +0800 [thread overview]
Message-ID: <20161006050443.GA17064@x1> (raw)
In-Reply-To: <CAF6-1L6y2uECc94nJGdPr581Eck6kQMkt1u8rk=jX208SVZA0Q@mail.gmail.com>
On 10/05/16 at 04:06pm, Sylvain Munaut wrote:
> Hi,
>
>
> I sent a series of 3 patch on the mailing list back in August :
>
> http://lists.infradead.org/pipermail/kexec/2016-August/017037.html
>
> They were pretty simple, but I didn't get any feedback (positive or
> negative) and I haven't seen them merged either ...
>
> Is there something more expected of me to get these upstream ?
You can repost. Usually maintainer may be very busy on other issues, you
can ping them one or two weeks later if no feedback.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-10-06 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 14:06 Patch merging process ? Sylvain Munaut
2016-10-06 5:04 ` Baoquan He [this message]
2016-10-07 2:52 ` Simon Horman
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=20161006050443.GA17064@x1 \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=s.munaut@whatever-company.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