From: Peter Wu <lekensteyn@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: David Miller <davem@davemloft.net>,
bhutchings@solarflare.com, netdev@vger.kernel.org,
nic_swsd@realtek.com
Subject: Re: [PATCH v3] r8169: fix invalid register dump
Date: Wed, 21 Aug 2013 23:13:35 +0200 [thread overview]
Message-ID: <4578926.BDvSIdbm2b@al> (raw)
In-Reply-To: <20130821205325.GA24054@electric-eye.fr.zoreil.com>
On Wednesday 21 August 2013 22:53:25 Francois Romieu wrote:
> Peter Wu <lekensteyn@gmail.com> :
> [...]
>
> > Please find the updated patch below. There may be differences in lines
> > because net-next has the r8169,sis190 patch and net the WOL fix.
> >
> > Can I consider Francois reply[1] as Acked-by?
>
> Yes, provided you insert an empty line between declarations and code.
Done, new patch will arrive in a minute.
> You may / should send patches as normal submissions. It will probably
> be easier for davem to use and you can always raise questions or add
> minor remarks in the "--- ... diff" section.
I noticed that patchwork also recognized submissions that are appended to a
mail, so I tried that out ;-) Well, apparantly it does not work well with git,
so I will just send a new patch with a useful In-Reply-To header.
Peter
next prev parent reply other threads:[~2013-08-21 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 13:41 [PATCH v3] r8169: fix invalid register dump Peter Wu
2013-08-18 21:21 ` Francois Romieu
2013-08-20 22:02 ` David Miller
2013-08-21 20:40 ` Peter Wu
2013-08-21 20:53 ` Francois Romieu
2013-08-21 21:13 ` Peter Wu [this message]
2013-08-21 21:17 ` [PATCH net-next v4] " Peter Wu
2013-08-22 21:26 ` David Miller
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=4578926.BDvSIdbm2b@al \
--to=lekensteyn@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.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 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.