linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Ganapathi Bhat <gbhat@marvell.com>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	James Cao <jcao@marvell.com>, Cathy Luo <cluo@marvell.com>,
	Mangesh Malusare <mmangesh@marvell.com>,
	Xinming Hu <huxm@marvell.com>, Zhiyuan Yang <yangzy@marvell.com>,
	Karthik Doddayennegere Ananthapadmanabha <karthida@marvell.com>,
	Brian Norris <briannorris@chromium.org>
Subject: Re: pull-request mwifiex-firmware 2017-10-31
Date: Thu, 23 Nov 2017 01:37:24 +0000	[thread overview]
Message-ID: <1511401044.14687.6.camel@decadent.org.uk> (raw)
In-Reply-To: <99832be6bb804911a374c85d1865d0b2@SC-EXCH02.marvell.com>

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

On Tue, 2017-10-31 at 15:34 +0000, Ganapathi Bhat wrote:
> The following changes since commit e0494e95192ac5329989f4d128cf95c417d618cc:
> 
>   linux-firmware: update Marvell PCIe-USB8997 firmware image (2017-08-01 23:55:30 +0530)

But that commit is not in linux-firmware.git.

> are available in the git repository at:
> 
>   git://git.marvell.com/mwifiex-firmware.git
> 
> for you to fetch changes up to db3e1855ea46bc1a22b8bbecb400c2909c551cf5:
> 
>   linux-firmware: update Marvell PCIe-USB8997 firmware image (2017-10-31 20:49:53 +0530)
> 
> ----------------------------------------------------------------
> Ganapathi Bhat (1):
>       linux-firmware: update Marvell PCIe-USB8997 firmware image
> 
>  WHENCE                        |   2 +-
>  mrvl/pcieusb8997_combo_v4.bin | Bin 620800 -> 622532 bytes
>  2 files changed, 1 insertion(+), 1 deletion(-)

There are three commits in this repository that aren't in linux-
firmware.git, not one.  Please either:

1. Send a pull request listing all the commits (the  <start> parameter
to git request-pull should be something like "origin/master"), or
2. Rebase this branch to include only the commit you want me to pull,
and send a pull request listing that.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-11-23  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 15:34 pull-request mwifiex-firmware 2017-10-31 Ganapathi Bhat
2017-11-23  1:37 ` Ben Hutchings [this message]
2017-11-23 13:25   ` [EXT] " Ganapathi Bhat
  -- strict thread matches above, loose matches on Subject: below --
2017-10-31 15:32 Ganapathi Bhat

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=1511401044.14687.6.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=briannorris@chromium.org \
    --cc=cluo@marvell.com \
    --cc=gbhat@marvell.com \
    --cc=huxm@marvell.com \
    --cc=jcao@marvell.com \
    --cc=karthida@marvell.com \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mmangesh@marvell.com \
    --cc=yangzy@marvell.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).