All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Flavio Suligoi <f.suligoi@asem.it>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>, Helge Deller <deller@gmx.de>
Subject: Re: [PATCH v2 0/3] backlight: mp3309c: Allow to use on non-OF platforms
Date: Thu, 8 Feb 2024 17:39:46 +0000	[thread overview]
Message-ID: <20240208173946.GX689448@google.com> (raw)
In-Reply-To: <ZcUMMyV_vBTNw8Rz@smile.fi.intel.com>

On Thu, 08 Feb 2024, Andy Shevchenko wrote:

> On Thu, Feb 08, 2024 at 11:34:25AM +0000, Lee Jones wrote:
> > On Thu, 01 Feb 2024, Andy Shevchenko wrote:
> 
> ...
> 
> > >   backlight: mp3309c: Utilise temporary variable for struct device
> 
> (1)
> 
> > Set no longer applies.  Please rebase, thanks.
> 
> I got a contradictory messages:
> 1) email that says that all had been applied;
> 2) this email (that tells the complete opposite);
> 3) the repository where the first two were applied.
> 
> While you can amend your scripts, I think I need to rebase only the last patch

This is what I assume happened:

1. Attempted to apply the set (as a set)
2. 2 commits applied cleanly
3. The final commit conflicted
4. I sent you a message to say that the set failed to apply
5. *** I forgot to remove the 2 successful patches ***
6. I applied another patch
7. b4 noticed the 2 patches that were applied and thanked you for them
8. *** I didn't notice that those tys were sent ***

No need to update the scripts. :)

> (1) that may not be found in your tree currently.

I'm going to remove the other ones now.  Please submit the set.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2024-02-08 17:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 15:14 [PATCH v2 0/3] backlight: mp3309c: Allow to use on non-OF platforms Andy Shevchenko
2024-02-01 15:14 ` [PATCH v2 1/3] backlight: mp3309c: Make use of device properties Andy Shevchenko
2024-02-02 10:28   ` Daniel Thompson
2024-02-01 15:14 ` [PATCH v2 2/3] backlight: mp3309c: use dev_err_probe() instead of dev_err() Andy Shevchenko
2024-02-02 10:28   ` Daniel Thompson
2024-02-02 10:48   ` Flavio Suligoi
2024-02-01 15:14 ` [PATCH v2 3/3] backlight: mp3309c: Utilise temporary variable for struct device Andy Shevchenko
2024-02-02 10:52 ` [PATCH v2 0/3] backlight: mp3309c: Allow to use on non-OF platforms Flavio Suligoi
2024-02-02 14:18   ` Andy Shevchenko
2024-02-08 11:34 ` Lee Jones
2024-02-08 17:15   ` Andy Shevchenko
2024-02-08 17:39     ` Lee Jones [this message]
2024-02-08 18:07       ` Andy Shevchenko
2024-02-08 18:14         ` Lee Jones
2024-02-08 18:24           ` Andy Shevchenko
2024-02-09  7:50             ` Lee Jones
2024-02-09 14:51               ` Andy Shevchenko
2024-02-08 14:30 ` Lee Jones
2024-02-23 13:51 ` Lee Jones

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=20240208173946.GX689448@google.com \
    --to=lee@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=daniel.thompson@linaro.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=f.suligoi@asem.it \
    --cc=jingoohan1@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.