From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8] Add support for Network Space v2 and parents
Date: Sun, 15 May 2011 22:05:47 +1000 [thread overview]
Message-ID: <4DCFC19B.3080903@gmail.com> (raw)
In-Reply-To: <20110515095525.A13B51491B06@gemini.denx.de>
On 15/05/11 19:55, Wolfgang Denk wrote:
> Dear Simon Guinot,
>
> In message <1305382159-5483-1-git-send-email-simon.guinot@sequanux.org> you wrote:
>> --===============2147409246==
>>
>> This patch add support for the Network Space v2 board and parents, based
>> on the Marvell Kirkwood 6281 SoC. This include Network Space (Max) v2
>> and Internet Space v2.
>>
>> Additional information is available at:
>> http://lacie-nas.org/doku.php?id=network_space_v2
>>
>> Signed-off-by: Simon Guinot <sguinot@lacie.com>
>
> Seems you manage to get irnored once more by patchwork.
>
I too have had patchwork send patches to /dev/null :(
> I notice that even though you appear to use git-send-email for
> sending, your patch is not submitted inline as I would expect, but as
> a multipart/mixed - are you doing anything special? Do you see any
> warnings?
I also only use git-send-email (but I do not have the multipart issue)
>
> I also see that you are using git 1.6.3.1 which is pretty old. Maybe
> you can update to a more revcent git version and check if this helps?
>
I was using 1.7.1 when my patches got dropped
Regards,
Graeme
next prev parent reply other threads:[~2011-05-15 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 14:09 [U-Boot] [PATCH v8] Add support for Network Space v2 and parents Simon Guinot
2011-05-15 9:55 ` Wolfgang Denk
2011-05-15 11:36 ` Simon Guinot
2011-05-15 11:51 ` Simon Guinot
2011-05-15 12:05 ` Graeme Russ [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-15 12:32 Simon Guinot
2011-05-15 12:45 ` Wolfgang Denk
2011-05-15 14:03 ` Simon Guinot
2011-05-16 7:27 ` Prafulla Wadaskar
2011-05-16 7:14 ` Prafulla Wadaskar
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=4DCFC19B.3080903@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/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