From: nishadkamdar@gmail.com (Nishad Kamdar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unable to view patches in https://patchwork.kernel.org/project/LKML/list/
Date: Sun, 22 Jul 2018 22:53:01 +0530 [thread overview]
Message-ID: <20180722172259.GB20134@nishad> (raw)
In-Reply-To: <20180722093430.GA9468@himanshu-Vostro-3559>
On Sun, Jul 22, 2018 at 03:04:31PM +0530, Himanshu Jha wrote:
> Hi Nishad,
>
> 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.
> >
> > Where can I see the patches that I submitted?
>
> https://lkml.org/lkml/2018/7/22/8
> https://marc.info/?l=linux-kernel&w=2&r=1&s=nishad+kamdar&q=b
>
> There are more archives, but marc.info is better than lkml.org.
> lkml.org is sometimes down.
>
> --
> Himanshu Jha
> Undergraduate Student
> Department of Electronics & Communication
> Guru Tegh Bahadur Institute of Technology
Ok, Thanks for the reply.
regards,
nishad kamdar
next prev parent reply other threads:[~2018-07-22 17:23 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 [this message]
2018-07-22 9:37 ` Greg KH
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=20180722172259.GB20134@nishad \
--to=nishadkamdar@gmail.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 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.