netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Rene Rebe <rene@exactcode.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] r8152 add Microsoft Dock IDs
Date: Thu, 14 Jan 2016 19:16:25 +0100	[thread overview]
Message-ID: <20160114181625.GK19773@lunn.ch> (raw)
In-Reply-To: <20160114.184626.1327276960383833164.rene@exactcode.com>

On Thu, Jan 14, 2016 at 06:46:26PM +0100, Rene Rebe wrote:
> Hi David,
> (my appologies for wasting your time with this noise)
> 
> rebased against your netdev git, and sent with Mew:

Hi Rene

So, slowly getting better. However, go read
Documentation/SubmittingPatches

Read the bit about the "---" marker.

netdev also has a few additional rules, which are not documented in
SubmittingPatches.

In the subject line, you should include which tree this patch is
supposed to be applied to. In this case, it is net-next. So you
subject line should be

Subject: [PATCH net-next] r8152 add Microsoft Dock IDs

and obviously, your patch needs to cleanly apply to net-next, not some
other random tree.

The other rule which is relevant at the moment, is that net-next is
closed, because the merge window is open. So please wait about 12 days
for net-next to reopen. David will probably send an email saying he is
ready to accept new patches.

      Andrew

  reply	other threads:[~2016-01-14 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 17:46 [PATCH] r8152 add Microsoft Dock IDs Rene Rebe
2016-01-14 18:16 ` Andrew Lunn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-13 17:06 René Rebe
2016-01-13 19:51 ` David Miller
2016-01-13 20:03   ` René Rebe
2016-01-13 20:49     ` 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=20160114181625.GK19773@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rene@exactcode.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).