From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHWORK] 71715 -> Not applicable.
Date: Thu, 18 Nov 2010 22:31:58 +0100 [thread overview]
Message-ID: <4CE59B4E.90804@free.fr> (raw)
Yay, my first todo in patchwork! :)
<http://patchwork.ozlabs.org/patch/71715/>
It was discussed there:
<http://www.mail-archive.com/u-boot@lists.denx.de/msg28003.html>
AIUI, the discussion was about asm-generic/unaligned.h rather than about
the patch itself. Personally I think that the patch could have been
applied, and *then* asm-generic/unaligned.h could have been brought in
sync with its Linux counterpart.
Anyway this patch requires a rebase now as the whole arch organization
has moved around. Ergo: not applicable; if the patch is needed, I'd like
it to be resubmitted based on current master.
Note: I am posting this to the list because we're only starting using
patchwork, so maybe we should share our experience for the moment; I
don't know yet what patchwork action is worthy of a post on the list and
what is not. For all I know, maybe patchwork itself is going to post
something right after I set the "not applicable" status...
In any case, *do not* blindly take this message as the Right Way To Do
Things With Patchwork! I don't want to start a wrong habit.
Amicalement,
--
Albert.
next reply other threads:[~2010-11-18 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 21:31 Albert ARIBAUD [this message]
2010-11-18 21:50 ` [U-Boot] [PATCHWORK] 71715 -> Not applicable Wolfgang Denk
2010-11-18 22:00 ` Mike Frysinger
2010-11-18 22:21 ` Albert ARIBAUD
2010-11-18 23:13 ` Mike Frysinger
2010-11-19 5:59 ` Albert ARIBAUD
2010-11-19 7:13 ` Mike Frysinger
2010-11-19 10:50 ` Albert ARIBAUD
2010-11-19 10:51 ` Mike Frysinger
2010-11-19 11:56 ` Albert ARIBAUD
2010-11-20 8:36 ` Mike Frysinger
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=4CE59B4E.90804@free.fr \
--to=albert.aribaud@free.fr \
--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 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.