From: Mark Brown <broonie@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: jon@ringle.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] regmap: Allow installing custom reg_update_bits function
Date: Tue, 6 Oct 2015 16:07:07 +0100 [thread overview]
Message-ID: <20151006150707.GT12635@sirena.org.uk> (raw)
In-Reply-To: <20151006.062208.1154490262564827766.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Tue, Oct 06, 2015 at 06:22:08AM -0700, David Miller wrote:
> Date: Tue, 6 Oct 2015 10:57:15 +0100
> > I obviously can't just merge in net-next.
> People do this all the time, when needed. My history never changes,
> and the networking tree is one of the first trees pulled into
> linux-next, so this is always safe.
Which would then make working with my tree annoying (I get net stuff
showing up in my diffs and logs) and gets in the way for sending pull
requests before Linus starts merging stuff which I tend to do.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-10-06 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 11:43 [PATCH net-next v2 1/2] regmap: Allow installing custom reg_update_bits function jon
2015-10-01 11:43 ` [PATCH net-next v2 2/2] net: Microchip encx24j600 driver jon
2015-10-01 12:26 ` [RFC PATCH] net: encx24j600_exit() can be static kbuild test robot
2015-10-05 10:54 ` [PATCH net-next v2 2/2] net: Microchip encx24j600 driver David Miller
2015-10-05 11:00 ` David Miller
2015-10-05 11:01 ` David Miller
2015-10-05 10:54 ` [PATCH net-next v2 1/2] regmap: Allow installing custom reg_update_bits function David Miller
2015-10-05 11:57 ` Jon Ringle
2015-10-05 13:16 ` David Miller
2015-10-05 14:25 ` Mark Brown
2015-10-06 6:21 ` David Miller
2015-10-06 9:57 ` Mark Brown
2015-10-06 13:22 ` David Miller
2015-10-06 15:07 ` Mark Brown [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=20151006150707.GT12635@sirena.org.uk \
--to=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jon@ringle.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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