From: Esben Haabendal <esben@geanix.com>
To: David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, michal.simek@xilinx.com,
linux-kernel@vger.kernel.org, ynezz@true.cz,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] net: ll_temac: Bugfixes and ethtool support
Date: Wed, 19 Feb 2020 11:53:00 +0100 [thread overview]
Message-ID: <875zg2n90z.fsf@geanix.com> (raw)
In-Reply-To: <20200218.115014.2022578847900470441.davem@davemloft.net> (David Miller's message of "Tue, 18 Feb 2020 11:50:14 -0800 (PST)")
David Miller <davem@davemloft.net> writes:
> Several errors in this submission:
>
> 1) Do not mix bug fixes and new features. Submit the bug fixes
> targetting 'net', and then wait for net to be merged into
> net-next at which time you can submit the new features on
> top.
>
> 2) As per Documentation/networking/netdev-FAQ.rst you should not
> ever CC: stable for networking patches, we submit bug fixes to
> stable ourselves.
Got it. I will resend against net and net-next.
/Esben
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Esben Haabendal <esben@geanix.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, andrew@lunn.ch,
michal.simek@xilinx.com, ynezz@true.cz
Subject: Re: [PATCH 0/8] net: ll_temac: Bugfixes and ethtool support
Date: Wed, 19 Feb 2020 11:53:00 +0100 [thread overview]
Message-ID: <875zg2n90z.fsf@geanix.com> (raw)
In-Reply-To: <20200218.115014.2022578847900470441.davem@davemloft.net> (David Miller's message of "Tue, 18 Feb 2020 11:50:14 -0800 (PST)")
David Miller <davem@davemloft.net> writes:
> Several errors in this submission:
>
> 1) Do not mix bug fixes and new features. Submit the bug fixes
> targetting 'net', and then wait for net to be merged into
> net-next at which time you can submit the new features on
> top.
>
> 2) As per Documentation/networking/netdev-FAQ.rst you should not
> ever CC: stable for networking patches, we submit bug fixes to
> stable ourselves.
Got it. I will resend against net and net-next.
/Esben
next prev parent reply other threads:[~2020-02-19 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 8:26 [PATCH 0/8] net: ll_temac: Bugfixes and ethtool support Esben Haabendal
2020-02-18 8:26 ` Esben Haabendal
2020-02-18 19:50 ` David Miller
2020-02-18 19:50 ` David Miller
2020-02-19 10:53 ` Esben Haabendal [this message]
2020-02-19 10:53 ` Esben Haabendal
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=875zg2n90z.fsf@geanix.com \
--to=esben@geanix.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=ynezz@true.cz \
/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.