netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull-request: mac80211 2017-03-16
Date: Fri, 17 Mar 2017 09:05:57 +0100	[thread overview]
Message-ID: <1489737957.2544.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20170316.111819.199681647414354942.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

On Thu, 2017-03-16 at 11:18 -0700, David Miller wrote:
> From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> Date: Thu, 16 Mar 2017 10:51:55 +0100
> 
> > Here's the pull request you were waiting for. I went through all my
> > pending patches but only this one is applicable for net.git at this
> > time, so it's just a single one.
> > 
> > Since I didn't have a current base, I forwarded to net.git first
> > and re-validated the patch there, but you might might have to be
> > careful if you merge to not fast-fwd on your side (though, even
> > if you do that, I don't think it matters much).
> > 
> > Please pull and let me know if there's any problem.
> 
> I was able to fast-forward pull this, so it should be fine.

Great, thanks. I somehow thought that you might _not_ want the fast
forward, to preserve where the patch came from, but personally I don't
care.

Thanks for merging it so quickly!

johannes

      parent reply	other threads:[~2017-03-17  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16  9:51 pull-request: mac80211 2017-03-16 Johannes Berg
2017-03-16 18:18 ` David Miller
     [not found]   ` <20170316.111819.199681647414354942.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-03-17  8:05     ` Johannes Berg [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=1489737957.2544.1.camel@sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).