From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] GPIO support for sh73a0/ag5evm
Date: Fri, 19 Nov 2010 06:15:30 +0000 [thread overview]
Message-ID: <20101119061530.GB16739@linux-sh.org> (raw)
In-Reply-To: <20101119130656.8b8a50b9.takashi.yoshii.zj@renesas.com>
On Fri, Nov 19, 2010 at 03:08:51PM +0900, Takashi Yoshii wrote:
> > Did something happen to your 1/2 patch?
>
> http://vger.kernel.org/majordomo-info.html says,
> > Message size exceeding 100 000 characters causes blocking.
>
> Seems to be this one. I've re-sent it to you directory.
> Should I re-send it compressed form to ML? (perhaps NO).
>
I can't imagine there are very many people on the list that would want to
read through this patch in its entirety, I certainly don't count myself
amongst them. There's nothing terribly interesting in it anyways, so I'll
just take care of it off-list for now.
next prev parent reply other threads:[~2010-11-19 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 4:06 [PATCH 0/2] GPIO support for sh73a0/ag5evm Takashi Yoshii
2010-11-19 5:20 ` Paul Mundt
2010-11-19 6:08 ` Takashi Yoshii
2010-11-19 6:15 ` Paul Mundt [this message]
2010-11-19 7:49 ` Paul Mundt
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=20101119061530.GB16739@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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