public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	gnurou@gmail.com, Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH] gpiolib: fix link error when sysfs is not built
Date: Sun, 10 Feb 2013 18:43:59 +0000	[thread overview]
Message-ID: <20130210184359.5FE083E10AE@localhost> (raw)
In-Reply-To: <1360504821-13110-1-git-send-email-gnurou@gmail.com>

On Sun, 10 Feb 2013 23:00:21 +0900, Alexandre Courbot <gnurou@gmail.com> wrote:
> From: Alexandre Courbot <acourbot@nvidia.com>
> 
> Fix all compilation errors and warnings triggered by my latest series of
> patch on Grant's linux-next branch. Please meld this patch into the culprit
> one to avoid ending with a commit that breaks compilation in the git history.
> 
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>

Applied, thanks. I've pushed it out as a separate commit since I had
already pushed my tree out. so I need to make sure linusw hasn't pulled
it and applied anything on top before I respin.

g.


  reply	other threads:[~2013-02-10 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51166e1c.NRfQN8VgI14zuNwf%fengguang.wu@intel.com>
2013-02-09 16:34 ` [grant:gpio/next 10/16] gpiolib.c:undefined reference to `gpiod_unexport' Grant Likely
2013-02-10 14:00   ` [PATCH] gpiolib: fix link error when sysfs is not built Alexandre Courbot
2013-02-10 18:43     ` Grant Likely [this message]
2013-02-10 14:04   ` [grant:gpio/next 10/16] gpiolib.c:undefined reference to `gpiod_unexport' Alex Courbot

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=20130210184359.5FE083E10AE@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=acourbot@nvidia.com \
    --cc=gnurou@gmail.com \
    --cc=linux-kernel@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