All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk>
To: Lukas Prediger <lumip@lumip.de>
Cc: axboe@kernel.dk, hch@infradead.org, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH v3] drivers/cdrom: improved ioctl for media change detection
Date: Mon, 13 Sep 2021 08:50:05 +0100	[thread overview]
Message-ID: <YT8CrdhydoHy373z@equinox> (raw)
In-Reply-To: <20210912191207.74449-1-lumip@lumip.de>

On Sun, Sep 12, 2021 at 10:12:08PM +0300, Lukas Prediger wrote:
> > Dear Lukas,
> > 
> > This v3 patch does not apply to my tree, or the mainline one for that
> > matter. A few problems I've noticed that are the cause of this:
> >
> > [..] 
> >
> > Please advise, many thanks. As mentioned before, v2 applied perfectly
> > fine for me.
> >
> > Regards,
> > Phil
> 
> Hey Phil,
> it seems I had accidentally formated the patch off my v5.4 testing branch.
> Here's the proper version based on current master, that should apply cleanly.
> 
> I've also removed the continuation backslashes that Randy pointed out now.
> 
> Sorry for the troubles,
> Lukas
> 
Dear Lukas,

No apology necessary - I will check this over after work this evening
and then send onto Jens. Many thanks.

Regards,
Phil

  reply	other threads:[~2021-09-13  7:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 21:16 [PATCH v3] drivers/cdrom: improved ioctl for media change detection Lukas Prediger
2021-09-10 21:41 ` Randy Dunlap
2021-09-11 11:00   ` Phillip Potter
2021-09-11 17:48     ` Lukas Prediger
2021-09-12 18:04       ` Phillip Potter
2021-09-12 19:12         ` Lukas Prediger
2021-09-13  7:50           ` Phillip Potter [this message]
2021-10-06 20:52           ` Randy Dunlap
2021-10-07 23:04             ` Phillip Potter
2021-09-13 23:09 Phillip Potter
2021-09-15  2:05 ` Jens Axboe
2021-09-16 23:07   ` Phillip Potter

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=YT8CrdhydoHy373z@equinox \
    --to=phil@philpotter.co.uk \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumip@lumip.de \
    --cc=rdunlap@infradead.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.