From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
arnd@arndb.de, gregkh@linuxfoundation.org, knaack.h@gmx.de,
pmeerw@pmeerw.net, lars@metafoo.de, devel@driverdev.osuosl.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id
Date: Sun, 3 Sep 2017 12:37:34 +0100 [thread overview]
Message-ID: <20170903123734.232932e7@archlinux> (raw)
In-Reply-To: <b84769c2-5fce-46ec-f272-408bd6bfe394@gmail.com>
On Tue, 22 Aug 2017 10:51:37 +0530
Arvind Yadav <arvind.yadav.cs@gmail.com> wrote:
> Hi
>
>
> On Tuesday 22 August 2017 01:50 AM, Dan Carpenter wrote:
> > Don't say "[PATCH 4/4]". It's not a patchset or a part of an email
> > thread.
> Yes, It's part of these patchset.
> [PATCH 1/4] misc: apds9802als: constify i2c_device_id
> [PATCH 2/4] misc: hmc6352: constify i2c_device_id
> [PATCH 3/4] misc: isl29020: constify i2c_device_id
> [PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id
For a series like this that is jumping around the kernel
it would have been better to have broken it up on a subsystem
basis. It is always confusing when people only see a small
part of a bigger series and need to go looking to find out
if they have missed something in the other patches.
Anyhow, applied to the togreg branch of iio.git which will
be pushed out as testing for the autobuilders to play with it.
Thanks,
Jonathan
>
> >
> > regards,
> > dan carpenter
> >
> ~arvind
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-09-03 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 16:43 [PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id Arvind Yadav
2017-08-21 20:20 ` Dan Carpenter
2017-08-22 5:21 ` Arvind Yadav
2017-09-03 11:37 ` 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=20170903123734.232932e7@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=arnd@arndb.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).