archive mirror
 help / color / mirror / Atom feed
From: jassi brar <>
To: Grant Likely <grant.likely-s3s/>
	David Brownell
	Ben Dooks <ben-SMNkleLxa3Z6Wcw2j4pizdi2O/>
Subject: Re: [git pull] 2nd batch of SPI changes
Date: Mon, 18 Jan 2010 18:49:37 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Dec 18, 2009 at 12:00 PM, Grant Likely
<> wrote:
> On Thu, Dec 17, 2009 at 5:45 PM, jassi brar <> wrote:
>> On Fri, Dec 18, 2009 at 1:40 AM, Grant Likely <> 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.
Now, that my SoC specific stuff has been sorted out and accepted in my
maintainer's tree, I am going to submit incremental patches for

Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
spi-devel-general mailing list

      parent reply	other threads:[~2010-01-18  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 16:40 Grant Likely
2009-12-18  0:45 ` [spi-devel-general] " jassi brar
2009-12-18  3:00   ` Grant Likely
     [not found]     ` <>
2010-01-18  9:49       ` jassi brar [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \
    --cc=ben-SMNkleLxa3Z6Wcw2j4pizdi2O/ \ \
    --cc=grant.likely-s3s/ \ \
    --subject='Re: [git pull] 2nd batch of SPI changes' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).