aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatthieu Baerts (NGI0) <matttbe@kernel.org>2024-04-29 18:13:36 +0200
committerMatthieu Baerts (NGI0) <matttbe@kernel.org>2024-04-29 18:13:36 +0200
commit2348e8c10c882a4e969d81bb810470e3c86e8dd7 (patch)
treee194c5a8ebd3d4da6a181e397a062626e9627a5d
parentba1cb99b559e3b12db8b65ca9ff03358ea318064 (diff)
downloadnet-next-2348e8c10c882a4e969d81bb810470e3c86e8dd7.tar.gz
EDITME: cover title for upstream-net-20240429-mptcp-snd_nxt-init-connect
# Describe the purpose of this series. The information you put here # will be used by the project maintainer to make a decision whether # your patches should be reviewed, and in what priority order. Please be # very detailed and link to any relevant discussions or sites that the # maintainer can review to better understand your proposed changes. If you # only have a single patch in your series, the contents of the cover # letter will be appended to the "under-the-cut" portion of the patch. # Lines starting with # will be removed from the cover letter. You can # use them to add notes or reminders to yourself. If you want to use # markdown headers in your cover letter, start the line with ">#". # You can add trailers to the cover letter. Any email addresses found in # these trailers will be added to the addresses specified/generated # during the b4 send stage. You can also run "b4 prep --auto-to-cc" to # auto-populate the To: and Cc: trailers based on the code being # modified. Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> --- b4-submit-tracking --- # This section is used internally by b4 prep for tracking purposes. { "series": { "revision": 1, "change-id": "20240429-upstream-net-20240429-mptcp-snd_nxt-init-connect-d9844d880f48", "prefixes": [ "net" ] } }
0 files changed, 0 insertions, 0 deletions