From: Daniel Vetter <daniel.vetter@ffwll.ch> To: Sam Ravnborg <sam@ravnborg.org> Cc: "DRI Development" <dri-devel@lists.freedesktop.org>, "Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>, "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>, LKML <linux-kernel@vger.kernel.org>, "Michał Mirosław" <mirq-linux@rere.qmqm.pl>, "Yisheng Xie" <ysxie@foxmail.com>, "Hans de Goede" <hdegoede@redhat.com>, "Mikulas Patocka" <mpatocka@redhat.com>, "Daniel Vetter" <daniel.vetter@intel.com>, "Peter Rosin" <peda@axentia.se> Subject: Re: [PATCH 27/33] fbdev: remove FBINFO_MISC_USEREVENT around fb_blank Date: Mon, 20 May 2019 19:29:52 +0200 [thread overview] Message-ID: <CAKMK7uEfyaex+kWyphReA9uaX9p21hDd_WquskocarvWtq1MHA@mail.gmail.com> (raw) In-Reply-To: <20190520172008.GB27230@ravnborg.org> On Mon, May 20, 2019 at 7:20 PM Sam Ravnborg <sam@ravnborg.org> wrote: > > Hi Daniel. > > > With the recursion broken in the previous patch we can drop the > > FBINFO_MISC_USEREVENT flag around calls to fb_blank - recursion > > prevention was it's only job. > > > When grepping for FBINFO_MISC_USEREVENT I get a few hits not addressed > in the patch below: > > drivers/video/fbdev/core/fbcon.c: if (!(info->flags & FBINFO_MISC_USEREVENT)) > drivers/video/fbdev/core/fbmem.c: if (!ret && (flags & FBINFO_MISC_USEREVENT)) { > drivers/video/fbdev/core/fbmem.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/ps3fb.c: info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/ps3fb.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/sh_mobile_lcdcfb.c: * FBINFO_MISC_USEREVENT flag is set. Since we do not want to fake a > include/linux/fb.h:#define FBINFO_MISC_USEREVENT 0x10000 /* event request > > The use in ps3fb looks like a candidate for removal and this file is not > touch in this patch series, so I guess I did not miss it. > > As I did not apply the full series maybe some of the other users was > already taken care of. It's also used to break recursion around fb_set_par and fb_set_pan. Untangling that one would be possible, but also requires untangling some locking, so a lot more work. If you chase all the call paths then you'll noticed that the users still left have no overlap with the ones I'm removing here. -Daniel > > > Sam > > > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> > > Cc: Hans de Goede <hdegoede@redhat.com> > > Cc: Yisheng Xie <ysxie@foxmail.com> > > Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl> > > Cc: Peter Rosin <peda@axentia.se> > > Cc: Mikulas Patocka <mpatocka@redhat.com> > > Cc: Rob Clark <robdclark@gmail.com> > > --- > > drivers/video/fbdev/core/fbcon.c | 5 ++--- > > drivers/video/fbdev/core/fbmem.c | 3 --- > > drivers/video/fbdev/core/fbsysfs.c | 2 -- > > 3 files changed, 2 insertions(+), 8 deletions(-) > > > > diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c > > index f85d794a3bee..c1a7476e980f 100644 > > --- a/drivers/video/fbdev/core/fbcon.c > > +++ b/drivers/video/fbdev/core/fbcon.c > > @@ -2382,9 +2382,8 @@ static int fbcon_blank(struct vc_data *vc, int blank, int mode_switch) > > fbcon_cursor(vc, blank ? CM_ERASE : CM_DRAW); > > ops->cursor_flash = (!blank); > > > > - if (!(info->flags & FBINFO_MISC_USEREVENT)) > > - if (fb_blank(info, blank)) > > - fbcon_generic_blank(vc, info, blank); > > + if (fb_blank(info, blank)) > > + fbcon_generic_blank(vc, info, blank); > > } > > > > if (!blank) > > diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c > > index 7f95c7e80155..65a075ccac4a 100644 > > --- a/drivers/video/fbdev/core/fbmem.c > > +++ b/drivers/video/fbdev/core/fbmem.c > > @@ -1194,10 +1194,7 @@ static long do_fb_ioctl(struct fb_info *info, unsigned int cmd, > > case FBIOBLANK: > > console_lock(); > > lock_fb_info(info); > > - info->flags |= FBINFO_MISC_USEREVENT; > > ret = fb_blank(info, arg); > > - info->flags &= ~FBINFO_MISC_USEREVENT; > > - > > /* might again call into fb_blank */ > > fbcon_fb_blanked(info, arg); > > unlock_fb_info(info); > > diff --git a/drivers/video/fbdev/core/fbsysfs.c b/drivers/video/fbdev/core/fbsysfs.c > > index 252d4f52d2a5..882b471d619e 100644 > > --- a/drivers/video/fbdev/core/fbsysfs.c > > +++ b/drivers/video/fbdev/core/fbsysfs.c > > @@ -310,9 +310,7 @@ static ssize_t store_blank(struct device *device, > > > > arg = simple_strtoul(buf, &last, 0); > > console_lock(); > > - fb_info->flags |= FBINFO_MISC_USEREVENT; > > err = fb_blank(fb_info, arg); > > - fb_info->flags &= ~FBINFO_MISC_USEREVENT; > > /* might again call into fb_blank */ > > fbcon_fb_blanked(fb_info, arg); > > console_unlock(); > > -- > > 2.20.1 > > > > _______________________________________________ > > dri-devel mailing list > > dri-devel@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch> To: Sam Ravnborg <sam@ravnborg.org> Cc: "Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>, "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>, LKML <linux-kernel@vger.kernel.org>, "DRI Development" <dri-devel@lists.freedesktop.org>, "Michał Mirosław" <mirq-linux@rere.qmqm.pl>, "Yisheng Xie" <ysxie@foxmail.com>, "Mikulas Patocka" <mpatocka@redhat.com>, "Daniel Vetter" <daniel.vetter@intel.com>, "Peter Rosin" <peda@axentia.se> Subject: Re: [PATCH 27/33] fbdev: remove FBINFO_MISC_USEREVENT around fb_blank Date: Mon, 20 May 2019 19:29:52 +0200 [thread overview] Message-ID: <CAKMK7uEfyaex+kWyphReA9uaX9p21hDd_WquskocarvWtq1MHA@mail.gmail.com> (raw) In-Reply-To: <20190520172008.GB27230@ravnborg.org> On Mon, May 20, 2019 at 7:20 PM Sam Ravnborg <sam@ravnborg.org> wrote: > > Hi Daniel. > > > With the recursion broken in the previous patch we can drop the > > FBINFO_MISC_USEREVENT flag around calls to fb_blank - recursion > > prevention was it's only job. > > > When grepping for FBINFO_MISC_USEREVENT I get a few hits not addressed > in the patch below: > > drivers/video/fbdev/core/fbcon.c: if (!(info->flags & FBINFO_MISC_USEREVENT)) > drivers/video/fbdev/core/fbmem.c: if (!ret && (flags & FBINFO_MISC_USEREVENT)) { > drivers/video/fbdev/core/fbmem.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbmem.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/core/fbsysfs.c: fb_info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/ps3fb.c: info->flags |= FBINFO_MISC_USEREVENT; > drivers/video/fbdev/ps3fb.c: info->flags &= ~FBINFO_MISC_USEREVENT; > drivers/video/fbdev/sh_mobile_lcdcfb.c: * FBINFO_MISC_USEREVENT flag is set. Since we do not want to fake a > include/linux/fb.h:#define FBINFO_MISC_USEREVENT 0x10000 /* event request > > The use in ps3fb looks like a candidate for removal and this file is not > touch in this patch series, so I guess I did not miss it. > > As I did not apply the full series maybe some of the other users was > already taken care of. It's also used to break recursion around fb_set_par and fb_set_pan. Untangling that one would be possible, but also requires untangling some locking, so a lot more work. If you chase all the call paths then you'll noticed that the users still left have no overlap with the ones I'm removing here. -Daniel > > > Sam > > > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> > > Cc: Hans de Goede <hdegoede@redhat.com> > > Cc: Yisheng Xie <ysxie@foxmail.com> > > Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl> > > Cc: Peter Rosin <peda@axentia.se> > > Cc: Mikulas Patocka <mpatocka@redhat.com> > > Cc: Rob Clark <robdclark@gmail.com> > > --- > > drivers/video/fbdev/core/fbcon.c | 5 ++--- > > drivers/video/fbdev/core/fbmem.c | 3 --- > > drivers/video/fbdev/core/fbsysfs.c | 2 -- > > 3 files changed, 2 insertions(+), 8 deletions(-) > > > > diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c > > index f85d794a3bee..c1a7476e980f 100644 > > --- a/drivers/video/fbdev/core/fbcon.c > > +++ b/drivers/video/fbdev/core/fbcon.c > > @@ -2382,9 +2382,8 @@ static int fbcon_blank(struct vc_data *vc, int blank, int mode_switch) > > fbcon_cursor(vc, blank ? CM_ERASE : CM_DRAW); > > ops->cursor_flash = (!blank); > > > > - if (!(info->flags & FBINFO_MISC_USEREVENT)) > > - if (fb_blank(info, blank)) > > - fbcon_generic_blank(vc, info, blank); > > + if (fb_blank(info, blank)) > > + fbcon_generic_blank(vc, info, blank); > > } > > > > if (!blank) > > diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c > > index 7f95c7e80155..65a075ccac4a 100644 > > --- a/drivers/video/fbdev/core/fbmem.c > > +++ b/drivers/video/fbdev/core/fbmem.c > > @@ -1194,10 +1194,7 @@ static long do_fb_ioctl(struct fb_info *info, unsigned int cmd, > > case FBIOBLANK: > > console_lock(); > > lock_fb_info(info); > > - info->flags |= FBINFO_MISC_USEREVENT; > > ret = fb_blank(info, arg); > > - info->flags &= ~FBINFO_MISC_USEREVENT; > > - > > /* might again call into fb_blank */ > > fbcon_fb_blanked(info, arg); > > unlock_fb_info(info); > > diff --git a/drivers/video/fbdev/core/fbsysfs.c b/drivers/video/fbdev/core/fbsysfs.c > > index 252d4f52d2a5..882b471d619e 100644 > > --- a/drivers/video/fbdev/core/fbsysfs.c > > +++ b/drivers/video/fbdev/core/fbsysfs.c > > @@ -310,9 +310,7 @@ static ssize_t store_blank(struct device *device, > > > > arg = simple_strtoul(buf, &last, 0); > > console_lock(); > > - fb_info->flags |= FBINFO_MISC_USEREVENT; > > err = fb_blank(fb_info, arg); > > - fb_info->flags &= ~FBINFO_MISC_USEREVENT; > > /* might again call into fb_blank */ > > fbcon_fb_blanked(fb_info, arg); > > console_unlock(); > > -- > > 2.20.1 > > > > _______________________________________________ > > dri-devel mailing list > > dri-devel@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-20 17:30 UTC|newest] Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-20 8:21 [PATCH 00/33] fbcon notifier begone! Daniel Vetter 2019-05-20 8:21 ` [PATCH 01/33] dummycon: Sprinkle locking checks Daniel Vetter 2019-05-20 8:21 ` [PATCH 02/33] fbdev: locking check for fb_set_suspend Daniel Vetter 2019-05-20 8:21 ` [PATCH 03/33] vt: might_sleep() annotation for do_blank_screen Daniel Vetter 2019-05-20 8:21 ` [PATCH 04/33] vt: More locking checks Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 05/33] fbdev/sa1100fb: Remove dead code Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 06/33] fbdev/cyber2000: Remove struct display Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 07/33] fbdev/aty128fb: Remove dead code Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 08/33] fbcon: s/struct display/struct fbcon_display/ Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 09/33] fbcon: Remove fbcon_has_exited Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-21 14:23 ` [PATCH] " Daniel Vetter 2019-05-22 10:04 ` Bartlomiej Zolnierkiewicz 2019-05-22 10:04 ` Bartlomiej Zolnierkiewicz 2019-05-22 10:38 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 10/33] fbcon: call fbcon_fb_(un)registered directly Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:33 ` Thomas Zimmermann 2019-05-20 8:33 ` Thomas Zimmermann 2019-05-20 8:37 ` Thomas Zimmermann 2019-05-20 8:37 ` Thomas Zimmermann 2019-05-21 15:09 ` Daniel Vetter 2019-05-21 15:09 ` Daniel Vetter 2019-05-20 17:08 ` Sam Ravnborg 2019-05-20 17:08 ` Sam Ravnborg 2019-05-20 17:08 ` Sam Ravnborg 2019-05-20 17:25 ` Daniel Vetter 2019-05-20 17:25 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 11/33] fbdev/sh_mobile: remove sh_mobile_lcdc_display_notify Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 9:04 ` Geert Uytterhoeven 2019-05-20 8:21 ` [PATCH 12/33] fbdev/omap: sysfs files can't disappear before the device is gone Daniel Vetter 2019-05-20 8:21 ` [PATCH 13/33] fbdev: " Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 14/33] staging/olpc: lock_fb_info can't fail Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 15/33] fbdev/atyfb: " Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:21 ` [PATCH 16/33] fbdev: lock_fb_info cannot fail Daniel Vetter 2019-05-20 8:21 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 17/33] fbcon: call fbcon_fb_bind directly Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 18/33] fbdev: make unregister/unlink functions not fail Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 19:08 ` [Intel-gfx] " kbuild test robot 2019-05-20 19:08 ` kbuild test robot 2019-05-20 19:08 ` kbuild test robot 2019-05-20 19:25 ` kbuild test robot 2019-05-20 19:25 ` kbuild test robot 2019-05-20 19:25 ` [Intel-gfx] " kbuild test robot 2019-05-20 21:45 ` kbuild test robot 2019-05-20 21:45 ` kbuild test robot 2019-05-20 21:45 ` kbuild test robot 2019-05-20 8:22 ` [PATCH 19/33] fbdev: unify unlink_framebufer paths Daniel Vetter 2019-05-21 10:52 ` Maarten Lankhorst 2019-05-20 8:22 ` [PATCH 20/33] fbdev/sh_mob: Remove fb notifier callback Daniel Vetter 2019-05-20 9:05 ` Geert Uytterhoeven 2019-05-20 9:19 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 21/33] fbdev: directly call fbcon_suspended/resumed Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 19:24 ` kbuild test robot 2019-05-20 19:24 ` kbuild test robot 2019-05-20 19:24 ` kbuild test robot 2019-05-20 8:22 ` [PATCH 22/33] fbcon: Call fbcon_mode_deleted/new_modelist directly Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 23/33] fbdev: Call fbcon_get_requirement directly Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 24/33] Revert "backlight/fbcon: Add FB_EVENT_CONBLANK" Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 25/33] fbcon: directly call fbcon_fb_blanked Daniel Vetter 2019-05-20 8:22 ` [PATCH 26/33] fbmem: pull fbcon_fb_blanked out of fb_blank Daniel Vetter 2019-05-20 8:22 ` [PATCH 27/33] fbdev: remove FBINFO_MISC_USEREVENT around fb_blank Daniel Vetter 2019-05-20 17:20 ` Sam Ravnborg 2019-05-20 17:20 ` Sam Ravnborg 2019-05-20 17:29 ` Daniel Vetter [this message] 2019-05-20 17:29 ` Daniel Vetter 2019-05-20 17:53 ` Sam Ravnborg 2019-05-20 8:22 ` [PATCH 28/33] fb: Flatten control flow in fb_set_var Daniel Vetter 2019-05-20 8:22 ` [PATCH 29/33] fbcon: replace FB_EVENT_MODE_CHANGE/_ALL with direct calls Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-21 10:56 ` Maarten Lankhorst 2019-05-21 10:56 ` Maarten Lankhorst 2019-05-21 12:42 ` Daniel Vetter 2019-05-21 12:42 ` Daniel Vetter 2019-05-21 12:42 ` Daniel Vetter 2019-05-20 8:22 ` [PATCH 30/33] vgaswitcheroo: call fbcon_remap_all directly Daniel Vetter 2019-05-20 8:22 ` Daniel Vetter 2019-05-20 8:37 ` Lukas Wunner 2019-05-20 8:37 ` Lukas Wunner 2019-05-20 8:22 ` [PATCH 31/33] fbcon: Call con2fb_map functions directly Daniel Vetter 2019-05-20 19:28 ` [Intel-gfx] " kbuild test robot 2019-05-20 19:28 ` kbuild test robot 2019-05-20 19:34 ` [Intel-gfx] " kbuild test robot 2019-05-20 19:34 ` kbuild test robot 2019-05-20 8:22 ` [PATCH 32/33] fbcon: Document what I learned about fbcon locking Daniel Vetter 2019-05-21 11:13 ` Maarten Lankhorst 2019-05-20 8:22 ` [PATCH 33/33] staging/olpc_dcon: Add drm conversion to TODO Daniel Vetter 2019-05-20 8:30 ` ✗ Fi.CI.CHECKPATCH: warning for fbcon notifier begone! Patchwork 2019-05-20 8:41 ` ✗ Fi.CI.BAT: failure " Patchwork 2019-05-20 8:44 ` ✗ Fi.CI.SPARSE: warning " Patchwork 2019-05-21 17:08 ` ✗ Fi.CI.CHECKPATCH: warning for fbcon notifier begone! (rev2) Patchwork 2019-05-21 17:22 ` ✗ Fi.CI.SPARSE: " Patchwork 2019-05-21 17:29 ` ✗ Fi.CI.BAT: failure " Patchwork 2019-05-22 8:15 ` ✓ Fi.CI.BAT: success " Patchwork 2019-05-22 18:43 ` ✓ Fi.CI.IGT: " Patchwork
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=CAKMK7uEfyaex+kWyphReA9uaX9p21hDd_WquskocarvWtq1MHA@mail.gmail.com \ --to=daniel.vetter@ffwll.ch \ --cc=b.zolnierkie@samsung.com \ --cc=daniel.vetter@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=hdegoede@redhat.com \ --cc=intel-gfx@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mirq-linux@rere.qmqm.pl \ --cc=mpatocka@redhat.com \ --cc=peda@axentia.se \ --cc=sam@ravnborg.org \ --cc=ysxie@foxmail.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: linkBe 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.