From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Tull <atull@kernel.org>
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
linux-fpga@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
atull <atull@opensource.altera.com>,
dinguyen@kernel.org
Subject: Re: [GIT PULL] fpga: Updates for 4.10-rc2
Date: Thu, 5 Jan 2017 08:51:48 +0100 [thread overview]
Message-ID: <20170105075148.GA4788@kroah.com> (raw)
In-Reply-To: <CANk1AXSjuBNuZqmKU==6DtEMDA8jigXkKPbTvtJkyUv6-KuTPw@mail.gmail.com>
On Wed, Jan 04, 2017 at 03:53:18PM -0600, Alan Tull wrote:
> On Wed, Jan 4, 2017 at 3:28 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Wed, Jan 04, 2017 at 02:00:23PM -0600, Alan Tull wrote:
> >> Hi Greg,
> >>
> >> Please pull these changes for FPGA.
> >>
> >> Thanks!
> >> Alan
> >>
> >> The following changes since commit e3d31bda06e43968cd215ae590eb7cda827f01e9:
> >>
> >> Add linux-next specific files for 20161224 (2017-01-04 10:26:49 -0600)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/atull/linux-fpga.git tags/fpga-for-greg-20170104
> >>
> >> for you to fetch changes up to 2dd088da8cce745c008fc7f8b64e1aef33eb37c2:
> >>
> >> ARM: ep93xx: Register ts73xx-fpga manager driver for TS-7300 (2017-01-04 10:27:26 -0600)
> >>
> >> ----------------------------------------------------------------
> >> fpga: Updates for 4.10-rc2
> >>
> >> * Add scatterlist based fpga programming
> >> * TS-7300 FPGA manager
> >> * zynq: Check for errors after completing DMA
> >> * fix sparse warnings in fpga-mgr and fpga-bridge
> >
> > These are all bugfixes or regression fixes? Doesn't seem like adding
> > new functionality and a new driver fits that category to me, why add
> > them now?
> >
> > Sorry, I can't take this, if you resend them as patches, I can be more
> > specific...
> >
> > thanks,
> >
> > greg k-h
>
> Hi Greg,
>
> Yes, sorry, I'm still learning here. One patch is a fix (sparse
> errors), the rest are new functionality.
Ok, let's stick to patches then, no git pull requests, it makes things
easier that way for things to be reviewed properly.
> Would it be appropriate to separate these and send you two pull
> requests - the sparse error fix for 4.10 and the rest (new
> functionality) for 4.11?
why would a sparse warning fix be ok for a -rc kernel? Is it a real
bug?
Send patches, we can go from there please.
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-05 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 20:00 Alan Tull
2017-01-04 21:28 ` Greg Kroah-Hartman
2017-01-04 21:53 ` Alan Tull
2017-01-05 7:51 ` Greg Kroah-Hartman [this message]
2017-01-05 20:49 ` Alan Tull
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=20170105075148.GA4788@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=atull@kernel.org \
--cc=atull@opensource.altera.com \
--cc=dinguyen@kernel.org \
--cc=linux-fpga@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
Powered by JetHome