From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Tull <atull@opensource.altera.com>
Cc: linux-kernel@vger.kernel.org,
Moritz Fischer <moritz.fischer@ettus.com>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
kernel-janitors@vger.kernel.org, delicious.quinoa@gmail.com
Subject: Re: [PATCH 0/1] One bug fix for FPGA
Date: Thu, 17 Nov 2016 08:14:34 +0100 [thread overview]
Message-ID: <20161117071434.GA26700@kroah.com> (raw)
In-Reply-To: <20161117015440.3113-1-atull@opensource.altera.com>
On Wed, Nov 16, 2016 at 07:54:39PM -0600, Alan Tull wrote:
> Hi Greg,
>
> Can you take this patch?
Yes, no need to send it 3 times :)
prev parent reply other threads:[~2016-11-17 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 1:54 [PATCH 0/1] One bug fix for FPGA Alan Tull
2016-11-17 1:54 ` [PATCH 1/1] ARM: socfpga: checking the wrong variable Alan Tull
2016-11-17 7:14 ` Greg Kroah-Hartman [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=20161117071434.GA26700@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=atull@opensource.altera.com \
--cc=dan.carpenter@oracle.com \
--cc=delicious.quinoa@gmail.com \
--cc=dinguyen@opensource.altera.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.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