Linux-IIO Archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>,
	Martijn Braam <martijn@brixit.nl>
Subject: Re: [PATCH v1 1/1] iio: light: stk3310: Drop most likely fake ACPI ID
Date: Mon, 29 Apr 2024 11:37:01 +0300	[thread overview]
Message-ID: <Zi9cLbf6JdomA8jW@smile.fi.intel.com> (raw)
In-Reply-To: <20240428164333.44a7f8f3@jic23-huawei>

On Sun, Apr 28, 2024 at 04:43:33PM +0100, Jonathan Cameron wrote:
> On Mon, 22 Apr 2024 14:06:16 +0300
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > On Mon, Apr 22, 2024 at 02:04:23PM +0300, Andy Shevchenko wrote:

...

> > P.S>  
> > What I may agree on is to drop Fixes tag.
> > 
> That's a compromise I'm fine with. As long as we've done due diligence on
> whether there are known cases we can take the risk of breaking someone (briefly)
> if these turn out to be in use.

I'll try to remember not putting Fixes in similar patches in the future,
if any.

> Applied,

Thank you!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2024-04-29  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 14:18 [PATCH v1 1/1] iio: light: stk3310: Drop most likely fake ACPI ID Andy Shevchenko
2024-04-20 11:26 ` Jonathan Cameron
2024-04-22 11:04   ` Andy Shevchenko
2024-04-22 11:06     ` Andy Shevchenko
2024-04-28 15:43       ` Jonathan Cameron
2024-04-29  8:37         ` Andy Shevchenko [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=Zi9cLbf6JdomA8jW@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martijn@brixit.nl \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).