From: Greg KH <greg@kroah.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Kernel Fedora <kernel@lists.fedoraproject.org>
Subject: Re: Oct. Fedora Kernel Patch Report
Date: Mon, 2 Dec 2013 09:49:50 -0800 [thread overview]
Message-ID: <20131202174950.GA30171@kroah.com> (raw)
In-Reply-To: <CA+5PVA5megGZVEFdmDGyeALQux2ppBEJtULm5hY81khhsFk0kA@mail.gmail.com>
On Thu, Oct 24, 2013 at 03:01:28PM -0400, Josh Boyer wrote:
> Here's this months Fedora kernel report. I intended to get it out
> last week, but Greg keeps releasing new stable kernels. Given he's at
> KS right now, I'll finally get it written before another release comes
> out.
>
> I've skipped the patches we tend to carry for default option changes
> and such. If people really want me to keep listing those, I'd be
> happy to.
<snip>
many thanks for this, I've picked up a number of patches for 3.10 from
here.
greg k-h
next prev parent reply other threads:[~2013-12-02 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 19:01 Oct. Fedora Kernel Patch Report Josh Boyer
2013-12-02 17:49 ` Greg KH [this message]
2013-12-02 18:41 ` Josh Boyer
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=20131202174950.GA30171@kroah.com \
--to=greg@kroah.com \
--cc=jwboyer@gmail.com \
--cc=kernel@lists.fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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