From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/2] sh_eth: check platform data pointer
Date: Wed, 30 Oct 2013 15:16:02 -0400 (EDT) [thread overview]
Message-ID: <20131030.151602.2034358719733053721.davem@davemloft.net> (raw)
In-Reply-To: <52716421.9080807@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Wed, 30 Oct 2013 22:55:13 +0300
> David, could you please merge this patch? It has a value of its own,
> regardless of the device tree support in patch 2 (which got bloked).
Then it needs to be resubmitted.
Any time a part of series is rejected or needs changes, it is entirely
dropped and no longer will I refer to it in patchwork.
To avoid any ambiguity, the submitted must then resubmit anythign he
wishes to be applied.
prev parent reply other threads:[~2013-10-30 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 0:23 [PATCH 1/2] sh_eth: check platform data pointer Sergei Shtylyov
2013-09-04 6:48 ` Simon Horman
2013-10-30 19:55 ` Sergei Shtylyov
2013-10-30 19:16 ` David Miller [this message]
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=20131030.151602.2034358719733053721.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).