From: Kyle McMartin <kyle@infradead.org>
To: "Jie, Yang" <yang.jie@intel.com>
Cc: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
"kyle@infradead.org" <kyle@infradead.org>,
"Woodhouse, David" <david.woodhouse@intel.com>,
"kyle@kernel.org" <kyle@kernel.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"Li, Jocelyn" <jocelyn.li@intel.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>,
"Chehab, John" <john.chehab@intel.com>,
"Hindman, Gavin" <gavin.hindman@intel.com>,
"Strasser, Kevin" <kevin.strasser@intel.com>,
"Accardi, Kristen C" <kristen.c.accardi@intel.com>,
"Schlobohm, Bruce" <bruce.schlobohm@intel.com>,
"Nikula, Jarkko" <jarkko.nikula@intel.com>
Subject: Re: Do you know who maintains firmware upstreaming for linux now?
Date: Sun, 30 Nov 2014 20:41:03 -0500 [thread overview]
Message-ID: <20141201014102.GA2930@merlin.infradead.org> (raw)
In-Reply-To: <E7B1D079BA13FB44A978CC8F69C7D6A901B731FB@SHSMSX101.ccr.corp.intel.com>
On Fri, Nov 28, 2014 at 11:51:16AM +0000, Jie, Yang wrote:
>
> Hi, All,
>
> Could someone clarify who maintains firmware upstreaming to Linux at the moment?
>
> We are working on upstream a firmware binary and its license to git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git, We've sent the patch to linux-firmware@kernel.org but got no reply for several(4~5) weeks.
> I can imagine that maintainers may be very busy, and not sure if Ben/Kyle have been on vacation, or can someone else help to review and apply our firmware patch?
>
Sorry, we've just been busy, and I figured someone would pick up my
slacking... I'll get to it tonight.
regards, Kyle
next prev parent reply other threads:[~2014-12-01 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 11:51 Do you know who maintains firmware upstreaming for linux now? Jie, Yang
2014-12-01 1:41 ` Kyle McMartin [this message]
2014-12-01 2:02 ` Jie, Yang
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=20141201014102.GA2930@merlin.infradead.org \
--to=kyle@infradead.org \
--cc=ben@decadent.org.uk \
--cc=bruce.schlobohm@intel.com \
--cc=david.woodhouse@intel.com \
--cc=gavin.hindman@intel.com \
--cc=jarkko.nikula@intel.com \
--cc=jocelyn.li@intel.com \
--cc=john.chehab@intel.com \
--cc=kevin.strasser@intel.com \
--cc=kristen.c.accardi@intel.com \
--cc=kyle@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=yang.jie@intel.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