From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Gonzalez Monroy,
Sergio"
<sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH v2] doc: add known issue for iommu and igb_uio
Date: Fri, 12 Dec 2014 17:34:15 +0100 [thread overview]
Message-ID: <1625343.s71lA0fsGY@xps13> (raw)
In-Reply-To: <548AF28C.6050900-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-12-12 14:50, Nicolas Dichtel:
> Le 12/12/2014 14:38, Gonzalez Monroy, Sergio a écrit :
> > Any ideas why patchwork is not showing these patches?
>
> No ...
> Thomas, do you have an idea?
The parsemail script is responsible of adding new patches.
So I guess the answer (bug?) is in this file:
http://git.ozlabs.org/?p=patchwork;a=blob;f=apps/patchwork/bin/parsemail.py
Sergio, maybe you could try the parsemail script locally with your patch.
--
Thomas
next prev parent reply other threads:[~2014-12-12 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:41 [PATCH] doc: Add known issue for iommu and igb_uio Sergio Gonzalez Monroy
[not found] ` <1418380884-6875-1-git-send-email-sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-12 12:06 ` [PATCH v2] doc: add " Sergio Gonzalez Monroy
[not found] ` <1418385971-17323-1-git-send-email-sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-12 12:59 ` Nicolas Dichtel
[not found] ` <548AE6BC.7060202-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-12-12 13:20 ` Gonzalez Monroy, Sergio
[not found] ` <91383E96CE459D47BCE92EFBF5CE73B004EFED22-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-12-12 13:28 ` Nicolas Dichtel
[not found] ` <548AED73.3030804-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-12-12 13:38 ` Gonzalez Monroy, Sergio
[not found] ` <91383E96CE459D47BCE92EFBF5CE73B004EFED5F-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-12-12 13:50 ` Nicolas Dichtel
[not found] ` <548AF28C.6050900-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-12-12 16:34 ` Thomas Monjalon [this message]
2014-12-12 14:43 ` [PATCH v3] " Sergio Gonzalez Monroy
[not found] ` <1418395427-17406-1-git-send-email-sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-15 10:32 ` [PATCH v4] " Sergio Gonzalez Monroy
[not found] ` <1418639563-3599-1-git-send-email-sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-17 10:01 ` Iremonger, Bernard
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=1625343.s71lA0fsGY@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.