All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Himangi Saraogi <himangi774@gmail.com>
Cc: devel@driverdev.osuosl.org, Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Julia Lawall <julia.lawall@lip6.fr>,
	Jonathan Cameron <jic23@kernel.org>
Subject: Re: question regarding drivers/staging/iio/adc/ad7280a.c
Date: Thu, 17 Jul 2014 18:27:29 -0700	[thread overview]
Message-ID: <20140718012729.GA24211@kroah.com> (raw)
In-Reply-To: <20140717205815.GB1532@kroah.com>

On Thu, Jul 17, 2014 at 01:58:15PM -0700, Greg Kroah-Hartman wrote:
> On Thu, Jul 17, 2014 at 11:40:04PM +0530, Himangi Saraogi wrote:
> > Hi,
> > 
> > I have sent in a patch for adding devm_kasprintf https://lkml.org/lkml/2014/7/
> > 16/667.
> > I will be updating this file and send in a patch once it is accepted. Was it
> > the right thing
> > to do to send the devm_kasprintf patch separately from the patch on the file to
> > use it for,
> > because the person applying the later may not see the dependency?
> 
> Well, you should have told me there was a dependancy :)
> 
> As I'll end up taking both of these patches in the end, I'll queue your
> devm_kasprintf patch up in my staging-next tree so that it will work
> properly with your patch.

Now applied there, so all should be good, right?

thanks,

greg k-h

      reply	other threads:[~2014-07-18  1:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 20:31 question regarding drivers/staging/iio/adc/ad7280a.c Himangi Saraogi
2014-07-15 17:31 ` Jonathan Cameron
2014-07-16 11:14   ` Lars-Peter Clausen
2014-07-17 18:10     ` Himangi Saraogi
2014-07-17 20:58       ` Greg Kroah-Hartman
2014-07-18  1:27         ` 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=20140718012729.GA24211@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=himangi774@gmail.com \
    --cc=jic23@kernel.org \
    --cc=julia.lawall@lip6.fr \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.