From: Richard Weinberger <richard@nod.at>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: Sabyasachi Gupta <sabyasachi.linux@gmail.com>,
yuehaibing@huawei.com, jdike@addtoit.com,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
jrdr.linux@gmail.com, brajeswar.linux@gmail.com
Subject: Re: [PATCH] um: Remove duplicate headers
Date: Fri, 18 Jan 2019 22:54:12 +0100 [thread overview]
Message-ID: <9119450.NpuUixIce5@blindfold> (raw)
In-Reply-To: <d9f525fb-847f-312e-43e7-c80b65936680@cambridgegreys.com>
Am Freitag, 18. Januar 2019, 21:00:22 CET schrieb Anton Ivanov:
> >> Hi Sabyasachi,
> >>
> >> I believe we have an identical patch enqueued already from a couple of
> >> weeks back.
> >
> > Hmm, did I miss that one in patchwork?
> >
> > Thanks,
> > //richard
> >
> >
> >
> > _______________________________________________
> > linux-um mailing list
> > linux-um@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-um
> >
> https://patchwork.ozlabs.org/patch/1020163/
Ahh, I thought I forgot this for the last merge window.
Now things make sense again.
Anton, can you please test/Ack the patch? Then it can go to -next.
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: Sabyasachi Gupta <sabyasachi.linux@gmail.com>,
yuehaibing@huawei.com, jdike@addtoit.com,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
jrdr.linux@gmail.com, brajeswar.linux@gmail.com
Subject: Re: [PATCH] um: Remove duplicate headers
Date: Fri, 18 Jan 2019 22:54:12 +0100 [thread overview]
Message-ID: <9119450.NpuUixIce5@blindfold> (raw)
In-Reply-To: <d9f525fb-847f-312e-43e7-c80b65936680@cambridgegreys.com>
Am Freitag, 18. Januar 2019, 21:00:22 CET schrieb Anton Ivanov:
> >> Hi Sabyasachi,
> >>
> >> I believe we have an identical patch enqueued already from a couple of
> >> weeks back.
> >
> > Hmm, did I miss that one in patchwork?
> >
> > Thanks,
> > //richard
> >
> >
> >
> > _______________________________________________
> > linux-um mailing list
> > linux-um@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-um
> >
> https://patchwork.ozlabs.org/patch/1020163/
Ahh, I thought I forgot this for the last merge window.
Now things make sense again.
Anton, can you please test/Ack the patch? Then it can go to -next.
Thanks,
//richard
next prev parent reply other threads:[~2019-01-18 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 14:58 [PATCH] um: Remove duplicate headers Sabyasachi Gupta
2019-01-18 14:58 ` Sabyasachi Gupta
2019-01-18 19:23 ` Anton Ivanov
2019-01-18 19:42 ` Richard Weinberger
2019-01-18 20:00 ` Anton Ivanov
2019-01-18 20:00 ` Anton Ivanov
2019-01-18 21:54 ` Richard Weinberger [this message]
2019-01-18 21:54 ` Richard Weinberger
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=9119450.NpuUixIce5@blindfold \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=brajeswar.linux@gmail.com \
--cc=jdike@addtoit.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=sabyasachi.linux@gmail.com \
--cc=yuehaibing@huawei.com \
/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.