linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	sfr@canb.auug.org.au, lkp@intel.com,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 1/3] i2c: Revert incorrect conversion to use generic helper
Date: Thu, 1 Aug 2019 15:54:51 +0200	[thread overview]
Message-ID: <20190801135451.GA26585@kroah.com> (raw)
In-Reply-To: <20190801102026.27312-1-suzuki.poulose@arm.com>

On Thu, Aug 01, 2019 at 11:20:24AM +0100, Suzuki K Poulose wrote:
> The patch "drivers: Introduce device lookup variants by ACPI_COMPANION device"
> converted an incorrect instance in i2c driver to a new helper. Revert this
> change.
> 
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Fixes: 00500147cbd3 ("drivers: Introduce device lookup variants by ACPI_COMPANION device")

I'll go add this...

  parent reply	other threads:[~2019-08-01 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01  5:05 linux-next: build warning after merge of the driver-core tree Stephen Rothwell
2019-08-01  6:10 ` Greg KH
2019-08-01 10:20   ` [PATCH 1/3] i2c: Revert incorrect conversion to use generic helper Suzuki K Poulose
2019-08-01 10:20     ` [PATCH 2/3] drivers: Fix typo in parameter description for driver_find_device_by_acpi_dev Suzuki K Poulose
2019-08-01 10:20     ` [PATCH 3/3] drivers: Fix htmldocs warnings with bus_find_next_device() Suzuki K Poulose
2019-08-01 13:54     ` Greg KH [this message]
2019-08-01 14:03       ` [PATCH 1/3] i2c: Revert incorrect conversion to use generic helper Suzuki K Poulose
2019-08-01 14:05         ` Greg KH

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=20190801135451.GA26585@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=suzuki.poulose@arm.com \
    --cc=wsa@the-dreams.de \
    /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).