From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unable to view patches in https://patchwork.kernel.org/project/LKML/list/
Date: Sun, 22 Jul 2018 11:37:27 +0200 [thread overview]
Message-ID: <20180722093727.GA13612@kroah.com> (raw)
In-Reply-To: <CADMaTkNF7fo_p7DJ1AUKxgP=wzfxfk0zQx9FyMUukD+PAK9-BQ@mail.gmail.com>
On Sun, Jul 22, 2018 at 12:22:30PM +0530, nishad kamdar wrote:
> Hello all,
>
> I created a patch and submitted it to the following e-mail addresses.
>
> Lidza Louina <lidza.louina@gmail.com>,Mark Hounschell <markh@compro.net>,Greg
> Kroah-Hartman <gregkh@linuxfoundation.org>,driverdev-
>
> devel at linuxdriverproject.org,devel at driverdev.osuosl.org,
> linux-kernel at vger.kernel.org.
>
> After submitting, I tried to view the patch on patchwork.kernel.org, but
> the webpage
> does not exist anymore. I could view my patches earlier on this webpage.
patchwork.kernel.org just got upgraded yesterday, perhaps lkml is not
yet finished the transition on that site. Give it a few days.
> Where can I see the patches that I submitted?
Look on the mailing list itself, that's the best place. Note that not
all subsystems/maintainers use patchwork, so even if you did see your
patch there, there's nothing it would show you that a mailing list
archive would not.
hope this helps,
greg k-h
next prev parent reply other threads:[~2018-07-22 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 6:52 Unable to view patches in https://patchwork.kernel.org/project/LKML/list/ nishad kamdar
2018-07-22 9:34 ` Himanshu Jha
2018-07-22 17:23 ` Nishad Kamdar
2018-07-22 9:37 ` Greg KH [this message]
2018-07-22 17:24 ` Nishad Kamdar
2018-07-22 19:45 ` Konstantin Ryabitsev
2018-07-23 15:29 ` Synaptics Driver Problem o at goosey.org
2018-07-23 17:44 ` valdis.kletnieks at vt.edu
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=20180722093727.GA13612@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).