mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, Ken Lin <ken.lin@advantech.com>,
	linux-iio@vger.kernel.org
Subject: Re: [PULL] IIO fixes for 4.10 set 3 - a couple of regression fixes.
Date: Sat, 11 Feb 2017 09:16:36 +0000	[thread overview]
Message-ID: <1e730cd9-8cb9-3752-cea0-58d4cd67695f@kernel.org> (raw)
In-Reply-To: <20170211071753.GB1345@kroah.com>

On 11/02/17 07:17, Greg Kroah-Hartman wrote:
> On Fri, Feb 10, 2017 at 11:35:35PM +0100, Peter Rosin wrote:
>>> On Sun, Feb 05, 2017 at 10:35:02AM +0000, Jonathan Cameron wrote:
>>>> The following changes since commit 5c113b5e0082e90d2e1c7b12e96a7b8cf0623e27:
>>>>
>>>>   iio: dht11: Use usleep_range instead of msleep for start signal (2017-01-22 13:35:40 +0000)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.10c
>>>
>>> It's a bit late for 4.10 for me, can I just pull this into my -next
>>> branch and will they get to 4.10.1 properly?  Meaning, do that have cc:
>>> stable markings on them?  Or do you want to fix that up and resend this
>>> request?
>>
>> Hi Greg,
>>
>> You should ask Ken Lin who has the HW and who is apparently affected.
>> I think it's bad that you are willing to have a known regression hit
>> v4.10 when all was fine in v4.9. Or perhaps you didn't realize that
>> the regression was from this cycle?
>>
>> The fixes are obvious. I don't understand your hesitation.
> 
> My "hesitation" is that I'm about to get on a plane for a day or so and
> don't have the time to get this to Linus before 4.10-final is out this
> Sunday.  Getting it in a week later should be ok, we all make mistakes,
> as long as we fix them it's all good, and for 4.10.1 should be ok.
Who knows, maybe Linus will delay another week anyway ;)  Wasn't looking
that clear when I sent these out.

>From my point of view, sure 4.10.1 should be fine. I'll put stable CCs
on them. Will send the pull out shortly so I don't forget about them.

Pull request clearly now becomes first set of fixes for 4.11.

Jonathan
> 
> thanks,
> 
> greg k-h
> --
> 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
> 

  reply	other threads:[~2017-02-11  9:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:40 [PATCH v2 0/2] iio: pressure: do not rely on structure field ordering Peter Rosin
2017-02-01 20:40 ` [PATCH v2 1/2] iio: pressure: mpl3115: " Peter Rosin
2017-02-05  9:37   ` Jonathan Cameron
2017-02-10 22:35     ` [PULL] IIO fixes for 4.10 set 3 - a couple of regression fixes Peter Rosin
2017-02-11  7:17       ` Greg Kroah-Hartman
2017-02-11  9:16         ` Jonathan Cameron [this message]
2017-02-14 14:29           ` Peter Rosin
2017-02-01 20:40 ` [PATCH v2 2/2] iio: pressure: mpl115: do not rely on structure field ordering Peter Rosin
2017-02-05  9:38   ` Jonathan Cameron

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=1e730cd9-8cb9-3752-cea0-58d4cd67695f@kernel.org \
    --to=jic23@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ken.lin@advantech.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /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

Powered by JetHome