public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@mleia•com>
To: Wolfram Sang <wsa@the-dreams•de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
	Maxime Ripard <maxime.ripard@free-electrons•com>,
	Jean Delvare <jdelvare@suse•com>,
	Ian Munsie <imunsie@au1•ibm.com>,
	Michael Neuling <mikey@neuling•org>,
	Arnd Bergmann <arnd@arndb•de>,
	linuxppc-dev@lists•ozlabs.org,
	linux-arm-kernel@lists•infradead.org, linux-i2c@vger•kernel.org,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH 0/8] misc: remove boundary checks from bin attr users
Date: Sat, 08 Aug 2015 15:51:54 +0300	[thread overview]
Message-ID: <55C5FB6A.5010300@mleia.com> (raw)
In-Reply-To: <20150807223456.GA1527@katana>

Hi Wolfram,

On 08.08.2015 01:34, Wolfram Sang wrote:
> 
>> if we're talking about this particular series, you should have them in
>> your mailbox, since you have them applied in wsa/i2c/for-next:
> 
> Those are already in linus tree. I mean all drivers which use struct
> i2c_driver. Or do you prefer they go via Greg? I am fine with both.
> 

I think you may find most of the changes applied by Greg into
misc/char-misc-next branch.

The only change from the series, which is not found in
misc/char-misc-next or i2c/for-next is related to at25 driver (IC is
sitting on SPI):

  https://lkml.org/lkml/2015/7/26/101

Change 8/8 for sunxi is outdated due to accepted NVMEM framework.

With best wishes,
Vladimir

  reply	other threads:[~2015-08-08 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-26 21:18 [PATCH 0/8] misc: remove boundary checks from bin attr users Vladimir Zapolskiy
2015-07-26 21:18 ` [PATCH 1/8] misc: cxl: clean up afu_read_config() Vladimir Zapolskiy
2015-07-26 23:06   ` Daniel Axtens
2015-08-05  7:48   ` Michael Neuling
2015-08-07 16:10 ` [PATCH 0/8] misc: remove boundary checks from bin attr users Wolfram Sang
2015-08-07 16:15   ` Vladimir Zapolskiy
2015-08-07 22:34     ` Wolfram Sang
2015-08-08 12:51       ` Vladimir Zapolskiy [this message]
2015-08-08 16:49         ` Wolfram Sang

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=55C5FB6A.5010300@mleia.com \
    --to=vz@mleia$(echo .)com \
    --cc=arnd@arndb$(echo .)de \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=imunsie@au1$(echo .)ibm.com \
    --cc=jdelvare@suse$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-i2c@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=maxime.ripard@free-electrons$(echo .)com \
    --cc=mikey@neuling$(echo .)org \
    --cc=wsa@the-dreams$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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