All of lore.kernel.org
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: jasowang@redhat.com, svens@stackframe.org
Cc: pangpei.lq@antfin.com, qemu-devel@nongnu.org, ezrakiez@gmail.com
Subject: Re: [PATCH v3 0/2] net: tulip: add checks to avoid OOB access
Date: Thu, 5 Mar 2020 17:46:33 +0530 (IST)	[thread overview]
Message-ID: <nycvar.YSQ.7.76.2003051742400.5086@xnncv> (raw)
In-Reply-To: <158323285268.8962.6657028418668892869@abdcc9e1aa82>

+-- On Tue, 3 Mar 2020, no-reply@patchew.org wrote --+
| Patchew URL: https://patchew.org/QEMU/20200303104724.233375-1-ppandit@redhat.com/
| fatal: unable to access 'https://github.com/patchew-project/qemu/': Failed connect to github.com:443; No route to host

@Jason, @Sven,
 These errors seem unrelated to the patch series. Please see patch v3 when you 
get time.

Thank you.
--
 - P J P
8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D



  reply	other threads:[~2020-03-05 12:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 10:47 [PATCH v3 0/2] net: tulip: add checks to avoid OOB access P J P
2020-03-03 10:47 ` [PATCH v3 1/2] net: tulip: check frame size and r/w data length P J P
2020-03-03 10:47 ` [PATCH v3 2/2] net: tulip: add .can_recieve routine P J P
2020-03-06 13:08   ` Stefan Hajnoczi
2020-03-16 18:01     ` P J P
2020-03-17  5:50       ` Jason Wang
2020-03-17 10:49         ` P J P
2020-03-18  2:07           ` Jason Wang
2020-03-19  9:58             ` P J P
2020-03-03 10:54 ` [PATCH v3 0/2] net: tulip: add checks to avoid OOB access no-reply
2020-03-05 12:16   ` P J P [this message]
2020-03-03 10:54 ` no-reply
2020-03-03 10:54 ` no-reply
2020-03-03 10:56 ` no-reply

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=nycvar.YSQ.7.76.2003051742400.5086@xnncv \
    --to=ppandit@redhat.com \
    --cc=ezrakiez@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=pangpei.lq@antfin.com \
    --cc=qemu-devel@nongnu.org \
    --cc=svens@stackframe.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.