Linux LED subsystem development
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>
Subject: Re: [GIT PULL 5.11-rc8] LED fix
Date: Sun, 14 Feb 2021 21:31:38 +0100	[thread overview]
Message-ID: <20210214203138.GA22191@amd> (raw)
In-Reply-To: <CAHk-=wgCp5n3sB_hDmOLSPiJcwJm9RErBHN_6ABhRWyVEkY4Xw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Hi!

> > Unfortunately, for some reason request-pull is not willing to
> > cooperate, so I'm just doing this manually.
> 
> The reason request-pull doesn't cooperate is actually spelled out explicitly:
> 
> > pavel@duo:/data/l/linux-leds$ git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/ 92bf22614b21a2706f4993b278017e437f7785b3 > /tmp/delme for-rc8-5.11
> > warn: No match for commit 92bf22614b21a2706f4993b278017e437f7785b3 found at git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/
> > warn: Are you sure you pushed '92bf22614b21a2706f4993b278017e437f7785b3' there?
> 
> Commit 92bf22614b21 is my rc7 commit. And it's not in your tree (which
> is based on rc1).
> 
> Why are you giving raw commit ID's to git request-pull? Particularly
> ones that aren't even in your upstream tree? Git figures things out on
> its own, why do you point to the rc7 commit that has nothing to do
> with what you're pushing?

I find raw commit IDs easier to work with than the tags.

> And yes, that commit exists on kernel.org through my tree, but it's
> not reachable from any tips in yours (because your work was based on
> earlier state - which is as it should be).

I don't understand.

I want you to apply dbeb02a0bc41b9e9b9c05e460890351efecf1352 .

92bf22614b21 is my rc7, and it is parent of the commit I want you to
apply. It is listed as so on
https://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/commit/?h=for-rc8-5.11 . I would call that "reachable"...?

So I guess I could update master to rc7 to get rid of this error and
retry request-pull?

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2021-02-14 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 17:13 [GIT PULL 5.11-rc8] LED fix Pavel Machek
2021-02-14 19:57 ` Linus Torvalds
2021-02-14 20:31   ` Pavel Machek [this message]
2021-02-14 20:55     ` Linus Torvalds
2021-02-19 11:20       ` Pavel Machek
2021-02-14 20:58 ` pr-tracker-bot

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=20210214203138.GA22191@amd \
    --to=pavel@ucw.cz \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox