linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Deepak R Varma <mh12gx2825@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-iio@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: iio: adis16240: add blank line before struct definition
Date: Sun, 11 Oct 2020 18:11:58 +0100	[thread overview]
Message-ID: <20201011181158.7541d290@archlinux> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2010111303540.2716@hadrien>

On Sun, 11 Oct 2020 13:06:06 +0200 (CEST)
Julia Lawall <julia.lawall@inria.fr> wrote:

> On Sun, 11 Oct 2020, Deepak R Varma wrote:
> 
> > Add a blank line before starting structure definition as per coding
> > style guidelines. Issue reported by checkpatch script.
> >
> > Signed-off-by: Deepak R Varma <mh12gx2825@gmail.com>  
> 
> Acked-by: Julia Lawall <julia.lawall@inria.fr>

Hi Deepak / Julia.

Applied to the togreg branch of iio.git.  Initially I'll be pushing that
out as testing, so that various systems that run build tests can check
we haven't missed anything.   Clearly they won't be finding anything in
this particular patch, but there are other things in that branch that
may be more problematic.

Given timing wrt to the merge window, these won't go upstream until
next cycle.  I will probably send Greg KH a pull request in a few
weeks time (after rc1) including this patch.

Thanks,

Jonathan


> 
> > ---
> >  drivers/staging/iio/accel/adis16240.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/staging/iio/accel/adis16240.c b/drivers/staging/iio/accel/adis16240.c
> > index 5064adce5f58..8d3afc6dc755 100644
> > --- a/drivers/staging/iio/accel/adis16240.c
> > +++ b/drivers/staging/iio/accel/adis16240.c
> > @@ -426,6 +426,7 @@ static int adis16240_probe(struct spi_device *spi)
> >
> >  	return devm_iio_device_register(&spi->dev, indio_dev);
> >  }
> > +
> >  static const struct of_device_id adis16240_of_match[] = {
> >  	{ .compatible = "adi,adis16240" },
> >  	{ },
> > --
> > 2.25.1
> >
> > --
> > You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20201011104800.GA29412%40ubuntu204.
> >  


      reply	other threads:[~2020-10-11 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 10:48 [PATCH] staging: iio: adis16240: add blank line before struct definition Deepak R Varma
2020-10-11 11:06 ` [Outreachy kernel] " Julia Lawall
2020-10-11 17:11   ` Jonathan Cameron [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=20201011181158.7541d290@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mh12gx2825@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=pmeerw@pmeerw.net \
    /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).