From: Grant Likely <grant.likely@secretlab.ca>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: spi-devel-general@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [spi-devel-general] [git pull] 2nd batch of SPI changes
Date: Thu, 17 Dec 2009 20:00:14 -0700 [thread overview]
Message-ID: <fa686aa40912171900k386c748awb8d6ccb37d95285f@mail.gmail.com> (raw)
In-Reply-To: <1b68c6790912171645m4de68ac9i6f31346249147bd1@mail.gmail.com>
On Thu, Dec 17, 2009 at 5:45 PM, jassi brar <jassisinghbrar@gmail.com> wrote:
> On Fri, Dec 18, 2009 at 1:40 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> Jassi Brar (1):
>> spi: Add s3c64xx SPI Controller driver
> IIRC, I didn't get any final ack of acceptance from you or any other maintainer.
> I thought perhaps the patch is lost and was preparing to resend after
> including some minor changes suggested by my ARCH maintainer(Ben Dooks).
> Though I can just as well send those changes as patches right away.
> I apologize, if i messed up.
Don't worry about it, just send an incremental patch. I'm new to the
SPI maintainer job, and I didn't know any of the background or see any
major reason not to merge the driver, especially since it is a new
driver, and not a change to an existing one.
g.
next prev parent reply other threads:[~2009-12-18 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:40 [git pull] 2nd batch of SPI changes Grant Likely
2009-12-18 0:45 ` [spi-devel-general] " jassi brar
2009-12-18 3:00 ` Grant Likely [this message]
[not found] ` <fa686aa40912171900k386c748awb8d6ccb37d95285f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-18 9:49 ` jassi brar
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=fa686aa40912171900k386c748awb8d6ccb37d95285f@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).