From: Joel Granados <j.granados@samsung.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Jens Axboe <axboe@kernel.dk>,
Phillip Potter <phil@philpotter.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the sysctl tree
Date: Thu, 12 Oct 2023 12:09:07 +0200 [thread overview]
Message-ID: <20231012100907.52wjhbcputj2dsrf@localhost> (raw)
In-Reply-To: <ZSb0oRABk03KOTKU@bombadil.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Wed, Oct 11, 2023 at 12:16:49PM -0700, Luis Chamberlain wrote:
> On Wed, Oct 11, 2023 at 10:36:12AM +0200, Joel Granados wrote:
> > On Wed, Oct 11, 2023 at 04:20:50PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > The following commit is also in the block tree as a different commit
> > > (but the same patch):
> > >
> > > 80f3c6cfab37 ("cdrom: Remove now superfluous sentinel element from ctl_table array")
> > >
> > > This is commit
> > >
> > > 114b0ff62a65 ("cdrom: Remove now superfluous sentinel element from ctl_table array")
> > >
> > > in the block tree.
> > Is this a warning on the merge? or did it actually error out? if it is a
> > wraning and one of the two was skipped, it can be safely ignored as they
> > are the same. I can also remove that commit from my set and send another
> > version. @luis: How do you want to handle it?
>
> I just removed the cdrom patch from my tree.
perfect thx.
>
> Luis
--
Joel Granados
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-10-12 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231011052057eucas1p2876288636c2eaaf61a36985cffb29f8e@eucas1p2.samsung.com>
2023-10-11 5:20 ` linux-next: duplicate patch in the sysctl tree Stephen Rothwell
2023-10-11 8:36 ` Joel Granados
2023-10-11 19:16 ` Luis Chamberlain
2023-10-12 10:09 ` Joel Granados [this message]
2023-07-14 4:48 Stephen Rothwell
2023-07-14 18:48 ` Luis Chamberlain
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=20231012100907.52wjhbcputj2dsrf@localhost \
--to=j.granados@samsung.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=phil@philpotter.co.uk \
--cc=sfr@canb.auug.org.au \
/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.